BALD arrived during an unusual window in Base’s history. The network was live, but its public opening had not happened. Traders found the chain, crossed an unfinished bridge experience and crowded into a meme whose liquidity was largely controlled by the same address that deployed it. When that address withdrew liquidity on July 31, 2023, the collapse looked sudden. The control path was visible all along.
This fifteenth Meme Autopsy is historical research, not breaking news. It reviews the original BALD contract at 0x27D2DECb4bFC9C76F0309b8E88dec3a601Fe25a8. It does not treat later tokens sharing the name as the same asset, and it does not identify the human behind the deployer address.
A public frenzy before the public launch
Base announced on July 13, 2023 that mainnet was open for builders, with general availability planned for early August. The notice asked builders not to expose user-facing apps yet and said there was no public bridge interface during that phase. It nevertheless documented the portal contract builders could use to move ETH onto Base.
That distinction matters. BALD did not trade on a testnet, and Base did not halt during the episode. It traded on a live mainnet that was accessible before the network’s intended public opening.
Blockworks reported that BALD’s name played on Coinbase co-founder Brian Armstrong’s appearance. That is meme-origin context, not evidence that Armstrong or Coinbase created the token. Base’s July notice also stated that the network had no plan to issue its own token. BALD was therefore not a Base network token merely because it launched there.
Start with the exact contracts
The BaseScan token record identifies the reviewed asset as Bald, symbol BALD, with a maximum supply of one billion tokens. The address BaseScan labels Bald: Deployer is 0xccFa0530B9d52f970d1A2dAEa670ce58E4176389.
The key pool in the reviewed transaction is 0xe96df8f5ef1a8790415068c798765b07d57643bd. Direct contract reads at the historical block identify its two assets as the original BALD contract and Base’s wrapped ether contract. This is the pool-level object that matters for the liquidity claim; a chart or token balance alone cannot show who held the withdrawal claim.
One receipt reproduces the exit
At 12:31:21 UTC on July 31, the deployer address sent transaction 0xd4fce790… to a router. The transaction landed in Base block 2,008,667 with receipt status 1, meaning the EVM accepted the execution rather than reverting it.
The calldata decodes as a request to remove BALD/ETH liquidity and names the deployer address as recipient. The receipt’s logs show roughly 986,110.82 pool-share tokens moving from the deployer to the pool and then being burned. The same receipt records approximately 142.79 million BALD and 6,809.966 wrapped ETH leaving the pool through the router, followed by the wrapped ETH withdrawal event.
Those observations are reproducible from the transaction and receipt. They establish a large, successful liquidity removal by the address that held the pool shares. They do not require a price chart or a wallet-label provider.
Blockworks described a broader sequence in which the deployer removed liquidity, returned some and removed it again. This review independently reproduced the cited large removal but did not build a complete profit-and-loss ledger for every transaction in that sequence. It therefore does not adopt a single dollar-profit or holder-loss figure.
Why “the deployer sold” is too imprecise
Liquidity removal and a token sale are different operations. A sale swaps one asset for another against a market. Removing liquidity redeems a pool position for the assets backing that position. Either action can affect a thin market dramatically, but the receipt should be described for what it records.
That is why the deployer’s control of the pool shares is the central fact. The token contract could continue to exist after the withdrawal. Holders could continue to own BALD. Yet the route and depth available to trade had changed because the dominant liquidity provider exercised its redemption claim.
Calling the incident a “rug pull” is a common shorthand for that market outcome. The narrower finding is stronger: a deployer-controlled position supplied substantial liquidity and then successfully removed it. Intent, private communications and the legal identity of the key holder are separate questions.
The address is not a person
Researchers linked the deployer address to older wallets and institutions, producing competing identity theories. Public transaction connections can show that addresses exchanged assets or interacted with the same protocols. They do not, by themselves, prove that one named person controlled every key.
No reviewed primary record supplies a verified real-world controller for the deployer at the time of the removal. This article therefore stops at the address-level attribution. “Bald: Deployer” is an explorer label describing a role in the contract history, not a government identity document.
What the record supports
| Status | Finding |
|---|---|
| Verified onchain | The original BALD contract, deployer-labeled address, BALD/WETH pool and successful July 31 liquidity-removal transaction. |
| Independently reported | BALD’s Armstrong-themed name, the pre-public-launch trading frenzy and a remove-return-remove sequence. |
| Reasonable analysis | Concentrated control of the pool position created a direct market-exit risk even though the token contract remained live. |
| Not established here | The deployer’s legal identity, criminal intent, one reconciled profit figure, aggregate buyer losses or responsibility by Coinbase or Brian Armstrong. |
BALD’s lasting lesson is not merely that a meme collapsed. It is that liquidity has an owner and a withdrawal path. A visible token contract did not make that market support permanent, and a visible deployer address did not reveal the human holding its key.
Continue with how to read an EVM transaction receipt, how to identify the position that can withdraw liquidity, why market cap is not exit liquidity and the meme-coin learning hub.
Reporting and image notes
Original AI-assisted historical analysis based on Base’s dated launch notice, the exact BaseScan token and transaction records, direct Base JSON-RPC reads, Ethereum’s receipt documentation and independent contemporaneous reporting. The article reports rounded onchain quantities and leaves identity, intent, aggregate proceeds and losses unresolved. The cover is Steve Jennings’ September 7, 2018 photograph of Brian Armstrong, supplied by Getty Images for TechCrunch and published by TechCrunch on Flickr under CC BY 2.0. It predates BALD and is origin context only, not token artwork, a launch photograph or evidence of Armstrong’s participation. The 1024-pixel photograph was not enlarged; it was placed at original resolution on a dark panel and converted to responsive WebP files.