Cross-chain routes
How a DAO-approved sale would settle across chains through NEAR Intents. These are live 1Click DRY quotes on mainnet liquidity: real prices and fees, but nothing is executed.
Where this fits
| Step | What happens | Status |
|---|---|---|
| 1. DAO-approved mandate | Sputnik DAO vote creates the mandate on our contract; only the DAO can create or cancel it. | REAL (testnet) real on public testnet (see Votes, Report) |
| 2. Non-custodial agent | The DAO funds a vault by vote; the agent cannot exceed the on-chain budget/window; a DAO cancel switches it off. | REAL (testnet) real on public testnet |
| 3. Price floor on every chunk | min_amount_out derived from the mandate floor is checked before each swap (Ref Finance on testnet). | REAL (testnet) real swaps on testnet; the same floor check runs in live-dryrun against mainnet quotes |
| 4. Intents routes | Sell wNEAR for USDC on NEAR, then route each payout to the contributor's chain through NEAR Intents. | QUOTED (mainnet, dry) live 1Click dry quotes below (nothing executed) |
| 5. Cross-chain settlement | OutLayer-custody / confidential swap and cross-chain withdraws execute the routes with real funds. | NOT PROVEN implemented and request-shape tested; NOT proven with real money |
Route quotes
Live executor path without funds (EXEC_MODE=live-dryrun)
The worker can run the live decision path against mainnet liquidity with every money-moving call blocked: it plans the next chunk, takes a real 1Click dry quote, applies the mandate price floor, and logs the exact OutLayer request (POST /wallet/v1/confidential/swap with body and X-Idempotency-Key) that it would send. It builds that request with the same client code the live executor uses, but its fetch is a recorder, so nothing leaves the process and nothing is written on chain. Unit tests assert that no money-moving endpoint is ever called. See worker/adapters/live-dryrun.ts and tests/routes.test.ts.