A Small Peek into the New LUNC Hyperlane UI Design

The LUNCDaily team has shared an early preview of the new Hyperlane UI design created by Igor Soares. This preview shows how Terra Classic can use Hyperlane in a safe, open, and community driven way while preparing for long term decentralization.

How the Bridge Will Be Managed

The Hyperlane bridge can be maintained by any qualified developer from the L1 team or the wider L2 community. To ensure security and transparency, official copies of all important code will stay inside the Classic Terra GitHub organization:

• hyperlane warp ui template
• hyperlane monorepo
• cw hyperlane

These official copies keep the full commit history, allow easy auditing, and prevent reliance on external repositories. Any future update must go through a Pull Request and will be reviewed by the developers responsible for the classic terra repository.

Warp UI Setup and Community Support

Any developer can support or improve the UI. A complete and ready to use version will be kept in a dedicated branch with installation steps, a guide for adding bridges, and instructions for maintenance and customization.

Because the UI requires hosting, the code will remain open so any community member can run their own Warp UI instance.

Possible community operators include:

• TerraPort
• TRIT
• Hexxgon
• StrathCole
• Garuda
• Any other provider interested in supporting users

All operators are free to fork, host, customize, or create their own versions of the UI.

Making Operation Easier for the Community

Hyperlane is the most complex part of the integration. To lower the technical barrier, the UI is delivered fully prepared. Operators only need to:

• Deploy and index a Terra Classic full node
• Update network configuration settings
• Apply the adjustments described in the technical proposal

This approach ensures the UI remains sustainable, decentralized, and reliable, and continues to operate even if contributors change.