Login Register
Download
QR
Scan to Download More Download Options
English
简体中文
한국어
日本語
Русский
繁体中文
Español
Tiếng Việt
Buy Crypto
Market
Trade
Futures
Copy Trading
Earn
Rewards Hub
Explore
Login Register
Transparency · Proof of Reserves

100% Proof of Reserves On-chain Transparency Based on Merkle Trees

ZKE uses a Merkle tree-based proof-of-reserves system, allowing every user to independently verify that their assets are fully included in the platform's reserves, achieving true "visible security."

Log in to Verify
Current Reserve Status
100%
Assets > Liabilities
Proof of Assets Public On-chain Addresses
Proof of Liabilities Merkle Tree
User-Side Verification Self-Hash Verification
1
100% Reserves Backing User Balances
By comparing the publicly disclosed on-chain asset pool with the total user liabilities, we mathematically prove that the platform's actual assets are always greater than or equal to the total assets of all users on ZKE.
2
Transparent Liability Structure with Privacy Protection
User account balances are hashed and aggregated into a large Merkle tree. Without exposing any individual user's privacy, the platform proves the total liabilities.
3
Independent Self-Verification for Every User
Proof of reserves is not just an audit report only auditors can see. After logging into ZKE, you can obtain your unique Merkle proof path to independently verify whether your funds are included in the tree, without trusting any third party.
Underlying Logic
How Does a Merkle Tree Prove Liabilities?
We simplify this complex technical black box into three intuitive steps:
  • 1

    User Balance Snapshot

    At a specific time, the platform extracts all users' account balances along with anonymized account identifiers as "leaf nodes" at the base of the Merkle tree.

  • 2

    Generate Merkle Root

    The leaf nodes are paired and hashed together,层层汇总向上，最终生成唯一的“根哈希”，它代表了全站用户的负债总和。

  • 3

    On-chain Asset Comparison Verification

    The "total liabilities" represented by the Merkle root is compared with the platform's publicly disclosed "on-chain total assets." As long as assets ≥ liabilities, 100% full reserves are proven.

Core Solvency Formula:
When Proof of Assets ≥ Proof of Liabilities ,
the platform has the ability to fully redeem all user assets at any time.
User Action
How Do I Verify My Assets Are in the Snapshot?
The verification process is simple and only requires a few clicks within the ZKE system:
  • 01

    Log into Your Account

    Go to the official website and log into your ZKE trading account.

  • 02

    Enter "Asset Audit"

    Find "Wallet/Assets" in the top navigation bar and click "Asset Audit" from the dropdown menu.

  • 03

    View Historical Audit Results

    The page will display the latest reserve snapshot batch. Expand the details to view your specific asset snapshot at that time.

  • 04

    Verify Hash Path Yourself

    The system will provide your Record ID and Merkle leaf node hash. You can use third-party open-source code or local tools to independently verify that your funds are included in the root hash.

Proof of Reserves is an auditing method based on cryptography and blockchain transparency. It proves to the market that the platform's actual on-chain assets are sufficient to cover all user deposits on the platform.
Absolutely not. When building the Merkle tree, your account ID and asset balance are first processed through a one-way hash function. The resulting tree structure only contains hash values, and no one can reverse-engineer your account information or real funds. You only have the "proof path" for your own verification.
In the design of the Merkle tree, negative balances are not allowed. If negative assets are included in the audit logic , the mathematical verification process during root aggregation will directly report an error. This ensures that the platform cannot disguise total liabilities by creating "fake account debts."
ZKE regularly performs asset snapshots and Merkle tree updates. As the underlying audit system continues to evolve and mature, we will continuously shorten the interval between snapshots, aiming to allow users to transparently supervise the platform's solvency in near real-time.