Non-Constitutional: Arbitrum Proposals App (GovHack Brussels Winner)

We are aiming at moving this proposal to a temperature check vote, on Snapshot, on Tuesday 23rd of July. Please provide feedback until then. Thank you! :pray:

Arbitrum Proposals App

Non-Constitutional

Challenge Statement:
Right now, DAO delegates want to understand proposals efficiently and accurately, but proposal information is scattered all over the place (tweets, Discord servers, Telegram chats, discourse posts, offchain proposals [on snapshot], onchain proposals [on tally], etc.). This is a serious issue because it leads to unnecessary friction and inaccessibility in governance participation and, ultimately, poor decision-making for the Arbitrum DAO.

Track Name at GovHack Brussels: GovTech
Team Number at GovHack Brussels: 16

Members: andreiv.eth + paulofonseca.eth

Team Lead: Paulo Fonseca – @paulofonseca1987 on Telegram or @paulofonseca__ on Twitter

2 minute Pitch: Posted on Youtube
Low Fidelity Design Prototype: (this is unfinished and in-progress work, since it was started during the GovHack itself) arbitrum.proposals.app

Abstract

To fund the design and development of an Arbitrum-focused responsive web app that shows all Arbitrum proposals across different stages in their lifecycle and aggregates information from Discourse, Snapshot, and the Arbitrum Onchain Governor contracts so that voters and delegates can more efficiently and accurately understand the context and the whole lifecycle of each proposal they should be voting on.

Motivation

The current governance state-of-the-art is quite messy. This is not just an Arbitrum DAO problem but it affects Arbitrum DAO governance quite a lot. Still to this day, most governance processes in most big DAOs are spread across multiple platforms and systems, from messaging apps like Discord, Telegram and Twitter, to Discourse forums, to offchain voting platforms like Snapshot and then to onchain voting front-ends like Tally.

In each of these platforms, delegates need to keep themselves up to date, review information about proposals coming to vote in the DAO and form their opinions about whether they should support a particular proposal. Delegates are also expected to actively share their concerns and provide feedback on proposals throughout the lifecycle of a proposal so that the proposal can advance through the several stages of the governance process successfully.

For a delegate, even to the most competent ones, to keep up with all of this information scattered around different sources is… overwhelming, to say the least. :melting_face:

As an example, this is roughly what happens when a delegate (or anybody else for that matter) tries to understand the context and form an opinion about an important Arbitrum proposal like the Gaming Catalyst Program that just recently passed.

How are we even governing ourselves like this?
Full video can be seen here.

If we expect more and better delegates to keep up with governance proposals adequately, we should invest in appropriate tooling to make their jobs much easier than they currently are.

Rationale

This proposal aligns with Arbitrum’s mission and community values by making the Arbitrum DAO more innovative, open, accessible, and inclusive to delegates and voters by allowing them another choice as users of Arbitrum’s DAO governance.
More specifically, the last community value in The Amended Constitution of the Arbitrum DAO, but to us, one of the most important community values, the one of attempting to be:

Neutral and open: Arbitrum governance should not pick winners and losers, but should foster open innovation, interoperation, user choice, and healthy competition on Arbitrum chains.

We know Tally has a great partnership with the Arbitrum DAO, and we are grateful for all the work the Tally team has done over more than a year to support the governance of Arbitrum DAO. We support their developments and future roadmap and are open to collaborating in any way to improve the user experience of delegates and voters in their day-to-day.

We also believe it is important for the Arbitrum DAO not to be vendor-locked in. More specifically, on the front end it offers its delegates and voters that allows them to participate in Arbitrum DAO’s onchain governance.

We believe there should be multiple front-ends to Arbitrum DAO’s onchain governance, so that we can attract more and better delegates and voters by providing them tools that suit their particular needs.

We also strongly believe that at least one of those front-ends should be fully open-source. For the obvious matters of the resilience of Arbitrum’s DAO governance, we believe there should be a fully open-source front-end for Arbitrum’s DAO on-chain governance that would allow delegates and voters to continue to participate in governance permissionlessly. proposals.app is fully open source and will continue to be. proposals.app and its future developments can also be self-hosted by anyone (like we’re doing now) under a new domain name, at any time.

Specifications

How might we enable DAO delegates, to get a more complete picture of how a proposal has evolved and what other people think about it, so that they can make a more informed voting decision, resulting in higher quality governance outcomes for the DAO?

This guiding question and a bunch of conversations and user research with DAO Delegates both in GovHack and previously when we were building Senate, has led us to believe that there is a need for a unified view of a canonical DAO proposal page that covers the whole proposal lifecycle, or at the very least, from the “initial Discourse forum post” stage to the “onchain execution” stage, obviously including temperature check poll on Snapshot, and onchain voting.

At proposals.app we already fetch Arbitrum’s DAO offchain and onchain proposals, and we also offer free email notifications to anybody that subscribes on the site. Everytime there is a new Arbitrum DAO proposal available, delegates and voters that have subscribed to proposals.app notifications, will get a fresh email in their inbox that looks like this.
proposals.app daily bulletin email notification

Currently, we are linking each offchain or onchain proposal to their respective Snapshot.org or Tally.xyz links so delegates and voters can easily exercise their governance rights.

With this project we will build a Unified Proposal Lifecycle page, that merges the information of offchain and onchain votes for the same proposal, so that delegates and voters can have easier access to all of the information of a proposal in a single place.

This Unified Proposal Lifecycle page will show information from the proposal’s Discourse post, from the Snapshot temperature check poll, and from the onchain vote.

The challenge to be able to achieve this is to include all relevant information in the right way, at the right time, so delegates and voters don’t feel overwhelmed by it.

We’ve been mapping the proposal elements across several platforms and feel confident we have a model that captures a proposal standard that is able to show the proposal lifecycle and how the proposal has evolved, and that will help delegates and voters get more transparency into the journey of a proposal and the context it’s current or final state.

mindmap

We will need to also manually map the discourse posts to the Snapshot polls and then to the onchain votes. Which is something that is not trivial to do for all past Arbitrum DAO’s proposals, but we will create a backoffice where a governance analyst can links all data sources of a proposal, to be shown in the Unified Proposal Lifecycle page.

Steps to Implement

We have a 2 part plan for this project:

  1. Design and Develop V1 of the Unified Proposal Lifecycle Page, which will include data and the mapping between Snapshot proposal data and Onchain proposal data.
  2. Design and Develop the V2 of the Unified Proposal Lifecycle Page that would add Discourse Post data.

Alongside this main plan, we need to create a mechanism to map discourse posts to Snapshot polls and then to onchain votes, so that eventually that mapping doesn’t need to be done manually for every proposal.

We are talking to @amanwithwings to move forward a daoURI standard in the Arbitrum DAO that could be extended so that Arbitrum DAO onchain proposals would include the link to their Discourse post in the onchain proposal metadata.
Once that standard would be adopted by the Arbitrum DAO, we would be able to automate the mapping of data for a single proposal. Until then, we will do it manually and very deliberately. :nerd_face:

Timeline

We will deliver the complete solution described above within a maximum of three months of the project’s kick-off.

Assuming the project kick-off is on August 1st, 2024, we commit to deliver the completed project with all it’s Milestones and deliverables by November 1st, 2024.

Milestone #1

Deadline: 30 days after project kick-off
Deliverables: an Arbitrum branded responsive web app, available at arbitrum.proposals.app where users can browse all Arbitrum DAO proposals since AIP-1. For each proposal, a detail page would show a unified view of the proposal data including data from offchain votes and onchain votes, in a single and unified view.

Milestone #2

Deadline: 90 days after project kick-off, 60 days after Milestone #1
Deliverables: an upgrade of the previous proposal details page on arbitrum.proposals.app where users will be able to see discourse forum data for each proposal, with a feed of the delegate and voter activity for each proposal that shows discourse comments, snapshot vote reasons and onchain vote comments, in a single and unified view.

After completing the project, we commit to maintaining and ensuring the resilient hosting of the web app for at least 36 months from the kick-off date.

Overall Cost

The overall cost for this 3 month long project totals $93,000 USD

Monthly Amount Duration Total Amount
Designer $10,000 USD 3 months $30,000 USD
Developer $10,000 USD 3 months $30,000 USD
Governance Analyst $5,000 USD 3 months $15,000 USD
Servers and Hosting $500 USD 36 months $18,000 USD

During these three months, we will ship two deliverables, the first at Milestone #1 at the 30 day mark, and the second at Milestone #2 at the 90 day mark.

The kick-off stage marks the beginning of the project after a successful onchain vote and completion of all compliance procedures with the Arbitrum Foundation.

We believe in performance-based compensation, so after the initial payment at the project kick-off date, we will only be compensated upon value delivery after successfully delivering each of the Milestones.

Payment schedule

Kick-off Milestone #1 Milestone #2
Deadline Day 1 Day 30 Day 90
Payment $13,000 USD $30,000 USD $50,000 USD

At the time of the onchain proposal, we will denominate this total amount in ARB, with a 20% volatility buffer to compensate for token price fluctuations.
For example, at today’s (July 21st, 2024) ARB price of ~0,78 USD, the $93,000 USD + 20% volatility buffer would be roughly ~143,077 ARB.

Then, after receiving the full amount in the multisig, we would swap the ARB for 93,000 USDC and return the remaining ARB to the Arbitrum DAO.

For the multisig, we would love to use the MSS to handle this payment, assuming it would be ready in time.
If the MSS it’s not ready in time, we will create a 4 out of 5 multisig that will hold these funds for the project’s duration and sign the corresponding transfers at each Milestone delivered. The composition of this multisig will be 2 members from proposals.app, @andreiv and @paulofonseca and then 3 recognized delegates that were kind enough to volunteer their time to be part of this multisig, @DisruptionJoe @hiringdevs.eth and @JoJo. These delegates would serve as reviewers, ensuring we deliver value for Arbitrum DAO and that the project should continue to the next Milestone.
The multisig signers will review our deliverables at each Milestone, and only after a positive review will the associated payment tranche be transferred to our own, proposals.app 2 out of 2 multisig. And from there, all contributors and expenses will be paid at our discretion, but still fully transparently and, of course, onchain. :sunglasses:

:pray:
Thank you for reading this proposal until the end, and please give us your honest and harshest feedback. We know we need it, and we truly welcome it! :innocent:

Also, special thanks to @DisruptionJoe, @hiringdevs.eth, @cliffton.eth, @JoJo and anybody else who provided valuable feedback on this proposal during GovHack Brussels and afterwards!
:raised_hands:

8 Likes

Excited to share our team’s proposal! We believe this initiative will address a significant pain point in DAO governance by consolidating fragmented proposal information into a unified, open source and resilient platform.

Let’s make governance more accessible and effective together!

2 Likes

Figma shows its edited 7 days ago idk if it’s bug or something but are you sure about it was done in govhack?

2 Likes

thank you for the diligence @ismailemin =)

I’m not really sure why the figma prototype embed component says 7 days ago… This file exists for months now… but this part of the file however, with the prototype for the Unified Proposal Lifecycle page proposal, was created last night… actually I was just editing it before I saw your comment.

You can see the whole file here, and you can also comment on it, with your feedback: https://www.figma.com/design/8c9gLo0ICTAhGMatRi3qU4/proposals.app?node-id=67-470&t=JB5d7ngDfckKvfh2-1

And as you can see from the figma file version history, this 2 frames were made from July 6th at 9:13AM (Brussels time I guess?) to today, July 7th, at 1:18PM

figma file version history

Great job folks! Really feel the pain of having to track everything from everywhere.

Vendor lock in is also real and something that bothers me despite being CEO of Tally.xyz. I’d love to see a world where Arbitrum owned it’s instance of Tally so that it wasn’t vendor lock in at all.

In the meantime, I think initiatives like this are super important!

4 Likes

thank you for the public support @dennison :pray:
it means a lot coming from you!

3 Likes

Congrats all, solid progress against real pain-points; hoping to see this come alive soon!

3 Likes

thank you @emjicy =) it will come alive soon!

Just did a livestream figuring out the information architecture for a aggregated proposal lifecycle page, that would show the info of a proposal from the discourse forum, to the snapshot temp check poll, to the onchain vote.

I mapped the pages from Tally, Aragon (old and new), and Snapshot, to have a diversity of inputs in this work so that I can understand what different product have deemed important when presenting the information of a DAO proposal.

You can browse and comment in the FigJam file that I created during this session, and if you have the patience for it, you can also watch the 3 hour long live stream (it was my first ever =).

I’ll do a second session tonight or tomorrow.

2 Likes

Hey Paulo and team,

Just wanted to say awesome job on the Arbitrum Proposals App. The idea of consolidating governance info in a nicely formatted and clean way for delegates to navigate is super important. Also, the plan to map the proposal lifecycle and make everything accessible in one place is spot on.

We’re close to releasing something similar at Open Dollar, apparently great minds think alike! We just teased it on our Twitter: x.com

Looking forward to seeing your project in action. Keep up the great work!

1 Like

@Bau thank you for the support! =) the fork feature you are doing is… chef’s kiss! =)

2 Likes

Hello all!

I just updated this proposal with a few more details.

We want to have this proposal on temperature check on Snapshop next Tuesday July 23rd.

Please provide your feedback soon!

Thank you!
:pray: