Detecting Ejection (cspr.live)

The validator selection occurs at the end of an Era. Due to the bonding delay, this determines the Validators for the Era after the Era about to start.
When your validating node does not participate in consensus for a length of time, it will be marked as invalid. It will be ejected at the end of the next Era.
For example, if we are in Era 100 and your node is invalid, your node will marked for ejection to be removed at the start of Era 102. This is due to the bonding delay of 1 Era.
If you were a previous validator and still exist on the Validators Auction tab on this page https://cspr.live/validators, but not in Validators, you may have been ejected or out bid.

Detecting Ejection (casper-client)

The full auction information is returned with casper-client get-auction-info. We need to filter this down to your public_key.
Replace below with your public_key.
casper-client get-auction-info | jq '.result.auction_state.bids[] | select( .public_key == "<public_key>")'
If running on a normally setup node, this will automatically put in your public_key:
casper-client get-auction-info | jq --arg pk "$(cat /etc/casper/validator_keys/public_key_hex)" '.result.auction_state.bids[] | select( (.public_key | ascii_downcase) == ($pk | ascii_downcase) )'
This will return your bid and show an "inactive" field. If this is true, you are ejected.
If you receive a parse error: Invalid numeric literal at, try running casper-client get-auction-info by itself. The reason for this is usually that your RPC port is not up yet. Get your node in sync and RPC will come up. This should be working before you try to recover.

Correcting your node issue

Before fixing the ejection, you need to correct whatever problem caused your node to be ejected.
Stage missed upgrades or correct any node issues and get your node in sync. If you cannot figure out the issue, as for help in the node-tech-support channel on discord.
To check your node is in sync, compare the current block height at https://cspr.live/ with the height from your node with:
curl -s localhost:8888/status | jq .last_added_block_info

Re-build Contracts for Bonding

Next, you need to re-build the smart contracts required for bonding by following these steps:

1. Navigate to the casper-node directory
2. Check out the current default release branch
3. Re-build the contracts required for bonding

   cd casper-node
   git checkout <replace with current default branch>
   make setup-rs
   make build-client-contracts
   

   Activate Bid

   With your node in sync and ready to validate again, we need to activate your invalid bid. We do that with the activate_bid.wasm contract. This will be part of the normal contracts compile.
   Run the following transaction to re-activate your bid and re-join the network. You will require a balance of at least 5 CSPR for this contract. (We are seeing some variability with this gas cost as of 1.4.9 and will dive into this and try to get better docs on this.)

   casper-client put-deploy --secret-key /etc/casper/validator_keys/secret_key.pem --chain-name casper --session-path "$HOME/casper-node/target/wasm32-unknown-unknown/release/activate_bid.wasm" --payment-amount 5000000000 --session-arg "validator_public_key:public_key='$(cat /etc/casper/validator_keys/public_key_hex)'"
   

   Check that the deploy was successful with the casper-client get-deploy <deploy_hash> or by searching for the deploy_hash on https://cspr.live/.

   Checking Activation

   Once your deploy processes, you can use the casper-client to check your bid again with the Detecting Ejection command above. You should now see "inactive": false,.
   If you wait until the next Era starts, you should also see your public_key as a future validator on https://cspr.live/validators.