The Ledger
Phoenix Labs Proposes Updating Spark Allocation Records
Phoenix Labs submitted SAEP-25 on 9 November 2026 to update Spark’s Allocation System Primitive records. The proposal would mark wound-down Instances as Completed, record current controller contracts and revise operational documentation.

Phoenix Labs submitted SAEP-25 on 9 November 2026, proposing edits to the Allocation System Primitive section of the Spark Artifact. The proposal recommends that Spark governance record wound-down Instances, RateLimitIDs and current controllers while updating directories and operational documentation. It says the changes would record the Spark Liquidity Layer as deployed and configured, without changing any contract, role, permission or rate limit onchain.
Source forum.skyeco.com
Phoenix Labs proposes moving ten wound-down Instances to Completed
Ten wound-down Instances whose rate limits are now zero onchain would move from Active to Completed, with three B2C2 transfer Instances and a Superstate USCC Instance on Ethereum Mainnet also recorded as Completed. The proposed recordkeeping changes include replacing future-iteration placeholders for RateLimitIDs, correcting values to match onchain configuration and filling addresses marked TBD. The Primitive Hub Document would gain entries for the Arbitrum Spark Savings v2 USDT Instance and the new Completed Instances.
Function documents would describe each function and include verified code instead of step-by-step operator instructions for ALM Controller and Ethena functions. The proposal would remove 52 per-step documents beneath the controller-function, rate-limit-management and emergency-procedure documents. For Completed Instances, it would also remove 49 example procedure documents for Mainnet Aave Prime USDS and Fluid, three placeholder-only Pool documents and 19 Ethena per-step documents; the proposal would point Active Instances’ operational processes to applicable general and emergency procedures and Completed Instances’ processes to general procedures.
The proposal records onchain state for three chains
As at 3 November 2026, Ethereum Mainnet was at block 26,331,099, Base at block 53,440,687 and Avalanche at block 99,269,269. At those states, MainnetController on Ethereum Mainnet and ForeignController contracts on Base and Avalanche hold the CONTROLLER role on their chains’ ALM Proxy and ALM Rate Limits contracts. The controllers currently named in the Artifact—one each for Ethereum Mainnet, Base and Avalanche—do not hold that role.
Of the 229 onchain values the proposal records, 225 were read and match, and none differs; four values were not confirmed. The two rate limits for the Spark Savings v2 USDG Instance on Robinhood Chain could not be read for want of an RPC endpoint. The two Centrifuge USDC RateLimitIDs hold 0 / 0 as stated but could not be recomputed from the current controller’s constants.
The proposed edit touches 512 documents
The edit would touch 512 documents: 212 would be amended, 175 added and 125 removed, while 1,173 documents would change number as Instances move between Active and Completed directories and removed documents leave gaps. Almost all of the edit would sit inside the Allocation System Primitive section. Outside it, the proposal would correct multiplication-sign rendering in the Supply Rate Definition and change “Unlimited” to “unlimited” for Spark Savings USDC on X Layer.
The Specification would adopt the edit by reference to Atlas PR #372 at commit ded3a5a and specifies the text, removals and moves that Spark governance is asked to approve. Endgame Edge, the Operational Facilitator, prepared the edit and opened the pull request, which is open and unmerged. Atlas PR #369 merged on 5 November 2026, after PR #372’s commit, and changed titles or lead-in sentences in 68 documents that PR #372 would replace.
At that commit, the reviewed version had git blob hash 5dd7798351e5a3507389e3f49a1a2d1d116edb76 and SHA-256 2a71e622d0bffec3d0f6a9029a261633ab408f374498cd4b51373b66e29f4dc9.
Sources
- Original source Sky Forum forum.skyeco.com