Appearance
Risks
What you take on by holding vATOM, in plain terms.
Most of it is the risk of staking ATOM at all — slashing, and the Cosmos Hub's 21-day unbonding period. Those apply whether you stake yourself, delegate through a wallet, or use this. The parts that are specific to vATOM are marked as such.
Staking risk
Your ATOM is really delegated to real validators, so it earns real rewards and carries real validator risk.
If a validator is slashed, the pool shrinks and the exchange rate falls with it. Two details are easy to miss:
- Slashing applies while you are unbonding. Redeeming does not put your ATOM out of reach for the 21 days it takes to unwind.
- A loss is recognised straight away, not smoothed over time. That is deliberate: smoothing it would let the fastest redeemers leave at a stale rate and pass the loss to everyone slower.
Deposits are spread across up to 20 validators, which limits what any single one can cost you. Correlated failures — shared infrastructure, a common client bug — are not covered by that.
Getting your ATOM back takes 21 days
Redeeming is not instant and cannot be cancelled. Your request waits for the next batch, then the Hub's unbonding period runs. See redeeming takes 21 days for the stages.
If vATOM trades on a market you may be able to sell sooner, at whatever price that market offers — typically below redemption value when people are in a hurry. The protocol neither supports nor backstops any market.
Some timings depend on somebody acting
vATOM-specific. Collecting rewards, processing a batch and finalizing a matured one are permissionless: anybody can call them, and nobody is obliged to. In practice an operator runs them on a schedule.
If they stop, the exchange rate stops rising and matured claims wait. Nothing is lost — a later call picks it all up, and you can make these calls yourself — but a claim can arrive later than you expected. See keeping it running.
The deposit cap can refuse a deposit
vATOM-specific. There may be a ceiling on the pool while the contract earns confidence. When it is reached, new deposits are refused; redemptions and claims are never affected. The dashboard shows the current headroom.
What the protocol cannot do
Worth knowing precisely, because these are places where protocols often do carry risk and this one does not:
- No fee. Fixed at zero basis points and not adjustable — there is no fee switch to be flipped later.
- Nobody can mint vATOM, redirect a mint or burn, or withdraw the pool. Those message types are compiled-in constants rather than configuration, so they cannot be pointed elsewhere.
- Nobody can take, freeze or confiscate your position. No message does that.
- No bridge. The contract runs on the Hub and stakes on the Hub — no relayers, no channels to get stuck, no packets to time out.
- No oracle. The exchange rate is computed from the contract's own on-chain delegation balance. There is no price feed to manipulate or halt.
- No rehypothecation. Your ATOM is delegated, not lent or leveraged.
- The rewards vault's code is immutable, and verified on chain before the main contract will use it.
Who can change things
Two keys, with deliberately different reach.
A guardian exists so somebody can act within minutes if a validator misbehaves. It can pause the contract, lower the deposit cap, and remove validators — and nothing else, because no other message accepts it. It cannot unpause, add a validator, or move a token, so even a stolen guardian key cannot take anything: at worst it stops the protocol until the admin restarts it.
Removing a validator also stops new deposits until an admin sets a new allocation, while redeeming and claiming keep working — a bad validator should not freeze anyone's exit.
The admin does everything else: unpause, raise the cap, add validators, move an existing delegation, transfer the role, and settle a batch with a stated slashing figure. These take effect immediately — there is no timelock in front of them today, so the admin key is one worth protecting, and putting it behind governance or a timelocked multisig is an open item. The fast defensive powers were split into the guardian precisely so that a delay on the admin would not slow the response to a bad validator.
Neither key can do anything in the list above.
Your keys are yours
Keplr keeps your key in the extension and shows you every transaction before you approve it. A website can ask; it cannot move anything you did not agree to.
The flip side is that nobody can recover your account for you. If you lose your seed phrase the position is gone, the same as any self-custodied wallet.
Using vATOM somewhere else
vATOM is an ordinary token, so other contracts can hold it. If you put it into a pool, a lending market or a vault, you take on that protocol's risk on top of this one. Nothing here says anything about the safety of wherever you take it next.