Available, delegated and unclaimed
Every token card carries an availability. It records what state the balance is in, not just how much of it there is, and it is the reason one wallet can have three cards for the same token.
The three states
| Availability | What it holds |
|---|---|
| Available | The liquid balance sitting in the wallet, free to move or spend. |
| Delegated | Funds actively staked: bonded or delegated to a validator. |
| Unclaimed | Pending staking rewards, plus anything in the unbonding or withdrawal period. |
Availability is set when you create the token card and defaults to Available. Cards are badged throughout the app: Available in green, Delegated in orange, Unclaimed in blue.
A wallet that does not stake needs only Available cards. Fiat cards on exchange wallets have no availability at all.
Why they are separate cards
Each availability is a different on-chain balance. A validator's bonded stake is not the wallet's spendable balance, and pending rewards are neither.
Because a token card is what SimplyLedger reconciles, keeping them separate means:
- Balances are fetched per availability. Creating a card reads the on-chain balance for that state specifically, not the wallet total.
- Reconciliation compares like with like. Each card is reconciled against the balance actually held in that state at the closing date. One combined card would never agree.
- The books show where value is. Staked capital and unclaimed rewards land in their own accounts rather than being indistinguishable from cash.
Availability cannot be edited later
It is fixed when the card is created, and the card is what postings and reconciliations attach to. If you create a staked position as Available and only notice after posting against it, the fix is a new card and corrected postings, not a setting.
Availability when posting
Staking moves value between the cards rather than in or out of the wallet, and posting is where that movement is recorded.
When a token has more than one card in a wallet, the contra dropdown lists each one separately (Wallet A (Available), Wallet A (Delegated), Wallet A (Unclaimed)), so you can post the movement between them:
| Event | Movement |
|---|---|
| Staking | Available → Delegated |
| Rewards accruing | into Unclaimed |
| Claiming rewards | Unclaimed → Available |
| Unbonding | Delegated → Unclaimed, then → Available when it lands |
Elsewhere in the app the same information appears in the card's label, alongside the token and its address:
Ethereum (ETH) · 0xC02aaA39b2…c2 · DelegatedWhere a wallet has only one card for a token, the suffix is dropped; it is shown to tell cards apart, not as decoration.
Availability in posting rules
A posting rule can target an availability, so recurring staking activity categorises itself. If your entity stakes on a schedule, this is worth setting up once rather than categorising each reward by hand.
Next
Tokens and addresses covers the reference data a token card is built on, and what to do when a token you hold is not there.