How It Works

You pick the token you want to sell, the token you want to receive, the amount, and a minimum output you're willing to accept. You also set a deadline — if the order isn't filled by then, it expires and nothing moves.

You choose a privacy level: whether solvers can see your full order, just the direction, or nothing at all until the batch closes.

Before anything leaves your device, the SDK encrypts the order payload using AES-256-GCM with a one-time session key. That session key itself is encrypted with the gateway's public key using X25519 key exchange. The result is a ciphertext that only the gateway can decrypt — and only after the batch closes.

Your actual amounts never travel in plain text. The gateway stores an encrypted blob.

Your wallet sends a short transaction to the IntentRegistry contract on Starknet. This transaction contains a fingerprint of your order (a Pedersen hash), not the order itself.

This is the binding step. Once this transaction confirms, the order exists on-chain and neither you nor the gateway can change it retroactively. Your funds aren't moved yet — only your intent is recorded.

The coordinator tracks time against a fixed schedule anchored to the genesis timestamp. When the current window closes, it announces the batch on-chain, sealing which orders belong to it. Orders that arrived after the cutoff roll into the next window.

Once the batch is announced, solvers receive the decrypted orders from the gateway. Each solver independently computes a solution — routing through DEXes, filling from inventory, or matching orders against each other — and submits it to the BatchAuction contract.

The contract scores each solution. The score is a weighted mix of: how much output traders receive, how low the solver's fees are, and the solver's historical track record. The best score wins.

The BatchSettlement contract verifies the winning solution against each order's on-chain commitment. If every fill is valid — amounts match, deadlines haven't passed, signatures check out — the token transfers execute atomically in a single transaction.

Either the entire batch settles or none of it does. There's no state where some orders fill and others don't.

The observer watches Starknet for settlement events. When it sees the batch settle, it notifies the gateway, which marks your order as settled. The dashboard updates. You can verify the transaction on Voyager at any time.