Policy runs in enclaves
Policy runs inside hardware enclaves on independent machines. Each proves which exact code it runs, and the build is reproducible from source.
For institutions · testnet
Contract logic for settlement on chains without a VM, starting with Bitcoin and the XRP Ledger. Assets stay in native accounts, and no single party, including us, can move them.
// 01 The problem
Holding or lending against BTC or XRP today means wrapping the coins onto another chain, which needs a bridge, or trusting one signing service: one point of failure. In October 2026, by Binance’s own first account, one compromised laptop reached the service that signs its hot-wallet withdrawals, and about $6B left. TRUST removes that single point without moving the assets.
// 02 How it works
Policy runs inside hardware enclaves on independent machines. Each proves which exact code it runs, and the build is reproducible from source.
Assets stay in the chain’s own accounts, signed M-of-N: a native multisig on the XRP Ledger, Taproot on Bitcoin, and the same on any chain with a standard signature scheme. No wrapped token, no master key.
Every withdrawal, liquidation or payout is checked against the customer’s policy by each machine before it signs: destinations, limits, collateral ratios.
Code changes need the operator group. A new build runs only after the machines admit it in a ceremony. Developers, us included, can’t push one alone.
// 03 Trust, declared
What you trust
What you don’t
“Trustless” is the wrong word. The trust is specific and small, and it’s declared above.
A deployment counts control domains, not companies: separate machines, separate admins, separate clouds or sites. Capturing one admin or one cloud must not reach a quorum; a deployment passes that test before it is called TRUST.
The customer chooses who runs them: its own control domains, or independent third-party operators. We never run nodes for anyone and never hold customer keys.
// 04 Where it fits
// 05 Proof and status
Three physically separate machines, run by us on testnet. Since May 2026 the running group has moved to new code through its update ceremony 10+ times, keeping its state.
With liquidations, running on the engine. It settled on XRP Ledger mainnet in a live demo in April 2026.
Published automatically through the engine from public sources, each with its own native escrow address.
Internal review rounds, including independent in-house security review. A third-party audit is planned before any mainnet funds.
// 06 Working with us
Software, not a service. You choose who runs it; we never run nodes and never hold customer keys. Commercial terms on request.
The team covers enclave and protocol security, smart-contract security, and derivatives markets and risk. Self-funded, including by our market-making business.
Open to partnerships with lenders, custodians and stablecoin operators, and to building partners’ settlement logic on the engine. Technical overview →
Your assets stay where they are. No single party can move them.