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|
|June 11, 2020||Provable Solvency Report #75 – Jun 2020||3,627.1768 XBT||FC08526659433B219E2DBDC53E6BD0F21E76C4BAC10BC0954B3EA3F30EB1646E||
9d668ea11483f2f8dd7e2dc2b6b9e3bd7a130d0d7d635892e2eaaee6dcf6a3dfCopy to clipboard
|May 13, 2020||Provable Solvency Report #74 – May 2020||3,756.9073 XBT||C60AB7D4A0CF6E10B948CCD7CD3B80C14E1D2E99F47419A4E52600C09BC1018C||
37fb654634c03b96393442810c5c747c4fcc7b01f27c51d158055d0053b82646Copy to clipboard
|Apr 15, 2020||Provable Solvency Report #73 – April 2020||3,667.3903 XBT||456E7C8A63EB0E30CD1A47495FF7E2880FA933B9EFF74653FEA8C4A336A88B48||
f3c9e47b3f963cee0038cfa18f1f98e92a8e9e8e476c57d5f3bb6eba99eb394fCopy to clipboard
|Mar 13, 2020||Provable Solvency Report #72 – March 2020||3,668.9920 XBT||B161B2DF5BFB7BC88AC4344942DFB89808F29F3262D57714E7D9392E8841555D||
f4121529e8f653b4766694c54c39f7c932d642541ff6e6613164f705f7ea1212Copy to clipboard
|Feb 17, 2020||Provable Solvency Report #71 – February 2020||3,682.9458 XBT||8AB00AB9181600EC44FA6972B267337F218D1D5E10CFBB091F31B9CFB6E7F802||
8ea4cdd4a9759846c1ed7a4ba99fdd280b4ca9c69c7d3a298909549df8b12548Copy to clipboard
|Jan 20, 2020||Provable Solvency Report #70 – January 2020||3,815.4219 XBT||1fa6c926cfda1639cd6d32e56c8002b83ca4b5eefc2cf4de4ea885bd0a3277bd||
b18053a66d1f0577231662596059f39e0bedaaa7fd42942a51e7e1c65a19c090Copy to clipboard
|Dec 11, 2019||Provable Solvency Report #69 – December 2019||3,778.6544 XBT||EAA1319D7706E3F02E74635E8F0D067B53E9112FDB35E53CA28CF7457C30B10F||
2129f845fb83b8ede7fbe35da5cb5fe8447f372aee4af2ec97a22dff7a615ef6Copy to clipboard
|Nov 14, 2019||Provable Solvency Report #68 – November 2019||3,961.8415 XBT||766332ADFED1E39AC1FE2A2FB4196D7221C46385635F1E95AE41E353359F3462||
35c90fa16acd63500f3a6c06ced2547d2f020450fa5fa2e87e3a9bee5773835cCopy to clipboard
|Oct 24, 2019||Provable Solvency Report #67 – October 2019||3,908.6071 XBT||D416EBDE74A254F4E6DA2828C2DAFDDB5DC036C69AD7114ABF54F57DD1B1686D||
c354df2e5d6a7c8fc77b28dfbbcaf70dc6beae755bbdeb877d2785b2343208d6Copy to clipboard
|Sep 30, 2019||Provable Solvency Report #66 – September 2019||3,907.8566 XBT||0F7C866DC215B965067F7E01828696216F19141CA11638AD21C7272E1879404C||
737282fa27d66208b53541a78b7c9a31c8e7bd7a8d52ad87de2498421ce0ea95Copy to clipboard
|Name of the report||Provable Solvency Report #75 – Jun 2020|
|SHA-256 Hash of the report||FC08526659433B219E2DBDC53E6BD0F21E76C4BAC10BC0954B3EA3F30EB1646E|
|Date (UTC+05:30)||June 11, 2020|
|Name of the report||Provable Solvency Report #74 – May 2020|
|SHA-256 Hash of the report||C60AB7D4A0CF6E10B948CCD7CD3B80C14E1D2E99F47419A4E52600C09BC1018C|
|Date (UTC+05:30)||May 13, 2020|
|Name of the report||Provable Solvency Report #73 – April 2020|
|SHA-256 Hash of the report||456E7C8A63EB0E30CD1A47495FF7E2880FA933B9EFF74653FEA8C4A336A88B48|
|Date (UTC+05:30)||Apr 15, 2020|
|Name of the report||Provable Solvency Report #72 – March 2020|
|SHA-256 Hash of the report||B161B2DF5BFB7BC88AC4344942DFB89808F29F3262D57714E7D9392E8841555D|
|Date (UTC+05:30)||Mar 13, 2020|
|Name of the report||Provable Solvency Report #71 – February 2020|
|SHA-256 Hash of the report||8AB00AB9181600EC44FA6972B267337F218D1D5E10CFBB091F31B9CFB6E7F802|
|Date (UTC+05:30)||Feb 17, 2020|
|Name of the report||Provable Solvency Report #70 – January 2020|
|SHA-256 Hash of the report||1fa6c926cfda1639cd6d32e56c8002b83ca4b5eefc2cf4de4ea885bd0a3277bd|
|Date (UTC+05:30)||Jan 20, 2020|
|Name of the report||Provable Solvency Report #69 – December 2019|
|SHA-256 Hash of the report||EAA1319D7706E3F02E74635E8F0D067B53E9112FDB35E53CA28CF7457C30B10F|
|Date (UTC+05:30)||Dec 11, 2019|
|Name of the report||Provable Solvency Report #68 – November 2019|
|SHA-256 Hash of the report||766332ADFED1E39AC1FE2A2FB4196D7221C46385635F1E95AE41E353359F3462|
|Date (UTC+05:30)||Nov 14, 2019|
|Name of the report||Provable Solvency Report #67 – October 2019|
|SHA-256 Hash of the report||D416EBDE74A254F4E6DA2828C2DAFDDB5DC036C69AD7114ABF54F57DD1B1686D|
|Date (UTC+05:30)||Oct 24, 2019|
|Name of the report||Provable Solvency Report #66 – September 2019|
|SHA-256 Hash of the report||0F7C866DC215B965067F7E01828696216F19141CA11638AD21C7272E1879404C|
|Date (UTC+05:30)||Sep 30, 2019|
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.