Illinois’ 0.2% Crypto Tax Hits a Self-Custody Problem

Key Takeaways

1. Brokers owe the 0.2% even if uncollected
2. Fees paid only to liquidity providers are exempt
3. Draft rules demand private keys in records
4. Enforcement pushed to July 2027, pending court approval

DeFi Education Fund announced on November 12 that it had joined Andreessen Horowitz, Paradigm and Uniswap Labs in filing an amicus brief against Illinois’ Digital Asset Tax Act, with 14 co-signers including Aave Labs, Aptos Labs, Chainlink Labs, Multicoin Capital, Phantom and the Solana Policy Institute.

The brief supports a lawsuit brought in Sangamon County circuit court by The Digital Chamber, the Blockchain Association and the Crypto Council for Innovation. Governor JB Pritzker signed the Act in June as part of the state’s fiscal 2027 budget, with a start date of January 1, 2027. The state has since agreed to push both effectiveness and enforcement to July 1, 2027, an arrangement that still needs the court’s sign-off.

A broker owes the tax whether it collected it or not

The Act charges 0.2% of the value of digital assets involved in a covered exchange, transfer or storage service, and makes the broker responsible for collecting it from the customer. On a $50,000 swap that is $100. Section 3-35 then adds the clause the coalition keeps returning to: a broker required to collect the tax is liable for it whether or not it has collected anything.

For a custodial exchange this is routine. It knows the customer, holds the balance and can debit the charge before the trade settles. For a business that is classified as a broker but was not built to be one, the same clause turns a definitional dispute into a bill paid out of its own revenue, transaction by transaction.

The sourcing rules raise the stakes. A customer is presumed to be in Illinois when the broker’s records show an Illinois mailing address or IP address, and the broker must prove otherwise to escape the charge. A business that sees only a public wallet address has no record to trigger that presumption and none to rebut it; it cannot tell which of its users the state would count. The same gap in who holds the records runs through the federal fight over DeFi reporting rules.

What the coalition says DeFi software cannot do

A swap from a self-custodial wallet usually passes through three hands that need not belong to one company: a website that assembles the transaction, wallet software that lets the user sign it, and a smart contract that executes it. The brief’s core claim is that the Act’s definitions treat each of those as if it were the exchange account it replaces.

Custodial exchange

Holds the assets, knows the customer, debits the fee. The model the Act was written for.

Non-custodial front-end

Runs the interface, may earn its own fee, may see an IP address. Cannot move the user’s funds.

Immutable protocol

Executes code as deployed. No operator to add a collection step or identify where users live.

Wallet software

Builds the signing tools. The developer never holds the key and never sees the balance. 

The narrowest point in that case is the front-end. A website that charges its own fee already has a payment relationship with the user, and asking for a second signature to cover a state charge is a product decision rather than a technical impossibility. The coalition’s answer, set out in an October 30 comment letter from a16z, DEF and Uniswap Labs, was to ask the Department of Revenue to write decentralized exchanges and the web apps that connect users to them out of the broker definition entirely.

The state’s draft already draws some lines

The department’s September 28 draft rules do not treat every DeFi transaction alike. A swap fee that goes entirely to liquidity providers, and a network fee that goes to the validators processing the transaction, do not count as the consideration that triggers the tax. A protocol fee kept by whoever operates the platform does. Two swaps that look identical in a wallet can sit on opposite sides of that line depending on where the fee lands, and on the draft’s reading a project that starts keeping part of the fee moves itself across it.

The draft is less accommodating on self-custody. Section 497.155(a)(3) requires account records showing asset movements to include private keys. A key is not a record of a transfer; it is the credential that authorizes one, and whoever stores it can spend from the wallet. The October 30 letter asked for that wording to go. It also objected to the draft treating withdrawals to a user’s own private wallet and cross-chain bridging as taxable transfers, which the letter described as taxing a person for moving money between their own accounts.

The same letter asked for self-custody wallets to be excluded from the broker definition outright. The Act’s reference to “storage” services is why: wallet software keeps keys on the user’s device, and the draft left the question open enough that the signatories wanted the exclusion written in rather than inferred.

Why a Fed Rate Hike Can Push DeFi Yields Lower

Where the case stands

Beyond feasibility, the brief argues that taxing blockchain-based financial activity while leaving comparable conventional services untouched breaches the uniformity clause of the Illinois Constitution and the federal Internet Tax Freedom Act, which bars taxes that discriminate against electronic commerce. It puts the number of Illinois residents holding digital assets at 2.64 million, fifth among the states. SIFMA and the U.S. Chamber of Commerce filed a separate brief on November 6 backing the challenge, and it is that filing which records the state’s agreement to the six-month delay Coindoo reported earlier.

The state’s public position so far consists of the Act and the September draft. Two things would change what businesses have to build before July 2027: the department’s final rules, and the court’s decision on whether the Act survives at all.

The statute is written for one broker that knows the customer and holds the money. A self-custody swap can involve three businesses that each hold a piece of that role, or none that fits it. Which of them inherits the collection duty depends on how the product was built, and the Sangamon County court has now been asked whether the state can lawfully impose it on any of them.