anza-xyz-agave/genesis

Genesis

There are a few ways to bake validator accounts and delegated stake into genesis:

1) Through bootstrap validator cli args:

--bootstrap-validator <IDENTITY_PUBKEY> <VOTE_PUBKEY> <STAKE_PUBKEY>
--bootstrap-validator-lamports <LAMPORTS>
--bootstrap-validator-stake-lamports <LAMPORTS>

Note: you can pass in --bootstrap-validator ... multiple times, but the lamports associated with --bootstrap-validator-lamports and --bootstrap-validator-stake-lamports will apply to all --bootstrap-validator arguments. For example:

cargo run --bin solana-genesis --
    --bootstrap-validator <IDENTITY_PUBKEY_0> <VOTE_PUBKEY_0> <STAKE_PUBKEY_0>
    --bootstrap-validator <IDENTITY_PUBKEY_1> <VOTE_PUBKEY_1> <STAKE_PUBKEY_1>
    ...
    --bootstrap-validator <IDENTITY_PUBKEY_N> <VOTE_PUBKEY_N> <STAKE_PUBKEY_N>
    --bootstrap-validator-stake-lamports 10000000000
    --bootstrap-validator-lamports 100000000000

All validator accounts will receive the same number of stake and account lamports

2) Through the primordial accounts file flag:

The primordial accounts file can be used to add accounts of any type to genesis. A user can define all account data and metadata. data field must be BASE64 encoded.

--primordial-accounts-file <PATH_TO_PRIMORDIAL_ACCOUNTS_YAML>

The primordial accounts file has the following format:

---
<IDENTITY_PUBKEY_0>:
  balance: <LAMPORTS_0>
  owner: <OWNER_PUBKEY_0>
  data: <BAS64_ENCODED_DATA_0>
  executable: false
<IDENTITY_PUBKEY_1>:
  balance: <LAMPORTS_1>
  owner: <OWNER_PUBKEY_1>
  data: <BAS64_ENCODED_DATA_1>
  executable: true
...
<IDENTITY_PUBKEY_N>:
  balance: <LAMPORTS_N>
  owner: <OWNER_PUBKEY_N>
  data: <BAS64_ENCODED_DATA_N>
  executable: true

The data portion of the yaml file holds BASE64 encoded data about the account, which can be vote or stake account information.

3) Through the validator accounts file flag:

The main goal with the validator accounts file is to:

• Bake validator stakes into genesis with different stake and account distributions

• Remove the overhead of forcing the user to serialize and deserialize validator stake and vote account state, as required by a primordial accounts file.

  --validator-accounts-file <PATH_TO_VALIDATOR_ACCOUNTS_YAML>
  

  The validator accounts file has the following format:

  validator_accounts:
  - balance_lamports: <BALANCE_LAMPORTS_0>
  stake_lamports: <STAKE_LAMPORTS_0>
  identity_account: <IDENTITY_PUBKEY_0>
  vote_account: <VOTE_PUBKEY_0>
  stake_account: <STAKE_PUBKEY_0>
  - balance_lamports: <BALANCE_LAMPORTS_1>
  stake_lamports: <STAKE_LAMPORTS_1>
  identity_account: <IDENTITY_PUBKEY_1>
  vote_account: <VOTE_PUBKEY_1>
  stake_account: <STAKE_PUBKEY_1>
  ...
  - balance_lamports: <BALANCE_LAMPORTS_N>
  stake_lamports: <STAKE_LAMPORTS_N>
  identity_account: <IDENTITY_PUBKEY_N>
  vote_account: <VOTE_PUBKEY_N>
  stake_account: <STAKE_PUBKEY_N>