-
Notifications
You must be signed in to change notification settings - Fork 810
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
Balances: Configurable Number of Genesis Accounts with Specified Balances for Benchmarking #6267
Conversation
Balances of |
please review @michalkucharczyk @skunert |
please review @bkchr @acatangiu |
@acatangiu @bkontur We need a bridges approval here because this touches some bridge-owned files. This PR helps us to simulate large states in various situations such as benchmarking and also for transactions tests. Approval would be appreciated, I'd like to merge this soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only reviewed the very trivial bridges and xcm related changes
04847d5
Thanks for the review! Glad to see this merged🎉 |
/tip small |
The referendum has appeared on Polkassembly. |
Derived Dev Accounts
Resolves #6040
Description
This update introduces support for creating an arbitrary number of developer accounts at the genesis block based on a specified derivation path.
Key Features
Arbitrary Dev Accounts at Genesis: Developers can now specify any number of accounts to be generated at genesis using a hard derivation path.
Default Derivation Path: If no derivation path is provided (i.e., when
Option<dev_accounts: (..., None)>
is set toSome
at genesis), the system will default to the path//Sender//{}
.No Impact on Total Token Issuance: Developer accounts are excluded from the total issuance of the token supply at genesis, ensuring they do not affect the overall balance or token distribution.
polkadot address: 14SRqZTC1d8rfxL8W1tBTnfUBPU23ACFVPzp61FyGf4ftUFg