Context
The Evolve chain launch blueprint includes a bridge UI as an optional user-facing component. Currently, bridge UI is either the default Hyperlane UI or a custom fork that requires frontend dev time per chain for branding.
Goal
Templatized bridge UI that skins automatically from chain config (name, colors, logo, supported assets). Ships as an optional module alongside Atlas -- not every chain needs a custom bridge frontend, but when they do, it should be zero custom code.
Requirements
- Connects to Hyperlane bridge contracts/warp routes
- Configurable via chain config (branding, supported tokens/routes)
- Responsive, production-grade UI
- Deployable as standalone or embedded in Atlas
Why optional
Not every deployment needs a branded bridge UI -- some clients are fine with the default Hyperlane interface. This should be an opt-in module.
Context
The Evolve chain launch blueprint includes a bridge UI as an optional user-facing component. Currently, bridge UI is either the default Hyperlane UI or a custom fork that requires frontend dev time per chain for branding.
Goal
Templatized bridge UI that skins automatically from chain config (name, colors, logo, supported assets). Ships as an optional module alongside Atlas -- not every chain needs a custom bridge frontend, but when they do, it should be zero custom code.
Requirements
Why optional
Not every deployment needs a branded bridge UI -- some clients are fine with the default Hyperlane interface. This should be an opt-in module.