-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arbitrum Foundation Grant #184
Comments
DAOs on Arbitrum (Sourced from https://portal.arbitrum.io/projects/defi?chains=arbitrum-one_arbitrum-nova):
|
How do we vastly accelerate / scale up our ability to onboard new DAOs?
|
We have the proposal live at Lodestar, soon at 1inch and hopefully Balancer, Gitcoin and Treasure. |
Note from discussion today: planning on a Snapshot partnership for the Snapshot X launch, but we need to ask for an extension from Arbitrum for this. |
Plan for milestone 2: we have a working prototype but still need to improve it, I'd suggest going with new minimal MVP that reflects the new standard that DOES NOT require additional technical resources, and then once we have a good MVP we can tap mendes or rashmi or others to implement. |
In discussion with Joni and @amanwithwings , we discussed the best way of resolving Milestone 2, "Development and deployment of the Regulatory Interface". If this is fully specified, it should only take Rashmi a week to implement.
For milestone 3, the initial version of the tax standard has already been largely written as part of the DAOstar Policy Trilemma report. |
Josh <> Joni <> Aman (12.06.2024)
|
Commencement date: December 5
Milestone #1: [due March 5, '24] A minimum of 3 DAOs on Arbitrum achieve EIP-4824 compliance by publishing a daoURI.
Milestone #2: [due June 5, '24] Development and deployment of the Regulatory Interface.
Milestone #3: [due September 5, '24] Release of the tax standard V1.0.
_"Milestone #1: First round of EIP-4824 adoption drive through Arbitrum
The milestone involves driving the adoption of EIP-4824 among DAOs in the
Arbitrum ecosystem. DAOstar is currently in the initial stages of this drive,
reaching out to DAOs and providing them with the necessary resources and
support to adopt EIP-4824.
KPIs: a minimum of 3 DAOs on Arbitrum achieve EIP-4824 compliance by
publishing a daoURI.
How to track KPIs: The Foundation will measure progress by tracking the
number of DAOs that have successfully adopted EIP-4824 and published a
daoURI. This information will be picked up by a subgraph that listens to
events from a RegistrationFactory contract that the Grant Recipient will
deploy on Arbitrum.
Milestone #2: Implementation of the Regulatory Interface
This milestone involves the development and deployment of the Regulatory
Interface. The Grant Recipient has already developed a prototype of the
interface, which can be viewed here:
https://develop.d61skfzwobmxx.amplifyapp.com/ (Lab tab here)
KPIs: successful deployment of the interface, the number of DAOs writing
information to it, and the number of regulators, policymakers, and legal teams
leveraging it.
How to track KPIs: The Grant Recipient should provide the Foundation with
the feedback gathered from users to ensure the interface is meeting its
intended purpose and is user-friendly.
Milestone #3: Authoring of the DAO tax standard
This milestone involves the creation of a comprehensive tax standard for
DAOs. The Grant Recipient is in the early stages of this task, conducting
research and gathering input from various stakeholders.
KPIs: the successful release of the tax standard V1.0.
How to track KPIs: The Grant Recipient should provide the Foundation with
the feedback gathered from stakeholders to ensure it meets the needs of DAOs
and complies with existing tax regulations. The Foundation will also measure
the number of DAOs that adopt the framework."_
_"Milestone #1 - within three (3) months from the Effective Date of the
Agreement;
Milestone #2 - within six (6) months from the Effective Date of the
Agreement;
Milestone #3 - within nine (9) months from the Effective Date of the
Agreement."_
The text was updated successfully, but these errors were encountered: