# [Arbitrum] Spark Liquidity Layer - Bridge sUSDS to Arbitrum

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xeF45Ee558e7AB2517446cBC8A397C07f207bd833
- State: Passed
- Voting type: Basic
- Start: 2026-10-12 16:01 UTC
- End: 2026-10-15 16:01 UTC
- Votes: 5
- Discussion: https://forum.skyeco.com/t/october-22-2026-proposed-changes-to-spark-for-upcoming-spell/28298
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0x47341f1ff9453d3f3c6b088ebe1137c17a14536dde08aed2581019ca7ccef2f8

## Results

- For: 633,160,570.25 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# [Arbitrum] Spark Liquidity Layer - Bridge sUSDS to Arbitrum - October 12, 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:

Bridge **100,000,000 sUSDS** from the Ethereum ALM Proxy to the Arbitrum ALM Proxy to replenish the inventory that the Arbitrum PSM3 sells.

### Required Context

Spark's Arbitrum PSM3 sells sUSDS to users in exchange for USDC and USDS. Its sUSDS comes from the Ethereum ALM Proxy over Sky's Arbitrum token gateway, and a top-up can only be made through a spell.

### Justification

**The Arbitrum PSM3 is running low on sUSDS.** It held 57,993,876 sUSDS at Arbitrum block 505,766,908 (2026-09-16) and 32,608,532.69 sUSDS at block 513,027,171 (2026-10-08). Users bought a net 1.15 million sUSDS a day from it on average over those 22 days, unevenly: the balance rose by about 4.5 million over the last four days. At the average rate the remaining sUSDS lasts about four weeks, so it would be close to running out around the time this spell executes.

Phoenix Labs sized the amount against the lead time for another top-up. PSM3's 32,608,532.69 sUSDS plus this amount gives about 132.6 million, roughly 115 days at the 22-day average. PSM3's balance will be lower by the time the spell executes, so the runway after the top-up is shorter by the days elapsed. The amount is fixed in the payload and does not move with balances.

### Proposed Actions

The Spark spell, executing as the Spark SubProxy, will:

1. Move `100_000_000e18` = 100,000,000 sUSDS, in share units, from the Ethereum ALM Proxy [`eth:0x1601843c5E9bC251A3272907010AFa41Fa18347E`](https://etherscan.io/address/0x1601843c5E9bC251A3272907010AFa41Fa18347E) to the Spark SubProxy.
2. Send the sUSDS over Sky's Arbitrum token gateway (`outboundTransfer`) to the Arbitrum ALM Proxy [`arb:0x92afd6F2385a90e44da3a8B60fe36f6cBe1D8709`](https://arbiscan.io/address/0x92afd6F2385a90e44da3a8B60fe36f6cBe1D8709), funding the retryable ticket from the Spark SubProxy's ETH balance.

#### Permissions and Limits

The Sky Arbitrum token gateway sits outside the `spark-alm-controller` rate-limit framework, and `MainnetController` exposes no function that calls it. The sUSDS therefore leaves the ALM Proxy through an admin role rather than a rate-limited controller function: the Spark SubProxy, as the ALM Proxy's `DEFAULT_ADMIN_ROLE` holder, grants itself `CONTROLLER`, transfers the sUSDS through `ALMProxy.doCall`, and revokes the role in the same call. Because `CONTROLLER` allows arbitrary calls from the ALM Proxy, the amount is bounded only by the fixed constant in the payload. No other role is granted or revoked.

No rate limit governs this leg: the L1 gateway checks only that it is open and that the token is registered. The size is a governance decision rather than a parameter constraint, as with the January 15, 2026 PSM3 top-up. No new controller code is introduced; the `ALMProxy` and the Sky Arbitrum token bridge are covered by existing ChainSecurity and Cantina audits.

---

Technical implementation details can be found under item 1 at [_Proposed Actions_ in the originating forum post](https://forum.skyeco.com/t/october-22-2026-proposed-changes-to-spark-for-upcoming-spell/28298).

## Outcomes

- If "For" receives more than 50% of votes cast, excluding abstentions, the proposal will be approved. 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

