-
Notifications
You must be signed in to change notification settings - Fork 470
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
Update ERC-4824: Move to Review #330
Conversation
move to Review status
including persons, organizations, foundations, etc.
also changed the ordering of the new added sections, clarified norm for removing fields
…d did format syntax
✅ All reviewers have approved. |
The commit 2103dc7 (as a parent of fb4e937) contains errors. |
EIP bot throwing an error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the "Community Consensus" subsection:
Please write proposals as if they are already final. It doesn't make much sense to say "X will happen in 2022" when the proposal is being read in 2032.
We generally don't do "acknowledgements" in the body of an EIP.
Responded to all review suggestions, moved the smart contract out into assets. Should be ready to move to review! |
Put up a pull request with some minor fixes: thelastjosh#3 |
Editor Suggestions for ERC-4824
Merged! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Reviewers Have Approved; Performing Automatic Merge...
Thank you!! |
I moved the example contract to the assets folder, made various minor clarifications about how daoURI and indexing should work, supplemented the rationale, changed the id format for members to align more closely with CAIP-10 (already used for proposals), and fixed a bunch of typos. All changes are backward compatible.