# [Arbitrum] Spark Liquidity Layer - Authorize the PAS Configurator on the Diamond PAU

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xeF45Ee558e7AB2517446cBC8A397C07f207bd833
- State: Passed
- Voting type: Basic
- Start: 2026-09-28 16:37 UTC
- End: 2026-10-01 16:37 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/0x4680fb4b5717156b6e53f858ab6a267190deab0d51380b5fb9d27910e09d4e74

## 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 - Authorize the PAS Configurator on the Diamond PAU - 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 grants the PAS Configurator admin over the Arbitrum Diamond PAU access controls and rate limits, bringing the Parallelized Allocation System into service on the Arbitrum Diamond PAU. It acts on the same new Arbitrum Diamond PAU stack as the concurrent polls for the Diamond PAU parallel controller with CCTP V2 and the Beacon admin transfer, and should be read together with them.

### Required Context

Today the Arbitrum Spark Executor is the sole admin of the Diamond PAU Beacon, access controls and rate limits. After this change, the PAS Configurator also holds admin over the access controls and the rate limits, operated by an accordant cBEAM within bounds set by Sky Core Council. This allows rate limits and pre-approved controller actions, including disabling the CCTP facet during an incident, to be managed without a spell each time. PAS is an integral part of the Diamond PAU architecture. Spark keeps admin of its own access controls and rate limits, and Spark governance can revoke either grant in one call.

### Proposed Actions

Executed by the Spark spell through `PAYLOAD_ARBITRUM`, as the Arbitrum Spark Executor (the body of `PASAuthorizeInPAU.authorize` in `sky-ecosystem/pas`):

- Grant `DEFAULT_ADMIN_ROLE` on the PAU Access Controls ([`arb:0x8386f819860D54B1180539Ff4852E4CAECef8A1D`](https://arbiscan.io/address/0x8386f819860D54B1180539Ff4852E4CAECef8A1D)) to the PAS Configurator. The access controls gate every facet admin setter and every controller admin function.
- Grant `DEFAULT_ADMIN_ROLE` on the PAU Rate Limits ([`arb:0x4824C4336a1a11979068A544958dCe5D49B42752`](https://arbiscan.io/address/0x4824C4336a1a11979068A544958dCe5D49B42752)) to the PAS Configurator. The rate limits gate `setRateLimitData`.

The PAS Configurator is not yet deployed on Arbitrum; the payload currently carries a zero-address placeholder.

### What This Enables

`DEFAULT_ADMIN_ROLE` would itself allow granting and revoking any role on each contract, but the Configurator can use it only through two functions, each callable only by an accordant cBEAM within bounds held in PAS BeamState:

- [setRateLimit](https://github.com/sky-ecosystem/pas/blob/947e71cd5dbaaf9c5b3840dd1b23e8e99d9a564d/src/Configurator.sol#L93): Set a rate limit, raising it to no more than the higher of its current value multiplied by `maxChange` and its registered default, and only once `hop` has passed since its last raise; lowering is immediate ([Atlas A.2.2.10.1.1.1.2.4.4.1](https://sky-atlas.io/#7a98000b-c069-42f3-b1a4-8a3e7323a960), [Atlas A.2.2.10.1.1.1.2.4.1.2.1](https://sky-atlas.io/#942d6607-b92c-4779-8012-ea3b259ebf2b)). A key that already reads as unlimited is locked there and cannot be lowered by the cBEAM ([Atlas A.2.2.10.1.1.1.2.4.1.3](https://sky-atlas.io/#92a74fe1-3115-4cd7-bbf8-4e16fb4b0aa8)).
- [callControllerAction](https://github.com/sky-ecosystem/pas/blob/947e71cd5dbaaf9c5b3840dd1b23e8e99d9a564d/src/Configurator.sol#L139): Execute a call only if its exact calldata has been pre-approved by Core Council for a target Core Council has registered. This is the path for disabling the CCTP facet with `removeIntegrations` during an incident.

The Configurator has no function to set a relayer or freezer or to grant a role directly; any such change would have to be one of the pre-approved calls.

The grant is only as narrow as the PAS parameters, registered inits, pre-approved controller actions and cBEAM holder make it, and none of these has yet been published for this PAU. For the Ethereum PAS, the Atlas sets `hop` at 16 hours ([Atlas A.2.2.10.1.1.1.2.4.1.1.2](https://sky-atlas.io/#f86fe54a-9770-41ad-8ad2-7c58090224ce)), `maxChange` at 1.20, a maximum 20% increase per step ([Atlas A.2.2.10.1.1.1.2.4.1.2.2](https://sky-atlas.io/#0414677e-d79e-4d84-b0aa-209f0fa3ffe3)). Whether these apply to the Arbitrum PAS is to be confirmed. The Arbitrum Timelock is deployed paused.

### Pre-requirements

- Sidestream must deploy PAS (BeamState, Configurator and Timelock) on Arbitrum through PASFactory in one transaction. The Configurator address must be fixed in the payload before it is finalised for review, since `grantRole` accepts the zero address, and the full deployment record with role checks must be published before handover. Spark deploys, initialises and configures no PAS contract in this spell.
- Before the final review of the payload, the Core Council Risk Advisor must recommend `hop` and `maxChange` for this PAU (the Ethereum PAS defaults are 16 hours and 1.20), and the Core Council must publish the init rate limits, permitted controller actions and cBEAM holder, as the Atlas records for the Grove and Osero Diamond PAUs [A.2.2.10.1.1.1.2.4.2](https://sky-atlas.io/#9593a6c6-521b-4680-8119-cb1f08b9a3e3). The Timelock is deployed paused.
- Before execution, the published configuration must be in place in PAS on Arbitrum (set through the PASFactory deployment), and Phoenix Labs must check the on-chain state against it.

---

Technical implementation details can be found under item 5 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/349

## 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

