Proof-of-reserves methodology
A methodology is not an attestation.
This describes the minimum controls Arkad would require before publishing a proof-of-reserves attestation. It does not report current assets, liabilities, custody, insurance, wallet balances, or member inclusion.
Open member centerIndependent scope
Independent scope
Any published attestation must identify its legal entity, custody providers, covered asset and liability populations, observation time, exclusions, reviewer independence, and the exact report or assurance standard used.
Privacy-preserving inclusion
Privacy-preserving inclusion
A member-verification design must use a cryptographic inclusion proof or an equally reviewable privacy-preserving mechanism. It must not expose another member’s balance, wallet address, provider identifier, or transaction history.
Operational controls
Operational controls
Publication requires a documented correction and incident process, retention of source evidence, independent review, and clear treatment of timing, pending transactions, liabilities, encumbrances, and assets outside the attested scope.
Current status
Current status
No Arkad proof-of-reserves attestation is published in this environment. The related member and crypto workflows remain unavailable unless separately shown as available through verified runtime evidence.