Sky Grove proposes retiring its CCTP v1 governance relay on Avalanche

What happened

Grove Labs proposed revoking the CCTP v1 receiver's authority to queue governance actions on Grove's Avalanche Executor in the October 22 spell.

What changed

If completed, the CCTP v2 receiver would become the sole authorized governance-message receiver. The same proposal includes an 800,000 USDS Grove Foundation operating grant.

What did not change

The proposal does not establish an executed revocation. The v1 receiver retains its role until the cross-chain message arrives and the Avalanche actions set executes.

Confirmed

• The proposed revocation targets receiver 0x26e9512547feC1906C55256e491DfB6673D8C23f on Executor 0x4b803781828b76EaBF21AaF02e5ce23596b4d60c.
• The intended remaining receiver is the CCTP v2 receiver at 0x8Ea8Dff8c29f568eA1E716E2C3AfbD003EB83cfA.
• The proposed process sends the message from Ethereum and executes a separate actions set on Avalanche.
• The scope identifies the revocation message as Grove's first use of the v2 relay.
• The operating grant requires a separate Atlas authorization through governance.

Still open

• Governance approval, final payload, Ethereum execution, and Avalanche delivery and execution are not established.
• The scope's reported existing role state and historical relay use were not independently reproduced.
• Successful v2 delivery and the final role checks remain prospective.

What it means for an advisor

• Track both execution stages in the Sky allocator authority record; Ethereum execution alone would not complete this control change.
• After Avalanche execution, verify the v1 role is absent and the v2 role remains present before updating the dependency assessment.
• Review governance-delivery continuity when the fallback relay is removed.