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|
|Sep 22, 2016||Provable Solvency Report #30 – September 2016||6,696.4111 XBT||36f1fab212f11c4660f7ec86f1fa5d57825550fdec5bf39388f1b6ab5707d3ff||
0a27f380fd63f9ea20338c7df84df9d67079035732e5aaecdf5c03d78fe48dd4Copy to clipboard
|Aug 24, 2016||Provable Solvency Report #29 – August 2016||6,098.5874 XBT||146e336baac80ccbe8c4784ecf07374bb33bb9fa81bd6529e41f9bb563c22d92||
141244f6fe25664029526124c8833fe3c3f9f32fcd2c3e37c4847c46e9e65a6dCopy to clipboard
|Jul 28, 2016||Provable Solvency Report #28 – July 2016||5,807.6364 XBT||2403e7a560ea9039b83bf8434f0828e7db759852e7a20df388dd4ef7aa628974||
29a7727b8b85902a59a0e0bb15227eddd0abf3583ae66e5eb0909c4362254971Copy to clipboard
|Jun 29, 2016||Provable Solvency Report #27 – June 2016||5,082.6582 XBT||7d643461e23278e6caef6351029b7b4334e0911f781b157c8270f057783deed8||
45fe6923d0cd4e6b23827188b19458066328aba671f9e575d667eeafce369f90Copy to clipboard
|May 19, 2016||Provable Solvency Report #26 – May 2016||8,712.5213 XBT||da023372865dc834b92093c88cdb53e18d1f3c99f544eee67cb64ad5d5e125ad||
5e4ad76ac1e6925d10746930f77a94d08746443182b412ea2d17b4c1358acaafCopy to clipboard
|Apr 26, 2016||Provable Solvency Report #25 – April 2016||8,381.2242 XBT||0d6a34438a0d598ed555d7cb666d05d2207dd5438782e7fe2c1214ba000fbc72||
5bd4a5f91d2b4907776c78825f04faaa0ec82ee634af7099e67285304f01158cCopy to clipboard
|Mar 23, 2016||Provable Solvency Report #24 – March 2016||8,322.2861 XBT||a31841239bbd31b76e0322288fd89e31eece750912ad3bf8081ceae5a67b9052||
b6739ec517db29917535b9e1d6152dda6e97075458718ad871f844813e17e25dCopy to clipboard
|Feb 24, 2016||Provable Solvency Report #23 – February 2016||8,043.8393 XBT||4d964eaf1a0bcc26473c917306375027bf1ef1e1250ea5bb817b7f1f657db764||
a60dd6841477ac3d9add9cf4ddb365911c8eba26484577f0227a607a4a4e5532Copy to clipboard
|Jan 28, 2016||Provable Solvency Report #22 – January 2016||7,890.9055 XBT||7b76c580fa788b94b7518e2acbb92dfd8fc09fda58ddb39422d4399c0d5b9acf||
22bbaefc0f630b2b5efc383db486db05636732d2bb5793e52c19ba7f10d9a66cCopy to clipboard
|Dec 17, 2015||Provable Solvency Report #21 – December 2015||8,715.8524 XBT||74f74bdb44b18f4ad362c2d09f24d6f767a8e2765982a6bf2c62d68b6bfed211||
16d8d0364b44178f4e2b4b6663beb4415b6d7377bd54696a188f85379944b94eCopy to clipboard
|Name of the report||Provable Solvency Report #30 – September 2016|
|SHA-256 Hash of the report||36f1fab212f11c4660f7ec86f1fa5d57825550fdec5bf39388f1b6ab5707d3ff|
|Date (UTC+05:30)||Sep 22, 2016|
|Name of the report||Provable Solvency Report #29 – August 2016|
|SHA-256 Hash of the report||146e336baac80ccbe8c4784ecf07374bb33bb9fa81bd6529e41f9bb563c22d92|
|Date (UTC+05:30)||Aug 24, 2016|
|Name of the report||Provable Solvency Report #28 – July 2016|
|SHA-256 Hash of the report||2403e7a560ea9039b83bf8434f0828e7db759852e7a20df388dd4ef7aa628974|
|Date (UTC+05:30)||Jul 28, 2016|
|Name of the report||Provable Solvency Report #27 – June 2016|
|SHA-256 Hash of the report||7d643461e23278e6caef6351029b7b4334e0911f781b157c8270f057783deed8|
|Date (UTC+05:30)||Jun 29, 2016|
|Name of the report||Provable Solvency Report #26 – May 2016|
|SHA-256 Hash of the report||da023372865dc834b92093c88cdb53e18d1f3c99f544eee67cb64ad5d5e125ad|
|Date (UTC+05:30)||May 19, 2016|
|Name of the report||Provable Solvency Report #25 – April 2016|
|SHA-256 Hash of the report||0d6a34438a0d598ed555d7cb666d05d2207dd5438782e7fe2c1214ba000fbc72|
|Date (UTC+05:30)||Apr 26, 2016|
|Name of the report||Provable Solvency Report #24 – March 2016|
|SHA-256 Hash of the report||a31841239bbd31b76e0322288fd89e31eece750912ad3bf8081ceae5a67b9052|
|Date (UTC+05:30)||Mar 23, 2016|
|Name of the report||Provable Solvency Report #23 – February 2016|
|SHA-256 Hash of the report||4d964eaf1a0bcc26473c917306375027bf1ef1e1250ea5bb817b7f1f657db764|
|Date (UTC+05:30)||Feb 24, 2016|
|Name of the report||Provable Solvency Report #22 – January 2016|
|SHA-256 Hash of the report||7b76c580fa788b94b7518e2acbb92dfd8fc09fda58ddb39422d4399c0d5b9acf|
|Date (UTC+05:30)||Jan 28, 2016|
|Name of the report||Provable Solvency Report #21 – December 2015|
|SHA-256 Hash of the report||74f74bdb44b18f4ad362c2d09f24d6f767a8e2765982a6bf2c62d68b6bfed211|
|Date (UTC+05:30)||Dec 17, 2015|
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.