Sky proposes delegated Smart Burn Engine parameter control through SBE BEAM

What happened

Sky contributors proposed initializing SBE BEAM and FarmOwner contracts so a permissioned operator could adjust Smart Burn Engine and staking-reward timing parameters outside the normal core-spell cadence.

What changed

If executed, the operator could jointly change kbump, burn, hop, and rewardsDuration within configured throughput, delay, and cooldown bounds.

What did not change

The cached record identifies an intended August 13 spell but does not prove initialization or execution. The Pause Proxy would remain administrator, and the operator's discretion would remain contractually bounded.

Confirmed

• The proposed SBEBeam address is 0xc8b61d211D3D03A630Fb09199E17953a8c9749a9.
• The proposed FarmOwner address is 0xA3d3A2e9Fe5d0901D720D5382E4a7eA12D4E2b0e.
• The permissioned operator address supplied by Soter Labs is 0x869294B42B80f99CF3Bdac0F44abddAd6cD41330.
• BA Labs recommended a 12,000 USDS maximum kbump, 550-second minimum hop, 350 million USDS annual maximum rate, and 30-minute cooldown.
• The contracts were described as pre-deployed and based on an audited commit, but initialization was assigned to a future core spell.

Still open

• Whether the August 13 executive spell passed and executed.
• The final live operator set, bounds, and contract permissions.
• Whether FarmOwner and SBE BEAM ownership was transferred and initialized exactly as proposed.
• How frequently the delegated operator uses the new authority and how changes are monitored.

What it means for an advisor

• Review Sky's delegated-authority and economic-control map if SBE BEAM becomes operative.
• Verify the executed initialization, operator list, bounds, Pause Proxy authority, and change history before relying on the new control model.
• Monitor whether delegated changes materially affect reserve retention, buybacks, or staking distributions supporting the broader Sky balance sheet.