Q markBridgeIntake Lane

Quote-first lane

Bridge Intake Lane

Bridge intake is the front desk for controlled asset passage. A visitor chooses the source asset, target output, Bridge receiver, and amount; Bridge prices the route, shows the source receiver or memo, then waits for source-chain finality before crediting output.

Intake desk

The lane is allowed to be visible before it is payable. Visibility lets a user see what Bridge will ask for; payment waits until the quote service returns a live receiver.

1Choose the passage.

Pick the host asset and the Bridge output. Bridge treats passage as a route, not a sale desk.

2Bind both sides.

The quote binds source address or memo, Bridge source receiver, Bridge receiver, asset, amount, expiry, and finality requirements.

3Wait for receiver.

If no payable Bridge source receiver is returned, the correct action is to stop. Do not guess an address.

4Settle by receipt.

Credit follows observed source delivery, Bridge route checks, fee boundaries, and receiver acknowledgement.

Bridge receiver

Add Bridge to Keplr and bind this quote to the public Bridge address that should receive the output. The page never asks for a seed phrase or private key.

Connect Keplr to bind the Bridge receiver address used by the quote.

Open an intake quote

The quote binds the route. Use the returned instruction exactly; do not send from a cached page, copied address, or guessed receiver.

Quote result

The estimate is informational until the live service returns a quote ID and instruction.

Quote IDloading
Route IDloading
Send to0xa4b10c9a78fa97a78b439b9c9244fc8f008a5f64
Sendloading
Source valueawaiting live source price
Bridge fee10 bps source-side
Receive estimateloading

Payable receiver

The Bridge source receiver is visible for audit. Value movement still needs a live quote, source receipt, and finality match.

Payment targetUse the Bridge pool receiver only with a live quote, amount, receiver, expiry, and finalized source transfer match.
Bridge source receiver0xa4b10c9a78fa97a78b439b9c9244fc8f008a5f64
Source token0x45804880de22913dafe09f4980848ece6ecbaf78
Payment amountQuote required
Source bindingRequired for shared-pool quote matching
Route fundingBridge decides this from route policy.
Output ruleBridge OBOL inventory
Relay ruleEthereum mainnet PAXG receipt/finality relay required before payment can settle.
Quote expiryQuote required
FinalityFinalized Ethereum transfer required
Binding / memoBridge source receiver + receiver
Quote stateLive price required before payment.
Match ruleQuote must bind token, expected sender, Bridge pool, amount, receiver, and expiry.
Fee boundaryAsset cost, host execution, proof and memory, service margin, and risk buffer stay separated.
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.

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.