Axelar approves a non-binding freeze and recustody signal

What happened

Axelar governance passed a non-binding signaling proposal supporting a coordinated freeze of funds attributed to the June Axelar–Secret IBC bridge attacker and later recustody to a vetted distributor.

What changed

The community created a formal on-chain record of recovery intent and authorized contributors to prepare a later binding proposal with freeze, custody, and redistribution mechanics.

What did not change

The text proposal did not freeze, seize, move, recustody, or distribute funds, and it did not select a distributor or approve a final victim-repayment plan.

Confirmed

• Proposal 490 passed.
• The proposal is explicitly non-binding and carries no automatic on-chain action.
• It identifies axelar1hzra9z4zn8q0w8f3dj2wnw0xgetu8dfdhl6ad8 as the attacker-controlled wallet.
• It calls for a later binding proposal specifying the freeze mechanism, distributor, and redistribution plan.

Still open

• Whether the identified funds were actually frozen remains unverified.
• The amount, asset composition, custody status, and recoverability of the referenced funds are not established by this record.
• No trusted distributor, binding payload, entitlement schedule, or repayment timing had been approved.

What it means for an advisor

• Keep the Axelar incident and recovery path under memo review; a favorable signal is not recovered funds.
• Require operative freeze evidence and a binding, auditable distribution plan before crediting recovery.
• Continue monitoring bridge loss-allocation, custody, and cross-chain administrator powers implicated by the response.