Read existing creator routing and topups

Creating and managing tokens · Reference and existing-action how-to · New router configurations are deferred. Existing controls, undo, history and topups remain individually capability-gated.

Interpret allocations, pauses, source-event receipts and scoped creator controls without treating deferred configuration as open.

Reviewed: 2026-10-18

Before you start

  • An existing coin routing record.
  • Recorded creator proof and an unexpired creator session for private controls; current capability for each action.

Splits, pauses and deferred recuts

Open the token’s Creator controls at /desks/:slug/manage and read the current split and effective allocation. New allocation/recut admission is deferred even if the editor or a preset exists. Do not treat a public routing view as authorization to change it.

For existing permitted pause controls, inspect affected destinations and confirm the exact review. Paused destinations can change effective allocation, but if all destinations are paused, inflows are held—not rerouted. Undo is available only for an eligible pending recut and within its displayed window.

  1. Load the existing routing record and retry a read error rather than assuming an empty allocation.
  2. Check the current split, pauses, held amounts and pending changes.
  3. If an existing pause or undo action is offered, review its exact effect and confirm once. Read the resulting state; a failed request is not a completed change.

Distinguish a guided transfer from registering a receipt

A guided topup prepares an exact asset, amount, destination, fee and expiry review before a permitted transfer. It is irreversible and nonrefundable routed revenue, not a balance you or the creator can later withdraw.

Manual deposit registration records an already-existing transaction using its signature, root instruction index, amount, asset/mint and source. It is not a request to send that payment again. Recognition as a source event is separate from destination execution.

  1. For a guided topup, choose a supported asset and positive amount, then Get exact quote.
  2. Inspect source, destination, network, mint/precision, transfer fee, inflow fee, remaining router amount and expiry. Resolve all blockers and acknowledge irreversibility.
  3. Use the offered authorization once. If reconciling or unknown, Refresh status on the saved topup; do not sign or send again.
  4. For manual registration, supply only the exact existing transfer evidence and inspect the returned source-event result. Do not create a new transfer to repair a missing read.

Follow attribution and execution separately

History shows source events, obligations and attribution; older records and read failures have their own paging/Retry controls. Use native-asset amounts rather than inventing a combined USD total.

A router source receipt, an allocation, a desk fill and a revenue/burn receipt are distinct evidence. Check the referenced transaction and status for the outcome you are trying to establish. A stale or partial history cannot prove no obligation exists.

Use scoped, expiring creator authority

Creator controls require proof from the recorded creator and an unexpired session. Read the session reason and expiry. A connected wallet with a different address is not interchangeable, and a public page does not grant creator rights.

When a session expires, use the offered re-verification flow and review the exact message. Desk manual/automatic controls, when present, remain independently gated; they do not override release admission, venue support, funding or signing policy.