Transfer Settlement Network
Research edition · TrustLink Labs

What Is a Privacy-First Decentralized Settlement Network?

Diagram showing how blockchain settlement, stablecoins, identity, authorization, private routing, confidential state, and settlement coordination form a privacy-first decentralized settlement network.

Stablecoins made digital value easy to move. Public blockchains made ownership changes verifiable. The next infrastructure question is how to make global payments private, identity-aware, and legally settled without giving up cryptographic settlement.

A privacy-first decentralized settlement network is payment infrastructure designed to coordinate identity, authorization, private routing, confidential state, and verifiable settlement — so that digital value can be moved and finally settled like money, without exposing more financial information than each participant, its counterparties, and its regulators actually need.

This is an emerging infrastructure category, not a synonym for a privacy coin, a private blockchain, a confidential wallet, or a zero-knowledge Layer 2. Those systems may provide useful capabilities. A settlement network describes the broader coordination required to turn digital value movement into a complete payment workflow.

Key ideas

  • Blockchains verify ownership changes; they do not, by themselves, make payments private, identity-aware, or legally settled.
  • A settlement network is the coordination layer between programmable value (stablecoins, tokenized deposits) and a usable payment workflow.
  • The institutional shift is real and dated: BlackRock BUIDL (2024), JPMorgan Kinexys (2024), the SIFMA Regulated Settlement Network (2024), BIS Project Agorá (2024–), and the U.S. GENIUS Act (signed 2025).
  • “Privacy-first” means data minimization plus scoped disclosure — not anonymity, and not hiding everything from everyone.
  • TSN is a research design from TrustLink Labs. Every cryptographic claim should trace to a named, tested mechanism — not an assertion.

The settlement problem the industry is trying to solve

For decades, banks moved value by moving messages and settling positions separately. A payment instruction traveled through messaging rails such as SWIFT or an automated clearing house, while the actual transfer of value happened later, through netting, a real-time gross settlement (RTGS) system, or a delivery-versus-payment (DvP) arrangement. Before that, settlement was even more literal: armored cars physically moving cash and securities.

Tokenization changes the proposition. When a tokenized asset is both the message and the value — a dollar-denominated token that is itself tradable, transferable, and redeemable — the distinction between “sending an instruction” and “moving value” collapses. A receiving institution no longer accepts a promise to settle later; it accepts a value it can hold, sell, or convert as it chooses.

This is no longer hypothetical. BlackRock launched BUIDL, a tokenized institutional money-market fund, in March 2024 on Ethereum, and it surpassed $1 billion in assets under management by March 2025. JPMorgan rebranded its Onyx unit as Kinexys in November 2024 and reported more than $3 trillion in cumulative transaction volume on its JPM Coin rails. A SIFMA-coordinated Regulated Settlement Network proof of concept, with Citi, JPMorgan, Mastercard, Visa, and DTCC, demonstrated in December 2024 that a shared ledger could settle tokenized commercial bank money, wholesale central bank money, and U.S. Treasury securities together. The Bank for International Settlements (BIS) Project Agorá is testing a “unified ledger” — tokenized central bank reserves and commercial bank deposits on one programmable, multi-currency platform — with seven central banks and more than forty private institutions.

The legal scaffolding is arriving too. The GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins Act) was signed into law on July 18, 2025 as Public Law 119-27, creating the first U.S. federal regime for payment stablecoins.

What a decentralized settlement network does

A blockchain settlement layer records and verifies state transitions. A decentralized settlement network coordinates the work around those transitions: accepting a payment intent, checking authorization, selecting an eligible route, advancing settlement, recording evidence, and handling retries or recovery.

The network may use several participants with separated responsibilities. A user device can authorize an exact intent. Coordination nodes can verify and queue work. Independent execution operators can submit transactions. Smart contracts can enforce the final state transition. Separating these duties reduces the need for one intermediary to control identity, funds, keys, and execution at the same time.

Blockchain settlement vs. payment settlement finality

One of the most important distinctions in this category is the difference between two meanings of “settlement.”

Blockchain finality is a technical, consensus property. In a proof-of-work chain it is probabilistic — a block is “final enough” once enough work has accumulated on top of it; in BFT or zero-knowledge-verified designs it can be deterministic — a state is accepted and cannot be reversed by protocol rules. In all cases it describes what the ledger guarantees.

Settlement finality in traditional finance is a legal construct. The BIS Committee on Payments and Market Infrastructures (CPMI) defines it as the moment a transfer becomes irrevocable and unconditional — unable to be unwound even in insolvency proceedings. Final settlement in central bank money is treated as the strongest form of settlement because claims on the central bank carry no commercial-bank credit or liquidity risk.

The gap matters. A tokenized deposit can be “settled” on-chain in the consensus sense while its legal finality still depends on the underlying framework and the settlement asset used. This is precisely why the institutional projects pair tokenized commercial bank deposits with wholesale central bank money, and why the Regulated Settlement Network tested settlement across asset classes rather than treating any single token as a complete answer.

Why public blockchain settlement is not private by default

Public ledgers are powerful because anyone can inspect shared state and verify transactions. That same visibility can expose wallet balances, counterparties, payment timing, supplier relationships, payroll patterns, and treasury activity.

Wallet pseudonyms do not provide financial privacy. An address is pseudonymous, not anonymous. Analysts cluster addresses using heuristics such as common-input-ownership (multiple inputs to one transaction are presumed to share an owner) and change-address detection (identifying which output returns change to the sender). Combined with graph analysis and off-chain data such as exchange know-your-customer records, these techniques frequently re-identify the entities behind pseudonyms. Confidential settlement therefore has to protect relationships and state, not merely replace one name with another.

The privacy mechanics toolkit

The privacy techniques available today are well documented. Each one hides something specific — and, just as importantly, fails to hide something else:

  • Zero-knowledge succinct arguments (zk-SNARKs). A prover proves a statement about hidden data without revealing it, producing a short proof verified by a fixed-size check. Most pairing-based SNARKs require a trusted setup (a one-time parameter generation whose randomness must be destroyed).
  • Zero-knowledge scalable transparent arguments (zk-STARKs). Similar in spirit but with no trusted setup and stronger scalability; they trade proof size for transparency.
  • Confidential transactions. Amounts are hidden by replacing them with Pedersen commitments (a binding, hiding commitment to a value) plus range proofs (such as Bulletproofs) that prove an amount is non-negative without revealing it.
  • Stealth addresses. A one-time address generated per payment, so the public ledger does not reveal the recipient’s real address.
  • Ring signatures. A signer proves membership among a set of possible signers, hiding which one authorized — the technique behind Monero’s sender privacy.

A responsible technical description names the implemented verification path and states which values are public, committed, encrypted, locally held, or selectively disclosed. A commitment is not automatically a proof: an encrypted or committed value binds data to an operation, but does not by itself prove that a balance is conserved or that a route is authorized.

Privacy, compliance, and the Tornado Cash lesson

Privacy that hides everything from everyone has collided with regulation. The U.S. Treasury sanctioned the Tornado Cash mixer in 2022; a U.S. appeals court held in November 2024 that the sanctions overstepped OFAC’s authority, and Treasury formally delisted Tornado Cash in March 2025. The episode clarified a durable design principle: privacy from bystanders is valuable; privacy from authorized parties is a liability.

The forward-looking pattern is therefore privacy with auditability. Techniques such as zero-knowledge identity proofs (sometimes called “zkKYC”), selective disclosure, and data minimization let a system reveal a specific fact to an authorized party — “this user passed compliance,” “this transfer is within policy” — without exposing the full transaction graph. The BIS Project Tourbillon explores this balance for central bank digital currencies: payer and recipient privacy combined with transparency to the central bank and auditors.

The architecture of the category

A practical model can be understood as six connected layers:

  1. Blockchain settlement: shared state, consensus, smart-contract execution, and technical finality.
  2. Stablecoin or tokenized money: the digital value being transferred.
  3. Confidential state: protected balances, commitments, notes, and transaction relationships.
  4. Identity: human- or institution-readable payment identifiers bound to controlled destinations.
  5. Authorization: payment intents, policies, approvals, expiry, replay protection, and scoped permissions.
  6. Settlement coordination: routing, liquidity, execution workers, receipts, and recovery.

The layers are complementary. Stablecoins provide value, but not necessarily identity. Privacy tools protect data, but not necessarily payment intent. Blockchain provides finality, but not necessarily a complete receipt or business workflow. The settlement network is the coordination layer that makes these capabilities work together.

Identity and authorization

Most people want to pay a person, business, or institution rather than copy a long wallet address. An identity layer can provide a human-facing payment reference while keeping the underlying cryptographic route controlled by the protocol and the authorized owner.

Identity alone is not enough. A payment should bind the recipient, asset, amount, source, fee policy, expiry, network, and authorization scope into one exact intent. That lets the system distinguish a requested payment from a technically valid but incorrectly redirected transaction.

Private routing and confidential state

Private routing separates the identity a user sees from the public destination or state used during settlement. Confidential state protects balances, ownership transitions, and relationships from observers who are not authorized to inspect them.

These mechanisms must not be described as stronger than the evidence supports. A research design should identify which values are public, committed, encrypted, locally held, or selectively disclosed — and name the proof system, verifier, and state model that make each claim checkable.

Cryptographic proofs and verifiable settlement

Cryptography can prove control, authorization, integrity, and state transitions. Depending on the design, proofs may show that a balance is conserved, a nullifier has not been reused, a route is authorized, or a settlement output follows the accepted intent.

A credible claim does not assert “SNARK” or “STARK” support in the abstract. It names the implemented verification path: the proof system, the verifier, the state model, and the tests that are operating together.

How TSN approaches the architecture

Transfer Settlement Network (TSN) is an emerging privacy-first decentralized settlement network designed as identity-based stablecoin payment infrastructure. This positioning describes the protocol architecture and category ambition of TrustLink Labs — a research design, not an industry-standard capability.

In the TrustLink Labs research model, TIN supplies a human-facing payment identity, GPRU represents protected routing coordination, TCap defines policy-bound confidential asset state, the TSN Node coordinates verified work, Crankers submit authorized transactions, and the TSN Program enforces settlement rules on Solana.

The architecture separates responsibilities deliberately. The authorized device resolves a recipient and constructs an exact payment intent. Coordination services verify bounded fields and prevent replay. Execution operators receive only the capability required for their work. The on-chain program enforces the state transition and produces settlement evidence.

Individual components should still be evaluated against their implementation and test evidence. TSN should not be presented as universally adopted, as regulatory infrastructure, or as a complete replacement for existing payment rails without independent evidence supporting those claims.

Use cases and tradeoffs

Identity-based private settlement could support remittances, merchant payments, payroll, treasury operations, and recurring payment workflows. Each use case still requires appropriate liquidity, compliance policy, availability, recovery, and user-protection controls.

Decentralization also has tradeoffs. More independent operators can reduce dependence on one service, but they introduce coordination, incentive, monitoring, and liveness requirements. Privacy can reduce public observability, so systems need carefully scoped receipts and disclosure paths. Stronger proofs can improve assurance while increasing cost or latency.

Conclusion

A privacy-first decentralized settlement network is the infrastructure between programmable value and usable global payments. It combines stablecoin assets and blockchain finality with identity, authorization, private routing, confidential state, execution coordination, and evidence.

Transfer Settlement Network (TSN) is one research approach to this category: a privacy-first decentralized settlement network designed for identity-based stablecoin payments. The category will become credible through precise definitions, independently verifiable implementations, transparent limitations, and research behind every published claim.

Research and further reading

Institutional tokenization and settlement

Settlement and finality

Privacy and cryptography

TSN protocol