Sky proposes Configurator controls for Spark’s Arbitrum allocation system

What happened

Sidestream published the technical scope for attaching predeployed PAS and Configurator contracts to Spark’s Arbitrum Diamond PAU.

What changed

The proposed authorization enables bounded rate-limit changes and a preconfigured emergency CCTP-facet removal without a new spell. Beacon administration is to move from Spark’s executor to the core governance relay.

What did not change

Deployment alone does not establish PAU authorization or live allocation operations. The initially paused Timelock prevents delayed operations until a future core spell unpauses it.

Confirmed

• The scope identifies Configurator 0xd11Dc57F3eF23bb7b3142588a461F68460a7C474.
• The new controller and legacy controller are intended to share the existing Arbitrum ALMProxy.
• The documented growth settings are a 16-hour interval and 1.20 multiplier, subject to required confirmations.
• The scope explicitly requires Configurator authorization on the new PAU’s access controls and rate limits.
• The documented Beacon still requires admin handoff to L2GovernanceRelay.

Still open

• Risk-parameter and operator-address confirmations.
• Final deployment validation and parallel-controller review.
• Spark Arbitrum spell execution, Configurator authorization and Beacon admin handoff.
• Actual rate-limit values and functioning emergency removal after activation.

What it means for an advisor

• Review Sky and Spark authority maps for shared custody, local operator powers and emergency facet removal.
• Verify paused-Timelock restrictions before treating the nominal 14-day delay as an active protection.
• Require executed authorization and final deployment review before recording these controls as operative.