[SEP 35] [OBRA] Improve voting UI/UX with SAFE on mobile

Please refer to the full proposal text on the SafeDAO forum. Some parts may have been removed to fit within the character limit on Snapshot.

Title:

[SEP 35] [OBRA] Improve voting UI/UX with SAFE on mobile

Authors:

@1a35e1

Created:

2024-07-05

Abstract

2. Abstract: Provide a brief summary of your initiative

In most governance systems, voters elect to place their governance tokens in a SAFE. This is especially true for delegates who sit across multiple governance projects.

Regardless of the underlying governance system (Snapshot, Agora, Tally, OZ Governor) collecting these signatures is a well known time sink and has been further evidenced in our ongoing user research.

3. Aligned strategy: Which pre-approved strategy is this initiative driving forward?

[Strategy 5] Increase governance participation

4. Funding request: What resources are being requested from SafeDAO in USDC?

• ~5-8k design UX sprint (1-2week)
• ~10-15k implementation (4-6 weeks)
• ~5k testing and iteration (1-2 weeks)

Total request (Lower Bound): 20k Total request (Upper Bound): 28k — Ideally

However, any grant amount between these ranges would be sufficient.

5. If applicable, upfront funding: Indicate if upfront funding is needed. Refer to 'Payout’ under Get funding from SafeDAO for lump sum payment options.

N/A

6. Relation to budget: State the requested funding as a percentage of the total initiative budget (e.g. if you ask for 50k for Strategy 1: 25%)

18%

7. Metrics and KPIs: Which metrics and KPIs will the initiative be measured against?

• Lead time from Proposal → Cancellation/Execution

  • Eg. It may take 15 hrs to collect and execute a transaction

  • Our system may reduce that time to 1-2 hrs.

• It would be great to get current stats on this from the SAFE team so we can benchmark impact over time.

8. Initiative description: What is the initiative about?

By making SAFEs easier to use from a native mobile interface. We promote stronger security models. For standard SAFE/s (3/5, 5/7, etc) this dramatically increases the possibility of a signer, being aware they need to act on a transaction.

We propose to leverage the SAFE SDKs to expedite proposing, collecting and executing transactions within the governance domain.

This will be delivered via our flagship product https://lighthouse.cx which is live and available on both (iOS/Android)-

This is also an R&D experiment in designing how to collect signatures on mobile devices.

Example flow:
* A new Proposal is submitted on-chain from Optimism.
* All recipients following Optimism will be notified
* Any voter on the SAFE may propose their choice (eg. 3/5)
* Other 4 signers may choose to sign
* After x mins/hours (configurable) a reminder is sent to sign to non-signers
* Based on thresholds, execute/reject txn can be committed.

Potential tailwinds

This eventually could also extend to treasury execution, we are working with Metagov to explore how we can index treasuries with DAO spaces.

9. Current status: Does the offering (product/service) already exist or is the funding used to create it?

• Our product Lighthouse already exists on both (iOS/Android)

• Many of our users are requesting SAFE support however we do not have the funds currently to build out this initiative.

10. Risks: What risks does the initiative entail?

• Our application relies heavily on wallet connect at the moment (as do most apps)

• We still need to add Ledger support and other wallets.-

  • This is a known unknown and will require iteration.

• This will be a brand new UI/UX experience never done before, so it will require some iteration. However we are confident in delivering an MVP that is usable.

11. Timeline and milestones: Provide a detailed timeline or roadmap, include key milestones

• Design UX sprint (1-2 weeks)

• UX, Messaging and Prototyping

• Implementation (4-6 weeks)

  • Vote using SAFE in app with snapshot based DAOs
  • Vote using SAFE in app with 1-2 Governor based DAOs (eg. Optimism, Nouns)

• Testing and iteration (1-2 weeks)

  • Community feedback and polishing where possible

12. Initiative lead: Who is the accountable initiative lead? (individual or organization)

Arnold Almeida, Founder, CTO - https://lighthouse.cx

13. Team: How many individuals in total will be working on this initiative and what role do they have? Please provide a brief background of the team members, highlighting their relevant experience and expertise

14. Additional support/resources: Are there any resources (non-financial) requested from the Safe Ecosystem Foundation or the core contributors?

• I don’t believe so. We will be for the most part leveraging SAFE SDK’s
• We may request SDK enhancements though our discovery phase.
• We may request validation from the SAFE team to field test our UX
• Explore Indexing options available to us
• Improving SDKs if necessary

15. Implementation dependencies: Does the implementation of this initiative require any prior changes in the current governance processes, e.g., updates to the governance framework, or have any other dependency? If yes, please specify these. Note that the funding of the initiative will be dependent on the approval and (if needed) successful implementation of such necessary governance modifications or any other dependency.

No, This would be a value-added addition to voting systems.

Google Doc here — https://docs.google.com/document/d/1u_q842Vus09VuVgLJDv4CAvLFUxzsOpAeDHlh1yODsU/edit?usp=sharing

EDITS:

1. Clarified grant request calculation to use upper bound of 28k USDC