# [Avalanche] Spark Savings and Spark Liquidity Layer - Deprecate Avalanche

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xF97c00fab22A45eB27163D0f0065Da00Da10624B
- State: Passed
- Voting type: Basic
- Start: 2026-11-09 16:15 UTC
- End: 2026-11-12 16:15 UTC
- Votes: 3
- Discussion: https://forum.skyeco.com/t/november-19-2026-proposed-changes-to-spark-for-upcoming-spell/28390/1
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0xf1426e0ea2fcab571a5d59e650b24a88f56c041efe8ddc31d22a9d354dd57f97

## Results

- For: 643,933,559.5 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# [Avalanche] Spark Savings and Spark Liquidity Layer - Deprecate Avalanche - November 9, 2026

Spark's Operational Facilitator has placed a proposal into the voting system on behalf of nested contributor Phoenix Labs.

## Review

The Spark community can hereby express support or opposition to the following changes:

This proposal approves deprecating Spark on Avalanche, closing Spark Savings USDC (spUSDC) to deposits with its rate fixed at 0%, closing the CCTP route to and from Ethereum, and retiring the Avalanche governance bridge. Reducing the number of chains Spark operates on cuts technical and operational overhead and reduces Spark's and Sky's risk surface.

### Change Summary

1. Close spUSDC to deposits:
   - Change spUSDC deposit cap from 500,000,000 USDC to 0. Withdrawals are not affected.
2. Fix the spUSDC rate at 0%.
3. Zero the Avalanche route to Ethereum:
   - Set `LIMIT_USDC_TO_DOMAIN` for domain 0 rate limits to 0.
4. Stop the ALM Proxy taking USDC from spUSDC:
   - Set `LIMIT_SPARK_VAULT_TAKE` to zero, so the relayer cannot move vault USDC into the ALM Proxy.
5. Zero the Ethereum route to Avalanche:
   - Set `LIMIT_USDC_TO_DOMAIN` for domain 1 rate limits to 0.
6. Retire the Avalanche governance bridge: from within the Avalanche payload, remove the Ethereum peer from the Avalanche Spark Receiver and revoke its `SUBMISSION_ROLE` on the Avalanche Spark Executor, so that no further governance message can reach Avalanche. The final calls will be confirmed by the Phoenix Labs smart contracts team before the payload is deployed.

The limit for transferring USDC into spUSDC stays unlimited, so that Phoenix Labs can add USDC for holders after the spell.

### Consequences and Timing

After execution, spUSDC on Avalanche can only be withdrawn from, at a fixed price, against USDC held in the vault, and its settings can no longer be changed by Spark governance. The Atlas will record the Avalanche instance as Completed.

The Avalanche Spark Executor applies a 3-day delay after the Ethereum spell, and must be executed within the following 7 days. The Spark Operations Multisig holds `GUARDIAN_ROLE` and can cancel the queued payload.

---

Technical implementation details can be found under item 4 at [_Proposed Actions_ in the originating forum post](https://forum.skyeco.com/t/28390/2).

The required Spark Artifact changes can be found in the following pull request: https://github.com/sky-ecosystem/next-gen-atlas/pull/381

## Outcomes

- If "For" receives more than 50% of votes cast, excluding abstentions, the proposal will be approved. The associated pull request will be merged into Spark's Artifact. When required, the listed changes will proceed to implementation by the relevant actors.
- If "Against" receives the most votes, the proposal will be rejected. No changes will be implemented.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

