ardmere

Public PoR Transparency Registry

ardmere Service Audience

ardmere is not just a PoR verification tool for retail users. It is PoR transparency infrastructure for regulators, institutional allocators, independent reviewers, and exchanges.

One-line positioning:

ardmere helps external observers determine whether an exchange PoR is genuinely verifiable, whether it meets an effective PoR standard, and which key evidence is missing.

1. Why PoR is required for digital asset exchanges

Digital asset exchanges that custody customer assets face a problem traditional financial reporting was not designed to solve alone: whether, at a defined moment, customer liabilities in scope are fully backed by reserves the exchange controls—and whether third parties can reproduce that claim without trusting exchange narrative.

1.1 Why exchanges need PoR

  1. Custody is the core product. Users deposit assets expecting same-day redemption. Unlike many traditional intermediaries where settlement and accounting lag behind user-facing balances, CEX liabilities are often represented as real-time account balances—and frequently tied to on-chain wallets, Merkle trees, or zero-knowledge proofs.
  2. Liabilities can be verified at user scale. PoR can commit to full user balance sets (or defined subsets) and let third parties re-run proofs. Financial audit typically relies on sampling, management representations, and company-level assertions—not publicly reproducible, user-level evidence.
  3. Risk windows are compressed. Market stress, bank runs, and insolvency events in crypto move faster than quarterly or annual audit cycles. PoR snapshots (and, at higher stages, anchoring and frequency) address timely reserve transparency, not just historical financial statements.
  4. On-chain and off-chain books diverge easily. Reserves may sit in hot wallets, cold storage, staking, lending books, or related entities. Without published wallet_address_list, ownership proof, and liability-side proof, outsiders cannot bind “what the exchange says it holds” to “what it owes users.”
  5. Marketing outruns evidence. Claims such as “100% backed,” “audited,” or “ZK verified” are often interpreted as solvency guarantees. Effective PoR requires artifact-bound, scope-stated, independently reproducible evidence—not slogans.

For licensing, listing, institutional custody, and counterparty risk, regulators and allocators therefore need a minimum effective PoR standard, not merely periodic company audits.

1.2 Why traditional audit cannot fully substitute

Traditional financial audit and PoR are complementary; neither replaces the other. Policy detail: Effective PoR Standard §1.3.

What auditors are strong at What audit typically does not give users or regulators for CEX custody
Financial statement fairness, going concern, internal control Per-user, publicly reproducible proof that your balance is included in a defined liability set
Off-chain cash, receivables, related-party and off-balance-sheet review Proof that listed reserve wallets are controlled by the exchange for the snapshot period
Periodic assurance over management’s books Continuous or high-frequency, artifact-archived reserve transparency between audit periods
AUP or limited procedures on agreed steps Permissionless re-verification of global_proof, roots, and parameters without exchange authorization

Common failure mode: an exchange (or group) receives a clean audit opinion while Stage 0 PoR remains—summaries or partial proofs exist, but independent third parties cannot reproduce the global asset–liability relationship. That gap is material for customer asset safety even when corporate financials look adequate.

Regulatory implication: adopt a dual-track model—financial audit for company-level integrity and off-chain risk; PoR Stage for publicly reproducible reserve transparency. Require both boundaries to be stated in disclosure; do not treat “audited” as equivalent to effective PoR.

2. Core audiences

2.1 Regulators / policymakers

Regulators are one of the most important audiences.

They do not need to run proofs themselves. They need answers to:

  1. Which exchanges have effective PoR?
  2. Which are only Stage 0 and must not be treated as effective PoR?
  3. Which key artifacts are missing?
  4. Are wallet_address_list, wallet_ownership_proof, and global_proof published?
  5. Does the proof system rely on an opaque trusted setup?
  6. Are there risks such as negative-net-worth fake users, negative balances offsetting real liabilities, off-chain distribution, or replaceable history?
  7. How should PoR requirements be written into rules or licensing conditions?

Value for regulators:

2.2 Institutional investors / market makers / custody clients

Institutional allocators care about exchange transparency and custody risk.

They need:

  1. Cross-exchange comparison of PoR transparency.
  2. Fact-checking of claims such as “100% backed”, “audited”, or “ZK verified”.
  3. Judgment on whether an exchange is Stage 0, Stage 1, or a Stage 2 candidate.
  4. Integration of PoR risk signals into exchange onboarding, limits, market-making risk, and custody risk models.
  5. Tracking of whether PoR is published continuously, historically archived, and whether standards have regressed.

Value for institutions:

2.3 Independent reviewers / security firms / accounting firms

Third-party reviewers can use ardmere as PoR review infrastructure.

They need:

  1. Automated checks that PoR artifacts are complete.
  2. Re-run proof / verifier workflows.
  3. Review of wallet_ownership_proof, global_proof, vk/config, and trusted setup transcripts.
  4. Checklists for AUP / technical verification / limited assurance work.
  5. Explicit marking of unverifiable scope and evidence gaps.

Value for reviewers:

2.4 Exchanges

Exchanges are also a potential audience, but independence must be preserved.

They need:

  1. A clear view of what is missing for Stage 1 / Stage 2.
  2. Pre-flight checks that PoR artifacts are complete.
  3. Validation of proof, verifier, disclosure format, historical archive, and user verification UX.
  4. A transparency improvement roadmap for regulators, users, and institutional clients.

Value for exchanges:

If serving exchanges, clearly separate:

Avoid “grading your own homework” trust conflicts.

2.5 Advanced users / researchers / media

These users rarely run proofs daily, but they cite ratings and reports.

They need:

  1. A concise, credible exchange transparency ranking.
  2. Traceable evidence links.
  3. Fact-checking of exchange marketing language.
  4. Readable explanations of PoR technical differences, review scope, and risk gaps.

Value for them:

3. Who are the first-phase direct customers?

Retail users are ultimate beneficiaries, but not necessarily first-phase direct customers.

First-phase priority audiences:

  1. Regulators and policy researchers: need to define the minimum standard for effective PoR.
  2. Institutional allocators: need to integrate PoR transparency into risk controls.
  3. Independent reviewers: need a toolized, standardized PoR review workflow.

Exchanges can be a second-phase audience, with clear independence boundaries.

4. Product surfaces

4.1 Public Transparency Dashboard

For the public, researchers, media, and institutional screening.

Core content:

4.2 Regulator / Institution Report

For regulators and institutional clients.

Core content:

4.3 Verification API

For reviewers, institutional clients, and internal systems.

Core capabilities:

4.4 Exchange Readiness Assessment

For exchanges, with independence preserved.

Core content:

5. Independence principles

To build long-term credibility, ardmere should enforce these boundaries:

  1. Public ratings cannot be purchased by exchanges.
  2. Paid technical assessments must disclose scope and conflicts of interest.
  3. Remediation consulting must not be equated with independent certification.
  4. Every rating must bind to artifacts, hashes, URLs, verification output, and timestamps.
  5. Missing data must be marked UNVERIFIABLE; it must not default to pass.

Phase 1: Public Methodology + First Reports

Goal: establish credible methodology and sample reports.

Suggested subjects:

Outputs:

Phase 2: Institution / Regulator Package

Goal: translate ratings into regulatory and institutional risk language.

Outputs:

Phase 3: API and Tooling

Goal: productize verification services.

Outputs:

Phase 4: Exchange Readiness / Remediation

Goal: help exchanges improve PoR without sacrificing independence.

Outputs:

7. Conclusion

ardmere’s direct customers should not be defined first as retail traders. They should be defined as:

regulators, institutional allocators, and independent reviewers.

Retail users are ultimate beneficiaries; exchanges are subjects of assessment and later service recipients.

The most robust product path is:

  1. Build public, independent, traceable PoR Stage ratings first.
  2. Serve regulators and institutional clients next.
  3. Serve exchange improvement last, under explicit independence boundaries.