Bitcoin audits help clients independently verify whether an exchange is solvent or whether they have been hacked or have misused their clients’ crypto.Coinfloor is a custodian of client bitcoins and we believe that we must set the industry standard for transparency and regular attestations. Without proper public accountability, the industry will not be able to grow and mature. This is why we have always committed to releasing a Bitcoin audit (also known as “Provable Solvency” or “Proof of Custody”) Report every month. Coinfloor is proud to have the longest track record in the world for creating these reports – in fact, we have produced more solvency reports than all other major cryptocurrency exchanges combined. You can review all our solvency reports below For more information about why Bitcoin audits and Proof of Custody is so important, see the excellent article on how to effectively scale the Bitcoin industry by Nic Carter, the respected crypto commentator.
The invention of the Bitcoin blockchain as a global decentralised ledger enables markets to produce new standards of accountability and the safeguarding of client funds. In a self-regulated environment such as Bitcoin, firms must compete for customers’ trust by providing greater transparency.
We believe that this approach is the best way to achieve maximum accountability while retaining privacy for our clients. We welcome feedback from the community and hope that other exchanges are also able to safeguard client funds and will provide proof of solvency as well.
Coinfloor is dedicated to accountability and has committed to publish a Provable Solvency Report every month, showing the total amount of client funds Coinfloor has on deposit and proving ownership of those funds on the blockchain.
Need help? Email us at [email protected]
|Date (UTC+05:30)||name of the report||Amount||SHA-256 Hash of the report||Transaction ID|
|Sept 16, 2021||Provable Solvency Report #90 – 16 Sept||2754.943368 XBT||EA08259CDC53A449314CA5E76635525476855550941D69EFE6A14E2B8CE55CF4||
4515308b6beef3df62e399eed05ca9640510fac723609b0af526db8c2f276057Copy to clipboard
|Aug 17, 2021||Provable Solvency Report #89 – Aug 2021||2801.94004 XBT||F27DCCCCFCDF72633828C2CFE2E73B772B91E4DAC9F8F74239754902ABBF6648||
226a9709d4158bf04ca7fb3464a9d6b03a44101cd857925051fbf5b3bb70decbCopy to clipboard
|Jul 13, 2021||Provable Solvency Report #88 – Jul 2021||2842.790209 XBT||886C5E5BA5EF164FDCC9F7B6C7B9998BF9B1991C374718D3A03CBB1A287F0CE7||
36ecb675e393e0669a90408f04b3360f57d228e282b29f7dc4ebaa44723f0d28Copy to clipboard
|Jun 15, 2021||Provable Solvency Report #87 – Jun 2021||2850.123127 XBT||49345A73077D4C53C3B57488CD2CE415E8006F26C1C17966BA317338D3CA647B||
b70c7e64ed6ebeff7724f7e91f6a07ed8b198b1ea9dd649341440075f4f322c8Copy to clipboard
|May 18, 2021||Provable Solvency Report #86 – May 2021||2869.165315 XBT||96E72B4701A1026CA1535F866C230D71BAC0DF2D361B47A2C3FDE5CF65092675||
b015e149d76316bcaedc530d6f2258fda71c63907831001fb639d54faf7181a9Copy to clipboard
|Apr 15, 2021||Provable Solvency Report #85 – Apr 2021||2682.85545506 XBT||CC2B9ABE7859A998DE644C6593ECA690AEEDFF8F1D62898FE79580454232C292||
2712d2d999975ef95eb0761e008179b0d7937e63c1f8a0d1e417a7ebb74b8e3fCopy to clipboard
|Mar 16, 2021||Provable Solvency Report #84 – Mar 2021||2991.867077 XBT||49C716E7432BF45F1C399FA13E173D4EAA38987493B6863098D0BBB928BD931A||
bbc4a344b0a1cbd7efb718c33cf39c99052f270dabaa95e7ef56be55a1a20383Copy to clipboard
|Feb 17, 2021||Provable Solvency Report #83 – Feb 2021||3077.4881 XBT||E35D5C054513A4DBF75CD6B5A7D72696C7B8BE4D9FC65E69E52DEBE9B9411C63||
22f16bd78c3103af76dedeac096fdc33382d2cd9bab43ab48ffd6dfef757b640Copy to clipboard
|Jan 15, 2021||Provable Solvency Report #82 – Jan 2021||3282.6026 XBT||FCDBCA550069A88594B7DDB834A02C1CE9F3150C70FF8F89D49158BF06C8AD04||
6b6ce7f33950eacbeaf0db1339725bfb7f104883189651e5511601daccdd793bCopy to clipboard
|Dec 15, 2020||Provable Solvency Report #81 – Dec 2020||3489.0246 XBT||20ded532d9885d256b294f5a644661a028a7487db8d41e77323061d5dc590dae||
fb713c3da05ef2868a4b76c668fb5ce62840ae099450e711f6cdad778700e848Copy to clipboard
|Name of the report||Provable Solvency Report #90 – 16 Sept|
|SHA-256 Hash of the report||EA08259CDC53A449314CA5E76635525476855550941D69EFE6A14E2B8CE55CF4|
|Date (UTC+05:30)||Sept 16, 2021|
|Name of the report||Provable Solvency Report #89 – Aug 2021|
|SHA-256 Hash of the report||F27DCCCCFCDF72633828C2CFE2E73B772B91E4DAC9F8F74239754902ABBF6648|
|Date (UTC+05:30)||Aug 17, 2021|
|Name of the report||Provable Solvency Report #88 – Jul 2021|
|SHA-256 Hash of the report||886C5E5BA5EF164FDCC9F7B6C7B9998BF9B1991C374718D3A03CBB1A287F0CE7|
|Date (UTC+05:30)||Jul 13, 2021|
|Name of the report||Provable Solvency Report #87 – Jun 2021|
|SHA-256 Hash of the report||49345A73077D4C53C3B57488CD2CE415E8006F26C1C17966BA317338D3CA647B|
|Date (UTC+05:30)||Jun 15, 2021|
|Name of the report||Provable Solvency Report #86 – May 2021|
|SHA-256 Hash of the report||96E72B4701A1026CA1535F866C230D71BAC0DF2D361B47A2C3FDE5CF65092675|
|Date (UTC+05:30)||May 18, 2021|
|Name of the report||Provable Solvency Report #85 – Apr 2021|
|SHA-256 Hash of the report||CC2B9ABE7859A998DE644C6593ECA690AEEDFF8F1D62898FE79580454232C292|
|Date (UTC+05:30)||Apr 15, 2021|
|Name of the report||Provable Solvency Report #84 – Mar 2021|
|SHA-256 Hash of the report||49C716E7432BF45F1C399FA13E173D4EAA38987493B6863098D0BBB928BD931A|
|Date (UTC+05:30)||Mar 16, 2021|
|Name of the report||Provable Solvency Report #83 – Feb 2021|
|SHA-256 Hash of the report||E35D5C054513A4DBF75CD6B5A7D72696C7B8BE4D9FC65E69E52DEBE9B9411C63|
|Date (UTC+05:30)||Feb 17, 2021|
|Name of the report||Provable Solvency Report #82 – Jan 2021|
|SHA-256 Hash of the report||FCDBCA550069A88594B7DDB834A02C1CE9F3150C70FF8F89D49158BF06C8AD04|
|Date (UTC+05:30)||Jan 15, 2021|
|Name of the report||Provable Solvency Report #81 – Dec 2020|
|SHA-256 Hash of the report||20ded532d9885d256b294f5a644661a028a7487db8d41e77323061d5dc590dae|
|Date (UTC+05:30)||Dec 15, 2020|
Copy the entire contents of the solvency report (including any leading or trailing spaces or blank lines) into the SHA-256 generator and calculate the SHA-256 hash of the report. You can confirm the hash generated matches with the SHA-256 hash of the report field.
You will find the hash generated in the previous step matches the hash in the “Hex” reference (at the top of the page below a heading saying “Data Embedded in Transaction with Unknown Protocol”) of the transaction published on the Bitcoin blockchain.
The provable solvency report consists of balances attached to SHA-1 hashes for each customer account.
You will need the timestamp from the Solvency Report (10 digit number on the first row of the report) followed directly by the API authentication cookie from your Coinfloor account.
API authentication cookie (API Key): 9BTa7M0Z/Mrk6tFMJwXXXXXXXXXX
Input to calculate you SHA1 Hash is: 1579519XXX9BTa7M0Z/Mrk6tFMJwXXXXXXXXXX
We believe that this approach is the best way to achieve maximum accountability whilst retaining privacy for our clients. We welcome your feedback and hope that in time, other exchanges will also help safeguard client funds by providing proof of solvency reports to their users on a regular basis.