Sealed batch execution.

Sealed batch execution not configured. TRADING_ADAPTER is not set.

How orders are sealed

Encrypted to the batch operator's threshold key, or committed to by hash and revealed after the batch closes. Which one changes who can read an order before settlement.

Who can decrypt or reveal

The operator set, a threshold of key holders, or only the trader at reveal time. A commit-reveal design exposes the order in plain text at reveal, before settlement completes.

Batch timing

A fixed cadence or a fill-triggered close. Orders received after the close roll to the next batch.

Cancellation rules

Whether a sealed order can be withdrawn before the close, and whether cancellation itself is visible.

Expiry

How many batches an unfilled order survives before funds are released.

Partial fill rules

Pro-rata, price-time or all-or-nothing when demand exceeds supply at the clearing price.

Pricing rule

A uniform clearing price per pair, bounded by a reference feed, or a published formula. The reference feed is never the executable price.

Fee calculation

Protocol fee, solver or operator fee, and gas, each expressed in a named asset.

Settlement contracts

The chain and verified contract addresses that custody sealed orders and execute settlement.

Refund or recovery

What happens to funds when a batch fails, an order expires or the operator is unavailable.

Order confidentiality limits

Sizes and pairs may be inferable from settlement, operators may see plaintext, and timing correlates orders with fills.

These are the questions, described generically. Answers come from a configured protocol adapter, not from this page.