Hey dev.to 👋
There's a specific moment a lot of people in this industry point back to. FTX collapsed, and it turned out a platform holding billions of dollars in user funds had been telling everyone their money was safe right up until it wasn't. Nobody outside the company had any way to check that in real time. You just had to believe the dashboard.
That was the moment "trust us" stopped being an acceptable answer from any crypto platform. And it's the reason proof of reserves went from a niche technical term to something users actually search for before depositing anywhere, including Wealtii.
I want to break down what proof of reserves actually means, because the term gets used loosely, and not every version of it is equally trustworthy.
The weak version: a snapshot, signed once
A lot of what got branded as "proof of reserves" after FTX is what I'd call attestation theater. A platform hires an accounting firm, the firm checks that assets matching customer balances existed in a wallet at one specific point in time, and the platform publishes a signed report saying so.
That's better than nothing. But it's a photograph, not a live feed. It tells you what was true on the day of the audit, not what's true right now, or what happened to those funds an hour after the snapshot was taken. Nothing structurally stops a platform from moving assets back into place for a scheduled check and moving them elsewhere the rest of the time. I'm not saying every platform doing this is acting in bad faith, most probably aren't, but the mechanism itself doesn't actually prevent bad faith. It just makes it slightly harder to get away with.
The stronger version: continuous, on-chain, checkable by anyone
The other approach, the one I built Wealtii around, is holding assets in a wallet that's public by default and verifiable at any moment, not just on audit day.
Every Wealtii fund is backed 1:1 by its underlying assets, held on chain, in a public multi-sig vault. There's no scheduled snapshot involved, because there doesn't need to be. The wallet address is public all the time. You can pull it up on a block explorer right now, this second, and see exactly what's held against the fund. Tomorrow you can check again, and the number should still make sense. That's a completely different guarantee than a signed PDF from an audit that happened three months ago.
I've written before about the specific multi-sig setup behind this, so I won't fully re-explain the mechanism here, but the short version is that no single key, including mine, can move those funds unilaterally. Continuous on-chain verifiability and multi-sig custody solve two different problems, and you actually want both. One proves what's there right now. The other limits who can move it and how.
Being honest about what proof of reserves doesn't solve
I think it's worth being precise here instead of treating "on-chain and verifiable" as a magic phrase that answers every question, because it doesn't answer all of them.
Proof of reserves, even the strong, continuous kind, tells you the assets exist. It doesn't automatically tell you about a platform's liabilities, meaning what it owes people versus what it holds. A platform could have fully verifiable reserves and still be mismatched if its obligations to users exceed what's actually backing them, if the structure allows for that kind of gap in the first place. For a simple 1:1 backed model like Wealtii's, where every fund unit is meant to correspond directly to real backing assets rather than IOUs or leverage on top of them, that particular failure mode is much narrower. But it's worth understanding the distinction generally, because plenty of platforms that talk about proof of reserves are running more complex balance sheets underneath, where reserves and liabilities are a genuinely separate question you should be asking.
I'd also say this plainly: on-chain verification proves custody, it doesn't prove that a token's price will hold, or that smart contract risk is zero, or that the broader crypto or tokenized asset market won't move against you. Those are different categories of risk. Proof of reserves answers "is the money actually there," not "will this investment do well." Conflating the two is exactly the kind of thing that erodes trust once people figure it out, so I'd rather draw the line clearly upfront.
A quick technical taxonomy, since "proof of reserves" gets used inconsistently
It's worth laying out the actual spectrum of approaches, because when I talk to other developers about this, I notice everyone means something slightly different by the phrase.
At the weak end, you have self-reported balances, where a platform just tells you a number on a dashboard with no external verification at all. That's not proof of anything, it's a claim, full stop.
One step up is the signed attestation, the accounting firm snapshot I described earlier. It adds a third party into the loop, which is genuinely better than nothing, but it's still a point in time check, and it still depends on you trusting the auditor's process and the platform's cooperation during the audit window.
Beyond that, some platforms use cryptographic proof of reserves, often built on Merkle tree structures, where individual users can verify their own balance is included in an aggregated total without the platform having to reveal every other user's holdings. This is a real improvement in privacy preserving verification, and it's a legitimate engineering achievement. But it typically still runs on a periodic cycle, published every so often rather than continuously live, and it usually only covers the reserve side, not a real time view of custody itself.
Then there's fully on-chain, continuously public custody, which is what I built Wealtii around. There's no periodic publishing cycle because there's nothing to periodically publish. The wallet is public all the time, the same way any other address on a public blockchain is public all the time. You're not looking at a report about the reserves. You're looking at the reserves.
Each step up that list trades some operational simplicity for stronger, harder to fake guarantees. I think the tradeoff is worth it, but it's a real tradeoff, not a free upgrade, and I'd rather be upfront that building this way is more constraining than the alternatives, not just better marketing copy.
Why this matters beyond just Wealtii
If you're a developer evaluating any platform, crypto or otherwise, that's asking you to deposit funds, I'd genuinely encourage applying this framework everywhere, not just here. Ask whether "proof of reserves" means a point in time snapshot or something you can check continuously yourself. Ask whether the custody mechanism structurally prevents unilateral fund movement or just relies on internal policy saying it won't happen. Ask what's actually backing the thing you're holding, and whether that backing is verifiable or asserted.
Those questions apply whether you're looking at a crypto exchange, a tokenized RWA platform, or honestly any fintech product making a custody claim. The answer to those questions matters a lot more than how confident the pitch sounds.
If you want to check this yourself
That's kind of the whole point of building it this way instead of writing another paragraph asking you to trust me. Go to wealtii.com, find the vault address, and look it up yourself on a block explorer. Compare what's actually there against what the platform claims is backing each fund. If the numbers don't line up, or if you spot something in the setup that looks off to you as a developer, I want to know about it, not after the fact, but now, while it's still useful feedback instead of a postmortem.
If you've built or evaluated proof of reserves systems yourself, I'd genuinely like to hear which approach you trust more and why. This is one of those areas where more outside scrutiny only makes the system stronger, not weaker.
Top comments (0)