“Is this stablecoin backed?” isn’t the right question.

The right one is: backed as of when?
Two words get used interchangeably in this space, and they shouldn’t be.
Attestation is a snapshot. An accountant reviews custody records on a given date and signs off that reserves matched supply at that moment. It’s backward-looking, periodic, and dependent on a human accounting cycle.
Proof of Reserve is continuous. Oracle infrastructure pulls custody data and writes it on-chain in real time, with no human step in between.
One tells you what was true. The other tells you what’s true right now.
…
α/ When Verification Arrives Too Late
A month-old attestation is fine until it isn’t.
> Reserves can shift between reporting dates
> Redemption pressure during a stress event moves faster than any accounting cycle
> By the time a lagging report publishes, the moment it needed to capture has already passed
The gap isn’t theoretical. It’s the exact window where a holder needs to answer the fastest, yet receives them the slowest.
…
β/ USD1’s Dual-Stack Approach
USD1 is a useful case study because it didn’t choose one method over the other. It stacked both.
USD1 has already published monthly attestations; better cadence than most of the industry, which typically reports quarterly.
Then, in February, it added a second layer. “Even monthly attestations have a one-month reporting delay because accounting takes time. We just solved that,” WLFI stated.
The new system updates reserve backing continuously. Chainlink oracles pull BitGo custody data on-chain to show live supply, reserves, and collateralization ratios, removing the manual accounting steps that slow traditional attestations. It’s designed to complement, not replace, the monthly attestation reports.
The timing wasn’t incidental. The shift came shortly after a coordinated attack on the ecosystem, compromised cofounder accounts, FUD campaigns, and short positions against WLFI during which USD1 briefly traded at $0.994. That’s precisely the kind of stress event where a 30-day-old report tells you nothing useful.
Furthermore, the dashboard code is open source, anyone can verify the backing without paid tools or private access.
…
γ/ Conclusion
This is where the entire stablecoin category is heading, whether every issuer admits it yet or not. Monthly PDFs were the standard because continuous on-chain verification used to be difficult to build. Now it isn’t.
The issuers still relying on attestation alone aren’t necessarily hiding anything. But they’re asking you to trust a number that’s already out of date the moment you read it.
Before you hold any stablecoin, ask if its proof keeps pace with its promise.