blockworks-foundation
/
solana-with-rpc-optimizations
mirror of https://github.com/blockworks-foundation/solana-with-rpc-optimizations.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
solana-with-rpc-optimizations/stake-monitor
History
Jon Cinque 1b1d34da59
Refactor stake program into solana_program (#17906) 
* Move stake state / instructions into solana_program

* Update account-decoder

* Update cli and runtime

* Update all other parts

* Commit Cargo.lock changes in programs/bpf

* Update cli stake instruction import

* Allow integer arithmetic

* Update ABI digest

* Bump rust mem instruction count

* Remove useless structs

* Move stake::id() -> stake::program::id()

* Re-export from solana_sdk and mark deprecated

* Address feedback

* Run cargo fmt
 		2021-06-15 18:04:00 +02:00
..
src Refactor stake program into solana_program (#17906) 2021-06-15 18:04:00 +02:00
.gitignore
…
Cargo.toml Refactor stake program into solana_program (#17906) 2021-06-15 18:04:00 +02:00
README.md Add 1 SOL grace, to allow for a complaint system account to fund a reasonable number of transactions. (#9359) 2020-04-07 13:43:43 -07:00

README.md

Overview

solana-stake-monitor is a utility that scans all transactions to ensure that stake accounts remain in compliance with the following rules:

  1. The stake account must be created after genesis
  2. The "compliant balance" of a stake account is set upon stake account initialization, system transfers of additional funds into a compliant stake account are excluded from the "compliant balance"
  3. The stake account cannot have a lockup or custodian
  4. Withdrawing funds from the stake account trigger non-compliance
  5. Stake accounts split from a compliant stake account remain compliant, and the "compliant balance" is adjusted accordingly for the original stake account

In terms of solana command-line subcommands:

  • create-stake-account: Creates a compliant stake account provided the --lockup-date, --lockup-epoch, or --custodian options are not specified
  • delegate-stake / deactivate-stake / stake-authorize / split-stake: These commands do not affect compliance
  • withdraw-stake / stake-set-lockup: These commands will cause non-compliance
  • transfer: Any additional funds transferred after create-stake-account are excluded from the "compliant balance"

System accounts can also be manually enrolled with the solana-stake-monitor enroll subcommand. An enrolled system account must always maintain a balance greater than the balance it had at enrollment minus 1 SOL.