Proof of Reserves

Bitget promises to hold 100% of users' assets in reserves, as well as publish its Merkle Tree proof, platform reserves, and platform reserve ratio on a monthly basis.
reserveCertificate-bannerRight
What is Proof of Reserves?
The term "Proof of Reserves" refers to an auditing procedure that verifies the holdings of an exchange through cryptographic proofs, public wallet ownership, and recurring audits. The custodian provides transparency and proof of the existence of liquid on-chain reserves that exceed or equal the sum of all user holdings.
To achieve this, Bitget stores the hash of each user account's assets in a leaf node on the Merkle tree. Each user can verify that their assets exist in the Merkle tree by checking the total amount of user assets stored in the Merkle tree leaf nodes.
If the total verified amount is greater than or equal to 100%, the platform demonstrates its ability to fully cover all user assets.

Bitget's open-source Proof of Reserves code is available on GitHub.

View here

reserveCertificate-reserveLeft-index1
reserveCertificate-reserveLeft-index2
Our commitment to maximum transparency
1. Each month, we take snapshots of all the assets held in our wallets and make them available publicly.
We take monthly snapshots of each user's assets and publish them after removing sensitive data.
3. Users can verify their assets anytime with just a few simple steps.
Why is a 100% reserve ratio important?
Inability to maintain 100% reserves

Indicates potential asset misappropriation.

reserveCertificate-redIcon-1

Limited risk tolerance for black swan events.

reserveCertificate-redIcon-2

Large-scale withdrawals can trigger a bank run, potentially resulting in the loss of user assets.

reserveCertificate-redIcon-3
Maintaining 100% reserves

Demonstrates that the platform holds sufficient reserves at all times.

Enhances the security of users' assets.

Ensures the platform can cover all withdrawals, even in a 100% withdrawal scenario.

no-risk-riskVs
Maintaining 100% reserves
Demonstrates that the platform holds sufficient reserves at all times.
Enhances the security of users' assets.
Ensures the platform can cover all withdrawals, even in a 100% withdrawal scenario.
no-risk-m-riskVs
Inability to maintain 100% reserves

Indicates potential asset misappropriation.

reserveCertificate-redIcon-m-1

Limited risk tolerance for black swan events.

reserveCertificate-redIcon-m-2

Large-scale withdrawals can trigger a bank run, potentially resulting in the loss of user assets.

reserveCertificate-redIcon-m-3
Merkle Tree basics
A Merkle Tree is primarily used to verify data integrity more efficiently. Each account is represented by an Acct node at the bottom, and the balances and account names of each account will be computed once with SHA256 encryption. The obtained hash value can be computed again with the adjacent one, and then layer by layer upwards until the hash calculation reaches the root of the Merkle tree. To verify whether the current reserves have been changed, the user only needs to follow the steps to make a hash calculation of their own account, find the position in the tree and the adjacent nodes, and then calculate the hash upward layer by layer until finally reaching the root of the tree calculated by the user. If it is consistent with the official announcement, then everything is accounted for.
As shown in the figure below:
merkelTree
Download app
Download app