feat: clone accounts on demand #22
Merged
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.
Summary
On demand cloning of accounts.
Details
When a transaction is sent we extract and validate the accounts we find in it that we either:
Those accounts are then cloned from devnet (hardcoded currently) if they are either readonly or
writable and delegated.
Issues/Todo
Since we don't allow new accounts to be created at this point that makes the validator less
usable locally since we cannot run any transactions that want to use accounts whose keypairs
are derived on the fly, i.e. the worm game doesn't work.
We will add a toml format to allow this behavior to be configured at validator start time and
thus it will be possible to allow new accounts to be created.