You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right after deployment, user should have the option to "apply" to join the DAOregistry curated by the Genesis DAO (Mosaic).
Frontend view would simulate whatever the 'New Proposal' pop-up in the DAOregistry queue in Alchemy Earth ends up looking like. User would be asked to fill in fields such as
short description of proposal (why this DAO should be accepted into the registry)
URL to a longer document that justifies the DAO's inclusion in the registry
Backend would generate a proposal to the Genesis DAO's DAOregistry scheme. We would need to make sure that proposals submitted through this view show up properly on Alchemy Earth (including all off-chain info that the user filled in).
The text was updated successfully, but these errors were encountered:
There's a feature that exists in the migration script + params where you can include a custom contract address + ABI to be called after the deployment of the DAO. Registering the DAO in the DAORegistry can happen here.
Right after deployment, user should have the option to "apply" to join the DAOregistry curated by the Genesis DAO (Mosaic).
Frontend view would simulate whatever the 'New Proposal' pop-up in the DAOregistry queue in Alchemy Earth ends up looking like. User would be asked to fill in fields such as
Backend would generate a proposal to the Genesis DAO's DAOregistry scheme. We would need to make sure that proposals submitted through this view show up properly on Alchemy Earth (including all off-chain info that the user filled in).
The text was updated successfully, but these errors were encountered: