# [Arbitrum] Spark Liquidity Layer - Transfer Beacon admin to the Sky governance relay

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xeF45Ee558e7AB2517446cBC8A397C07f207bd833
- State: Passed
- Voting type: Basic
- Start: 2026-09-28 16:46 UTC
- End: 2026-10-01 16:46 UTC
- Votes: 3
- Discussion: https://forum.skyeco.com/t/october-8-2026-proposed-changes-to-spark-for-upcoming-spell/28265
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0x84f74256a6f0e41078483b5c7ce8dad4b885f5bc656a5bcaccb84f36d74e536c

## Results

- For: 630,215,697.16 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# [Arbitrum] Spark Liquidity Layer - Transfer Beacon admin to the Sky governance relay - September 28, 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 transfers admin of the Arbitrum Diamond PAU Beacon from the Arbitrum Spark Executor to the Sky governance relay on Arbitrum, placing the Beacon under Sky governance. It acts on the same new Arbitrum Diamond PAU stack as the separate polls for the Diamond PAU parallel controller with CCTP V2 and the PAS Configurator authorization, and should be read together with them.

### Required Context

The Beacon ([`arb:0x86036CE5d2f792367C0AA43164e688d13c5A60A8`](https://arbiscan.io/address/0x86036CE5d2f792367C0AA43164e688d13c5A60A8)) is the canonical registry of which facet belongs to each integration. `DEFAULT_ADMIN_ROLE` on the Beacon gates `setIntegration` and `removeIntegration`. The Arbitrum Spark Executor is currently its only holder.

After this change, registering a new integration for Spark's Arbitrum controller becomes a Sky governance action. Spark can still pull an integration the Beacon already carries into its own controller with `updateIntegrations`, but cannot add a new one to the Beacon. Spark keeps admin of its own access controls and rate limits. The CCTP facet used by the Diamond PAU parallel controller is already registered and synced, so that item does not depend on the Beacon after this transfer.

### Proposed Actions

Executed by the Spark spell through `PAYLOAD_ARBITRUM`, as the Arbitrum Spark Executor, in this order:

- Grant `DEFAULT_ADMIN_ROLE` on the Beacon to the Sky governance relay on Arbitrum ([`arb:0x10E6593CDda8c58a1d0f14C5164B376352a55f2F`](https://arbiscan.io/address/0x10E6593CDda8c58a1d0f14C5164B376352a55f2F)), controlled by Sky governance through the L1 governance relay ([`eth:0x9ba25c289e351779E0D481Ba37489317c34A899d`](https://etherscan.io/address/0x9ba25c289e351779E0D481Ba37489317c34A899d)).
- Revoke `DEFAULT_ADMIN_ROLE` on the Beacon from the Arbitrum Spark Executor ([`arb:0x65d946e533748A998B1f0E430803e39A6388f7a1`](https://arbiscan.io/address/0x65d946e533748A998B1f0E430803e39A6388f7a1)).

The grant comes first so that the Beacon is never left without an admin, which could not be recovered. **The transfer cannot be undone without Sky governance acting.**

### Pre-requirements

Sky, through Pullup Labs, must publicly confirm (for example in a forum post or the Atlas) the Sky governance relay as the intended admin of the Arbitrum Beacon before the payload is finalised for review. The grantee is a compile-time constant, currently a zero-address placeholder in the payload.

---

Technical implementation details can be found under item 6 at [_Proposed Actions_ in the October 8, 2026 Spell Technical Scope forum post](https://forum.skyeco.com/t/october-8-2026-proposed-changes-to-spark-for-upcoming-spell/28265/3#p-107461-proposed-actions-1).

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

## 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 once the Executive Vote that contains this proposal is 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

