Spark's planned Base operator authority

What happened

Sidestream described operator authority for Spark's planned Base deployment on October 28 in Sky's official forum.

What changed

Spark plans to let cBEAM adjust rate limits and remove its CCTP integration during emergencies, subject to specified permissions.

What did not change

Sidestream states that the timelock will initially remain paused. Sky governance would retain responsibility for the most security-critical actions.

Confirmed

• Sidestream identifies November 5, 2026, as Spark's target activation date.
• Sidestream describes a parallel deployment that shares the existing ALMProxy with the older controller.
• Sidestream states that Spark must authorize the Configurator before it becomes functional.
• Sidestream identifies Spark's Executor as the Beacon administrator pending a planned transfer to Sky's governance relay.

Still open

• The notice does not establish completed activation or the planned administrator transfer.
• Sidestream requests confirmation of risk parameters, operator addresses, and deployment values from the responsible teams.
• Ketju has not established the final permissions after Spark executes its planned changes.

What it means for an advisor

• Ketju should review the Sky memo's description of delegated rate changes and emergency actions before the Base deployment becomes functional.
• Ketju should verify that Spark transfers Beacon authority to Sky's governance relay and authorizes only the intended Configurator.