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|
|Jun 18, 2019||Provable Solvency Report #63 – June 2019||3,855.4261 XBT||7EB79875D7896EBBE511F20382A3F9F8F64E9BBCAEBDD34975FCF766000377F1||
33d4d4d18705a0011cba593bce3cde564a41e53c48463ca0e69838e0e1208cf1Copy to clipboard
|May 29, 2019||Provable Solvency Report #62 – May 2019||4,121.1897 XBT||64BF0AAC619BE4A5E4D848D6055EA41554D3ED265AFEFB2D30AB2ADBED100C7C||
c91158b6dad7794072d2a6d06ca3e8496d81e564ad2d1c8850ae582760d1fe07Copy to clipboard
|Apr 23, 2019||Provable Solvency Report #61 – April 2019||4,373.9570 XBT||61E9889A1AE35FB8B7C262F3344B82B2B835929A4B522D9109A349ED6554E466||
79c0383df1635ef6f95772a746754c250c229137f72887510703104df789e6d6Copy to clipboard
|Mar 19, 2019||Provable Solvency Report #60 – March 2019||4,532.9639 XBT||76317D6B10758EB9D3ED459482323FD5C7F1AAD5841C6C0C98C26CF4036FB143||
64289aa946d94298a796e4c0769cc8b9b5bda180c6060d7efa6e867f86fcaad1Copy to clipboard
|Feb 27, 2019||Provable Solvency Report #59 – February 2019||4,317.9491 XBT||95D273CBBA0FCCCC53BDE91AF6891A95C4BC3793A4DDCBE93CD352CA036A95D4||
2b51089d23f9d9d8f062213310814e4c8d6bb85f8647492aae2b19f6c2abe0c7Copy to clipboard
|Jan 28, 2019||Provable Solvency Report #58 – January 2019||4,309.4410 XBT||7953449A3037AE8D9A61276C844F3B54D53DBBB6C96CD2AD974420894B7BDAF3||
6e2d4e7d2cd86c43e59ab43a057a740eb4498d5560b6b53b1fbd7740b27e666eCopy to clipboard
|Dec 27, 2018||Provable Solvency Report #57 – December 2018||4,448.8289 XBT||2BF69C4FA152B8851D18FD4E01FEF1DED41F39EC51FAE2A98D84301DF9B82E0A||
4a4be973c0bc6c694b43b7ffcb49a17b25efeebbdc3b5031c05cecb6abaf1c92Copy to clipboard
|Nov 28, 2018||Provable Solvency Report #56 – November 2018||4,446.1628 XBT||300820EF379C78C36021F4D8618D747E06E7E1FA00BEC44F77FFFA65C94386E9||
8d6c62b1d495d999b0d0332856ff051439a4cf6aafefbe3da89d11aa081eb61aCopy to clipboard
|Oct 23, 2018||Provable Solvency Report #55 – October 2018||4,460.1497 XBT||7BC72810C8718D12AF1EB53014EBC07612606F0DD4804E435CB0FA9846646C60||
388349c4f871ac07653e61d3592244eacc509d6db7282416f3379c5d2af3e806Copy to clipboard
|Sep 17, 2018||UK Provable Solvency report #54||4,588.8802 XBT||A1B378359A88DB417F6EFE0C6C7CCE8CA1E223005AF243A9B78A3CF0EEF44448||
4d873b5c1f240a27ad724c26c411efb46320f4592e341f0270d1153ef3c82c71Copy to clipboard
|Name of the report||Provable Solvency Report #63 – June 2019|
|SHA-256 Hash of the report||7EB79875D7896EBBE511F20382A3F9F8F64E9BBCAEBDD34975FCF766000377F1|
|Date (UTC+05:30)||Jun 18, 2019|
|Name of the report||Provable Solvency Report #62 – May 2019|
|SHA-256 Hash of the report||64BF0AAC619BE4A5E4D848D6055EA41554D3ED265AFEFB2D30AB2ADBED100C7C|
|Date (UTC+05:30)||May 29, 2019|
|Name of the report||Provable Solvency Report #61 – April 2019|
|SHA-256 Hash of the report||61E9889A1AE35FB8B7C262F3344B82B2B835929A4B522D9109A349ED6554E466|
|Date (UTC+05:30)||Apr 23, 2019|
|Name of the report||Provable Solvency Report #60 – March 2019|
|SHA-256 Hash of the report||76317D6B10758EB9D3ED459482323FD5C7F1AAD5841C6C0C98C26CF4036FB143|
|Date (UTC+05:30)||Mar 19, 2019|
|Name of the report||Provable Solvency Report #59 – February 2019|
|SHA-256 Hash of the report||95D273CBBA0FCCCC53BDE91AF6891A95C4BC3793A4DDCBE93CD352CA036A95D4|
|Date (UTC+05:30)||Feb 27, 2019|
|Name of the report||Provable Solvency Report #58 – January 2019|
|SHA-256 Hash of the report||7953449A3037AE8D9A61276C844F3B54D53DBBB6C96CD2AD974420894B7BDAF3|
|Date (UTC+05:30)||Jan 28, 2019|
|Name of the report||Provable Solvency Report #57 – December 2018|
|SHA-256 Hash of the report||2BF69C4FA152B8851D18FD4E01FEF1DED41F39EC51FAE2A98D84301DF9B82E0A|
|Date (UTC+05:30)||Dec 27, 2018|
|Name of the report||Provable Solvency Report #56 – November 2018|
|SHA-256 Hash of the report||300820EF379C78C36021F4D8618D747E06E7E1FA00BEC44F77FFFA65C94386E9|
|Date (UTC+05:30)||Nov 28, 2018|
|Name of the report||Provable Solvency Report #55 – October 2018|
|SHA-256 Hash of the report||7BC72810C8718D12AF1EB53014EBC07612606F0DD4804E435CB0FA9846646C60|
|Date (UTC+05:30)||Oct 23, 2018|
|Name of the report||UK Provable Solvency report #54|
|SHA-256 Hash of the report||A1B378359A88DB417F6EFE0C6C7CCE8CA1E223005AF243A9B78A3CF0EEF44448|
|Date (UTC+05:30)||Sep 17, 2018|
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.