Binance adds zk-SNARK verification to its proof of reserves system

Binance has upgraded its proof-of-reserves (PoR) system with zk-SNARK verifications, a form of zero-knowledge proofs that preserves the privacy and security of sensitive user information.

Binance CEO Changpeng Zhao said the improvement was implemented in accordance with Ethereum co-founder Vitalik Buterin’s suggestion. Buterin had laid out his ideas on promoting trustless centralized exchanges through transparent proof-of-reserves systems in November.

Binance first published its PoR system in November 2022 as users started demanding more transparency from exchanges in the aftermath of the FTX collapse. At the time, Binance used Merkle tree cryptography to enable users to verify their holdings.

Yet, the system had two major drawbacks. Firstly, the leaf nodes in the Merkle tree represented the hash of users’ holdings to protect privacy, which meant that the Merkle root could not reflect the sum of its leaf nodes’ balance information.

Secondly, a malicious entity could potentially add a negative balance under a fake account somewhere in the tree to make the size of required reserves appear smaller.

Binance claims that zk-SNARKs solve these challenges. The zero-knowledge verification system can ensure that all leaf nodes in the Merkle tree have contributed to Binance’s claimed total user balance of each cryptocurrency. It will also ensure that there is no user with a negative balance included in the tree.

Binance will generate and publish zk-SNARK proof for the construction of the Merkle tree to prove its reserves. By verifying the Merkle proof Binance users can check whether their balance is included in the Merkle tree root. Users can verify the zk-SNARK proof to ensure that the Merkle tree construction was free from any tampering.

Because Binance has millions of users, it’s not possible to get a single proof of the Merkle tree construction. Therefore, Binance will split users into batches of 864 each. It would take 110 seconds to generate zk proof for a single batch of users. The proof can be verified in less than 1 millisecond.

It would take 2 hours for Binance to generate proof for all accounts at the cost of about $1,000. The exchange is working on implementing the solutions suggested by Buterin to improve the efficiency of the proof generation process, which should lower cost and enable it to provide proofs more frequently.

Binance’s PoR system currently supports 13 cryptocurrencies, with 4 recent additions, and it plans to add more tokens in the coming weeks.

Binance is also making the code for its PoR system open-source with the aim of providing more transparency to its users.

Posted In: , Exchanges

Bookmark (0)

Related Posts

USDC issuer Circle issues warning about hacked executive account

USDC issuer Circle issues warning about hacked executive account

The hacker tweeted about a fake USDC airdrop to compensate holders who held the stablecoin during its depeg.

Bookmark (0)
Former Coinbase CTO urges ‘get to Bitcoin’ before CBDC digital lockdown

Former Coinbase CTO urges ‘get to Bitcoin’ before CBDC digital lockdown

Balaji Srinivasan warns of impending financial tyranny under CBDC system, advocates for Bitcoin as a solution.

Bookmark (0)

Virtual Duo Babka and Nushi Honor Game Developers Worldwide at GDC

Bookmark (0)
DeFi insurance grew in 2022 to include nearly two dozen providers

DeFi insurance grew in 2022 to include nearly two dozen providers

A new report published using industry data shows that DeFi insurance claims paid out a total of $34.4 million in 2022.

Bookmark (0)
Sushi and its ‘head chef’ receive SEC subpoena

Sushi and its ‘head chef’ receive SEC subpoena

The SushiSwap group and its leader aim to create a $3 million legal defense fund.

Bookmark (0)
OneCoin associate Irina Dilkinska charged following US extradition

OneCoin associate Irina Dilkinska charged following US extradition

Dilkinska is the latest individual to face charges in a $4 billion crypto scam.

Bookmark (0)

Leave a Reply

Your email address will not be published. Required fields are marked *