Thanks for taking the time to provide your reasoning.
While I understand the case where fragmentation could be a problem. In this scenario. I would posit that it’s actually a positive that we have client diversity.
The bottom line being that the more people we have aware of multisig txns that are in context (in this case DAO proposals) and able to sign.The better it is for the ecosystem as a whole.
The current SAFE mobile app is still the vessel for signing transactions. The main point here is that we can originate/streamline multi-sig transactions for narrow use cases more effectively.
The recent Compound governance attack being a prime example of where inactive participants who were probably busy or not in front of their computer could not react in a timely fashion.
Hi all. We have been itching to share progress on this update and gather feedback before we can start spreading the word about this cool feature. We apologise for not communicating publicly but we have been in touch with the OBRA team staying on top of our reporting requirements.
We have iterated on the designs and experience and believe this is hands down a first when it comes to voting with a Safe on Snapshot proposals.
Given this was an experimental piece of work, we ended up having to cut the Governor support as we simply did not have the bandwidth or budget to deliver to a level we would like to.
That said we used that time to go deep and deliver a really clean voting experience which means the Snapshot <> Safe <> Lighthouse voting experience is top notch.
Given some of you may have not used Lighthouse before, I took the liberty to record some quick snippets of key experiences.
