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
Apr 23, 2018 Provable Solvency Report #49 – April 2018 5,246.4536 XBT 9343469d75a98a4ffefcbc48edc8bd84cf8f025a2ffa0f305548f87947c8dddc
c6c43ff810d3512ec5f7b6bd1f53cc5a3bdc9f28110b5f5c6ced07bb87a0e962
Copy to clipboard
Mar 29, 2018 Provable Solvency Report #48 – March 2018 5,445.3368 XBT a2bf71f04d0ee1efd05e196230b2842477711779076f67b4c330f49dc823289e
fb6795fb5766d4b500c696c11bbfc63f42bc438e44026e18624618b6b9faf610
Copy to clipboard
Feb 28, 2018 Provable Solvency Report #47 – February 2018 5,249.9435 XBT 9f3af0656361b95a63b48048aad212dac8f8c5055353beaaabbde24d979cdcf2
7a99984e31485fabc7f6224dc9cc5eaf573ef04bcaf571017caff2e1eee750a1
Copy to clipboard
Jan 31, 2018 Provable Solvency Report #46 – January 2018 5,338.5714 XBT b32cc17288e563e24b35a52a44da212aeef853d1b3b1df0aa92dcaf683ef35c3
cd6b491a8850ada9ee0a8271327f1f313e1cab5cba36bc9a4a73484a50364419
Copy to clipboard
Dec 22, 2017 Provable Solvency Report #45 – December 2017 5,558.6370 XBT a90073e1572eb77abf4e023b819416d0579ed8d6bd85b9a77e7fb377aa8bc06b
f26cec99157799d2c5a4a4d104f56b033c5e4f46c7f735d2a8917e19381458be
Copy to clipboard
Nov 30, 2017 Provable Solvency Report #44 – November 2017 5,907.1208 XBT d894881b97887730d4d1d29b508a51167cc36d2759cc7a8094d3c6efe30983fa
d537d970bc04fcde70d503f610872862384f50e66e8d217e16b7a16e78fff6a3
Copy to clipboard
Oct 25, 2017 Provable Solvency Report #43 – October 2017 5,026.6256 XBT a35c4581ae835ad28066a2e2be6c2b1b8439439713f7d4929f83072765de9175
5ac9bc29148a7c82d10452921e780f3f4e3c9f2128f507df9b4d101b4a7c86bb
Copy to clipboard
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
Transaction ID
c6c43ff810d3512ec5f7b6bd1f53cc5a3bdc9f28110b5f5c6ced07bb87a0e962
Name of the report Provable Solvency Report #49 – April 2018
Amount 5,246.4536 XBT
SHA-256 Hash of the report 9343469d75a98a4ffefcbc48edc8bd84cf8f025a2ffa0f305548f87947c8dddc
Date (UTC+05:30) Apr 23, 2018
Transaction ID
fb6795fb5766d4b500c696c11bbfc63f42bc438e44026e18624618b6b9faf610
Name of the report Provable Solvency Report #48 – March 2018
Amount 5,445.3368 XBT
SHA-256 Hash of the report a2bf71f04d0ee1efd05e196230b2842477711779076f67b4c330f49dc823289e
Date (UTC+05:30) Mar 29, 2018
Transaction ID
7a99984e31485fabc7f6224dc9cc5eaf573ef04bcaf571017caff2e1eee750a1
Name of the report Provable Solvency Report #47 – February 2018
Amount 5,249.9435 XBT
SHA-256 Hash of the report 9f3af0656361b95a63b48048aad212dac8f8c5055353beaaabbde24d979cdcf2
Date (UTC+05:30) Feb 28, 2018
Transaction ID
cd6b491a8850ada9ee0a8271327f1f313e1cab5cba36bc9a4a73484a50364419
Name of the report Provable Solvency Report #46 – January 2018
Amount 5,338.5714 XBT
SHA-256 Hash of the report b32cc17288e563e24b35a52a44da212aeef853d1b3b1df0aa92dcaf683ef35c3
Date (UTC+05:30) Jan 31, 2018
Transaction ID
f26cec99157799d2c5a4a4d104f56b033c5e4f46c7f735d2a8917e19381458be
Name of the report Provable Solvency Report #45 – December 2017
Amount 5,558.6370 XBT
SHA-256 Hash of the report a90073e1572eb77abf4e023b819416d0579ed8d6bd85b9a77e7fb377aa8bc06b
Date (UTC+05:30) Dec 22, 2017
Transaction ID
d537d970bc04fcde70d503f610872862384f50e66e8d217e16b7a16e78fff6a3
Name of the report Provable Solvency Report #44 – November 2017
Amount 5,907.1208 XBT
SHA-256 Hash of the report d894881b97887730d4d1d29b508a51167cc36d2759cc7a8094d3c6efe30983fa
Date (UTC+05:30) Nov 30, 2017
Transaction ID
5ac9bc29148a7c82d10452921e780f3f4e3c9f2128f507df9b4d101b4a7c86bb
Name of the report Provable Solvency Report #43 – October 2017
Amount 5,026.6256 XBT
SHA-256 Hash of the report a35c4581ae835ad28066a2e2be6c2b1b8439439713f7d4929f83072765de9175
Date (UTC+05:30) Oct 25, 2017
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

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.
Coinfloor CFUK logo

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.