Skip to content
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

Genesis/bootstrapped state is currently duplicated across all shards. #1099

Open
stringhandler opened this issue Jul 29, 2024 · 1 comment
Open

Comments

@stringhandler
Copy link
Contributor

For example, the XTR resource exists in the state store of all validators even though only the applicable shard's XTR resource is used as an input. This means that this is probably not really an issue however it does not seem correct that all genesis state exists in all shards. The shard should bootstrap only the applicable state.

@stringhandler
Copy link
Contributor Author

There is also a case to be made for making Resources always duplicated across all shards. Having a Resource in only one shard means that any foreign transaction must always ask for the Resource to be pledged. Maybe there should be a ResourceMaster in one shard and a ResourceClone in all the others. The ResourceClone can be pledged for existence and readonly methods, allowing LocalOnly transactions in the shard, but write updates to the ResourceMaster must force all ResourceClones to be locked for update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant