# 🔄🚀 One-Click Cross-Chain Transactions

Real-World Value 💡

* Simplicity: Single flow for multi-hop, cross-chain transfers.
* Efficiency: Optimizes cost/latency; fails over to alternate paths automatically.
* Safety: Atomic settlement prevents partial execution; clear UX for fees/slippage.\ <br>

Problems Solved 🛠️

* Eliminates manual bridge/DEX choice and fee/slippage guesswork.
* Reduces failed routes and mis-sends; lowers total execution cost.
* Harmonizes confirmations, receipts, and status tracking across chains.\ <br>

Technical Architecture 🧱

* Liquidity network modeled as a weighted graph (edges = bridges/AMMs/routes with costs for gas, latency, depth, risk).
* Dijkstra-class shortest-path with real-time weights; HTLC/atomic-swap settlement and path failover.
* Microservices: price/quoter, pathfinder, signer, settlement, reconciliation; MEV-aware execution where supported.\ <br>

Mathematical Modelling 📐

* Composite cost function:\
  C(path)=α⋅gas+β⋅latency+γ⋅priceImpact+δ⋅risk+ε⋅reliabilityPenaltyC(path) = \alpha \cdot gas + \beta \cdot latency + \gamma \cdot priceImpact + \delta \cdot risk + \varepsilon \cdot reliabilityPenaltyC(path)=α⋅gas+β⋅latency+γ⋅priceImpact+δ⋅risk+ε⋅reliabilityPenalty
* Constraints: minimum liquidity depth, maximum slippage, time-to-finality bounds.
* Dynamic re-pricing from orderbooks, bridge quotes, and gas oracles.<br>

Explanations 🗒️

* Atomicity ensures either all hops settle or none do.
* Re-pricing avoids stale quotes; failover selects the next best route.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.1fuel.io/readme-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.