docs.rs failed to build solana-stake-monitor-1.2.19
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
solana-stake-monitor-1.7.4
Overview
solana-stake-monitor
is a utility that scans all transactions to ensure that stake accounts remain in compliance with the following rules:
- The stake account must be created after genesis
- 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"
- The stake account cannot have a lockup or custodian
- Withdrawing funds from the stake account trigger non-compliance
- 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 specifieddelegate-stake
/deactivate-stake
/stake-authorize
/split-stake
: These commands do not affect compliancewithdraw-stake
/stake-set-lockup
: These commands will cause non-compliancetransfer
: Any additional funds transferred aftercreate-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.