Rondo protocol

Direct, escrowed JPYC, IDRX and IDRP orders against USDT on Kaia — with atomic settlement and oracle-aware pricing.

LIVE ON KAIA MAINNET

Trade regional stablecoins and USDT directly.

Makers escrow what they offer. Takers choose a live order. Rondo moves both legs together in one on-chain transaction — without routing the trade through a liquidity pool.

Open Rondo ↗Read the quickstart →

MARKETSJPYC · IDRX · IDRP / USDT

NETWORKKaia · 8217

SETTLEMENTAtomic

TAKINGOpen by default

Start with your goal

Use Rondo

Learn which side of the book to open, what to enter in the ticket, and why a fill may be disabled.

Start trading

Build an integration

Read the book at one block, reproduce the contract’s rounding, and construct safe fill arguments.

Integration guide

The settlement in one view

maker ── sell token into escrow ──▶ Rondo

taker ── token wanted by maker ─────────────────▶ maker
Rondo ── escrowed token, less protocol fee ─────▶ taker
                         one atomic transaction

The maker’s sell-side funds are already in the contract before an order appears. On fill, the taker’s payment goes directly to the maker and the escrowed asset goes to the taker. If any check or transfer fails, the whole transaction reverts.

Fixed price

The maker stores one ratio. It does not move after posting and a fill does not read the oracle.

Oracle-pegged

Every fill reprices from Orakl. The maker chooses the taker’s premium and a floor below which the order pauses.

Compare both order types →

What the protocol guarantees

Every visible order is escrow-backed

The maker transfers the full offered amount into Rondo when the order is created. The contract records what remains and never depends on the maker sending that token later.

Both legs settle together

Payment to the maker and release from escrow happen in one transaction. There is no protocol state in which one leg completed while the other is still waiting for an operator.

A price move cannot exceed a signed bound

The taker signs a maximum payment. A pegged maker stores a minimum acceptable rate. Movement outside either bound causes a revert instead of an unexpectedly bad fill.

Protocol controls do not disable exits

Pause and oracle staleness stop trading, not cancellation or expiry. Read the security model.

Fees are isolated from maker escrow

Protocol fees are accounted for separately from the balance still owed to open orders.

Access model

Action	Who can do it
Post an order	Wallets with MAKER_ROLE
Fill an order	Anyone while takerWhitelistEnabled == false — all deployed instances currently use this mode
Cancel an order	Its maker; unused escrow is returned
Sweep an expired order	Anyone; the refund always goes to the maker

Taking availability is configurable. Integrations should call canTake(account) on the selected market rather than infer access from TAKER_ROLE alone.

Security model

How Rondo protects escrow, settlement and transaction bounds.

Review protections

Verified deployment

Market, lens, oracle and token addresses with the live configuration.

See addresses