Sky confirms Prime Agent settlement and oracle-accounting corrections

What happened

Sky's settlement operator published a reconciliation correcting prior Prime Agent revenue and Sky-share calculations after identifying methodology, data-source, block-timing, and oracle-feed errors.

What changed

The reconciliation adds approximately 820,320 USDS of net Prime Agent revenue and 297,559 USDS of net Sky share to later settlement calculations, while replacing or correcting several accounting inputs.

What did not change

The report does not identify a loss of client USDS or impairment of sUSDS redemption. It does not establish that every historical accounting case is resolved, and two Distribution Rewards cases remain outside scope.

Confirmed

• Spark corrections included previously missed aToken yield, a phantom idle-stablecoin outflow, a subsidized-borrow benchmark change, and data-source revisions.
• Grove corrections included fabricated T-bill series rows and an ACRDX Chronicle consumer feed that continued returning a stale value after its last update on May 7, 2026.
• Obex, Skybase, and Keel calculations were affected by an end-of-month block pinned approximately 2.8 hours early.
• The reconciliation reports approximately 820,320 USDS owed to Prime Agents and 297,559 USDS of net additional Sky share.
• Morpho-market and certain frontend Distribution Rewards cases remain for future reconciliation.

Still open

• The final correction for the two excluded Distribution Rewards cases.
• Whether every corrective mint and transfer was executed as calculated.
• The duration and financial effect of the stale Chronicle feed outside the reported settlement calculations.
• Whether the accounting-control changes prevent recurrence across all Prime Agents.

What it means for an advisor

• Review the Sky memo's allocator reporting and oracle-accounting controls because the errors affected multiple months and Prime Agents.
• Verify corrective execution and later reconciliation reports rather than treating the published calculations as settled on-chain state.
• Continue monitoring for any evidence that accounting errors affected backing, reserve coverage, or client redemption capacity.