pubkey:
.
<AMOUNT>
tokens are transferred from the account at the “from” <KEYPAIR>
to a new stake account at the public key of stake-account.json.
The stake-account.json file can now be discarded. To authorize additional actions, you will use the --stake-authority
or --withdraw-authority
keypair, not stake-account.json.
View the new stake account with the orbition stake-account command:
--stake-authority
and --withdraw-authority
options, or afterward with the orbition stake-authorize
command. For example, to set a new stake authority, run:
<KEYPAIR>
to authorize a new stake authority <PUBKEY>
on the stake account <STAKE_ACCOUNT_ADDRESS>
.
--seed
option:
<STRING>
is an arbitrary string up to 32 bytes, but will typically be a number corresponding to which derived account this is. The first account might be “0”, then “1”, and so on. The public key of <STAKE_ACCOUNT_KEYPAIR>
acts as the base address. The command derives a new address from the base address and seed string. To see what stake address the command will derive, use orbition create-address-with-seed
:
<PUBKEY>
is the public key of the <STAKE_ACCOUNT_KEYPAIR>
passed to orbition create-stake-account
.
orbition validators
command:
orbition delegate-stake
:
<KEYPAIR>
authorizes the operation on the account with address <STAKE_ACCOUNT_ADDRESS>
. The stake is delegated to the vote account with address <VOTE_ACCOUNT_ADDRESS>
.
After delegating stake, use orbition stake-account
to observe the changes to the stake account:
orbition deactivate-stake
command:
<KEYPAIR>
authorizes the operation on the account with address <STAKE_ACCOUNT_ADDRESS>
.
Note that stake takes several epochs to “cool down”. Attempts to delegate stake in the cool down period will fail.
orbition withdraw-stake
command:
<STAKE_ACCOUNT_ADDRESS>
is the existing stake account, the stake authority <KEYPAIR>
is the withdraw authority, and <AMOUNT>
is the number of tokens to transfer to <RECIPIENT_ADDRESS>
.