​
Intent-Based Execution

Traditional bridges operate on a transaction model—users initiate specific transactions that lock, verify, and unlock assets across chains. This creates complexity and failure points. Gasyard uses an intent model—users declare their desired outcome, and the protocol figures out how to achieve it.
Intent vs Transaction Model

​
Core Principles

Instant Execution

Solvers use their own liquidity to fulfill intents immediately—no waiting for block confirmations or verification.

Predictable Output

Every intent includes minimum output guarantees and expiry protection. Users know exactly what they’ll receive.

Guaranteed Refunds

If an intent can’t be fulfilled before expiry, the RefundPool automatically returns funds. No stuck assets, ever.

Isolated Liquidity

Each solver operates their own liquidity pool. One solver’s failure cannot affect others or the system.

​
How It Works

​
The Intent Lifecycle

1

Intent Submission

User submits an intent to the Gateway contract specifying destination chain, asset, minimum output, and expiry.
2

Gateway Validation

Gateway validates parameters, applies fees, and emits an OrderCreated event—the canonical record of the intent.
3

Solver Competition

Independent solvers monitor events and compete to fulfill intents. The fastest solver wins.
4

Instant Settlement

The winning solver pays the user from their own liquidity on the destination chain.
5

Verification

Watcher nodes verify the solver’s execution matched the intent requirements.
6

Credit Issuance

After verification, the solver receives a USDC settlement credit on Base.

​
Key Guarantees

GuaranteeHow It’s Enforced
Solvers never touch user fundsAssets go directly to Gateway, not solver wallets
No double executionOrder IDs are unique and marked finalized on-chain
Minimum output protectionOn-chain enforcement—solver must meet threshold
Automatic refundsRefundPool triggers if no valid execution before expiry
Solver isolationEach solver has independent liquidity pools

​
What’s New in V3.5

Swap any input token into the bridge asset before creating the intent.
User pays ETH on Ethereum
    ↓
Router swaps ETH → USDC
    ↓
Gateway creates intent
    ↓
Solver executes on destination

​
Supported Ecosystems

EVM Chains

Ethereum, Base, Arbitrum, Polygon, Optimism, BNB, Sei

Move VMs

Movement ecosystem with native Move contracts

Solana

Native Solana programs for cross-ecosystem routing
Next: Learn about the Architecture — how all the components fit together.