Every 42,400 BLOCKS (3 days) the system will churn its nodes.
Nodes wishing to leave, and/or
The most unreliable node(s), and/or
The oldest node
But a maximum of 1/3rd the network
The node(s) with the highest bond (typically 4).
Churned out nodes will be put in standby, but their bond will not automatically be returned. They will be credited any earned rewards in their last session. If they do nothing but keep their cluster online, they will be eventually churned back in.
Alternatively, an ACTIVE node can leave the system voluntarily, in which case they are marked to churn out first. Leaving is considered permanent, and the node-address is permanently jailed. This prevents abuse of the LEAVE system since leaving at short notice is disruptive and expensive.
If a Node Operator wants to retrieve part of their bond & rewards (such as deciding to take profits), they can simply Unbond. This keeps their Node on standby, ready to be churned back in.
To unbond from the system, simply send an UNBOND transaction.
Example, this will draw out 10k in RUNE from the bond, as long as the remaining amount is higher than the minimum bond.
If you can't UNBOND, it means your ygg-vault still has funds on it. This means your node spent more gas than it was supposed to during the cycle (various reasons) and is partially insolvent. To fix this you need to rectify your node's insolvency first (send it the missing funds direclty) before doing anything.
Leaving is considered permanent. There are two steps.
If you are Active, send a LEAVE transaction to be ear-marked to churn out. This will take several hours even after changing your status to 'Standby'.
If you are Standby, send a LEAVE transaction to get your bond back and be permanently jailed.
To leave the system, send the following transaction from your original bond address to the Vault Address:
LEAVE:<ADDRESS> with at least 1 tor in funds. Or use ASGARDEX.
⏱Wait a few hours, verify on the /nodeaccount endpoint that you are now
disabled👀 Then send another LEAVE:
⏱Wait a few minutes, verify you have received your bond back 👀 -
make status should show
BOND 0.00 and your wallet should get the full Bond back.
🔥 Commence destroying your node 🔥
If your node is completely offline or destroyed, you will have to perform a manual return of Yggdrasil funds in order to prevent 1.5x bond fine. Ensure you have reviewed this procedure and have all tools ready to go in case you need to do it in anger. This is a time-critical event - you have a few hours to return all funds before the network assumes you have stolen them.
Requirement: You have your
make mnemonic Yggdrasil mnemonic available. If you do not have this, you cannot manually return funds.
Options: 1. Coming Soon: Use ASGARDEX for Manual Return. 2. Coming Soon: Check Discord Dev channels for manual return cli tool. 3. Extract Private Key + Manual return each asset using wallets:
make mnemonic phrase is used to generate the
m/44'/931'/0'/0/0 private key which is used for all chains. Pasting the mnemonic into common wallets will not work as they will be looking under a different "standard" HD Path. Instead, go to https://iancoleman.io/bip39/ and paste in your mnemonic, select RUNE from the Dropdown list and in the bottom table, copy the
m/44'/931'/0'/0/0 private key string. Use this to import into wallets.
The next step is to find the latest inbound addresses. Use https://thornode.thorchain.info/thorchain/inbound_addresses
The memo required is
YGGDRASIL-:<BlockHeight>. For example
YGGDRASIL-:782412. The block height can be found from the
status_since field here:
https://thornode.thorchain.info/thorchain/node/<your node address>
You should complete this checklist before you do the next step:
Have you sent a final LEAVE transaction and have you received your BOND back - ie 1,000,000 RUNE, and can your account for any slash points or rewards?
If yes, then proceed:
To destroy and remove previously created resources, you can run the command below.
First, destroy the node and tools, this will delete your node then your tooling 1-by-1. Do this from the
make destroy destroy-tools
Then destroy the cluster from the
You will be asked to confirm: