gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
v1.7.1
solana/stake-monitor
History
mergify[bot] e247625025 Create solana-poh and move remaining rpc modules to solana-rpc (backport #17698) (#17745) 
* Create solana-poh and move remaining rpc modules to solana-rpc (#17698)

* Create solana-poh crate

* Move BigTableUploadService to solana-ledger

* Add solana-rpc to workspace

* Move dependencies to solana-rpc

* Move remaining rpc modules to solana-rpc

* Single use statement solana-poh

* Single use statement solana-rpc

(cherry picked from commit 544b3c0d17)

# Conflicts:
#	Cargo.lock
#	banking-bench/Cargo.toml
#	core/Cargo.toml
#	core/benches/banking_stage.rs
#	local-cluster/Cargo.toml
#	rpc/Cargo.toml
#	stake-monitor/Cargo.toml
#	validator/Cargo.toml

* Fix conflicts & versions

Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
Co-authored-by: Tyera Eulberg <tyera@solana.com>
2021-06-04 18:19:08 +00:00
..
src
Create solana-poh and move remaining rpc modules to solana-rpc (backport #17698) (#17745)
2021-06-04 18:19:08 +00:00
.gitignore
…
Cargo.toml
Create solana-poh and move remaining rpc modules to solana-rpc (backport #17698) (#17745)
2021-06-04 18:19:08 +00: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.