Bridging Solutions

Eclipse offers multiple bridging options.
Inter-Blockchain Communication (IBC)
Supported VMs
Consensus Mechanism
Native consensus
Tendermint PBFT
Configurable ISMs (Interchain Security Modules)
Validator-based, rules may vary per chain; proof-of-authority intermediary
Time to Finality
Based on the finality time of the origin chain, and a block on the destination.
Fast finality facilitated by Tendermint chain
Congestion Handling
Only worried about congestion on the chains being connected, as there is no Hyperlane chain.
Relayers in IBC have not yet broadly implemented a fee market. During congestion, end users will need to pay higher fees.
Censorship Resistance
Censorship resistant by construction. Hyperlane’s permissionless nature ensures its neutrality, as it can be run without any dependency on external actors.
Bridging through IBC relies on a set of untrusted relayers and the validator set of the Polymer and external Cosmos chain. Messages will go through if there is one honest relayer and the chains will continue to make progress as long as there is an honest majority of validators.
Update Authority
You retain and decide the upgrade authority for your warp routes, and you can control it for the Mailbox deployed on your chain or rollup.
To update one side of the bridge requires trusting the settlement of one network. To withdraw requires the settlement of the other network. Polymer acts as a router and does not hold funds directly on their bridge.
Additional Tools
Hyperlane Explorer; can be accessed via API.
Mintscan block explorer and open source light clients.