Garden Finance on RAVN: HTLC Rails for Native BTC

Quick answer

Garden Finance is a native-Bitcoin venue in RAVN's router. On pairs with real BTC on exactly one side, RAVN can query Garden for an HTLC atomic swap against a solver's pre-committed price. If Garden wins the race on best execution, you settle through Garden's rails. RAVN still does not custody funds and does not run Garden's contracts.

Where Garden sits in the stack

RAVN is an execution layer, not a single-bridge product. For native BTC cross-chain routes, eligible venues are raced together. In the shipping router that set includes:

• GardenHTLC atomic swaps, native BTC either direction against EVM or Solana assets Garden supports.
• RelayRelayer network with broader pair coverage and different latency tradeoffs on the same corridors.
• NEARNEAR Intents for any-to-any deposit flows when the pair is available.

Garden is not a duplicate of Relay. Adapter notes treat them as complements: Garden is firm-priced and often around the ~20s class on pairs it serves; Relay can be faster or slower depending on the leg, and it covers pairs Garden refuses.

HTLC atomic swaps in plain language

Garden settles with hashed timelock contracts (HTLCs). In practice for users:

• A solver commits to a price for the swap.
• Funds lock under cryptographic conditions so both sides complete or the swap does not settle as a one-sided gift.
• You end with the destination asset from that settlement path, not a RAVN-minted receipt token.

That design is why Garden shows up as a firm quote style in RAVN: the quoted output is the number the path is built to deliver, or the path fails rather than silently filling worse. RAVN records that as zero slippage for the Garden quote when Garden reports slippage 0.

What pairs Garden is for on RAVN

In the RAVN adapter, Garden only races when native BTC is on exactly one side of the trade. BTC to BTC is not a swap. Non-BTC-only pairs that Garden might support elsewhere are not claimed by RAVN's Garden lane when other venues own them better.

Supported chain surface in the adapter includes Bitcoin, Solana, and EVM chains Garden maps (for example Ethereum, Base, Arbitrum, BNB, HyperEVM, Monad, Robinhood Chain), subject to Garden asset lists, min/max amounts, and live solver liquidity.

Two normal "no" answers from Garden (not outages):

• Pair not served (blacklist or no order pair), e.g. some Base USDC to BTC style corridors Garden declines.
• Insufficient liquidity right now, even if the pair is allowed.

In both cases RAVN drops Garden from that race and keeps other venues. That is how coverage stays up without pretending Garden does everything.

What you do when Garden wins

Execution type depends on which side is Bitcoin and which chain you are leaving:

• DEPDEPOSIT when Bitcoin is the source: send native BTC to the address Garden returns for the order.
• TXTRANSACTION when the source lock is an on-chain initiate (EVM initiate tx, or Solana versioned transaction into Garden's HTLC).
• SIGSIGNATURE on some EVM-to-BTC flows: sign EIP-712 initiate data so a solver can submit the lock (gasless lock path where Garden supports it). Approvals may still apply for ERC-20 sources.

You always branch on RAVN's single executionType field. You do not learn Garden's private API shape as an integrator.

Garden vs Relay (why both race)

Best execution still decides. A firm Garden quote that loses on net take-home does not win just because it is Garden. A Relay quote that is slower for almost the same net may lose on speed when values are close. See the best execution guide for ranking rules.

What RAVN adds on top of Garden

• Parallel quote against Relay and NEAR Intents (and any other registered BTC venue).
• Normalized quote and execute flow for app users and API integrators.
• Net-of-gas and slippage-aware ranking across unlike venue models.
• No RAVN custody layer in the middle of the Garden fill.

If you only used Garden's own app, you would get Garden alone. Inside RAVN, Garden is a specialist rail competing for the win.

Limits and honesty checks

• Garden enforces per-asset min and max sizes. Out-of-range amounts exit the race quietly.
• Decimals must match between RAVN token metadata and Garden assets or the venue is skipped (better than a silent decimal shift on BTC).
• Affiliate or integrator fee parameters only apply when configured; direct app users still see zero RAVN markup by product policy.
• Timing depends on Bitcoin confirmations and solver fulfillment. The in-app status is the source of truth for a fill.

FAQ