The four layers
TSN is not one program. It is four cooperating layers, each with a strict boundary.
The layers are separated on purpose. A GPRU signature alone cannot move custody. A cranker cannot rewrite an authorization. TCAP owns the tip and sequence, not payment intent. TIN never holds a key.
What is deployed today
- Solana Devnet. All four programs (TSN, TCAP, TIN Registrar, Stable TCAP Faucet) are live.
- Privacy-safe credit path. The TCAP credit instruction uses opaque commitments, sequence checks, and nullifiers. There is no per-transfer PDA and no receipt joining funding to credit.
- Debit and exit. Proof-gated and disabled. Live confidential debit and exit return
ProofSystemNotEnableduntil an audited proof verifier and the surrounding invariants are enabled.
Protocol layers
Each layer has its own page detailing every operation and its status.TSN
Settlement coordination, epoch treasury, Mother-rooted DNA permits.
TIN
10-digit payment identity and route discovery.
GPRU
Non-custodial authorization and routing.
TCAP
Confidential balances: credit (live), debit and exit (in development).
Where to go next
How It Works
What the user sees versus what happens under the hood.
Current Architecture
The canonical TIN → GPRU → TSN → TCAP model with the end-to-end sequence
diagram.
FAQ
Answers about privacy boundaries, deployment status, and the debit gate.
Run a Cranker
Operator process that leases work and pays Solana fees.
About TrustLink Labs
TrustLink Labs is the team building TSN. Everything on this site describes the Transfer Settlement Network protocol itself, not any hosted product.GitHub Organization
All open-source repositories from TrustLink Labs.
Follow on X
Protocol announcements and Devnet updates.
Blog
Engineering notes and protocol write-ups.
Protocol Source
TSN, TCAP, TIN Registrar, and Faucet program source.
Docs Source
This documentation site.