What are Bitcoin Audits?

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.

Make Exchanges Prove their Reserves

Powered by the Bitcoin Blockchain

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.

Maximum Accountability since 2014

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.

Report Published Every Month

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.

All published Provable Solvency Reports

Need help? Email us at [email protected]

Date (UTC+05:30) name of the report Amount SHA-256 Hash of the report Transaction ID
Feb 28, 2017 Provable Solvency Report #35 – February 2017 9,233.9805 XBT 24ac5217a7648c9b717b110072fa795b3e48b0c0f072772dd34404b2c25a64ea
0b57be09e2ff03f4408e931b160230622966dcc515e7561e95f0035da053c0e
Copy to clipboard
Jan 30, 2017 Provable Solvency Report #34 – January 2017 7,590.4195 XBT 9ff020ba1187401c80c2fdf8184e4a90f6371746ac5e97d8495e7c181ebd2467
781a1d44f0ee0d8de8f34f3f1e4fe509ee4ecbb07a0e0a21e985fffc130d2c0f
Copy to clipboard
Dec 20, 2016 Provable Solvency Report #33 – December 2016 6,193.0988 XBT 74eca22a2790bcecbf10e690bef09c48d41c5248b86a57d9ba7903df3513c1c5
5185b7374eec400d9f8b70ebe3787aad2b54fdfcf1766b9d6bdb45ea98e0514b
Copy to clipboard
Nov 28, 2016 Provable Solvency Report #32 – November 2016 5,840.9455 XBT 2f3e5539a6d32ee8f0d9a7ca62d2ee5ad90ced46e74e8c9cca07cc7c360be285
325d3bec9b3cd17b8966c06513cef64bfa023d192058b522b7ba0fdb2f5e7398
Copy to clipboard
Oct 26, 2016 Provable Solvency Report #31 – October 2016 7,455.5317 XBT d14c5370812ff2896dd83a889d93f692e7e32c770ecdac0eade2470bf752f8d3
d14c5370812ff2896dd83a889d93f692e7e32c770ecdac0eade2470bf752f8d3
Copy to clipboard
Sep 22, 2016 Provable Solvency Report #30 – September 2016 6,696.4111 XBT 36f1fab212f11c4660f7ec86f1fa5d57825550fdec5bf39388f1b6ab5707d3ff
0a27f380fd63f9ea20338c7df84df9d67079035732e5aaecdf5c03d78fe48dd4
Copy to clipboard
Aug 24, 2016 Provable Solvency Report #29 – August 2016 6,098.5874 XBT 146e336baac80ccbe8c4784ecf07374bb33bb9fa81bd6529e41f9bb563c22d92
141244f6fe25664029526124c8833fe3c3f9f32fcd2c3e37c4847c46e9e65a6d
Copy to clipboard
Jul 28, 2016 Provable Solvency Report #28 – July 2016 5,807.6364 XBT 2403e7a560ea9039b83bf8434f0828e7db759852e7a20df388dd4ef7aa628974
29a7727b8b85902a59a0e0bb15227eddd0abf3583ae66e5eb0909c4362254971
Copy to clipboard
Jun 29, 2016 Provable Solvency Report #27 – June 2016 5,082.6582 XBT 7d643461e23278e6caef6351029b7b4334e0911f781b157c8270f057783deed8
45fe6923d0cd4e6b23827188b19458066328aba671f9e575d667eeafce369f90
Copy to clipboard
May 19, 2016 Provable Solvency Report #26 – May 2016 8,712.5213 XBT da023372865dc834b92093c88cdb53e18d1f3c99f544eee67cb64ad5d5e125ad
5e4ad76ac1e6925d10746930f77a94d08746443182b412ea2d17b4c1358acaaf
Copy to clipboard
Transaction ID
0b57be09e2ff03f4408e931b160230622966dcc515e7561e95f0035da053c0e
Name of the report Provable Solvency Report #35 – February 2017
Amount 9,233.9805 XBT
SHA-256 Hash of the report 24ac5217a7648c9b717b110072fa795b3e48b0c0f072772dd34404b2c25a64ea
Date (UTC+05:30) Feb 28, 2017
Transaction ID
781a1d44f0ee0d8de8f34f3f1e4fe509ee4ecbb07a0e0a21e985fffc130d2c0f
Name of the report Provable Solvency Report #34 – January 2017
Amount 7,590.4195 XBT
SHA-256 Hash of the report 9ff020ba1187401c80c2fdf8184e4a90f6371746ac5e97d8495e7c181ebd2467
Date (UTC+05:30) Jan 30, 2017
Transaction ID
5185b7374eec400d9f8b70ebe3787aad2b54fdfcf1766b9d6bdb45ea98e0514b
Name of the report Provable Solvency Report #33 – December 2016
Amount 6,193.0988 XBT
SHA-256 Hash of the report 74eca22a2790bcecbf10e690bef09c48d41c5248b86a57d9ba7903df3513c1c5
Date (UTC+05:30) Dec 20, 2016
Transaction ID
325d3bec9b3cd17b8966c06513cef64bfa023d192058b522b7ba0fdb2f5e7398
Name of the report Provable Solvency Report #32 – November 2016
Amount 5,840.9455 XBT
SHA-256 Hash of the report 2f3e5539a6d32ee8f0d9a7ca62d2ee5ad90ced46e74e8c9cca07cc7c360be285
Date (UTC+05:30) Nov 28, 2016
Transaction ID
d14c5370812ff2896dd83a889d93f692e7e32c770ecdac0eade2470bf752f8d3
Name of the report Provable Solvency Report #31 – October 2016
Amount 7,455.5317 XBT
SHA-256 Hash of the report d14c5370812ff2896dd83a889d93f692e7e32c770ecdac0eade2470bf752f8d3
Date (UTC+05:30) Oct 26, 2016
Transaction ID
0a27f380fd63f9ea20338c7df84df9d67079035732e5aaecdf5c03d78fe48dd4
Name of the report Provable Solvency Report #30 – September 2016
Amount 6,696.4111 XBT
SHA-256 Hash of the report 36f1fab212f11c4660f7ec86f1fa5d57825550fdec5bf39388f1b6ab5707d3ff
Date (UTC+05:30) Sep 22, 2016
Transaction ID
141244f6fe25664029526124c8833fe3c3f9f32fcd2c3e37c4847c46e9e65a6d
Name of the report Provable Solvency Report #29 – August 2016
Amount 6,098.5874 XBT
SHA-256 Hash of the report 146e336baac80ccbe8c4784ecf07374bb33bb9fa81bd6529e41f9bb563c22d92
Date (UTC+05:30) Aug 24, 2016
Transaction ID
29a7727b8b85902a59a0e0bb15227eddd0abf3583ae66e5eb0909c4362254971
Name of the report Provable Solvency Report #28 – July 2016
Amount 5,807.6364 XBT
SHA-256 Hash of the report 2403e7a560ea9039b83bf8434f0828e7db759852e7a20df388dd4ef7aa628974
Date (UTC+05:30) Jul 28, 2016
Transaction ID
45fe6923d0cd4e6b23827188b19458066328aba671f9e575d667eeafce369f90
Name of the report Provable Solvency Report #27 – June 2016
Amount 5,082.6582 XBT
SHA-256 Hash of the report 7d643461e23278e6caef6351029b7b4334e0911f781b157c8270f057783deed8
Date (UTC+05:30) Jun 29, 2016
Transaction ID
5e4ad76ac1e6925d10746930f77a94d08746443182b412ea2d17b4c1358acaaf
Name of the report Provable Solvency Report #26 – May 2016
Amount 8,712.5213 XBT
SHA-256 Hash of the report da023372865dc834b92093c88cdb53e18d1f3c99f544eee67cb64ad5d5e125ad
Date (UTC+05:30) May 19, 2016

Instructions For Validating A Solvency Report:

  1. Open the Provable Solvency Report file by clicking on the name of the report.
  2. Go to https://passwordsgenerator.net/sha256-hash-generator/ or to your SHA256sum calculating application.
  3. 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.

  4. Go to: The Bitcoin block explorer https://live.blockcypher.com/btc/ and search for the Transaction ID of the report.
  5. 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.

Instructions For Finding Your Account Balance Within A Solvency Report

The provable solvency report consists of balances attached to SHA-1 hashes for each customer account.

  1. You can generate your SHA-1 hash by using your local SHA1sum application or online calculators such as https://xorbin.com/tools/sha1-hash-calculator.
  2. 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.

    Example :

    Timestamp: 1579519XXX

    API authentication cookie (API Key): 9BTa7M0Z/Mrk6tFMJwXXXXXXXXXX

    Input to calculate you SHA1 Hash is: 1579519XXX9BTa7M0Z/Mrk6tFMJwXXXXXXXXXX

  3. Find the resulting hash in the solvency report. Your balance is shown on that line in satoshi units. 1 bitcoin = 100 000 000 satoshis. For your convenience, here is a link to a bitcoin unit converter: http://www.satoshi.24ex.com.

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.