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 block chain

The invention of the block chain 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 block chain.

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
Sep 29, 2017 Provable Solvency Report #42 – September 2017 5,900.6846 XBT 5dd6f40c93b1db05756e30288b1e9e027fdabeac9320ae1e737553356d78b77b
719dfbc49ca5a338012de68804fd6cf8c0ce7431d008537a3edea8f523a28c88
Copy to clipboard
Aug 31, 2017 Provable Solvency Report #41 – August 2017 5,324.1443 XBT ca9b391efa05105ee7ac38ce55c782904db213625e9c8c78ba1a23fa60619bcd
6440ab75455562924fab18c71bd6c393af56b7aa0b7474c7a8b811c3af0da33c
Copy to clipboard
Jul 28, 2017 Provable Solvency Report #40 – July 2017 5,216.3059 XBT 20170728514ca4d6cb04287fc3c1db0e5517ca086a2c395f0c34fad8677f7cf7b43933c6
27d73ad80ad69dd74e388f18f60dac03f327a79daef07c5afbeb8443bed71968
Copy to clipboard
Jun 29, 2017 Provable Solvency Report #39 – June 2017 7,509.3716 XBT 9e93994fb9e0d28404554e2cb25caed719421fde2bf52a4c125538c9aac8112d
d8db433ee015655963895abf734c257cad97b5c5da53991c8b4872b898560002
Copy to clipboard
May 24, 2017 Provable Solvency Report #38 – May 2017 6,749.3719 XBT c66dcdde432206d1701c94a0afdb0ac8ec174d892ab3e696a40988633e2132a5
f2633bdac628c594f6176775d9bc920ab18a49e73f26e02f28ce6df24dac5777
Copy to clipboard
Apr 27, 2017 Provable Solvency Report #37 – April 2017 7,454.8454 XBT f25d13c2f51e5fef270c90f6c2bb36991bfa92a06a3106c917624226b03caba3
729c3b600efa179e0fc67055b7953be1e3f7718c73eade77cbdec0c34a999af4
Copy to clipboard
Mar 22, 2017 Provable Solvency Report #36 – March 2017 7,825.2923 XBT ec8279bf42aa915ee43378587e53eec6c864e0d65260669f54d4bec7223e5629
2f3ce9d2a1a891abc3338c46bf6ba082424aaa6ac72e2a6ef7e9db8115064063
Copy to clipboard
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
Transaction ID
719dfbc49ca5a338012de68804fd6cf8c0ce7431d008537a3edea8f523a28c88
Name of the report Provable Solvency Report #42 – September 2017
Amount 5,900.6846 XBT
SHA-256 Hash of the report 5dd6f40c93b1db05756e30288b1e9e027fdabeac9320ae1e737553356d78b77b
Date (UTC+05:30) Sep 29, 2017
Transaction ID
6440ab75455562924fab18c71bd6c393af56b7aa0b7474c7a8b811c3af0da33c
Name of the report Provable Solvency Report #41 – August 2017
Amount 5,324.1443 XBT
SHA-256 Hash of the report ca9b391efa05105ee7ac38ce55c782904db213625e9c8c78ba1a23fa60619bcd
Date (UTC+05:30) Aug 31, 2017
Transaction ID
27d73ad80ad69dd74e388f18f60dac03f327a79daef07c5afbeb8443bed71968
Name of the report Provable Solvency Report #40 – July 2017
Amount 5,216.3059 XBT
SHA-256 Hash of the report 20170728514ca4d6cb04287fc3c1db0e5517ca086a2c395f0c34fad8677f7cf7b43933c6
Date (UTC+05:30) Jul 28, 2017
Transaction ID
d8db433ee015655963895abf734c257cad97b5c5da53991c8b4872b898560002
Name of the report Provable Solvency Report #39 – June 2017
Amount 7,509.3716 XBT
SHA-256 Hash of the report 9e93994fb9e0d28404554e2cb25caed719421fde2bf52a4c125538c9aac8112d
Date (UTC+05:30) Jun 29, 2017
Transaction ID
f2633bdac628c594f6176775d9bc920ab18a49e73f26e02f28ce6df24dac5777
Name of the report Provable Solvency Report #38 – May 2017
Amount 6,749.3719 XBT
SHA-256 Hash of the report c66dcdde432206d1701c94a0afdb0ac8ec174d892ab3e696a40988633e2132a5
Date (UTC+05:30) May 24, 2017
Transaction ID
729c3b600efa179e0fc67055b7953be1e3f7718c73eade77cbdec0c34a999af4
Name of the report Provable Solvency Report #37 – April 2017
Amount 7,454.8454 XBT
SHA-256 Hash of the report f25d13c2f51e5fef270c90f6c2bb36991bfa92a06a3106c917624226b03caba3
Date (UTC+05:30) Apr 27, 2017
Transaction ID
2f3ce9d2a1a891abc3338c46bf6ba082424aaa6ac72e2a6ef7e9db8115064063
Name of the report Provable Solvency Report #36 – March 2017
Amount 7,825.2923 XBT
SHA-256 Hash of the report ec8279bf42aa915ee43378587e53eec6c864e0d65260669f54d4bec7223e5629
Date (UTC+05:30) Mar 22, 2017
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

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 block chain.

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.