-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: SpendingKey self derivation, parallel iteration
Primary features: 1. SpendingKey can now derive its own children without any wallet state. This enables RPC clients to derive keys themselves. 2. Derivation iterators. SpendingKeyIter and SpendingKeyParallelIter. The latter leverages rayon to utilize all cpu cores. 3. /known_keys rpc now returns a SpendingKeyRange instead of a list of addresses. This is a big perf win for large wallets. changelog: refactor spending-key types so each key can derive its own children known_keys rpcs now return iterators instead of Vec DerivationIndex: u64 -> u128. fix premine_distribution(). separate test vs non-test. make it aware of current network impl IntoIterator for SpendingKey GenerationReceivingAddress::derive_from_seed() -> from_seed() impl rayon parallel iterators SpendingKeyIter now starts at child 0, instead of parent_key. fix some DoubleEndedIter issues iteration tests add test double_ended_range_iterator_meet_middle add test double_ended_iterator_to_first_elem add tests double_ended_range_iterator_to_first_elem, range_iterator_to_last_elem, iterator_nth separate SpendingKeyParallelIter from SpendingKeyIter add par_iter tests iterator accepts any impl RangeBounds tests to validate RangeBounds conversions known_keys() rpc returns SpendingKeyRange instead of SpendingKeyIter only perform extra GenerationSpendingKey assertions for debug build. add comments
- Loading branch information
Showing
18 changed files
with
1,019 additions
and
126 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
Oops, something went wrong.