Staking lets supported accounts participate in ledger-specific staking workflows from Ripple Custody.
- Cardano supports staking address registration, stake-pool delegation, reward withdrawal, and staking address unregistration.
- Tezos supports delegating and undelegating validation rights without transferring token ownership.
- Polkadot staking is available with API workflows for validator-related staking tasks.
- Staking operations are submitted as transaction orders and follow the normal intent approval flow.
Staking turns custody accounts into active network-participation accounts. Operators can delegate, withdraw rewards, or manage staking state while retaining the approval, signing, audit, and policy controls used for other Ripple Custody transaction workflows.
For operators: Staking workflows help manage rewards and validator participation without leaving the custody operating model.
For architects: Staking setup depends on ledger-specific account state, fee handling, and approval policy. Plan which accounts can initiate staking operations and which users can approve them.
Before setting up staking, confirm:
- The account is on a supported ledger.
- The account has enough funds to cover transaction fees and any staking amount.
- The users who submit and approve staking intents have the required permissions.
- Ledger-specific prerequisites are complete. For example, Tezos accounts must have their public key revealed on chain before delegation or undelegation.
| Ledger | UI procedure | API procedure | Supported operations |
|---|---|---|---|
| Cardano | Set up Cardano staking in the UI | Set up Cardano staking with the API | Register staking, delegate staking, unregister staking, withdraw rewards |
| Tezos | Delegate Tezos staking in the UI | Delegate Tezos staking validation rights with the API | Delegate validation rights, undelegate validation rights |
| Polkadot | Not available in the UI | Set up Polkadot staking with the API | Bond, unbond, rebond, bond extra, withdraw unbonded, chill, nominate, set payee, set controller |
Staking tasks use the transaction-order workflow. The exact payload depends on the ledger, but the operating pattern is consistent:
When the transaction order is successfully approved and executed, Ripple Custody creates a transaction to broadcast the staking operation to the blockchain. It also creates one or more transfers to represent the amounts associated with the transaction, such as the cryptocurrency amount and fees.
| Ledger | What to understand |
|---|---|
| Cardano | Staking setup involves registering a staking address and delegating to a stake pool. After registration, you can withdraw staking rewards or unregister the staking address. |
| Tezos | Token holders can delegate validation rights to validators or bakers without transferring ownership of their tokens. The account as a whole is delegated. |
| Polkadot | Polkadot staking uses staking operations such as bonding, nomination, chilling, and reward payee configuration. Polkadot ledgers use stash and controller account roles, although Ripple Custody does not require separate accounts. |
| Topic | Description |
|---|---|
| Accounts | Understand the accounts that initiate staking operations. |
| Manage accounts with the API | Find account IDs and check balances before submitting staking intents. |
| Transaction initiation | Understand transaction order creation. |
| Intents and approvals | Understand how staking changes are approved and executed. |
| Reveal Tezos accounts | Prepare Tezos accounts for delegation in the UI. |