The Coinbase summons is the case that taught crypto holders the IRS could reach inside an exchange. It is also widely misdescribed. The cleanest public account of what happened is in the First Circuit’s opinion in Harper v. Werfel, 118 F.4th 100 (1st Cir. 2024), which summarizes the district court’s 2017 order in detail. Everything below comes from that opinion unless I say otherwise.

The original request: everyone, 2013 through 2015

The IRS issued the John Doe summons to Coinbase in 2016. As first written, it sought information on all United States Coinbase accountholders who conducted digital currency transactions between 2013 and 2015.

It asked for a lot. The First Circuit lists the categories: complete user profiles, know-your-customer due diligence, documents regarding third-party access, transaction logs, records of payments processed, correspondence between Coinbase and its users, account or invoice statements, records of payments, and exception records produced by Coinbase’s anti-money-laundering system.

Coinbase opposed it. The IRS filed a petition to enforce the summons in the United States District Court for the Northern District of California. The case is United States v. Coinbase, Inc., No. 17-cv-01431-JSC.

The IRS narrowed it to the $20,000 users

The IRS then voluntarily narrowed the summons. As narrowed, it covered only users who had engaged in $20,000 worth of any one type of digital currency transaction (buying, selling, sending, or receiving) in any one calendar year.

The First Circuit reports that, as narrowed, the summons targeted 14,355 Coinbase accounts. The narrowed request still sought registration information including name, address, tax ID number, date of birth, account opening records, copies of passports or driver’s licenses, all wallet addresses and all public keys; know-your-customer due diligence; agreements giving third parties access; transaction activity including counterparties; correspondence; and all periodic statements or invoices.

Coinbase kept fighting. The court allowed a John Doe to intervene and permitted three amici to file briefs opposing the summons.

What the court enforced on November 28, 2017

The district court enforced the summons in part. It found the IRS justified, under IRC 7602(a), in obtaining:

  • Taxpayer ID number.
  • Name.
  • Date of birth.
  • Address.
  • Records of account activity, including transaction logs or other records identifying the date, amount and type of transaction (purchase, sale or exchange), the post-transaction balance, and the names of counterparties to the transaction.
  • All periodic statements of account or invoices, or the equivalent.

The order is reported at 2017 WL 5890052. Neither side appealed.

What the court refused

As narrowed by the court, the summons excluded records of know-your-customer diligence, agreements or instructions granting a third party access, control or transaction approval authority, and correspondence between Coinbase and the user or any third party.

The reasoning matters, because later courts repeated it. In the Kraken matter in 2021, a magistrate judge in the same district described the Coinbase ruling this way: the court “rejected the IRS’s position that similarly broad categories of information were relevant, and held that the IRS should first review basic user information and transaction histories before determining whether further subpoenas, either to the cryptocurrency exchange or to individual users, were necessary.”

That is the template. Identify the user. Get the transactions. Then decide who deserves a closer look.

Three misconceptions about the Coinbase summons

“They took everyone’s records.” Not as enforced. The original summons reached all U.S. accountholders with transactions from 2013 through 2015, but the IRS narrowed it to the $20,000 users before the court ruled, and the court then trimmed the categories further.

“Under $20,000 means I was never reportable.” The $20,000 line defined who the summons covered. It had nothing to do with whether you owed tax. A $2,000 gain was reportable in 2014 the same as a $200,000 gain.

“Sending to my own wallet was not a transaction.” For purposes of the summons, “sending” and “receiving” were transaction types counted toward the $20,000 threshold. A transfer between your own wallets is generally not a taxable disposition, but it could still put your account inside the summons scope and in the records the IRS received.

Why identity plus transactions is enough

People sometimes take comfort that the court kept out KYC files and correspondence. Do not. Name, tax ID, date of birth, address and a transaction log are exactly what the IRS needs to match a person to a return.

With those records, the IRS could see who bought, sold, sent or received at least $20,000 of one transaction type in a year, and then check whether that person reported anything. That is a matching exercise, not a mystery.

What happened next

In July 2019, the IRS announced in IR-2019-132 that it had begun mailing Letters 6173, 6174 and 6174-A to more than 10,000 taxpayers with virtual currency transactions, with names “obtained through various ongoing IRS compliance efforts.” The IRS did not say which efforts.

One recipient, James Harper, alleged that his 2019 letter referred to information the IRS obtained through the Coinbase summons, and he sued to make the IRS return or destroy his records. He lost in the district court and in the First Circuit, and the Supreme Court denied review on June 30, 2025. See the Harper ruling explained.

If you were a Coinbase user from 2013 to 2015

Here is the practical read.

  • If you had at least $20,000 of one transaction type in a year in that window, your account was within the scope the court enforced. Assume the IRS received your identity and transaction records.
  • If you reported that activity accurately, you have nothing to fix. Keep your records.
  • If you did not, the next question is whether the years are still open. The general three-year assessment period in IRC 6501(a) has long run for an accurate-enough return from those years. But a year with no return filed stays open under IRC 6501(c)(3), and a fraudulent return stays open under IRC 6501(c)(1). See the statute of limitations guide.
  • If you received a 2019 letter and did nothing, read what happens after an ignored crypto letter.

How to check your own exposure

Coinbase account histories from that era can be hard to reconstruct, but start with what you can get: any CSV exports you saved, emails confirming purchases and sends, and bank statements showing dollar transfers to and from the exchange. Then look at each year separately and ask a simple question: did any one transaction type cross $20,000? If yes, you were in scope. If you are close, assume you were.

Next, pull your IRS wage and income and account transcripts for those years. They will not show exchange data from a summons, but they will show what you filed and whether the IRS has already made changes. That tells you whether the year is quiet, adjusted, or never filed.

The lesson for every exchange user

Coinbase was the first crypto John Doe summons, not the last. The IRS later obtained court authorization for summonses involving Circle, Kraken and SFOX, plus a bank that served SFOX customers. See Circle, SFOX and the bank summons.

And since sales on or after January 1, 2025, brokers file Form 1099-DA, so the IRS does not need a court order to learn about most new exchange activity. The summons cases are history. The data flow they started is now routine.

My own takeaway after a lot of years watching the IRS work: it rarely needs everything. It needs your name and a number that does not match your return. The Coinbase court gave it both.

One last point for people who are only now reading about this. The 2017 order is nearly a decade old. If you were in scope and the IRS never contacted you, that is not proof you are clear. It may mean your returns matched, it may mean the IRS never got to your file, or it may mean the year is open and waiting. Find out which before you decide how worried to be.