-
Notifications
You must be signed in to change notification settings - Fork 483
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
Add ERC: Store, Table-Based Introspectable Storage #711
base: master
Are you sure you want to change the base?
Conversation
ERCS/erc-xxxx.md
Outdated
@@ -0,0 +1,499 @@ | |||
--- | |||
eip: <to be assigned> | |||
title: Store, Table-Based Introspectable Storage |
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.
title: Store, Table-Based Introspectable Storage | |
title: Table-Based Introspectable Storage |
Maybe simplify the title
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.
We would like to keep the name for now. Thanks for the feedback!
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.
For context - we feel it's important to keep the term "Store" in the title since it's the name of the pattern, ie all events are prefixed with Store
The commit d60529d (as a parent of 571b06e) contains errors. |
Co-authored-by: Andrew B Coathup <[email protected]>
Co-authored-by: Andrew B Coathup <[email protected]>
Co-authored-by: Andrew B Coathup <[email protected]>
@abcoathup please let us know if there are any other requested changes before we can get this merged as draft! |
This standard introduces a flexible on-chain storage pattern that organizes data into structured tables with schemas, similar to a traditional database. This approach allows new tables to be added at runtime without impacting existing contracts, thereby simplifying upgrades and extensions. By providing a unified interface for data access, the standard enables any contract or off-chain service to read stored data without the need for custom getter functions. Additionally, by standardizing event emissions for state changes it enables automatic, schema-aware indexing.