PEPE Renounced Ownership. A 2.519T Wallet Is Still Blocked.

A wallet bought the frog early. The balance grew into the kind of number that turns a trading screenshot into a legend.

But the number on the screen was never the whole story. The wallet could hold PEPE without being able to move it.

Panther rechecked the Ethereum contract and the purchase receipt on October 23, 2026. The address still holds roughly 2.519 trillion Pepe ($PEPE), and the token’s blacklist mapping still returns true for it. Contract ownership is also renounced. Both facts can coexist.

This PEPE blacklist investigation finds a persistent transfer restriction and a gap in how some public descriptions explain it. It does not establish a fresh developer dump, identify a serial scammer, or predict a rug pull.

PANTHER JOURNAL #056 · Memecoin investigation · Ethereum mainnet. On-chain observations checked October 23, 2026, approximately 21:30–21:45 UTC; latest-state reads, not a block-pinned forensic export.

Why PEPE qualified for this investigation

The research universe was limited to Solana, Ethereum and BNB Chain, the leading three chains by seven-day DEX volume in the DefiLlama snapshot reviewed. BONK, PEPE and MUBARAK formed the initial shortlist. This article investigates PEPE; it does not present completed investigations of the other two.

PEPE cleared the popularity screen through multiple signals: roughly 395,000 CoinGecko portfolio additions, reported daily turnover in the hundreds of millions of dollars, and markets across established exchanges. CoinGecko’s market page documents that breadth. Etherscan showed 597,395 holder addresses when inspected.

Those are indicators of reach and activity, not a census of humans. Exchanges can represent many customers in one address; one operator can control many addresses. Reported volume and social engagement can contain automation. No claim that every trade or holder is organic is warranted.

Identity matters: this report covers the Ethereum ERC-20 at 0x6982508145454Ce325dDbE47a25d4ec3d2311933, linked by the project’s website. It does not cover the separate Pepecoin network or tokens borrowing the same name.

The purchase: 0.013 ETH, plus a fee that screenshots omit

On April 14, 2023, at 19:46:59 UTC, address 0xAf2358e98683265cBd3a48509123d390dDf54534 executed a successful Uniswap V2 purchase.

The transaction receipt, at Ethereum block 17,047,545, records approximately 0.01300003445 ether ($ETH) exchanged for 2,519,324,010,963.419102704251293024 PEPE. It separately records a transaction fee of approximately 0.00975169851 ETH.

That fee matters. A headline built only around the swap input understates the transaction’s total ETH outlay. The dollar values an explorer displays today are also not automatically the purchase-date cost or a realizable sale value.

The receipt proves this address received those tokens through that swap. It does not identify the person behind the address, establish a developer connection, or explain why the wallet was later restricted.

PEPE blacklist: what renounced ownership left behind

Using Etherscan’s Read Contract panel, Panther queried the token directly through the explorer’s read-only interface:

The balance returned in raw units was 2519324010963419102704251293024; the token uses 18 decimals. That is about 0.599% of its approximately 420.69 trillion token supply, calculated from the observed balances and supply. It is not 0.599% that can necessarily enter the market.

The verified source explains the mechanism. Its transfer hook requires both sender and recipient to be absent from the blacklist. The setter, blacklist(address,bool), is restricted to onlyOwner.

Renouncing ownership removes the ordinary owner’s ability to change the mapping; it does not reset existing entries. On the inspected implementation and state, this address’s ordinary PEPE transfers remain blocked. The zero owner also means the normal owner-only route cannot simply clear that entry.

This is a narrow conclusion about one verified address. It is not evidence that developers can newly blacklist arbitrary holders today. The historical restriction was already publicly discussed by software engineer cygaar in May 2023 and reported at the time. Panther is revalidating it, not claiming to have discovered it first.

Why the wording still matters in 2026

A Canary PEPE ETF registration amendment filed October 2, 2026 describes renounced ownership and says no blacklist functions remain. That is a registrant’s disclosure, not an SEC finding or a safety endorsement.

The source still contains a blacklist setter and an enforced blacklist mapping. The important distinction is an owner power that can no longer be exercised versus a restriction that was already written into storage. A description that collapses those two ideas misses the blocked wallet.

This comparison does not establish deceptive intent, a legal violation or a new threat to other wallets. It establishes why investors should verify code and state even when reading formal documents. An immutable contract can preserve an old restriction just as effectively as it preserves protections against new intervention.

A 4.917T transfer is not proof of a developer dump

A separate recent example shows the opposite analytical trap: seeing a large transfer and jumping straight to an insider accusation.

At 07:04:11 UTC on October 16, 2026, transaction 0x9c7d…1053d moved approximately 4.9168 trillion PEPE from 0x8fCA4adE3a517133fF23ca55CdAea29C78C990b8 to 0xC011358A6b9C36322ED21B3975DC9624f8801954.

Etherscan labels the sender Poloniex 7 and the recipient an HTX deposit address. The Whale Alert detail page carries an unknown-wallet headline while its receiver detail labels HTX. That difference is a reason to inspect the underlying addresses.

The receipt records a token transfer, with one event log—not a DEX swap. Exchange labels are third-party attribution, not cryptographic proof of beneficial ownership. The transaction alone establishes neither a sale inside HTX nor a developer relationship. It could be consistent with an exchange-related movement; the ultimate purpose remains unverified.

Panther therefore does not classify it as a confirmed insider dump or a confirmed whale accumulation. Neither conclusion follows from this receipt.

What an investor can actually learn

The useful lesson is to separate four questions that social feeds often merge:

• Can the token contract change your transfer rights? Inspect present privileges and existing restrictions. Renounced is a starting point, not the end of the check.
• Can a particular balance move? A portfolio valuation can include tokens the address cannot transfer. A paper balance is not an executable exit.
• Who controls a wallet? A funding link, an explorer label or a shared exchange withdrawal source is insufficient by itself to identify a developer or scammer.
• Was something sold? Distinguish transfers, liquidity operations, on-chain swaps and opaque exchange activity. Attribute only what the evidence supports.

For reproducibility, use Panther’s Etherscan guide and wallet-tracing guide. Liquidity needs its own examination: a claim about burned LP tokens at launch does not establish the ownership, depth or withdrawal rights of every current pool. This investigation does not certify all PEPE liquidity or all connected wallets.

Panther Takeaway

A renounced contract can still enforce an old blacklist. A trillion-token transfer can still prove no sale at all.

The edge is in reading exactly what the chain says—and refusing to add the accusation, reassurance or profit story it does not support.

Sources, method and limits

Primary evidence: the linked Ethereum purchase and transfer receipts; the verified PEPE source; latest-state owner, limit, blacklist and balance reads through Etherscan; PEPE’s own website; the dated Canary registration amendment. Independent context: cygaar’s historical observation and contemporaneous BlockBeats reporting; CoinGecko market data and DefiLlama chain volumes for selection.

The contract’s on-chain identity was cross-checked against the official site and CoinGecko. Dollar-value estimates were deliberately excluded from the blocked balance and large-transfer findings because prices move and displayed valuations do not prove realizable proceeds. Latest-state explorer reads were not independently replayed against a second Ethereum node.

This is a targeted public-evidence investigation, not a complete security audit or a reconstruction of every historical team wallet. No verified current developer sale, wallet owner identity, coordinated insider cluster or serial-scammer link was established in the reviewed evidence. Missing evidence is not proof that such conduct exists or that it does not. Findings can be updated when reproducible evidence changes them. The cover is an AI-generated conceptual illustration, not a transaction record.