Comment on page

Staking via community site

To comply with recent SEC rulings, United States persons and persons from OFAC-sanctioned regions cannot receive token rewards from staking. All participants will be required to pass KYC to receive rewards.
You don't, however need to use the community site. You may perform all staking functions directly on-chain by interacting with DPoS contract.
If you still wish to use the community site, please follow the steps below.

0. Register an account on the community site

Navigate to the community site and register an account.

1. Pass KYC

To claim rewards (e.g., staking commission, yields) from the community site, you must pass KYC. It is in the profile section.
DISCLAIMER: To comply with recent SEC rulings, United States persons and persons from OFAC-sanctioned regions cannot receive token rewards from running nodes. All participants will be required to pass KYC to receive rewards.

2. Connect your wallet

Connect your wallet (upper-right corner). You may use any web3-enabled wallet that works with the Taraxa network, we recommend MetaMask.

3. Delegate to a validator

Once your wallet is connected, navigate to the community site's staking page and select one ore more validators to delegate to.
On this page you'll see a list of validators that have listed their nodes up for delegation. The "Avalailable for Delegation" shows you how much more delegation this specific node is able to take in. Each node can take on a total of 80 million TARA in delegation, beyond that no more delegation is possible for the specific node.
NOTE: the dev team is working to gather and display past uptime statistics (work in progress) so that you may make an informed choice on which validator to delegate your tokens to. Uptime is critical as it impacts the effective yield rate - i.e., if a node is not turned on, it does not earn any yields.
Minimum delegation per validator node is 1000 TARA.

4. Claim staking yields

You may claim your staking yields by clicking the "Claim" button next to each of the nodes you've delegated to. You may claim your yields at anytime there are yields available to be claimed.

5. Re-delegate

Sometimes if the validator node you're delegating to is under-performing, shut down, or for whatever reason you no longer wish to delegate to that node anymore, you could shift your delegation to another validator node. This is called re-delegation.
On the staking page of the community site, you can see a button called "Shift delegation OUT" next to the validator nodes you have delegated to. This button helps you to move delegation OUT of that particular node and into another one.
For example, let's say that a user is no longer happy with the validator node 0xC83e..., and wants to shift delegation out of it, and INTO the validator node 0x94Ca...
The user will then click on the "Shift delegation OUT" button next to the node they're unhappy with, and you'll see a screen that asks them where you want to shift their delegation into. At the top left corner is the validator node to shift delegation OUT from, and at the bottom is a list of validator nodes, from which they'll be able to select one that they'd want to shift the delegation INTO.
In this example, they pick the one 0x94Ca... and click on the "Shift delegation IN" button next to the node.
Once the button is clicked, a confirmation screen will pop up that allows the user to specify how many tokens they'd like to shift over.
Once the re-delegate button is clicked and the transaction is confirmed, the re-delegation has been completed.
Make sure to confirm that the re-delegation has gone through properly, refresh the staking page.
Here we see that indeed 500k TARA has been moved from validator node 0x94Ca...

6. Un-delegate

You may choose to un-delegate your tokens from a validator node at any time, simply select the "Un-delegate" button next to the node.
Here are a few things to remember when un-delegating,
  • Un-delegate initiates a removal of a defined amount of delegated tokens from the validator node
  • Once you initiate un-delegation, there's a delay of 700,540 blocks (~30 days) delay before you can claim your tokens
  • If you simply wish to shift delegation from an under-performing node to one that performs better, you should consider using re-delegation which only has a few PBFT block delay (a few seconds)
  • You can un-delegate, using the same wallet, from multiple validators simultaneously
  • You can NOT un-delegate, using the same wallet, from the same validator multiple times - you'd have to either cancel the un-delegation (at the top of the community staking page), or wait till the current un-stake delay has fully elapsed and execute a new un-stake