PEPE is engineered to be tradable, not governable

PEPE’s “product” is the token itself. The official site is explicit: it is “completely useless and for entertainment purposes only,” with “no intrinsic value or expectation of financial return,” and “no formal team or roadmap.”

That framing matters because it changes what “tokenomics” can credibly mean. You are not modeling protocol cash flows, staking yields, or fee capture. You are modeling token economy components like supply shape, liquidity structure, and discretionary control surfaces around listings, bridges, and any reserve wallets.

On CoinGecko, the canonical Ethereum contract address for PEPE is shown as 0x6982508145454ce325ddbe47a25d4ec3d2311933.

The official site also claims PEPE launched “stealth with no presale,” with “zero taxes,” “LP burnt,” and “contract renounced.”

Supply: fixed genesis mint, no emissions schedule

Genesis supply is encoded directly in the contract deployment. The verified contract shows the constructor mints the full supply to the deployer, and the constructor argument decodes to 420,690,000,000,000 tokens (with 18 decimals).

There is no ongoing emission schedule in this design. Minting is performed only inside the constructor via _mint, with no external mint function exposed in the PEPE-specific contract.

CoinGecko lists 420,690,000,000,000 as circulating supply, total supply, and max supply.

On-chain, total supply can decline because the contract includes a callable burn function that reduces _totalSupply.

For example, Etherscan’s token supply checker shows total supply slightly below the genesis mint for the snapshot date March 6, 2026.

Decimals are standard ERC-20 18 decimals.

Allocations: what’s documented, and what isn’t

The official site states “LP tokens are burnt, and contract ownership is renounced,” but it does not publish a full allocation table on that page.

Because primary documentation is thin here, the clearest numerical breakdown comes from third-party disclosures. Kraken’s Payward Ltd launch distribution (dated August 26, 2024) states the launch distribution below, including both percentages and approximate token amounts.

As an Operator Discretion Skeptic, I treat that “multi-sig wallet” line as the structurally important part. Not because 6.9% is unusually large for meme coins, but because it creates an explicit discretionary control point in a token that otherwise advertises “no formal team.”

Transfer mechanics: “zero taxes” is true, but the contract is not “dumb”

PEPE’s contract implements standard ERC-20 balance moves with no fee-on-transfer logic. The internal _transfer subtracts amount from the sender and adds the same amount to the recipient, and emits a Transfer for that amount.

The official site summarizes that as “ZERO taxes,” and reiterates “No Taxes, No Bullshit.”

Burns exist, but they are not an automatic tax. The contract exposes burn(uint256 value), which simply burns the caller’s own balance by calling _burn(msg.sender, value), reducing total supply.

The non-obvious part is that the PEPE-specific layer adds transfer restrictions that can be toggled by the owner. Concretely:

Blacklisting: the contract includes blacklist(address,bool) and a mapping blacklists, and rejects transfers if from or to is blacklisted.

Trading gate: if uniswapV2Pair is not set, transfers revert with “trading is not started,” unless the owner is the sender or receiver.

Anti-whale rule: if limited is enabled, buys (transfers from the Uniswap pair) enforce min and max holding bounds via maxHoldingAmount and minHoldingAmount.

All three controls are set by onlyOwner functions (blacklist and setRule).

This is where “contract renounced” becomes a trade-off, not a slogan. If ownership is renounced, these controls become inert going forward. If ownership is not renounced, they are active admin privileges. Either way, the existence of these pathways means PEPE is not purely a passive ERC-20. It has an operator control plane embedded at the token layer.

The official site claims ownership is renounced.

Control surfaces: where discretion still matters after “renounce”

Even if you accept the public claim that ownership was renounced, two discretion vectors remain structurally relevant.

1) The multi-sig reserve (if it exists in practice). Third-party disclosures describe a dedicated multi-sig wallet allocation intended for listings, bridges, and liquidity.

That wallet, by definition, is operator discretion. It can fund exchange listings. It can provide or remove liquidity on other venues. It can be sold. The token contract being immutable does not eliminate that. It just confines it to treasury behavior instead of code behavior.

2) State persistence in the token contract. Renouncing ownership prevents future changes, but it does not rewrite history. If any addresses were blacklisted during the “ownered” period, the blacklist check in _beforeTokenTransfer still applies forever because the mapping is read on every transfer.

The same goes for trading gates and anti-whale constraints. Once uniswapV2Pair is set and limited is configured, those state values govern transfers. Renouncement locks those parameters in whatever shape they were last set.

There is a second-order issue here. Public memecoin discourse often compresses “renounced” into “trustless.” In PEPE’s case, the verified code shows there were meaningful admin levers before any renouncement could have happened. That is normal for fair launches. It is still operator discretion at genesis.

One more practical point. Etherscan indicates no contract security audit has been submitted for the token contract.

Liquidity and cross-chain representations: where new trust assumptions sneak in

PEPE is an Ethereum ERC-20 at its core. CoinGecko also lists other-network contracts for PEPE, including Avalanche, BNB Smart Chain, and Arbitrum One.

Cross-chain versions are rarely “free.” They usually imply some bridge, custodian, or mint-and-burn mechanism that is outside the original ERC-20 contract; our bridge risk research tracks common failure modes. A useful comparison is the custodial wrapper model used by WBTC.

If your thesis depends on “no admin keys,” bridged liquidity often reintroduces exactly the discretion you were trying to avoid.

The official PEPE site links to a “BRIDGE” property.

When a token’s primary stated utility is trading and social coordination, liquidity venues become the functional center of gravity. That shifts risk away from “does the contract have an upgrade key” toward “who can influence liquidity, listings, and narrative.” The reserve-wallet claim in third-party disclosures is the cleanest example.

PEPE’s own site explicitly leans into this. It tells users to buy on Uniswap, and reiterates there are no taxes beyond Ethereum gas.

Risk analysis: PEPE’s dominant risk is operator discretion around “the 6.9%”

PEPE’s token contract is simple in one sense. It does not skim transfers. It does not have protocol fees. It does not promise yield.

It is not simple in the way many holders assume. There are explicit admin functions for blacklisting and for enforcing holding limits, plus an owner-controlled trading start gate.

The bigger issue is off-contract power. A reserve allocation, if real, is the closest thing PEPE has to a “policy rate.” It governs how aggressively the project can pursue listings and bridges, and how much supply can appear on the market outside organic trading.

Dominant risk: The discretionary reserve (commonly described as a multi-sig wallet) creates a permanent “operator layer” in a token marketed as having “no formal team,” and PEPE has already experienced a major multi-sig governance failure.

In August 2023, reporting on the reported multi-sig incident described how an announcement from the official account claimed “three ex-team members” stole ~16 trillion tokens from the multi-sig wallet and sent them to exchanges, and that the multi-sig signature threshold was changed (reported as 5/8 to 2/8) around the event.

From a token-economy standpoint, that incident matters more than the headline dollar value. It demonstrates that any “foundation wallet” or “listing wallet” is a governance system, whether or not the token has formal governance. Signer sets, threshold rules, key custody hygiene, and internal accountability become the real protocol. Most of that is off-chain and unmodelable unless transparently disclosed.

Even worse, this risk does not get solved by contract renouncement. If the reserve exists, it remains an operator-controlled balance sheet. If bridged versions exist, they often expand the operator surface area through bridge contracts, custodians, and chain-specific liquidity management.

Finally, the contract itself contains a blacklist mechanism and an owner-controlled rule setter. Even if the owner is renounced today (as claimed), the mere presence of those functions tells you PEPE’s early lifecycle included a period where an operator could gate trading, block addresses, and set buy-side holding limits. That is a real trust window at launch.

Speed of iteration versus decentralization is the trade. Admin controls let a team launch fast, handle bot pressure, and coordinate liquidity. They also create a single point of failure. PEPE’s public brand says “no team,” but the multi-sig episode shows team-like operational reality can still exist.

Top 3 risks

  1. Reserve-wallet discretion and key-risk. Trigger: large transfers from any disclosed or suspected reserve / multi-sig wallet, signer changes, or abnormal approval patterns. Mechanism: concentrated balances enable step-function supply dumps, listing-bribe spend, or bridge-liquidity decisions that reprice the market; compromised keys or rogue signers can force sales. Who bears it: spot holders and LPs, first, via price impact and liquidity shocks. Measurable indicators: on-chain outflows from known reserve addresses, changes in multi-sig threshold or signer set reported by the project, and exchange deposit address clustering around those flows.
  2. Parameter opacity and “renounce” unverifiability for most users. Trigger: conflicting claims about taxes, burns, redistribution, or admin control across exchanges, influencers, and dashboards. Mechanism: the contract includes admin-only controls (blacklist, trading gate, anti-whale rule), and users often rely on narrative summaries instead of reading verified code; this can produce mispriced risk and reflexive volatility when reality reasserts itself. Who bears it: retail holders and market makers who quote tight spreads on incorrect assumptions. Measurable indicators: discrepancies between third-party descriptions and verified contract behavior, plus sudden liquidity withdrawal or price gaps following “contract risk” headlines.
  3. Cross-chain representation risk. Trigger: rapid growth in non-Ethereum volumes, bridge pauses, or chain-specific contract issues on listed networks. Mechanism: bridged tokens typically add external trust assumptions (bridge operators, custody, chain-specific liquidity managers); failures can break the “same asset” parity and fragment liquidity. Who bears it: holders who move across chains and LPs on secondary networks, then Ethereum spot holders via sentiment spillover. Measurable indicators: depegs between chain venues, bridge mint/burn anomalies, and sudden changes in contract addresses or “wrapped” labels on aggregators.

If you’re doing tokenomics design work around a PEPE-adjacent launch, the takeaway is narrow and practical. Do not hand-wave “renounced” as a security model. Inventory every off-chain control point, especially reserve wallets and bridges, and publish constraints that reduce operator discretion rather than celebrating it.



This article is part of our Tokenomics Deep Dive series.