solana-with-rpc-optimizations/stake-monitor
dependabot[bot] 1df93fa2be
chore: bump serde from 1.0.112 to 1.0.118 (#14828)
* chore: bump serde from 1.0.112 to 1.0.122

Bumps [serde](https://github.com/serde-rs/serde) from 1.0.112 to 1.0.122.
- [Release notes](https://github.com/serde-rs/serde/releases)
- [Commits](https://github.com/serde-rs/serde/compare/v1.0.112...v1.0.122)

Signed-off-by: dependabot[bot] <support@github.com>

* [auto-commit] Update all Cargo lock files

* Update frozen_abi digest following serde update

* Revert "chore: bump serde from 1.0.112 to 1.0.122"

This reverts commit a3ef4442a4c985144ae2bd7ceaf8899a7ab8d7c0.

* Revert "[auto-commit] Update all Cargo lock files"

This reverts commit c41c3b005fb1ccade55155302c52cd5736c4b55f.

* chore: bump serde from 1.0.112 to 1.0.118

Bumps [serde](https://github.com/serde-rs/serde) from 1.0.112 to 1.0.118.
- [Release notes](https://github.com/serde-rs/serde/releases)
- [Commits](https://github.com/serde-rs/serde/compare/v1.0.112...v1.0.118)

Signed-off-by: dependabot[bot] <support@github.com>

* [auto-commit] Update all Cargo lock files

* Remove serum-dex pinning

* blind commit!

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: dependabot-buildkite <dependabot-buildkite@noreply.solana.com>
Co-authored-by: Ryo Onodera <ryoqun@gmail.com>
2021-02-02 23:28:16 +09:00
..
src Remove serial_test_derive dependency (#14891) 2021-01-28 22:35:31 -07:00
.gitignore
Cargo.toml chore: bump serde from 1.0.112 to 1.0.118 (#14828) 2021-02-02 23:28:16 +09:00
README.md

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.