1. Docs
  2. Products
  3. Positions and claims

Products

Positions and claims

Find wallet-linked positions, verify live state, and understand the cost of each action.

Revision 64 min read
On this page
  1. Find a position
  2. Practical example
  3. Fees and costs
  4. Verify before claiming
  5. Profile workspace
  6. When a position is missing
  7. Common problems

My positions is a discovery workspace for every indexed position where the connected wallet is the creator, beneficiary, or participant: token locks, vesting schedules, payment streams, stake positions, airdrop claims and campaigns, Digital Asset locks, and LP locks.

My positions as a sortable table with position-type tabs, role and status filters, and claim actions
Fig. 01My positions as a sortable table with position-type tabs, role and status filters, and claim actionsFull size

The page does not custody funds and does not decide whether a wallet may claim. Before a transaction, the destination page reads authoritative Move state and recomputes signer eligibility.

Find a position#

  1. Connect the wallet that created or benefits from the position.
  2. Open My positions from the dApp sidebar and confirm Supra Testnet is selected.
  3. Choose a Position type tab: Token locks, Vesting, Payment streams, Staking, Airdrops, Digital asset locks, or LP locks. Each tab shows its position count.
  4. Narrow the list with the wallet role (All roles, Beneficiary, or Creator; on Airdrops, My claims or My campaigns) and the status filter, such as Locked, Ready to claim, or Claimed for timed locks.
  5. Search by token, address, or vault ID, or turn on Claimable only. Search and Claimable only apply to the rows on the current page.
  6. Sort by Position, Amount, Claimable, or Unlock / next (UTC) by selecting the column header, and use Rows per page and the page controls for long lists.
  7. Use the row action: Claim when value is ready, Manage, Reclaim, or View otherwise, and Proof to open the public proof in a new tab.
  8. Compare the exact object address with the original transaction and review authoritative on-chain state before signing any action.

Amounts in the table are compacted for overview; the exact value is available on hover or focus and on the claim page. On narrow screens each position is shown as a card with the same fields. The Stream claims, Liquidity claims, and Digital asset claims links in the sidebar show how many of those positions are ready to claim.

Practical example#

Alice is the beneficiary of one fixed token lock and one vesting schedule.

  • My positions lists them on the Token locks and Vesting tabs after the indexer processes their creation events.
  • Before maturity, the lock row shows the unlock time and no claim action.
  • After maturity, she claims the full lock with no protocol claim fee, paying only network gas.
  • She then opens vesting, reviews 10,000 EXR gross claimable, a 100 EXR protocol fee at an example 1% snapshotted rate, and 9,900 EXR net before signing.

The two claim flows have different fees even though they appear in the same discovery page.

Fees and costs#

Browsing and filtering positions is read-only: it needs no transaction, protocol fee, or gas. A claim or management action follows the underlying product's rules:

Underlying actionTrust Stack protocol feeOther cost
Fixed token-lock claimNoneBeneficiary pays network gas
Vesting claimSnapshotted rate, at most 1%, of gross released assetBeneficiary pays network gas
Payment-stream claimNoneBeneficiary pays network gas
Staking reward claim or withdrawalNoneParticipant pays network gas
Airdrop claimNoneRecipient pays network gas
Digital Asset or LP-lock claimNoneBeneficiary pays network gas

The product page and final transaction review are authoritative for the exact action. See Fee governance.

Verify before claiming#

Check:

  • the complete position object address;
  • connected wallet and expected beneficiary;
  • token or object identity;
  • gross amount, protocol fee, and net amount where applicable;
  • maturity, cliff, campaign, or cancellation state;
  • prior claims and current expected vault balance; and
  • the transaction function and network shown in the wallet.

Never sign only because a position appears in a list. Indexing is a discovery aid, not transaction authorization.

Profile workspace#

Profile page showing local identity and wallet-linked positions
Fig. 02Profile page showing local identity and wallet-linked positionsFull size

My profile, at the bottom of the dApp sidebar, combines a browser-local display name and profile picture with a public position overview and links to each product workspace. These preferences do not replace the address as on-chain identity, grant account authority, or change fees.

When a position is missing#

  1. Confirm the same wallet address and Supra Testnet network.
  2. Open the creation transaction in SupraScan and verify successful finalization.
  3. Copy the exact emitted object address.
  4. Refresh after the indexer has processed the block.
  5. Use the direct management or claim route with the object address if discovery remains delayed.

A missing list item does not prove that creation or a claim failed. Current Move state and the transaction receipt remain the source of truth.

Common problems#

  • Wrong role filter: switch between creator and beneficiary, or choose All roles.
  • Claim disabled: confirm signer, current chain time, lifecycle state, and remaining claimable value.
  • Search finds nothing: search and Claimable only cover only the current page; widen the filters or change page.
  • Unexpected fee: open the underlying product page and verify gross, fee, and net before signing.
  • Duplicate-looking entries: identify positions by full object address and creation hash.
  • Indexer delay: use authoritative direct reads instead of submitting another creation transaction.