Sky proposes delegated Smart Burn Engine controls and new Uniswap functions

What happened

Sky's weekly Atlas proposal would create a bounded external-access module for the Smart Burn Engine, delegate parameter authority to a 4-of-6 operator multisig, and add Uniswap v3 liquidity and swap functions to Diamond PAU controllers.

What changed

The proposal defines a new no-executive-vote control path for kbump, hop, and burn settings and expands controller capabilities available to Prime Agents.

What did not change

The proposal was not yet approved or executed. Existing Smart Burn Engine authority and controller functions remained operative pending governance action.

Confirmed

• The proposed operator is a whitelisted 4-of-6 multisig.
• Proposed bounds include a 12,000 USDS maximum kbump, 550-second minimum hop, and 350 million USDS annual maximum rate.
• The proposed burn setting can range from 0% to 100%.
• The Atlas edit would add Uniswap v3 add-liquidity, remove-liquidity, and swap controller functions.

Still open

• Whether governance approved and implemented the Atlas edit.
• A documented tension between the existing parameter-governance text and the proposed multisig's 0%-100% burn authority.
• The final deployed contracts, bounds, and operator membership.

What it means for an advisor

• Review the Sky memo's administrator and delegated-authority map if the proposal became operative.
• Verify whether inherited Uniswap capabilities or burn discretion affect any approved or client-used Sky product before relying on existing control assumptions.