Skip to main content
TSN distinguishes request acceptance, verification, transaction submission, and Solana confirmation. A failure or timeout at one stage does not prove that a later stage ran. A confirmed funding transaction also does not prove a separate credit transaction succeeded. The expected behavior is to stop when a required authorization, identity, proof, asset, liquidity, or chain check cannot be established. Applications should show the reported stage and reason without describing unconfirmed work as settled.

​
Safe application response

  1. Preserve the request identifier and any transaction signatures.
  2. Query the latest request status and inspect each transaction on the selected network.
  3. Do not retry with altered sender-approved terms.
  4. If an owner-signed transaction has expired, prepare a new one and request the owner’s signature again.
GPRU is intended to guard the private state presented to TCAP; TCAP governs funds and applies authorized transitions atomically. The hidden-head proof path is not established end to end, so an application must not promise that proof-gated settlement is available. Internal rejection reasons and operator recovery procedures are maintained in the repository runbooks.