TECHNICAL ARCHITECTURE

System overview

YardRoute is an aggregation layer. It does not deploy bridge contracts. It does not custody user funds.

High-level flow:

User/App → YardRoute UI or API → Route engine → Bridge protocols → Destination chain

Key components:

• Frontend UI (Phase 1).

• REST API (Phase 2).

• Route selection engine.

• Bridge integration layer.

• Transaction monitoring.

Bridge aggregation strategy

Goals:

• Best pricing.

• Redundancy.

• Broad chain coverage.

Bridge integrations mentioned:

• Relay.

• Symbiosis.

• StarkGate.

• TON Bridge.

• Curve Finance.

• Chain-native bridges as needed.

YardRoute does not:

• Hold liquidity.

• Custody funds.

• Handle private keys.

Route selection engine

Selection criteria:

1. Total cost (gas + bridge fee + slippage).

2. Estimated time.

3. Liquidity depth.

4. Reliability and historical success rate.

5. Source/destination support.

Example decision:

Goal: 100 USDC from Base → Starknet

Option A: Relay (Base→Ethereum) + StarkGate (Ethereum→Starknet)
- Cost: $1.20
- Time: ~3 min
- Reliability: 99.5%

Option B: Orbiter (Base→Starknet)
- Cost: $0.85
- Time: ~2 min
- Reliability: 98.7%

Selected: Option B