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
Currently EDS works great for factory-like apps however there is a use case to improve also apps that act as centralized registries.
Example of such is any application today that implements a digital asset, such as ERC20 token.
The core concept is that standard definitions, like ERC-20 standard, define only the interface, not the ways how to store the records.
Currently, most (if not all) projects store such data in centralized contract that also is interface implementer.
With this, developers face a choice of either making their asset contracts upgradable (and hence custodian centralized), or they risk to become outdated as industry develops new standards since their contracts cannot be upgraded.
In any case, this creates a problem for end user as they are not able to have full custody over their asset together with the ability to stay up to date with industry development.
EDS could help projects in that regard by defining a standardized and secure way of deterministically generating app-specific storages that
Are derived from a versioned repository hosting application logic
Require user permit in order to switch interface logic that drives them
Can be mutated only by the applications derived from the app repository
This would allow different users to use different contract versions to control same asset. Developers an create new interfaces and new functionality, keeping their asset up to date with newest trends, yet it's users decision to opt in using newest interfaces or not.
Things to discuss:
Overall technical spec of the solution
How third parties can enforce user storage using specific app versions
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently EDS works great for factory-like apps however there is a use case to improve also apps that act as centralized registries.
Example of such is any application today that implements a digital asset, such as ERC20 token.
The core concept is that standard definitions, like ERC-20 standard, define only the interface, not the ways how to store the records.
Currently, most (if not all) projects store such data in centralized contract that also is interface implementer.
With this, developers face a choice of either making their asset contracts upgradable (and hence custodian centralized), or they risk to become outdated as industry develops new standards since their contracts cannot be upgraded.
In any case, this creates a problem for end user as they are not able to have full custody over their asset together with the ability to stay up to date with industry development.
EDS could help projects in that regard by defining a standardized and secure way of deterministically generating app-specific storages that
This would allow different users to use different contract versions to control same asset. Developers an create new interfaces and new functionality, keeping their asset up to date with newest trends, yet it's users decision to opt in using newest interfaces or not.
Things to discuss:
Beta Was this translation helpful? Give feedback.
All reactions