Moving money was the easy part

When we wrote about why we built ReineiraOS, we made one claim: blockchains gave money a transport layer, but transport alone does not settle the outcome of a deal.

This is the other half of that argument. Because the missing layer is barely about moving money at all.

Moving money was the easy part.

The easy part#

A rail's whole job is to answer one question: did the money move? Bitcoin answered it. Ethereum answered it. Every stablecoin and faster-payments rail since has answered it cheaper, quicker, in more places. That race is real, and it is nearly won.

But a settled transfer is not a settled deal. The money moving was never the part anyone lost sleep over. What keeps a supplier awake is whether the buyer pays. What a buyer hesitates over is whether the goods arrive. Commerce is the management of that gap — the distance between paying and being sure — and no amount of throughput closes it.

Commerce has always run on recourse#

For as long as there has been trade, the answer to that gap has been recourse: a credible promise that if the deal breaks, you are made whole. The letter of credit, the escrow agent, the surety bond, the trade-credit insurer, the card chargeback — each is the same instrument in a different century. Act first, and if it goes wrong, someone makes you whole.

Notice what they share. Every one is a separate institution, bolted on beside the payment. You move money on one rail and buy your recourse at another counter — a bank, a broker, an insurer — slowly, on their terms, with your numbers handed over to whoever underwrites it. The transfer got faster every decade. The recourse stayed manual, intermediated, and exposed.

Bonded Settlement#

Bonded Settlement is the category we are building: settlement that carries its own recourse. An actor posts a bond before it acts. A verified failure pays the harmed party back, automatically and in private. In buyer deployments, the principal mandates and funds that bond.

The rail does more than confirm movement. It holds funds in confidence, releases them on a verified event, and defines what follows failure.

Three properties, one rail#

• Live Escrow. Funds held in confidence until the outcome is known, with no party holding them in the middle.
• Live Gate. Release on a verified event, not a human sign-off — a pluggable verifier that settles the moment the proof checks out.
• Testnet Recourse. Coverage that pays out when a counterparty fails. The contract flow is live with test assets; real risk pricing and a capitalized pool are next.

And all of it confidential by default, FHE-encrypted via Fhenix CoFHE — because commerce is private. Your prices, your exposures, and your counterparties are not for the whole market to read. The Escrow and the Gate are Arbitrum Sepolia today; the recourse layer is the round's work, disclosed as such.

Recourse has to be private to be real#

Here is what the bolted-on model can never fix. To price recourse, the underwriter has to see your book — who your counterparties are, how exposed you are, what you pay. That is your most sensitive commercial information, handed to a third party as the cost of being covered.

Built into the rail, those inputs can stay encrypted. The design goal is to price recourse over FHE-encrypted data without publishing the underlying book. Real risk pricing is not live yet. For commerce, where margins and counterparties are sensitive, privacy is a requirement rather than an extra.

You can already see the shape#

One worked example of Bonded Settlement is Prova, a pre-launch trade-credit application built around these primitives. It demonstrates the intended flow on testnet; production underwriting and capital are not live.

A category, not a company#

Bonded Settlement is a category, which means it cannot belong to one company. The Reineira Settlement Standard (RSS) is the open, forkable specification of these primitives, so any team can build on a common settlement model instead of defining every contract and interface from scratch.

If you are building commerce#

Ask it this way: if your rail could stand behind the deal — hold the funds, release on proof, and make the wronged side whole when it breaks, all in private — what would you stop bolting on by hand? Three places to go next:

• Whitepaper (PDF) — the formal specification of the primitives and the standard.
• Quickstart, to build your first testnet flow.
• Telegram — tell us the deal you would want the rail to stand behind. We read every message.