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|
|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
|Aug 21, 2018||Provable Solvency Report #53 – August 2018||4,785.5339 XBT||9C0A664E610C1267C36F10521C48D590AD95C1F6C59A172104CA9EEF06F62739||
76212aee6b69e9c06e386712c66415893f1b82893c56d9949ee1a1bf0e37921bCopy to clipboard
|Jul 17, 2018||Provable Solvency Report #52 – July 2018||5,162.7939 XBT||6C10D76FB401D3C91D75894ABF216D55B9F834031E2AFE75FA1582778BBF6B75||
bc1a27916242f69d59ae1296d28e3407c2e2038820ebc1de83bf805a16db4bacCopy to clipboard
|Jun 27, 2018||Provable Solvency Report #51 – June 2018||5,460.3197 XBT||ba595a76394992150b7ba47e821e852596fa0f4d1c78c5f517c993bb62c13f6e||
19b2f3a11d6b2299bfcd85f392d6a25f051c5487b9731c079ab94161117bf9cbCopy to clipboard
|May 25, 2018||Provable Solvency Report #50 – May 2018||5,431.2487 XBT||25ec8d127c930bd29b4521a8d64a74a5fd4415b0c97188e173ff88719c62ec42||
7574b8e28bba481f00c839f0064f5b32a1aba19a805aa6a00e00ff340d0853a4Copy to clipboard
|Apr 23, 2018||Provable Solvency Report #49 – April 2018||5,246.4536 XBT||9343469d75a98a4ffefcbc48edc8bd84cf8f025a2ffa0f305548f87947c8dddc||
c6c43ff810d3512ec5f7b6bd1f53cc5a3bdc9f28110b5f5c6ced07bb87a0e962Copy to clipboard
|Mar 29, 2018||Provable Solvency Report #48 – March 2018||5,445.3368 XBT||a2bf71f04d0ee1efd05e196230b2842477711779076f67b4c330f49dc823289e||
fb6795fb5766d4b500c696c11bbfc63f42bc438e44026e18624618b6b9faf610Copy to clipboard
|Feb 28, 2018||Provable Solvency Report #47 – February 2018||5,249.9435 XBT||9f3af0656361b95a63b48048aad212dac8f8c5055353beaaabbde24d979cdcf2||
7a99984e31485fabc7f6224dc9cc5eaf573ef04bcaf571017caff2e1eee750a1Copy to clipboard
|Jan 31, 2018||Provable Solvency Report #46 – January 2018||5,338.5714 XBT||b32cc17288e563e24b35a52a44da212aeef853d1b3b1df0aa92dcaf683ef35c3||
cd6b491a8850ada9ee0a8271327f1f313e1cab5cba36bc9a4a73484a50364419Copy to clipboard
|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|
|Name of the report||Provable Solvency Report #53 – August 2018|
|SHA-256 Hash of the report||9C0A664E610C1267C36F10521C48D590AD95C1F6C59A172104CA9EEF06F62739|
|Date (UTC+05:30)||Aug 21, 2018|
|Name of the report||Provable Solvency Report #52 – July 2018|
|SHA-256 Hash of the report||6C10D76FB401D3C91D75894ABF216D55B9F834031E2AFE75FA1582778BBF6B75|
|Date (UTC+05:30)||Jul 17, 2018|
|Name of the report||Provable Solvency Report #51 – June 2018|
|SHA-256 Hash of the report||ba595a76394992150b7ba47e821e852596fa0f4d1c78c5f517c993bb62c13f6e|
|Date (UTC+05:30)||Jun 27, 2018|
|Name of the report||Provable Solvency Report #50 – May 2018|
|SHA-256 Hash of the report||25ec8d127c930bd29b4521a8d64a74a5fd4415b0c97188e173ff88719c62ec42|
|Date (UTC+05:30)||May 25, 2018|
|Name of the report||Provable Solvency Report #49 – April 2018|
|SHA-256 Hash of the report||9343469d75a98a4ffefcbc48edc8bd84cf8f025a2ffa0f305548f87947c8dddc|
|Date (UTC+05:30)||Apr 23, 2018|
|Name of the report||Provable Solvency Report #48 – March 2018|
|SHA-256 Hash of the report||a2bf71f04d0ee1efd05e196230b2842477711779076f67b4c330f49dc823289e|
|Date (UTC+05:30)||Mar 29, 2018|
|Name of the report||Provable Solvency Report #47 – February 2018|
|SHA-256 Hash of the report||9f3af0656361b95a63b48048aad212dac8f8c5055353beaaabbde24d979cdcf2|
|Date (UTC+05:30)||Feb 28, 2018|
|Name of the report||Provable Solvency Report #46 – January 2018|
|SHA-256 Hash of the report||b32cc17288e563e24b35a52a44da212aeef853d1b3b1df0aa92dcaf683ef35c3|
|Date (UTC+05:30)||Jan 31, 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.