Settled one by one
Each of the three obligations settles on its own, so the full gross value moves. Settling each one on its own can move substantially more gross value than the final net positions require.
Institutional clearing and settlement infrastructure on Stellar, demonstrated on Testnet. Production deployment not yet approved.Learn more
Tobin is an open clearing protocol that helps financial institutions net payment obligations and settle the resulting balances on Stellar.
The problem
When institutions owe each other in several directions, settling each obligation on its own can move far more gross value than the final net positions need.
SEP-31 gives two anchors a common way to carry a payment, but it does not define an open, network-level way to aggregate obligations from many institutions and settle only the net.
Each of the three obligations settles on its own, so the full gross value moves. Settling each one on its own can move substantially more gross value than the final net positions require.
Cleared first, the net positions are A pays $30, B receives $20, C receives $10, so only $30 is settled.
Net positions always sum to zero; a session that breaks that rule must not finalize.
Illustrative arithmetic, not data.
Whether real Stellar payment flows are connected enough for clearing to reduce gross settlement has not been measured yet.
Proposed design
01
Institutions and counterparties

Institutions submit authenticated payment obligations, and counterparties accept them.
Obligations in, net positions out. Because the calculation is deterministic, the same set of obligations always produces the same result.
Built and planned
The institutional workflow is built and hosted: organizations and roles, obligations, deterministic netting, calculation approval, settlement batch preparation and review, and a Soroban clearing contract deployed and exercised on Stellar Testnet. The code is open source and tested on every change. The evidence so far comes from the implementing team; an independent security review is planned before any production use, and production deployment has not been approved.
7 implemented · 1 differs from the broader design · 6 planned
Organizations with admin, member and reviewer roles and invitation-based membership, enforced on the server and covered by tenant-isolation tests.
TECHNICAL.md
Read the technical overview (opens in a new tab)Clearing sessions and obligations in the institutional application and, on chain, in the clearing contract.
contracts/README.md
Read the contracts (opens in a new tab)Net positions computed by a deterministic TypeScript engine and saved as immutable calculation snapshots; any change to the inputs makes a snapshot stale.
packages/mvp1-sdk/README.md
Read the engine notes (opens in a new tab)A reviewer approves the exact calculation. An administrator prepares an immutable batch of settlement instructions, and a reviewer approves it; the person who prepared a batch cannot approve it. Prepared batches move no funds.
TECHNICAL.md
Read the technical overview (opens in a new tab)Every admitted participant approves a settlement proposal. The broader design needs only the participants with non-zero net positions to sign.
docs/reference/MVP-1-ABI-AND-AUTHORIZATION-REFERENCE.md
Read the ABI reference (opens in a new tab)A Soroban contract validates a settlement plan and moves the net amounts atomically. Deployed on Stellar Testnet and exercised from session creation to settlement in eight transactions, with multisig co-signing and a governed test token (a fixed one-unit scenario run with owner tools).
docs/scf/implementation/testnet-engineering-evidence.md
Read the Testnet evidence (opens in a new tab)A web application and backend API deployed on Vercel and Railway, with role-based access, request-origin checks, rate limits and a public Discover API. Single-region and Testnet only.
TECHNICAL.md
Read the technical overview (opens in a new tab)More than 800 automated tests across the contracts, backend and web application run on every pull request, with compiled-contract tests and a browser journey on the main branch. Results are public.
.github/workflows
Read the workflow runs (opens in a new tab)The hosted application prepares and approves settlement batches. Connecting an approved batch to Stellar signing, submission and independent reconciliation is the next planned engineering work.
Planned before any production use. The contracts, the signer and the application have not yet been independently reviewed.
Designed to limit the exposure that can enter a session. Part of the broader protocol design.
Designed so the chain holds commitments, not an obligation book. Part of the broader protocol design.
Part of the broader protocol design.
Planned. No packages are published today; the MVP-1 netting engine exists as source in the repository.
Built for Stellar
Stellar provides the settlement network.
Soroban supports Tobin's on-chain protocol logic.
Tobin adds a clearing layer above existing payment infrastructure.
SEP-31 stays in place. Tobin is designed to complement it, not replace it.
Simplified architecture for illustration.
What Tobin is
The code, documentation and specification the project owns or controls are licensed under Apache-2.0, and the repository is public. The Tobin name and logo are not covered by that licence.

What it is
The code, documentation and specification are licensed under Apache-2.0, and the repository is public. The Tobin name and logo are not licensed under it.
Status
A working institutional clearing application, its contracts and an open-source SDK.
Organizations and roles, obligations, deterministic netting, calculation approval and settlement batch preparation, deployed as a hosted web application and API, with a Soroban clearing contract and the netting engine in the repository under Apache-2.0.
The settlement path runs on Stellar.
Automated tests in the Soroban test host, and an owner-run Stellar Testnet execution of eight transactions with multisig co-signing, read back from the network and compared with the approved plan. The verification record is public in the repository. The evidence so far comes from the implementing team.
Signing, submission and reconciliation from the hosted application.
Connecting an approved settlement batch to Stellar signing and independent reconciliation, followed by the broader protocol design: deadlines, abort, default and recovery handling, collateral, Merkle commitments, and a public SDK and CLI.
How much gross settlement multilateral clearing removes on real Stellar payment flows.
The first planned step uses historical Stellar ledger data and ends in an explicit go, modify or stop decision. The built milestones tested the clearing mechanics; this analysis tests the economics.
An independent security review is planned before any production use.
The protocol specification (M0) is a published draft. The code, tests and reviews so far are the team's own; no independent audit has been performed and production deployment has not been approved.
Read the source
