Terra Classic Proposal Seeks Governance Ownership of 12 Hyperlane Contracts

A new Terra Classic governance proposal could move ownership of the chain’s Hyperlane infrastructure from a single deployer wallet to the Terra Classic governance module, putting future ownership controlled configuration changes under the governance process.

The proposal, titled “Claim Hyperlane infrastructure ownership for governance,” covers 12 Hyperlane contracts on Terra Classic, including the Mailbox, ISM contracts, hooks, IGP, and native LUNC and USTC warp routes.

As of September 29, 2026, the first step of the ownership transfer has already been completed and verified on chain, while the governance proposal required for the final ownership claim had been generated but not yet submitted.

Terra Classic Moves Hyperlane Ownership Toward Governance

The proposal is designed to complete the transfer of Hyperlane infrastructure ownership from the original deployer to Terra Classic governance.

According to the proposal documentation, the Hyperlane contracts were initially deployed and administered by a single wallet during installation and testing. The proposed handoff would make the Terra Classic governance module the owner of the contracts, meaning future ownership controlled configuration changes would require governance action rather than a signature from the original deployer.

The proposal uses a two step hpl_ownable ownership process.

First, the current owner initiates the transfer by setting the governance module as the pending owner. Second, governance calls claim_ownership to formally become the owner.

The first step has already been completed.

First Ownership Transfer Completed for All 12 Contracts

The proposal documentation states that init_ownership_transfer was executed on September 28, 2026, across all 12 contracts included in the governance transfer.

Each transaction was reported as successful with a transaction code of zero, and the resulting pending owner was independently checked on chain.

The designated governance owner is:

terra10d07y265gmmuvt4z0w9aw880jnsr700juxf95n

The documentation identifies this address as the Terra Classic x/gov module account rather than a privately controlled wallet.

The proposal documentation says all 12 pending owner values matched the governance address when independently queried on September 28.

What Contracts Are Included?

The proposed ownership transfer covers several core components of Terra Classic’s Hyperlane infrastructure.

These include the Hyperlane Mailbox, routing and multisig Interchain Security Modules, hook contracts, the Interchain Gas Paymaster, and native warp routes for LUNC and USTC.

The 12 contracts are located on Terra Classic. The proposal does not seek ownership of Hyperlane infrastructure on BSC, Ethereum, or Solana. Those components remain governed through mechanisms on their respective networks.

Two Hyperlane Contracts Are Not Ownable

The documentation also distinguishes between ownership and contract administration.

Validator Announce and the Merkle Hook do not implement the hpl_ownable interface and therefore do not have an owner field that can be transferred through the proposed ownership mechanism.

The proposal documentation says on chain queries confirmed that these contracts do not support the ownable query interface. This means there is no ownership claim to make for these two contracts.

However, their CosmWasm migration administration was handled separately.

Migration Admin Has Already Been Transferred

An important part of the proposal is that migration administration is separate from contract ownership.

The migration admin controls contract code upgrades, while the owner role controls functions exposed through the Hyperlane ownership interface.

According to the documentation, the migration admin was already transferred to the Terra Classic governance module on September 29 for the contracts with a mutable admin. The transfer was completed through individual transactions and subsequently verified by querying the contracts directly.

The LUNC and USTC warp contracts are described as having no migration admin, meaning their admin field is immutable rather than transferable.

This distinction is important because the new governance proposal is specifically focused on the ownership claim, not the migration admin transfer.

Governance Would Become the Owner

If the second step is successfully executed, the Terra Classic governance module would become the owner of all 12 applicable Hyperlane contracts.

The proposed claim_ownership message requires the transaction sender to match the pending owner. Since the pending owner has already been set to the governance module, the proposal is designed to allow governance to complete the transfer.

The proposal documentation also states that the 12 ownership claim messages would be executed atomically. If one of the messages fails, the transaction would not partially transfer ownership across the contracts.

This is intended to prevent a situation where only some of the Hyperlane infrastructure changes ownership while other contracts remain under the previous owner.

What Changes If Governance Claims Ownership?

The main change would be how future owner controlled configuration changes are authorized.

Before the transfer is completed, the original owner remains the actual owner of the 12 contracts even though governance has already been designated as the pending owner.

After a successful governance claim, governance becomes the owner.

The proposal documentation states that reversing the transfer would then require another governance process to initiate an ownership transfer to another address, followed by that address claiming ownership.

In practical terms, the proposal changes the ownership model from a deployer controlled arrangement to one where the Terra Classic governance process becomes the controlling authority for the applicable Hyperlane contracts.

Proposal Has Not Yet Been Submitted

Despite the first ownership transfer step being completed, the governance vote itself was not yet submitted as of September 29, according to the proposal documentation.

The claim ownership governance transaction has already been generated, but the proposal deposit was still partial at the time of the published audit. The document notes that the deposit figures can change as additional funds are added.

This means the current status should be understood as pre submission, rather than an active governance vote.

Why the Verification Matters

The proposal includes transaction hashes, contract addresses, block heights, contract queries, source code references, and repository commits intended to allow validators and community members to independently verify the ownership transfer.

The documentation says the underlying contract implementation was checked against the Hyperlane Terra Classic codebase, including the hpl_ownable implementation and the ExecuteMsg::Ownable wiring used by the applicable contracts.

The published audit also records the relevant source commit and tooling used to prepare the ownership transfer.

This approach allows the community to verify the technical claims directly rather than relying only on the proposal description.

What Happens Next?

The immediate next step is the submission of the governance proposal containing the 12 claim_ownership messages.

If submitted and approved, the Terra Classic governance module would claim ownership of the applicable Hyperlane contracts.

For now, the key milestones are:

The proposal represents a technical governance transition for Terra Classic’s Hyperlane infrastructure, with the first ownership transfer step already completed and the final claim dependent on the subsequent governance process.