feat(examples): option to derive account from an encrypted keystore #186
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
traderben
requested changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds optional ability to derive a
LocalAccountto use within the provided examples from a local encrypted keystore.Currently, the
LocalAccountwithinexample_utils.pyis created off a provided secret key- but I think it's reasonable to assume that some devs will have secret keys within a keystore that they'd like to use instead. For instance, Foundry users might have keys stored within the Foundry default dir of~/.foundry/keystores/<NAME>.These changes provide the ability for devs to specify a path to a keystore in their
config.json. If they do so, theLocalAccountwill be derived from here, rather than the secret key.