TCAP: Private Balance and Token Authorization for TSN
TSN architecture · TCap
TCAP (Transfer Confidential Asset Protocol): Private Balance for TSN
TCAP is the private balance and asset-accounting layer of TSN. It keeps balance details in encrypted owner-authorized snapshots while placing only commitments, sequence state, policy references, and replay protection at the protocol boundary.
What TCAP owns
- Token identity, registry policy, and governed asset acceptance.
- TCAP TIN tips with monotonic sequence and commitment transitions.
- One-time nullifiers and TSN settlement authorization receipts.
- Encrypted balance snapshots that the owner decrypts locally.
How a private balance is read
- The client fetches the public TCAP tip and its current commitment.
- The owner loads one encrypted snapshot by opaque commitment locator.
- The SDK verifies the snapshot hash and sequence against the tip.
- The owner decrypts the snapshot locally and reads token balances.
Observers see coordination commitments and state transitions, not plaintext balances, TIN secrets, wallet roots, or encrypted snapshot contents.
TCAP and TSN separation
TSN coordinates payment intents, epoch treasury obligations, Mother DNA, and settlement work. TCAP coordinates private balance credits and policy-bound token state. GPRU routes and authorizes; it never holds funds.
Production security model
Every credit binds the previous tip, new commitment, sequence, token policy, GPRU scope, nullifier, TSN settlement commitment, and expiry. A replayed or altered credit fails before state movement, preserving a deterministic private balance history.
Read the GPRU authorization and routing layer → · Read about TIN identity → · Read the TSN settlement flow →