TRUSTSettlement-execution layer
Platform overview · technical →

A technology — not an app

TRUST

TRusted  ·  Unchained  ·  SettlemenT

The trust technology — and everything you can build on it.

TRUST is the engine: the work a smart contract would do, run inside verified hardware, signed by a group that no single party controls, settling on each chain’s own rails. The products are applications of that engine — prediction markets, perpetual futures, and a cross-chain bridge run on it today, and the next idea plugs into the same engine tomorrow. Each application inherits the security for free.

// The technology

One engine. The applications sit on top.

The hard, dangerous work lives in the engine, not in each app. Build it once; every application above inherits the same guarantees — and more applications can be added at any time.

PhoenixPrediction markets
XPerpPerpetual futures
TRUST BridgeShielded cross-chain · privacy in dev
all run on ↓

The TRUST engine · hardware-attested

Smart-contract-equivalent execution, settling on each chain’s native rails

Matching, settlement math and vaults run inside secure, independently-verified hardware; the group signs with a shared key no one holds alone; value settles on the chain’s native multisig — no wrapped tokens, no single custodian — and no code update ships unless the whole group agrees.

BitcoinXRPLnext chainsno bridges for settlementno single key

// What the engine guarantees

No single key or person

Control is split across independent machines. A group must act together; a hacked node or a runaway insider holds one useless piece.

Verified hardware

The software runs sealed in secure hardware. Every machine proves it runs the exact, unaltered code — and no one, not even the operator, sees the keys.

Proof, not promises

Money moves only when the chain itself proves what happened, and the amount out is tied to the amount that really went in.

Updates by group ceremony

Every change — even a tiny test — goes live only after the group of independent machines checks and agrees. No master key, no quiet push.

// Running today — three flagships

Same engine, three products running today

Phoenix

Prediction markets

Native-coin prediction markets, settled on each chain’s own primitives.

  • 170,000+ auto-published markets, mirrored from public sources, across XRPL and Bitcoin testnets
  • Settled in the native coin — no wrapped tokens, no IOUs
  • Markets resolved inside the hardware; a 7-source oracle
  • Snapshot commitments anchored on-chain — a public audit trail
ph18.io →

Status · testnet MVP

XPerp

Perpetual futures

Perp futures with native collateral and fast on-chain settlement.

  • Native XRP collateral, settled on-chain in 3–5s — no bridges, no L2 delays
  • Margin engine inside the hardware — operators can’t see positions or front-run
  • Every payout is group-signed — no single party can move funds
  • Demoed on XRPL Mainnet at Hack the Block Paris; 20+ internal adversarial security-review rounds
xperp.fi →

Status · testnet, public relaunch next

TRUST Bridge

Shielded cross-chain

A shielded Bitcoin ↔ Zcash bridge — cross-chain and private at once.

  • Every payout released only when the source chain proves the funds really locked
  • Group-signed, keys sealed in hardware — no single custodian, no wrapped BTC
  • The amount out is bound to the amount proven locked — nothing minted unbacked
  • Privacy via Zcash’s shielded pool (in development)
Bridge overview →

Status · testnet · privacy in development

// Why it’s a platform

The technology is the product. Applications are interchangeable.

Point the engine at a new idea and it inherits everything — the hardware attestation, the group-held key, the native-chain settlement, the update ceremony. Nobody re-earns trust per app. Three products already run on the same engine; here’s a sample of what plugs in next.

Confidant → shielded XRPL

Confidant is our compliant shielded pool for XRPL — private transfers with selective disclosure (hackathon build, testnet). Run its pool inside the enclave for shielded XRPL on attested hardware.

Options DEX

Same group-signed settlement on BTC / XRPL, different payoff math.

Lending vaults

Native-coin collateral and lending, margined inside the enclave.

Attested oracles

A hardware-attested oracle network — signed data anyone can verify.

// What makes it different

Decentralized from day one — not “later.”

Most projects run on “trust us now, we’ll decentralize later.” That “later” is where keys get stolen and teams disappear. TRUST has no “later”: no master key, and every update — even a test — needs the group of physical machines to agree before it runs. So “the signers ran off” has nothing to grab — no single party, not an attacker, not an operator, not the founders, can move the funds or change the code.

What you trust

  • + The chip maker — the same trust as your own CPU
  • + A reproducible build anyone can independently check
  • + The operator group — agrees on every update and payout

What you don’t

  • − The dev team — can’t ship code the group didn’t sign
  • − Any single operator — no one moves funds alone
  • − Bridges, wrapped tokens, off-chain custody

All applications run on testnet today; mainnet and full privacy are in development. “Trustless” is the wrong word — the trust is specific and small, declared above. The hard security lives in the engine; every application inherits it.

One engine. Any application. No one who can betray it.