How to delegate to others
Delegate to other validators
Delegate to an address [TO], pointing to the bucket [BUCKET_ID] where the frozen KLV is located.
docker run -it --rm --user "$(id -u):$(id -g)" \
-v $(pwd)/wallet:/opt/klever-blockchain \
--network=host \
--entrypoint=/usr/local/bin/operator \
kleverapp/klever-go:latest \
--key-file=./walletKey.pem \
--node=https://node.mainnet.klever.finance \
account delegate \
klv186vg5k3pqetmfuy04620htcvz3krugu7hqe4ukczdy48r222j78q9y8vm5 \
--bucketID=db0748c562c413a68b21a75249e1b936339fc03513e0bf076d3850b7a81113d2
It's important to know that there's a minimum self-staking amount for the validator. The structure for delegate command is:
[DELEGATE TO ADDRESS].
[DELEGATE TO ADDRESS] is the address you want to delegate the frozen bucket power (in this case your validator address) --bucketID is the bucket hash, which can be found in the frozen TX ID or in Klever testnet explorer.WIth the operator CLI, you can check the bucket ID with the command
tx-by-id followed by the hash of the freeze transaction:docker run -it --rm --user "$(id -u):$(id -g)" \
-v $(pwd)/wallet:/opt/klever-blockchain \
--network=host \
--entrypoint=/usr/local/bin/operator \
kleverapp/klever-go-testnet:latest \
--key-file=./walletKey.pem \
tx-by-id \
45db3a993b64323df2d9841c0ac9a78c8a1760804557a65ca866163e64138bbf
This process is the same of Delegating froozen KLV to node; however, here we choose who we want to delegate to.
To redelegate, you just need to keep the same Bucket ID and type a new address to whom the delegation will be done.
Last modified 1yr ago