Staking
Assets held in a custody wallet can be staked without the keys ever leaving the MPC scheme: the platform builds the staking transaction, the transfer goes through the same policy, approval and MPC signing pipeline as a withdrawal, and the platform broadcasts the signed result.
Staking is an optional module, enabled per network. TRON (TRX) is available today.
TRON (TRX)
TRX staking on The Vault is resource freezing with voting: TRX frozen from a wallet votes for a Super Representative and earns rewards. Staking transactions are built through an external staking provider, signed with MPC, and broadcast by the platform; on-chain state is read back from a TRON node. For the network’s own resource model, see TRON.
Operations
| Operation | What it does |
|---|---|
| Stake | Freezes TRX for the configured resource and votes for an allow-listed Super Representative |
| Unstake | Starts the network’s 14-day unbonding. Each unstake becomes its own lot with its own maturity |
| Withdraw | Returns matured unfrozen TRX to the wallet’s spendable balance |
| Claim rewards | Claims accumulated voting rewards. The network allows one claim per 24 hours and only when a reward is actually pending |
Amounts are handled in SUN (1 TRX = 1,000,000 SUN).
Unstaking is not instant and it is not one amount: each unstake matures on its own schedule, and TRX becomes spendable only after a Withdraw once its lot has matured. The dashboard shows each pending lot with its own maturity time.
Policies Apply to Every Step
A staking operation can involve more than one on-chain step — freezing, then voting — and each step is submitted as a transfer. Policies, approval quorums and mobile signing therefore apply exactly as they do to a withdrawal, and a policy that blocks the transfer blocks that step.
Because the steps are separate transfers, an operation can stop half-way: TRX can already be frozen while the voting step is still waiting for approval or was rejected. Make sure the policies that govern a staking wallet allow every step of the operation before you stake with it.
Operation Statuses
An operation is reported as pending while it is being built and validated,
awaiting approval while its transfer goes through governance, sent once
broadcast, and confirmed when the chain confirms it. CONFIRMED is the
terminal success state; REJECTED, FAILED, CANCELLED and EXPIRED are the
terminal failures. An operation that is not confirmed within its configured
lifetime expires.
Positions
The dashboard shows, per wallet: the staked amount and its resource, the pending unfreeze lots with their maturity times, the nearest withdrawal time, and when the position was last reconciled against the chain. Positions are a projection of on-chain state, refreshed on a schedule; if the node is briefly unavailable, the last known position is kept rather than shown as zero.
Deployment Settings
Set per deployment, not per profile: the network (mainnet or the Nile testnet), the resource to freeze (Bandwidth or Energy), the allow-list of Super Representatives that votes may go to, whether voting is active, the lifetime of an unconfirmed operation, and the reconciliation interval. Votes can only go to an allow-listed Super Representative.