Spark approves Avalanche governance-bridge timelock and guardian

What happened

Spark governance approved adding a three-day timelock and a guardian multisig to the Avalanche governance bridge.

What changed

The approved design inserts a delay before governance actions become effective and gives a guardian multisig cancellation power during that delay.

What did not change

The guardian is not granted general administrative authority over the Avalanche deployment, and the proposal does not resolve Spark's other per-chain control or legal-entity disclosure gaps.

Confirmed

• The Snapshot vote closed on June 25 with all recorded voting power in favor.
• The proposal identifies roughly 17 million spUSDC liabilities on Avalanche.
• The planned guardian requires at least five signers and a quorum of half the signer set rounded up.
• The guardian's stated power is limited to cancelling pending actions during the timelock.

Still open

• The candidate does not establish contract deployment or activation of the timelock and guardian.
• The final signer set and whether the planned multisig address was retained remain unresolved.

What it means for an advisor

• Update the Spark Liquidity Layer control map if implementation is confirmed, recording both the three-day notice period and the cancellation controller.
• Do not treat this chain-specific mitigation as resolving undisclosed control structure across Spark's other deployments.
• Verify deployed contracts and role assignments before giving the proposal credit in any future reopen review.