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]
| Transaction ID | 3a5860f230c9e56e784c2600c1116e846027dc9d8002e5240f17bed4b1d2eb60
|
| Name of the report | Provable Solvency Report #8 – November 2014 |
| Amount | 4072.1269 XBT |
| SHA-256 Hash of the report | f5a78eeb21fd68c2bcdb4f4b222f59285b6705de0af0e7cd1a8ec5ba86f9fa25 |
| Date (UTC+05:30) | Nov 19, 2014 |
| Transaction ID | 843dbafbc64bd83094e0d9c2668ae8ef9302a1c84c87ecf30799ff0c4115dae8
|
| Name of the report | Provable Solvency Report #7 – October 2014 |
| Amount | 2507.0061 XBT |
| SHA-256 Hash of the report | 6e57d304f290c51ea801e57b5593fe28bfc78df2e482bd1a2dab5b1af94264e5 |
| Date (UTC+05:30) | Oct 22, 2014 |
| Transaction ID | 66755a993681437e8e1a94d3ec4eabcd039a9c9bc0db76d465402c41c1d41330
|
| Name of the report | Provable Solvency Report #6 – September 2014 |
| Amount | 2356.378 XBT |
| SHA-256 Hash of the report | 0fda488186148304b7f1181ec9f01201566d98980e5f88e1c92e37e05dcceb65 |
| Date (UTC+05:30) | Sep 22, 2014 |
| Transaction ID | 74ca117615fd8f0fbaaf2e722e14b9123bc9061d72eb1ac236122f5971d4bda1
|
| Name of the report | Provable Solvency Report #5 – August 2014 |
| Amount | 1682.6508 XBT |
| SHA-256 Hash of the report | 2c167b8083f43c0fade21c81ad9cd7cc096992e1549d374c7c26a24b55b386b4 |
| Date (UTC+05:30) | Aug 18, 2014 |
| Transaction ID | 23efc10d505b536b332ffbec343389f39e4d4654b888fa1a30cb258c30c1f19f
|
| Name of the report | Provable Solvency Report #4 – July 2014 |
| Amount | 1193.2385 XBT |
| SHA-256 Hash of the report | 17fcd432d8ddb52829f6fc7937e7889ef0ad063fa90d743b2b6a320930e93048 |
| Date (UTC+05:30) | Jul 21, 2014 |
| Transaction ID | fc5d279f675bd697483cab7b02ca34bc89fc1ba6b190ba4e23f14a31a2e2dcac
|
| Name of the report | Provable Solvency Report #3 – June 2014 |
| Amount | 846.579 XBT |
| SHA-256 Hash of the report | 3a093308c48daa40e0201d290f76a762fab416c86e6052a58bb139cdef74e2ce |
| Date (UTC+05:30) | Jun 18, 2014 |
| Transaction ID | 635dc48a0841f30ad9723839aad90fdf6d7da12a623f2a7c1607c681b311026b
|
| Name of the report | Provable Solvency Report #2 – May 2014 |
| Amount | 292.75683101 XBT |
| SHA-256 Hash of the report | 4b4fc702ca3093a9b3dc3f026e8b6d35a70ffd8e183c5bf49c18db00ac97b8e4 |
| Date (UTC+05:30) | May 19, 2014 |
| Transaction ID | 573d096e74324683d9dc7e47af2a9df07b09bbd46c93f77bb4a4825ac685f595
|
| Name of the report | Coinfloor’s First Provable Solvency Report |
| Amount | 160.29654334 XBT |
| SHA-256 Hash of the report | 156f86147d4c0e9dbfb37bed290980807939c50df3a3b6e11e160ced4ce54c47 |
| Date (UTC+05:30) | Apr 17, 2014 |
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.
Example :
Timestamp: 1579519XXX
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.
