System Overview
Gasyard’s architecture separates concerns into distinct layers, each with specific responsibilities.| Layer | Components |
|---|---|
| Applications | Wallets · dApps · Exchanges · Agents |
| SDK / API | REST API · TypeScript SDK |
| On-Chain | Gateway · GatewayRouter · SolverPool · SolverRouter · Settlement · RefundPool |
| Off-Chain | Coordination Engine · Solver Network · Rebalancing · Monitoring · Fallback Routing |
| Networks | EVM · Movement (Move) · Solana |
Transaction Flow
1
User Initiates
User sends any supported token to the GatewayRouter (or Gateway directly for bridge tokens)
2
Source Swap
GatewayRouter swaps the input token into the bridge asset via whitelisted DEX aggregators
3
Intent Created
Gateway validates the intent, applies fees, and emits
OrderCreated4
Solver Competes
Solvers detect the event and race to fulfill the intent
5
Destination Execution
Winning solver pays from their SolverPool on the destination chain
6
Destination Swap
SolverRouter optionally swaps the payout into the user’s requested token
7
User Receives
Final token delivered to user’s wallet
8
Settlement
Solver receives USDC credit on Base after watcher verification
On-Chain Components
Gateway
Core intent contract. Validates parameters, emits events, tracks finality. Non-upgradeable for trust.
Routers
GatewayRouter (source swaps) and SolverRouter (destination swaps) enable any-to-any token transfers.
SolverPool
Isolated liquidity vaults per solver. Each solver’s funds are separate for safety.
Settlement
Watcher validation and USDC credit issuance on Base.
Component Interaction
Off-Chain Components
| Component | Purpose |
|---|---|
| Coordination Engine | Cross-chain event monitoring, intent classification, task allocation |
| Solver Network | Decentralized executors competing to fulfill intents |
| Rebalancing System | Automated liquidity management across chains |
| Monitoring | System health, fraud detection, reorg handling |
| Fallback Routing | External liquidity integration for edge cases |
Contract Deployment Pattern
Gasyard uses deterministic deployment across EVM chains where possible:| Contract | Pattern |
|---|---|
| Gateway | Same address on most EVM chains |
| SolverPool | Same address on most EVM chains |
| Routers | Chain-specific deployment |
Security Architecture
| Layer | Security Features |
|---|---|
| Trust Boundary | Non-upgradeable Gateway · Role-based access control · Token whitelisting · Replay protection |
| Execution Layer | Isolated solver pools · Verified execution via watchers · Automatic refund triggers · Rate-limited rebalancing |
Next: Learn about Cross-Chain Execution — how swaps work end-to-end.