solana-foundation/stake-o-matic

Solana Foundation stake bot used on the Solana Testnet and Mainnet-Beta

🏖️ 🏖️ 🏖️

The stake-o-matic has retired!

Visit https://solana.org/delegation-program for the lastest information about the Solana Foundation Delegation Program.

stake-o-matic's Issues

Error withdraw and re-register new key

I register testnet and mainnet key the same. Now I can't withdraw and re-register new key for mainnet (Error: "Registration already exists")
When I try withdraw registration
[2021-06-17T12:40:41.908291066Z DEBUG solana_client::rpc_client] -32002 Transaction simulation failed: Error processing Instruction 0: invalid account data for instruction [2021-06-17T12:40:41.908303953Z DEBUG solana_client::rpc_client] 1: Program reg8X1V65CSdmrtEjMgnXZk96b9SUSQrJ8n1rP1ZMg7 invoke [1] [2021-06-17T12:40:41.908305990Z DEBUG solana_client::rpc_client] 2: Program log: Withdraw [2021-06-17T12:40:41.908307218Z DEBUG solana_client::rpc_client] 3: Program log: Error: mainnet and testnet identities must be unique [2021-06-17T12:40:41.908308479Z DEBUG solana_client::rpc_client] 4: Program reg8X1V65CSdmrtEjMgnXZk96b9SUSQrJ8n1rP1ZMg7 consumed 2160 of 200000 compute units [2021-06-17T12:40:41.908309831Z DEBUG solana_client::rpc_client] 5: Program reg8X1V65CSdmrtEjMgnXZk96b9SUSQrJ8n1rP1ZMg7 failed: invalid account data for instruction [2021-06-17T12:40:41.908311228Z DEBUG solana_client::rpc_client] Error: "error: send transaction: RPC response error -32002: Transaction simulation failed: Error processing Instruction 0: invalid account data for instruction [5 log messages]"

I still don't have “baseline” delegation from the Solana Foundation. it's still N/A

Hi Guys I'm having problem . Pls help me to understand what's wrong. I registered in Nov 21, signed by solana-foundation-delegation-program and yes, I missed some epochs by delinquent state, but at least for few month it's ok. But I still don't have “baseline” delegation from the Solana Foundation. it's still N/A. My pubkey is 2Sd3GfDQHaPcSaza2vB2AqVhL48kS122y75iRKsRbhS1

Stake bot stopped working on mainnet

When collecting data from InfluxDB, it is returning results of different lengths (some rows are 10 long, others are 11).

Either need to change the db query, or update to parse rows with different lengths.

The error in the log is:

Error: Error(UnequalLengths { pos: Some(Position { byte: 135537, line: 849, record: 849 }), expected_len: 10, len: 11 })

Stake bot stopped working on testnet.

The stake bot stopped working on testnet

Here is the command:

./solana-stake-o-matic --url https://REDACTED --participant-url https://REDACTED --cluster testnet --quality-block-producer-percentage 30 --max-poor-block-producer-percentage 20 --max-infrastructure-concentration 25 --min-epoch-credit-percentage-of-average 35 --infrastructure-concentration-affects destake-new --min-release-version 1.11.10 --max-old-release-version-percentage 20 --performance-db-url 'https://REDACTED' --performance-db-token REDACTED --require-performance-metrics-reporting --csv-output-mode first --epoch-classification first --confirm stake-pool-v0 --min-reserve-stake-balance 2 REDACTED /REDACTED.json 5000

And the end of the logs look like this:

Failed transaction: TransactionStatus { slot: 150888844, confirmations: None, status: Err(InstructionError(0, Custom(12))), err: Some(InstructionError(0, Custom(12))), confirmation_status: Some(Finalized) }
Failed transaction: TransactionStatus { slot: 150888844, confirmations: None, status: Err(InstructionError(0, Custom(12))), err: Some(InstructionError(0, Custom(12))), confirmation_status: Some(Finalized) }
⠙ 100.0% | Checking transaction status...           [block height 122623086; re-
[2022-09-13T19:53:42.801944416Z INFO  solana_client::pubsub_client] websocket thread - shutting down
[2022-09-13T19:53:42.801986900Z INFO  solana_client::pubsub_client] websocket - exited receive loop
Error: "Failed to create validator stake accounts"
🚨 Error: The command exited with status 1

I believe 12 is a StakeError::InsufficientDelegation error, so the working hypothesis right now is that the error has to do with the recently added minimum delegation amount. One possibility is that the split_with_seed instruction here (https://github.com/solana-labs/stake-o-matic/blob/master/bot/src/stake_pool_v0.rs#L570) is responsible for attempting to create a stake account with stake below the minimum.

Cannot load validator wiki

For the last couple of weeks I've gotten this error message, more often than not, while loading my wiki:

The wiki page took too long to render.
This wiki page’s content is too large to render on this page.

The mainnet staking bot is removing validators from the delegation program due to incorrect commission change detection in validators.app.

The site validators.app identified a huge number of validators changing fees at the same time at the border of epochs 403 and 404, when in reality this did not happen. As a result, the mainnet staking bot, based on this information, removed these validators from the delegation program.
Third party commission change detection sites such as https://stakewiz.com or https://validators-api.marinade.finance/reports/commission-changes did not capture commission changes.
https://www.validators.app/commission-changes?locale=en&network=mainnet
A few examples besides dozens of others.

CXASPwmruKhiL4eRWEREYktgQHvTMJcXVFwRgXRaswe9
https://www.validators.app/validators/CXASPwmruKhiL4eRWEREYktgQHvTMJcXVFwRgXRaswe9?network=mainnet
https://solana.org/sfdp-validators/CXASPwmruKhiL4eRWEREYktgQHvTMJcXVFwRgXRaswe9
https://stakewiz.com/validator/BGFALjMdG8x4Vzwh5H1q61HWZagMXEk2wkFMteH5qcNk

GezZ48oKmb79E9V4ouz53eNVifLGz8QqabVuVVJdvWqk
https://www.validators.app/validators/GezZ48oKmb79E9V4ouz53eNVifLGz8QqabVuVVJdvWqk?network=mainnet
https://solana.org/sfdp-validators/GezZ48oKmb79E9V4ouz53eNVifLGz8QqabVuVVJdvWqk
https://stakewiz.com/validator/7oRCGUVzrprUqt9HqMuiSDMDhyN4proYsSGSLiFjHme2

8LVVWgBvrRaAmcRB8BQ77BNe8YEqZ3zydMHhUYXx1bV
https://www.validators.app/validators/8LVVWgBvrRaAmcRB8BQ77BNe8YEqZ3zydMHhUYXx1bV?network=mainnet
https://solana.org/sfdp-validators/8LVVWgBvrRaAmcRB8BQ77BNe8YEqZ3zydMHhUYXx1bV
https://stakewiz.com/validator/ADepVu5y5n4uF5zcuFpccbY4FWa5XY5RWMViGXNeC8gb

CTwsruptUccEtZGNxBDbuusHYxkBX3P6ndrxVjSG213y
https://www.validators.app/validators/CTwsruptUccEtZGNxBDbuusHYxkBX3P6ndrxVjSG213y?network=mainnet
https://solana.org/sfdp-validators/CTwsruptUccEtZGNxBDbuusHYxkBX3P6ndrxVjSG213y
https://stakewiz.com/validator/Fhks5gukimP6vxKYbRY4V1aw888EgHhpdDSscD9V6bub

ESihGHvvNWPBTu3RZohRgEEuBmoyVhgHYTf3Cot9523L
https://www.validators.app/validators/ESihGHvvNWPBTu3RZohRgEEuBmoyVhgHYTf3Cot9523L?locale=en&network=mainnet&order=stake&refresh=
https://solana.org/sfdp-validators/ESihGHvvNWPBTu3RZohRgEEuBmoyVhgHYTf3Cot9523L
https://stakewiz.com/validator/HtRAGpko23W2t8wPUU8HuUQC1TrRUuK64K8RCqRD5ubX

Stake Bot in the testnet removes the stake from all nodes

In the testnet epoch 391, the stake bot identified all nodes from the delegation program as violating the conditions according to the metrics. It is based on the results of epoch 389:

https://discord.com/channels/428295358100013066/712904308282097695/1045496460810145814

Validators by stake level: None=2057, Baseline=5, Bonus=0
Non-reporting epochs: "388, 389"

However, according to https://metrics.solana.com/d/EcFDgFgVk/validator-last-optimistic-slot?orgId=1&refresh=1m for each individual node, you can see that the metrics are being sent right.

It is not clear if this is related to the warp jump during the testnet restart, because we restarted it to epoch 387, that is, the metrics are considered to be skipped after the warp jump.

Result: now the bot removes the entire stake from all nodes:
Balance: 47726.812844392 SOL
Delegated Stake: 47726.810561512 SOL
Active Stake: 47726.810561512 SOL
Stake deactivates starting from epoch: 391

At the moment, there are about 4 hours left until the end of the epoch.

If do not stop the deactivation untill end of this epoch, then this can lead to problems with the testnet (big part of stake deactivates at one moment).

In addition, it is needed to exclude the None stake status for all nodes that it was defined by the bot based on the results of epoch 389 and correct it for future epochs.

Otherwise, this may soon lead to deactivations in the mainnet due to violations of the "Testnet Performance >= 5/10" condition.

Do not rely only on validators.app for DC concentration score

The stake-o-matic implementation relies on single centralized, potentially unreliable data source for stake concentration calculation.

The internet routing table is one of the most replicated pieces of data in existence. It would be very possible to use multiple RIS data sources or even BGP/BMP feeds to independently construct a data center mapping.

Can't install 1.0.5 version of solana-foundation-delegation-program-cli

What i did:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
sudo apt update -y
sudo apt install -y libudev-dev
cargo install solana-foundation-delegation-program-cli

Errors:

$ cargo install solana-foundation-delegation-program-cli
    Updating crates.io index
  Installing solana-foundation-delegation-program-cli v1.0.5
error: failed to compile `solana-foundation-delegation-program-cli v1.0.5`, intermediate artifacts can be found at `/tmp/cargo-installIGObAS`

Caused by:
  failed to select a version for the requirement `crypto-mac = "^0.7"`
  candidate versions found which didn't match: 0.11.1, 0.11.0, 0.10.1, ...
  location searched: crates.io index
  required by package `hmac v0.7.0`
      ... which is depended on by `hmac-drbg v0.2.0`
      ... which is depended on by `libsecp256k1 v0.3.5`
      ... which is depended on by `solana-sdk v1.7.4`
      ... which is depended on by `solana-account-decoder v1.7.4`
      ... which is depended on by `solana-client v1.7.4`
      ... which is depended on by `solana-foundation-delegation-program-cli v1.0.5`

How to fix

add dependencies to Cargo.toml

[[bin]]
name = "solana-foundation-delegation-program"
path = "src/main.rs"
[dependencies.clap]
version = "2.33.3"

[dependencies.crypto-mac]   <<< add this
version = "=0.7.0"                  <<< add this

[dependencies.solana-account-decoder]
version = "=1.7.4"

DEVELOPERS, please build your package and publish it again

if you want to build manually:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
sudo apt update -y
sudo apt install -y libudev-dev
cargo install cargo-download
cargo-download solana-foundation-delegation-program-cli -x
cd solana-foundation-delegation-program-cli-1.0.5

### maybe it will be required 
### sudo apt install build-essential libudev-dev pkg-config libssl-dev -y

### Edit Cargo.toml
add this

[dependencies.crypto-mac]
version = "=0.7.0"

### save Cargo.toml

### in the same folder solana-foundation-delegation-program-cli-1.0.5

cargo build
cd target/debug
./solana-foundation-delegation-program --version
./solana-foundation-delegation-program apply ...

-no issue-

pls delete issue

Mainnet Epoch 192 missing

Mainnet epoch 192 is missing in wiki.

Not all dependencies are listed in installation instruction.

README says:

$ sudo apt install libudev-dev
$ cargo install solana-foundation-delegation-program-cli

But for my Ubuntu 20.04 it was necessary to install some other packages:
apt install build-essential libudev-dev pkg-config libssl-dev -y

Without it there were errors during cargo's installation, like this:

error: failed to run custom build command for `hidapi v1.2.6`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installZevy2N/release/build/hidapi-4e8337fb40e827d6/build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=LIBUDEV_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=LIBUDEV_STATIC
  cargo:rerun-if-env-changed=LIBUDEV_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at 'Unable to find libudev: Command { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"libudev\"", cause: Os { code: 2, kind: NotFound, message: "No such file or directory" } }', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/hidapi-1.2.6/build.rs:53:54
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `solana-foundation-delegation-program-cli v1.0.1`, intermediate artifacts can be found at `/tmp/cargo-installZevy2N`

Caused by:
  build failed

error: failed to run custom build command for `hidapi v1.2.6`

Hi
I am trying to install but I am getting this error: error: failed to run custom build command for hidapi v1.2.6 . I already have tried it on two different instances still I am getting this error. I may be doing something wrong. Please advise.

https://github.com/solana-labs/stake-o-matic.wiki.git

Testnet bot didn't run on Epoch 212 (current)

Hello,

this is kind of an urgent issue since there's still time to prevent/fix it.

The testnet bot didn't run in this Epoch yet (212).

There's still time to fix it (14 hours for the epoch to finish).

I spoke with @t-nelson and it looks like there's an issue with it: