If you search on Google for broken proofs of solvency, you will find our full report. There are so many different names and one of them was using short hashes. I could literally create a fake proof of liability for everything. So yes, these are the four attacks that you can find at the moment on proof sliabilities. People are actually doing their own checks by their mobile phones or their website of the company. The whole industry should change the name to tell you the truth. We should use proof of solvence and proof of liabilities and proof of assets.
This week, Anna explores the topic of proof of solvency with Kostas Chalkias, co-founder and chief of Cryptography at MystenLabs. They cover Kostas’ background in Cryptography and explore his work on Proof of Reserves, otherwise known as Proof of Solvency. They review past Proof of Solvency models using ZKPs and look at the protocols that major centralized exchanges are currently using. Then they dive into the security vulnerabilities, privacy issues, and general bugs that Kostas and his collaborators have identified in these protocols and their recommendations on how to better build Proof of Solvency systems.
Here are some additional links for this episode:
Today’s episode is sponsored by Aleo
Aleo is a new Layer-1 blockchain that achieves the programmability of Ethereum, the privacy of Zcash, and the scalability of a rollup.
If you’re interested in building private applications then check out Aleo’s programming language called Leo. Visit leo-lang.org to start building.
You can also join Aleo’s incentivized testnet3 by downloading and running a snarkOS node. No sign-up is necessary to participate. For questions, join their Discord at aleo.org/discord.
If you like what we do: