ardmere

Public PoR Transparency Registry

BITGET 20261021 PoR Transparency Report

Methodology: PoR Stage Framework
Assessment JSON: 20261021-assessment.json

1. Summary

Field Value
Exchange bitget
Snapshot 20261021
Snapshot time 2026-10-21T04:00:00Z
PoR Stage Stage 0 — Trust the Exchange
Gen / Evidence Gen 1 / E1
Confidence low
Effective PoR false

bitget snapshot 20261021 remains Stage 0 in the ardmere public evaluation set.

Public artifacts do not support independently reproducible global solvency verification for this snapshot.

2. Stage Decision

Stage 0, not effective PoR

Missing / Blocked Evidence Risk Flag Max Stage Reason
wallet_address_list UNVERIFIABLE Stage 0 No public wallet_address_list.

3. Frequency and Freshness

Field Value
Latest snapshot (evaluation set) 2026-06-18T10:00:00Z
Previous snapshot UNVERIFIABLE
Observed cadence ~22 days between snapshots
History available 2 snapshot(s) in public evaluation set
Event-triggered updates UNVERIFIABLE
Daily root / commitment anchor UNVERIFIABLE
Stage impact Monthly or slower cadence; does not meet Stage 2 frequency expectations.

4. Evidence and Bundles

Public Artifacts

Artifact SHA-256 Source
summarySnapshot 454c285e51482d8ae5c2f5826d1eebc285d2c965ac0e6b99fb0c8c58c37cbb01 https://www.bitget.com/proof-of-reserves

Bundle References

Bundle Value
Artifact bundle root 0x7adf28382288995b46d94918f4de17a0afcd73aae748ecaac705b81b10809f47
Verification bundle root 0xc3e6df8346f31ca2ab5b0126fe3340a2f8e95f6e47b46041a37518a88572ab3f
Artifact bundle SHA-256 8b0e0a2e93862c0094e343d25436ce5cb85bc994596a2d60266605c51d2abdca
Verification bundle SHA-256 22e78f2b4a02781f9c759b51f3a922afd65073f040301204793b2c7528e30602

Local bundle paths: 20261021.artifact-bundle.json, 20261021.verification-bundle.v2.json

5. Verifier Evidence

Verifier Version Verdict Coverage Summary
artifact-integrity 1.0 PASS 1.0000
solvency-claim 1.0 PASS 1.0000
user-merkle-proof bitget-1 UNVERIFIABLE 0.0000 merkel_tree_bg.json not present; download from Bitget while logged in and import via -user-proof
internal-consistency 0 UNVERIFIABLE 0.0000 No public wallet address CSV; cannot reconcile summary vs address aggregates
btc-anchor 0 UNVERIFIABLE 0.0000 Summary does not declare a BTC block height time anchor
onchain-balance-hot 0 UNVERIFIABLE 0.0000 No public HotCold wallet address list
onchain-balance-token 0 UNVERIFIABLE 0.0000 No public wallet address list for ERC20/BEP20 audit
onchain-balance-ledger 0 UNVERIFIABLE 0.0000 Verifier not available for this exchange snapshot
address-ownership 0 UNVERIFIABLE 0.0000 No public download channel for wallet ownership signatures / proofs
global-zk-proof 0 UNVERIFIABLE 0.0000 Bitget uses pure Merkle Tree with 64-bit truncated SHA-256 (no ZK)
third-party-attestation 0 UNVERIFIABLE 0.0000 No clearly identified independent third-party PoR attestation in machine-readable form
cross-chain-wrapped 0 UNVERIFIABLE 0.0000 No per-row wrapped-asset metadata in public PoR artifacts (token contract, representation type e.g. WBTC/cbBTC, canonical asset, custody mode)

6. Verifier Finding Details

This section explains FAIL, WARN, and UNVERIFIABLE outcomes from the verification bundle. Row-level UNVERIFIABLE entries often mean the verifier does not yet support that (coin, network) pair, not that the exchange failed the check. Full machine-readable output: 20261021.verification-bundle.v2.json in the local artifact bundle.

Capability and artifact gaps (UNVERIFIABLE)

Verifier Explanation
user-merkle-proof merkel_tree_bg.json not present; download from Bitget while logged in and import via -user-proof
internal-consistency No public wallet address CSV; cannot reconcile summary vs address aggregates
btc-anchor Summary does not declare a BTC block height time anchor
onchain-balance-hot No public HotCold wallet address list
onchain-balance-token No public wallet address list for ERC20/BEP20 audit
onchain-balance-ledger Verifier not available for this exchange snapshot
address-ownership No public download channel for wallet ownership signatures / proofs
global-zk-proof Bitget uses pure Merkle Tree with 64-bit truncated SHA-256 (no ZK)
third-party-attestation No clearly identified independent third-party PoR attestation in machine-readable form
cross-chain-wrapped No per-row wrapped-asset metadata in public PoR artifacts (token contract, representation type e.g. WBTC/cbBTC, canonical asset, custody mode)

No additional row-level FAIL or WARN findings beyond the summary table in §5.

7. Minimal Checklist

Requirement Status Notes
Has public PoR been published during the last 12 months? (S0-1) pass Snapshot 20261021 is in the public evaluation set.
Is snapshot time explicit? (S0-2) pass 2026-10-21T04:00:00Z
Is there reserve summary or wallet_address_list? (S0-3) pass Summary present; wallet_address_list absent.
Is wallet_address_list public and on-chain verifiable? (S1-1) fail No public wallet_address_list artifact.
Is wallet_ownership_proof public and batch-verifiable? (S1-2) unverifiable address-ownership verifier UNVERIFIABLE.
Is global_proof public and independently reproducible? (S1-3) unverifiable global-zk-proof verifier UNVERIFIABLE.
Is independent third-party review available with stated scope? (S1-4) unverifiable third-party-attestation verifier UNVERIFIABLE.
If trusted setup is required, is transcript public; otherwise is the proof system transparent setup? (S1-5) not_applicable No global ZK proof in the assessed public artifact set.
Is root/proof/vk canonically anchored outside exchange servers? (S2-1) not_applicable Stage 2 is not evaluated until Stage 1 blockers are resolved.
Is publication frequency sufficient for Stage 2 (weekly full PoR / daily anchor)? (S2-2) not_applicable Stage 2 is not evaluated until Stage 1 blockers are resolved.

8. Recommendations

Priority Recommendation Related Risk
P0 Publish missing public artifacts required for independent reproduction. UNVERIFIABLE

9. Boundary

This report evaluates public PoR artifacts and reproducibility. It does not evaluate the exchange’s overall financial health, corporate governance, internal controls, off-chain assets, legal compliance, or complete off-balance-sheet liabilities.

Missing data must be marked as UNVERIFIABLE, not treated as PASS.

Capture notes / gaps (2026-10-31)