Bridge to HYVECHAIN
Transfer assets from any EVM chain or Cosmos ecosystem. One bridge for everything.
Seven EVM chains, via Noble over IBC · Skip Go, Circle CCTP & IBC · seconds fast, ~15 min standard · Automated routing
How It Works
Initiate Bridge
~30 secApprove, then send via Skip Go
Circle CCTP, or a solver
13-19 min · or secondsStandard waits for finality on the source chain, then mints on Noble. Fast has a Skip solver front it instead
IBC Transfer
~30 secNoble forwards to HYVE by itself
Arrives as USDC
InstantSpendable on HYVE, no extra step
Resources
Bridge
Routed by Skip Go, moved by Circle CCTP
—
Supported Routes














HYVE Privacy Lane
The bridge ingress stays the same. Noble and Osmosis remain public endpoint chains, and HYVE becomes the privacy hop only after assets land on the Cosmos side.
FAQ
Seven. Six of them in one signature: Ethereum, Base, Arbitrum, Polygon, Optimism and Avalanche, all through Circle CCTP to Noble and then IBC to HYVE. BNB Chain is the seventh and it takes two, because there is no CCTP route out of it at all - BSC USDC is Binance-Peg rather than Circle-native, and CCTP moves value by burning the native one. Measured on 2026-09-21, Skip answered six separate queries out of BSC with "no routes found". So the bridge relays it to Base first, through LI.FI, at about 0.26% and a few seconds, and then takes the ordinary Base route. The page asks for the second signature once the first hop has landed, and the USDC is in your own wallet on Base in between - so a closed tab costs you a reload, not a transfer.
That depends on which of the two routes you pick, and the difference is large. Standard is Circle CCTP, which waits for hard finality on the source chain before it will mint on Noble: about 15 minutes, measured at 13 minutes and still waiting out of Base on 2026-09-19, and two minutes out of Polygon. Fast skips that wait entirely - a Skip solver fronts the USDC on the other side and carries the finality risk itself - which measured 20 seconds out of Base on 2026-09-21, for about 0.1% instead of 0.02%. Fast runs between about $10 and $20,000 - measured against Skip on 2026-09-22. That range belongs to their solvers rather than to us, so it moves. Outside it the quote comes back as the standard route and the page says so rather than promising seconds. Either way you can close the page; the transfer does not need it.
Three things, and they are ours to different degrees. We charge 0.25 USDC per transfer, which is the only part that is revenue - it pays the relayer that carries your USDC the last hop from Noble to HYVE, and what is left over is ours. The route itself takes its own cut and we never see it: about 0.02% on the standard route, about 0.12% on the fast one, because a solver is fronting the money. And you pay gas on the chain you are sending from, which is a few cents everywhere except Ethereum. On $100 from Base that is roughly $0.27 standard or $0.37 fast, all in.
Yes. Routing is Skip Go, the cross-chain leg is Circle CCTP (USDC is burned on the source chain and minted on Noble), and the last hop is IBC. Your USDC lands on a Noble forwarding address derived from your own HYVE address, so it can only ever reach you.
Not yet. Withdrawals stay off until somebody has confirmed that the relayer requires a SIGNED withdrawal instruction - one signed by the address that made the deposit. Without that, a deposit is claimed by whoever posts its transaction hash first, and a hash on a public chain is public. That is the flaw the endpoint was disabled for, and a status code changing is not evidence it was fixed: the relayer answered 410 then and answers 400 now, which is what both a fixed one and a broken one return to an empty request. So the widget refuses rather than take your funds. Inbound bridging is unaffected.