Q markBridgeIntake Lane

Quote-first lane

Bridge Intake Lane

Choose the passage from either side of the same matrix: start with the asset you hold or start with the output you want. A live quote must open the intake instruction and accept target capacity before any funds move.

Get a Bridge intake quote

Complete these steps in order. The final step opens only when Bridge returns a live payment instruction.

1
Choose the Bridge receiver

This public Bridge address receives the output. No seed phrase or private key is requested.

Connect Keplr to bind the Bridge receiver address used by the quote.
2
Choose what leaves and what arrives

Start from either side; both controls resolve to the same route matrix.

Source-first: choose what you hold, then its output.

3
Open the live quote

Complete the required fields above.

4
Send exactly what Bridge quotes

Amount, network, address, memo, receiver, and expiry stay together here.

No payment instruction yet. Complete steps 1–3; do not send from a preview.
Send exactlyLive quote requiredSource chain returned by the quote
To this addressNo payable address issued
With this memoReturned only by the live quote
Output receiverConnect Keplr first
You receiveLive quote required
Quote expiresLive quote required
Quote IDNo quote issued
Technical route details

Intake and output readiness, route matching, finality, fees, and raw quote data.

Route IDChoose a pair
IntakeWaiting for pair selection
OutputWaiting for pair selection
Bridge feeReturned by the quote
Payment targetUse the Bridge pool receiver only with a live quote.
Source tokenReturned by live quote
Payment amountQuote required
Source bindingReturned by live quote
Route fundingBridge decides this from route policy.
Output ruleLive quote checks target price, capacity, and delivery rail
Relay ruleSelected intake route determines source receipt and finality requirements.
FinalityReturned by the selected route
Quote stateLive quote required before payment.
Match ruleQuote must bind the payment tuple.
Fee boundaryReturned by the selected route and live quote.
Developer quote JSON 
{}

Intake queue

Each payment attempt should sit in one clear state. The page should make the wait state obvious before a user moves value.

PreviewRoute visible, not payable

Bridge can show the lane shape before it has a payable receiver.

QuotedReceiver and binding returned

The asset, source binding, amount, expiry, Bridge source receiver, and Bridge receiver are bound to a quote ID.

ObservedHost payment found

Bridge sees the source-chain transfer and waits for finality plus route checks.

ResolvedCredited, refused, or quarantined

The lane closes with an output receipt, refusal receipt, refund posture, or quarantine label.

Where the intake resolves

The lane does not credit output from a form submit. The source-chain payment has to match the quote and pass route law first.

1. QuoteThe lane returns route id, amount, Bridge source receiver, Bridge receiver, source fee, expiry, and next step. 2. Source paymentOnly the quoted denom or token, amount, source receiver, binding, and Bridge receiver can match the quote. No receiver means no payment. 3. Finality proofBridge waits for host-chain delivery, finality, and transfer matching before crediting route output. 4. Bridge outputOutput comes from Bridge-side inventory or policy after quote, fee, receiver, and admission checks pass. 5. Receiver boundaryDelivery is not destination admission. The receiving surface still defines local meaning.

Intake rules

  • Use a fresh quote before sending any source-chain payment.
  • Do not send if the returned instruction says the receiver is not published.
  • For ERC20 lanes, enter the Ethereum address that will send the token so Bridge can disambiguate shared-pool quotes.
  • For memo-capable IBC lanes, use the exact memo returned by the live quote.
  • The source price is fetched by Bridge; a visitor-entered market price is not payment truth.
  • Ethereum has no memo, so Bridge binds by token, expected sender, pool receiver, amount, expiry, and Bridge receiver.

What this page is not

  • Not an OBOL sale desk.
  • Not a wallet, custody service, airdrop, or reward claim.
  • Not destination admission, redemption, wrapper mint, sell desk, or public exit.
  • Not private route procedure, signer policy, provider topology, or operator timing.

Refusal rules

A Bridge intake lane that cannot prove the route should stop cleanly.

Wrong asset

Unsupported source denoms are refused or quarantined instead of silently reinterpreted.

Expired quote

Stale price, stale route evidence, or expired instruction cannot become payment truth.

Missing receiver

A payable receiver must exist before Bridge can accept the route.

Missing finality

Ethereum mainnet delivery must be final and matched before Bridge can credit output.

Bad output

If the requested target output cannot be sourced under policy, the lane waits, refuses, or quarantines.

Fee shock

Host gas, execution rent, proof costs, and buffers stay separate from Bridge margin.

No admission by delivery

Even delivered output still needs the receiver boundary to define local meaning.