On March 19, 2019, Bitwise, a crypto asset management firm, filed a report with the U.S. Securities & Exchange Commission (SEC) in hopes of getting approval for their Bitcoin ETF. In the report, Bitwise asserted that 95% of exchange volume was fake and only 10 exchanges had "real volume." 

This report spread like wildfire throughout crypto Twitter.

Today, I'm joined by Nathaniel Whittemore, curator of Long Reads Sunday and coauthor of the 6,000-word mammoth on our blog entitled, "Crypto Market Cap: An In-Depth Review & Survey Of Emerging Alternatives." In this episode, we turn the tables as he interviews me about my take on the Bitwise report. 

Please enjoy this conversation between myself and Nathaniel Whittemore.

In this episode we discuss:

• The proper context for understanding the purpose of the Bitwise report
• A high-level overview of what was included in the report
• How the analysis is fair for a Bitcoin ETF, but probably not fair for considering the rest of the cryptosphere
• Why clearly defining terms and methodology matters
• A primer on crypto market data
• What the best exchanges have in common
• What the worst exchanges lack
• What crypto Twitter got wrong about the report
• How inaccurate crypto data is negatively impacting our everyday lives
• Why we must demand for accurate data from exchanges
• How the Nomics API is addressing the data problem
• The reasons why accurate data benefits everyone, including exchanges

Sponsor: Nomics’s Cryptocurrency Market Data API

The Nomics API offers squeaky clean and normalized primary source trade data offered through fast and modern endpoints. Instead of having to integrate with several crypto exchanges, you can get everything through one screaming fast fire hose. If you found that you or your developer have to spend too much time cleaning up and maintaining datasets & ingesting market cap data, instead of identifying opportunities. Or if you’re tired of interpolated data and want raw primary source trades delivered simply and consistently with top-notch support in SLAs, then check us out here.