Skip to content Skip to footer

The Epstein Contract: How McAfee Engineered Conspiracy Into Code

Most conspiracy theories are told. John McAfee deployed one. In November 2019 he shipped a smart contract to the Ethereum blockchain and gave it a name that no one chooses by accident. The contract that powers the $WHACKD token is called “Epstein.” You can read that for yourself on Etherscan, where the source code is verified and has been for years. Five years after McAfee’s death, that single naming choice remains the most quietly deliberate thing he ever did in crypto.

A name with a timeline

Jeffrey Epstein died in a New York jail cell in August 2019. The death was ruled a suicide, and a very large portion of the public refused to believe it. Three months later, in November 2019, McAfee named his new token’s contract after him.

This was not a man reaching for shock value at random. McAfee was, at that point, a fugitive from the US government, openly expecting to be pursued and arrested. By borrowing Epstein’s name for his own code, he was making a prediction and an accusation at the same time. If a high-profile target of the state could die in custody and have it written off as suicide, so could he. The contract name said it before he ever did out loud.

He made the subtext text soon enough. On 30 November 2019 he posted a photo of a fresh “$WHACKD” tattoo on his arm, writing that he was getting messages from US officials and that if he were ever reported to have killed himself, he had not. Almost a year later, from a Spanish prison, he repeated it almost word for word: “Know that if I hang myself, a la Epstein, it will be no fault of mine.”

The contract, the tattoo, and the tweets were one message delivered in three media. The code was just the version that could not be deleted.

What the contract actually does

Strip away the symbolism and the “Epstein” contract is a competent, simple piece of work. It is a verified ERC-20 token, compiled with an older Solidity version, with no proxy tricks and no external dependencies. Its mechanics are visible to anyone who wants to look.

The token is hyper-deflationary by two rules. Every transfer burns 10% of the amount moved, sending it to the zero address forever. And a counter in the contract tracks transactions so that roughly every thousandth transfer is burned in full, the sender losing everything and the recipient receiving nothing. The community called this getting “whackd,” and it is enforced by the code, not by anyone’s discretion.

There is a grim elegance to it. McAfee built a token whose own logic could wipe you out at random, named after a man the internet believed had been wiped out by the state, launched by a fugitive who expected the same fate. The theme runs from the contract header all the way down to the burn function.

When the code became a prophecy

McAfee was found dead in Brians 2 prison near Barcelona on 23 June 2021, hours after a court approved his extradition. Within an hour of the news, his Instagram posted a single letter “Q” and then deleted itself. Within days, the token spiked roughly 733%. Four days after his death it touched its all-time high of $0.082111.

Then the machinery of the conspiracy kicked in, and the “Epstein” contract sat at the centre of it. A website appeared at britbonglogpost.com showing McAfee’s face, a countdown timer, and the $WHACKD contract address highlighted in green, under the words “Contingency plan activated. Something big is coming.” Believers argued that the metadata of the Instagram “Q” image pointed back to a contract called “Epstein,” which led to the token. The pieces seemed to fit because McAfee had spent eighteen months making sure they would.

And then nothing. The countdown hit zero with no revelation. Analysts found the Instagram image’s metadata began with “FBMD,” ordinary Facebook data rather than a hidden key. There was no dead man’s switch in the contract, because there was never any code to do that job. The “Epstein” contract was a deflationary token with a provocative name. It was a brilliant piece of narrative engineering and an ordinary piece of software, and both things were true at once.

Why it still matters

The lasting interest of the Epstein contract is not whether McAfee was murdered. Our companion piece on the death controversy weighs that evidence, and it does not resolve cleanly. The interesting part is what McAfee understood about the blockchain that most people in 2019 did not.

He grasped that code is permanent and uneditable in a way that tweets and tattoos are not. A tweet can be deleted, an account can be wiped, a body can be cremated before anyone independent examines it. A verified contract on Ethereum cannot be quietly taken down. By writing his suspicion into a smart contract, McAfee gave it the one property the rest of his story lacks: it cannot be revised after the fact. The “Epstein” name will sit in that contract for as long as Ethereum exists.

That is the real trick, and it is worth respecting even if you believe, as the official record concludes, that he died by his own hand. McAfee did not just claim he might be killed and silenced. He published the claim somewhere it could never be silenced. Whatever the truth of his death, he made sure the accusation would outlive him, immutable, on a chain he did not control and no government can edit. For a man whose entire philosophy was about putting things beyond the reach of authority, it may have been the most on-brand act of his life.

Part of Blockleaders’ “John McAfee: Five Years On” series. See also our full $WHACKD token explainer, our evidence-led look at the death controversy, and Jillian Godsil’s reflection on the man.