solana-with-rpc-optimizations/stake-o-matic
Tyera Eulberg ffa5c7dcc8
Deprecate commitment variants (#14797)
* Deprecate commitment variants

* Add new CommitmentConfig builders

* Add helpers to avoid allowing deprecated variants

* Remove deprecated transaction-status code

* Include new commitment variants in runtime commitment; allow deprecated as long as old variants persist

* Remove deprecated banks code

* Remove deprecated variants in core; allow deprecated in rpc/rpc-subscriptions for now

* Heavier hand with rpc/rpc-subscription commitment

* Remove deprecated variants from local-cluster

* Remove deprecated variants from various tools

* Remove deprecated variants from validator

* Update docs

* Remove deprecated client code

* Add new variants to cli; remove deprecated variants as possible

* Don't send new commitment variants to old clusters

* Retain deprecated method in test_validator_saves_tower

* Fix clippy matches! suggestion for BPF solana-sdk legacy compile test

* Refactor node version check to handle commitment variants and transaction encoding

* Hide deprecated variants from cli help

* Add cli App comments
2021-01-26 19:23:07 +00:00
..
src Deprecate commitment variants (#14797) 2021-01-26 19:23:07 +00:00
.gitignore
Cargo.toml
README.md
stake-o-matic.sh Display solana version (including commit sha1) before starting SoM 2021-01-14 21:17:54 -08:00

README.md

Effortlessly Manage Cluster Stakes

The testnet and mainnet-beta clusters currently have a large population of validators that need to be staked by a central authority.

Staking Criteria

  1. All non-delinquent validators receive 50,000 SOL stake
  2. Additionally, non-deliquent validators that have produced a block in 75% of their slots in the previous epoch receive bonus stake of 500,000 SOL

A validator that is delinquent for more than 24 hours will have all stake removed. However stake-o-matic has no memory, so if the same validator resolves their delinquency then they will be re-staked again

Validator Whitelist

To be eligible for staking, a validator's identity pubkey must be added to a YAML whitelist file.

Stake Account Management

Stake-o-matic will split the individual validator stake accounts from a master stake account, and must be given the authorized staker keypair for the master stake account.