This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
Add design for structured accounts as an alternative to Generalized Ownership #4452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Current implementations of ownership rely on account pubkeys, which cannot be composed across programs.
How these problems manifest in Ethereum. https://medium.com/@kelvinfichter/looking-at-ownership-in-the-evm-6e6914d341d
This is an alternative to #3216, which defines how programs can interoperate strictly inside the
data
context of the Accounts. The downside of #3216 approach is that performance improvements like Credit-Only accounts are harder to apply.Summary of Changes
Propose a design that defines a specific structure for accounts that is generalized between many programs.
Three kinds of accounts are proposed:
CC #3266 #3216 @garious