Super bridge native routes follow the rollup’s settlement path

A super bridge native route moves tokens through the bridge contracts maintained by a rollup and its settlement chain. For a transfer between two rollups in the same ecosystem, that can mean moving out of the source rollup and into the destination through their shared settlement layer. The shared ecosystem can make the route easier to understand, but it does not turn two separate rollup bridges into one direct bridge.

Superbridge presents routes from native bridges and third-party providers for supported transfers. Its interface builds transactions for the selected route, which the user reviews and signs from a wallet. In this account, super bridge refers to the native route category: the underlying contracts determine how the transfer settles, not the interface displaying it.

What does a native route do between rollups?

A native route uses each rollup’s own bridge to move assets between that rollup and its settlement chain. A settlement chain is the chain on which a rollup posts data and to which its native bridge connects. If two rollups share a settlement chain, a transfer between them may involve a withdrawal from the source and a deposit into the destination. The exact steps depend on the chains and route available for the chosen token.

That distinction matters. “Same ecosystem” describes a relationship between chains; it does not by itself establish that their native bridges support a direct rollup-to-rollup transfer. The route may involve separate transactions on separate chains. A third-party bridge or interoperability protocol may offer a direct route instead, with its own contracts and security assumptions.

Native routes can deliver the canonical asset recognized by the destination chain. A canonical asset is the representation issued or recognized through that chain’s official bridge path. This can matter when several tokens share a ticker but have different contract addresses or origins. Route availability is specific to the source, destination, token and amount; a native option for one combination does not guarantee one for another.

Why can a native route take longer?

Depositing from a settlement chain to a rollup usually requires one transaction and often completes within minutes. Withdrawing from a rollup can take longer because the settlement chain must wait for the rollup’s state claim to pass its challenge period. The challenge period is the window in which a false claim can be disputed. Some rollups also require a separate proof and finalization transaction.

The delay follows from the rollup’s settlement rules. It is not a processing estimate that a bridge interface can remove. On some rollups, a withdrawal takes hours; on many that settle on Ethereum, the wait can be about seven days. A route that chains a withdrawal and a deposit may therefore take longer than a transfer handled by a faster third-party provider.

Native routes can also need more than one wallet confirmation and gas on more than one chain. Some withdrawals require the user to return after a waiting period and submit another transaction. If the destination step needs gas, a transfer can be ready to finish but still require the user to fund the wallet on that chain.

How should you compare routes?

Compare the route’s estimated arrival, total amount received, provider fees, network fees and required transactions. The lowest displayed provider fee may not mean the lowest total cost: network fees can accrue across several steps, while a provider fee may be deducted from the amount received. Superbridge’s route view shows these details for the options it finds.

• Check that the destination token is the asset you intend to receive, including its contract or canonical representation.
• Read the transaction count and route instructions. A later step may require another wallet signature.
• Confirm that you have gas for each chain where the route asks you to transact.
• Choose a native route when its security model and wait suit the transfer; compare alternatives when timing is the priority.

For a transfer that can wait, the native route keeps the bridge mechanism within the rollup’s own contracts and settlement rules. That avoids relying on a separate third-party bridge for the transfer, but it does not remove the rollup’s own assumptions or make the route immediate. A faster alternative may be more practical for a small, time-sensitive transfer, provided its provider model is acceptable to the user.

What is confirmed about a super bridge route?

The confirmed mechanism is straightforward: a native bridge connects a rollup to its settlement chain, and the route follows that chain’s contract rules. Those rules determine whether the transfer needs a waiting period, proof, finalization or additional gas. The interface can show available route details and prepare transactions, but the on-chain contracts perform the transfer.

What remains unverified until a route is selected is whether a particular same-ecosystem pair has a native path for the chosen token and amount, whether it will require one or several transactions, and how long each step will take in current conditions. Treat the route shown for the specific transfer as the relevant evidence; ecosystem membership alone does not confirm a direct native route.