Skip to main content
TSN settlement is designed to bind an authorized action to its funding context and to apply state changes through an atomic predecessor check. When the expected state has already advanced, a duplicate settlement cannot apply as though it were new. For a balance-changing action, GPRU is intended to prove that the hidden user state is current and that the proposed transition follows from it. TCAP checks the relevant authorization and asset conditions and applies the transition atomically. The hidden-head proof path is not established end to end, so applications must not treat this design description as evidence that the capability is active.

​
Handling an uncertain result

  1. Keep the original request identifier and any transaction signature.
  2. Query the SDK or configured service for the latest request status.
  3. If a transaction signature exists, check its result on the intended Solana cluster before resubmitting.
  4. If the sender’s signed transaction expired or its blockhash is stale, prepare a fresh transaction and ask the sender to authorize it again.
Do not let an operator edit the payment amount, destination, or other sender-approved terms to make a retry succeed. A service timeout is not proof that a transaction failed; rely on the chain result and current protocol state. For the full replay/nullifier contract and source-level behavior, see the repository’s security and protocol documentation.