Architecture
Khalani Arcadia organizes the end-to-end intent lifecycle into five layers that clearly separate concerns and trust boundaries. The diagram below shows the direction of each message as it travels from the user interface down to off-chain execution and back.
1. UI & Application Layer
Front-ends, wallets, aggregators, and AI agents live here. They translate human goals into machine-readable intents and after fulfillment, surface outcome back to users.
2. Pub/Sub & Events Layer
A stateless off-chain relay mesh converts every intent, lock, proof, and receipt into a signed event and broadcasts it over multiple transports - gossip networks, web sockets, cross-chain relays, or through centralized gateways using a simple publish/subscribe scheme.
Anyone can spin up new gateways or transports without permisison.
Events are time-stamped and signed, with built-in replay protection.
3. Trust & Proof Layer (Pluggable)
This layer certifies cross-domain claims. Developers choose the mechanism: optimistic challenges, ZK proofs, light clients, multi-sig attestations, appropriate to their risk and latency budget. Once a proof is accepted, it is emitted as a signed event: downstream, the Intents Layer consumes the event to authorise the corresponding intent state transition; upstream, the UI layer ingests the same event as a receipt and displays a verified fulfilment to the user.
4. Intent Layer
An extensible suite of on-chain contracts that track assets, commitments, and settlement. All settlements clear through this layer, ensuring atomicity even when execution spans multiple chains or trust vendors.
MToken: A multi-chain, intent-aware accounting token that escrows assets and records cross-chain liabilities.
IntentBook: Order-book-style registry of intents that matches commitments with solver submissions and escrows settlement funds.
Receipts & Proofs: Immutable records of intent publication and fulfillment.
5. Execution & Solving Layer
Off-chain solver networks handle routing, liquidity sourcing, and bid construction. They watch the Pub/Sub stream, evaluate whether they can satisfy an intent under its settlement conditions, and submit transactions.
Specialists (routing, liquidity, proof) may form ad-hoc coalitions to win complex intents.
Enclaves or TEEs can be used for private order-flow auctions when needed.
End to End Flow
A UI signs and publishes an intent.
The event layer relay mesh propagates the event to all listening solvers and proof vendors.
If the intent spans domains, a proof vendor first attests that the publication is confirmed.
The Intents Layer escrows funds and logs the commitment.
A solver executes the task and emits evidence on settlement through the relay mesh.
The Trust Layer verifies the solver’s proof; the Intents Layer releases or re-locks funds accordingly.
A settlement event is broadcast back to every subscriber.
The UI receives the receipt and confirms fulfillment to the user.
This modular architecture allows Arcadia to evolve one layer at a time: new transports, proof mechanisms, or solver strategies can plug in without protocol-wide migrations, preserving sovereignty for chains and composability for builders while delivering a cohesive, intent-driven user experience.
Last updated