Thanks for your reply and it makes sense that required updates are likely limited but committed to be taken care of. Thanks for sharing the repository as well. Just a small suggestion: add README to explain what the software should solve and add links to the non-technical documentations!
2 Likes
Hey all!
After a few conversations with top delegates in the Arbitrum DAO we will rework this proposal a little bit and we will post some updates on it, in the next few weeks. We will also keep working on the designs that we have in mind for this project, so that we can get the larger community and delegates feedback about it.
Because of this, we will not be moving this proposal to a temperature check vote, on Snapshot, as of now.
Thank you!
3 Likes
yes, for sure! we need to tidy up this repo… right now, this repo is mostly me and @andreiv offending each other on commit messages… ahahah =)
if and when this proposal passes and the project kickoff happens we will make sure to have a properly documented github repo. specifically so that anybody else in the world can easily spin up their own instance of proposals.app and the future arbitrum.proposals.app as well.
3 Likes
From the point of view of convenience for me personally - it would be interesting to implement some kind of information window right on the forum.
So that where notifications about messages come, there would be information about how many unread proposals I have and how many are currently in the voting.
4 Likes
this is a very interesting suggestion @cp0x thank you!
we have some experience developing discourse forum integrations for Aave and Uniswap forums in the past, so we might take into account your feedback and propose a discourse customization that would achieve something similar to what you’re suggesting, I think…
thank you again for your feedback!
2 Likes
we just got a Questbook Grant approved to execute on this proposal, with a slightly different scope and timeline, but more importantly to the DAO, for less than half the cost originally proposed ($43k USD instead of the original $93k USD).
We’ve updated the original post in this thread with the changes in the milestones, timelines, and budget breakdown.
Here is the Questbook Grant application that we will be executing on for the next 4 months, starting today.
Going forward, we will be reporting the progress of the project in this thread. Thank you!
4 Likes
Here is our first milestone deliverable for the questbook project that includes:
- back-end discourse indexing system
- mapping backoffice to map discourse data to snapshot and onchain proposals
- setup of self-hosted infrastructure with a real-time status page monitoring which can be seen at status.proposals.app
Watch the video deliverable on Youtube
Thank you! 
7 Likes
Governance Analyst bounty
Context
“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.”
Bounty
| Tenure | part time |
|---|---|
| Start Date | 26/10/2024 - $500 USDC |
| Terms | Half at the beginning, half on delivery |
| Product | Map offchain and onchain proposals in proposals.app backend |
| Date of Completion | Mapping completed (first round) -02/12/2024- $500. Final mapping and forum Report: 16/12/2024 |
Methodology:
Index, read, clean, and categorize every single proposal that was motioned in Arbitrum governance forum from inception till 25/10/2024
Index
I was provided (thankfully so) a database of proposals in raw text format by the proposals team to start the manual mapping.
Buckets
I read, filtered, and categorised the proposals into four buckets
-
Discussions:
Discourse posts/ proposals that motioned the attention of delegates but failed to gain enough consensus for a snapshot instance . -
Debates:
Failed snapshot proposals proposals - debates -
Deliberations:
snapshot proposals that were
- Elections
- Selections & Challenges
- Social Agreements
- Policy Redraft recommendations
- Decisions
Onchain proposals that were discussed, debated, deliberated and tabled for onchain vote
Mapping
All the above proposals were mapped at the proposals.app backend manually . I have attached the mapped index of all proposals (ranked from proposals with the most amount of assets to the least ones).
1 Like
I am ready to vote ..we are ready to push arbitruim forward
1 Like
Here is our second milestone deliverable for our questbook grant, submitted on January 1st, 2025.
Watch the video deliverable on Youtube
Here is our third milestone deliverable for our questbook grant, submitted on January 27th, 2025.
Watch the video deliverable on Youtube
1 Like
Here is our forth and final milestone deliverable for our questbook grant, submitted on April 3rd, 2025.
Watch the video deliverable on Youtube
2 Likes
We launched the app during ETH Bucharest 2025, on April 4th, and you can just try it out at arbitrum.proposals.app and tell us what you think about it.
2 Likes
Thanks for the app
Of the obvious pros:
- you can immediately see who submitted the proposal
- you can see how much longer the voting will last
- you can see the quorum
Of the cons:
- you can add % of votes (at least this information is important to me, I understand how supported this proposal is)
- it would be good to leave all the same information for those votes that have already taken place, otherwise you have to open them one by one to understand - accepted or not, whether there was a quorum or not
- it is not obvious that the list contains not only votes, but also discussions of future votes, perhaps they should be highlighted somehow
2 Likes
Is there plans to include allowing people to vote for a given proposal directly through this app? My thought process is since people are there already it could be helpful to allow them to make/edit their votes after going through the consolidated information.
2 Likes
I second this it would as help against having a single point of failure
2 Likes