Despite not following the traditional forum protocol, I think its a great proposal, it costs no money directly, it just requires the foundation to add some data to their ENS handle. The DAOstar/Metagov crew work tirelessly to bring these standards to the DAO space, it is very thankless work. I am a huge fan.
IMO, all of us voting no on this and then forcing them to repost again IMO is a waste of everyone’s time and a bad reason to vote against.
I understand the concern that the usual process may not have been followed, and that such practices shouldn’t become common. However, recognizing that the DAO’s onboarding process and the appropriate paths to follow might not always be clear, I believe the implementation of this proposal is highly useful. The benefit-to-risk ratio doesn’t justify rejecting it.
This proposal serves to both enhance the ecosystem and improve our onboarding process for the development of future proposals.
We voted against this proposal during the temperature check process due to procedural flaws and the lack of a thorough security review. The proposal was not properly categorized in the forums, potentially limiting its visibility and feedback. Additionally, it has not been assessed by an ARDC security provider, which is crucial for its technical implementation.
However, if these issues are addressed, we will support the proposal in future voting stages.
Hey all, thank you for your valuable feedback. We have created a new forum post in the correct category. I’ve also requested a security evaluation from the ARDC. We look forward to reposting the improved proposal to Snapshot after ARDC’s evaluation.
I voted in favor of the proposal because I believe it will help us gather the necessary and reliable data for decision-making in the governance. I would also appreciate it if you could address some of the delegates’ concerns and resubmit the proposal on Snapshot.
A go-to source of truth is a great idea. We are in favor of setting up a platform like this. At Uniswap, we’ve had experience with managing a couple of ENS subdomains under Uniswap.eth. This was initially set in place in order to give additional use grants to certain deployers who would request the DAO for the ability to deploy Uniswap v3 contracts onto a new EVM. This was only required while there was a BSL in place. Since April of last year, we continued similar record management to have a source of truth regarding the “real” Uniswap v3 contracts on each of the 23 chains that we’re deployed on. This has helped from a security and standardization standpoint. Therefore, exploring record management such as this for Arbitrum is beneficial as well.
Unfortunately, due to issues surrounding the procedure, we voted against this proposal. We will vote For a revised proposal though.
This proposal came out of nowhere. The proposal seems reasonable, but would hope to discuss / hear from the proposers live on this before going forward with a more formal vote so that delegates have time to engage and learn.
Just voted in favor of using ENS txt records on Snapshot. EIP-4824 is a solid and useful standard, and it’s great to see it getting implemented on Arbitrum. Having a reliable source for trusted info will definitely help newcomers and anyone diving deeper into Arbitrum. Plus, no additional funding needed for this proposal is a huge bonus.