-
Notifications
You must be signed in to change notification settings - Fork 403
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This PR adds support for each Caliper client to have its own Ethereum account to be deterministically derived from a seed value using BIP-44 style key derivation. This is only supported for the `fromAddress` value. To use this instead of specifying a `fromAddresss` and optional private key instead a `fromAddressSeed` is specified, which is a 128 bit hex encoded value used as the seed for key derivation. Each client uses its client index as the account field. In the future where multiple accounts are needed per caliper client the address_index field will be incremented or mapped to the account value. The genesis file in the samples and integration tests for besu have had the first 10 keys pre-seeded with test ether. The sample and integration test for besu has also been updated to use a from address seed. Signed-off-by: Danno Ferrin <[email protected]>
- Loading branch information
Showing
6 changed files
with
120 additions
and
12 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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