Swarm Pepes: ranked growth plan

Research date: 3 October 2026. Research only; no deployment, grants, wallet extraction, or partner outreach performed.

Evidence key: Context = supplied by the requester, not independently verified; Fact = linked primary source; Proposal/estimate = our judgment, not a measured result. Rankings favor sustained participation over speculative trading.

Context: Ethereum contract 0x999ce0ce8c5f7661e0c74a568ffe27ceb9177bdb; 5,000 maximum supply; three per wallet; allowlisted wallets mint through a 0 ETH transaction; owner uses grant(address[], uint256); 27-hour reveal window and permanent ghosts; Gold skin 1%, Crown hat 3%; 10% unenforced royalties; initial audience comprises IMD seat holders and swarm-job payers. Retrieval of the website and contract page failed. These links identify verification targets, not corroborating evidence. Free mint means zero mint price, not zero Ethereum transaction fees.

1. Top five growth ideas

All effort and impact ratings below are estimates. Effort means approximate person-days, excluding ongoing moderation and external review.

Rank	What to do	Effort	Expected impact and measurement
1	Reveal rendezvous. Invite small allowlist waves to a live CRT-themed reveal session. Provide a personal deadline/status display and opt-in reminders; explain permanent ghosts before minting. Schedule across time zones. Exact reveal actions and timer origin must first be verified.	3–5 days plus an event host	High activation: fewer accidental ghosts and a shared first experience. Measure invited-wallet mint rate and on-time reveals; report intentional ghosts separately if users opt to identify them.
2	Pepe workbench utility. Pilot a weekly holder workshop where IMD contributors help turn one small creative brief into pixel art, copy, or a simple tool. Offer a fixed number of sponsored jobs with a published budget; select participants by contribution, not NFT quantity. Include ghost holders.	5–8 days; recurring contributor time	High retention: connects the collectible to the existing swarm-job audience. Measure unique participating holders, completed jobs, and 30-day return participation. This is proposed access, not an existing benefit or unlimited service promise.
3	Pixel-art partner jam. Approach Blitmap first, then Nouns creators: a shared theme, two short workshops, a community gallery, and a small allowlist wave. Obtain partner agreement before using affiliation language. Blitmap explicitly supports community-created works; Nouns publishes open art/protocol resources. Blitmap, Nouns protocol.	4–7 days plus partner lead time	Medium–high acquisition: relevant creators bring work and relationships. Measure new-to-Swarm minting wallets and subsequent contributions by partner cohort. Partner interest is untested.
4	Onchain provenance arcade. Build a read-only gallery that renders each Pepe from its contract metadata, shows token identity and verified reveal state, and exports a shareable CRT card. Add a community challenge to build alternate viewers. ERC-721 defines ownership and optional metadata interfaces; Swarm's actual interface still needs inspection. ERC-721.	6–10 days	Medium credibility and sharing: makes the onchain claim tangible. Measure completed renders, exports, and referred visits. Do not imply that onchain art guarantees a website's continued availability.
5	Ghost radio and trait nights. Monthly pixel-story screenings give ghosts their own lore alongside Gold and Crown showcases. Invite holders to submit 20-second scenes; publish a curated compilation and credit creators. No trait-based service advantages or rarity rewards.	2–4 days per event	Medium retention; modest acquisition: makes common and ghost tokens socially useful. Measure distinct creators and repeat attendance rather than floor price. Trait frequencies are Context, not audited probabilities.

Suggested sequence: week 1 verify mint/reveal behavior and establish baseline; week 2 run a 100-wallet reveal pilot; weeks 3–4 trial the workbench and one partner jam. The 100-wallet size is a proposed cap, subject to supply. Use cohort links and public onchain outcomes, not promised conversion percentages. Budget operations independently of resale royalties: ERC-2981 describes voluntary royalty payments, and does not establish that Swarm implements that standard. ERC-2981.

2. Top five wallet groups to allowlist next

These are external expansion cohorts beyond the IMD wallets already served. All wallet ranges are low-confidence planning estimates of potentially eligible unique addresses, not live holder counts. No RPC snapshot was run. Token supply is not wallet count. Pilot caps are separate, deliberately small limits; overlap and existing Swarm eligibility must be subtracted.

Common selection recipe (proposed): choose and publish a finalized Ethereum block B before announcing eligibility. For ERC-721 collections, reconstruct ownership using Transfer(address,address,uint256) logs through B, handle burns, and confirm ownerOf at B. Require continuous ownership of at least one token for 90 days using transfer history. Deduplicate addresses across cohorts; exclude existing Swarm holders and previously granted wallets using verified Swarm state/history. Review custodians and vaults; do not reject all smart-contract wallets, since legitimate multisigs exist. Historical ownership methods follow the ERC-721 specification.

1. Blitmap long-term holders. Best fit: a small pixel-art community with an established remix culture. Fact: 100 original works plus 1,600 siblings; the official site links the original contract 0x8d04a8c79ceb0889bdd12acdf3fa9d207ed3ff63. Read its Transfer events and apply the common recipe. Estimate: 300–800 wallets; pilot up to 100. The range assumes multiple works per collector and attrition from the age filter, not a measured ownership distribution. Risk: medium; collectors can split holdings across old wallets, and vaults obscure beneficiaries. Official collection and contract link.

2. Nouns long-term holders. Fit: onchain art and community project funding; good candidates for creator sessions. The documented token is 0x9C8fF314C9Bc7F6e59A9d9225Fb22946427eDC03. Read token Transfer logs and ownerOf; do not substitute auction bidders for holders. Estimate: 100–400 wallets; pilot up to 75. This is a conservative operational hypothesis, not a current supply-derived count. Risk: medium; DAO treasuries, escrow, concentrated ownership, and delegated governance can make holder addresses poor proxies for active people. Resolve custody before granting. Nouns contract documentation.

3. Blitnauts holders who do not hold Blitmap. Fit: a robot-themed, community expansion audience adjacent to the swarm aesthetic, while the exclusion adds reach beyond rank 1. The official Blitmap site links 0x448f3219CF2A23b0527A7a0158e7264B87f635Db as the Blitnauts collection. Read Transfer logs, confirm owners, then subtract current Blitmap holders and earlier cohorts. Estimate: 200–700 wallets after exclusion; pilot up to 75. No current overlap measurement supports this range. Risk: medium–high; ecosystem overlap and multi-wallet splitting could materially shrink unique-person reach. Official Blitnauts description and contract link.

4. Autoglyphs long-term holders. Fit: collectors who already value art generated and stored onchain; best approached through a technical art salon rather than rarity marketing. Contract 0xd4e4078ca3495de5b1d4db434bebc5a986197782; read Transfer and ownerOf. Fact: 512 total works, so direct current owner addresses cannot exceed 512. Estimate: 80–200 eligible wallets; pilot up to 50. Risk: low–medium for new acquisition farming, but substantial custody and collector-concentration risk; expensive holdings do not prove humanity. Larva Labs project, official contract archive.

5. Native CryptoPunks long-term holders. Fit: pixel-avatar culture and a free-claim origin; broader reach but less direct connection to IMD utility. Contract 0xb47e3cd837dDF8e4c57F05d70Ab865de6e193BBB; query punkIndexToAddress(0…9999) at B. Use Assign, PunkTransfer, and PunkBought history for the holding-age filter; generic Transfer is not an ERC-721 token-ID log here. Exclude wrapper/custody addresses from this first cohort until beneficial ownership is resolved. Estimate: 500–1,500 direct eligible wallets; pilot up to 100. Risk: medium: custodial ownership, inactive wallets and sophisticated multi-wallet collectors; likely lower response to a new small collection. Creator's project account, original contract source.

Allocation controls: the five pilot caps total 400 addresses before deduplication. Propose one slot each, only after confirming whether grant overwrites or adds allowance and how the three-per-wallet rule is enforced. Remaining supply and outstanding allowances must cover the allocation; do not assume all 5,000 are available. Holding age raises farming costs but does not establish one person per wallet. Review shared funding and circular transfers as flags, not automatic proof of sybil activity. None of these groups is an agreed partner.

3. Top five short vertical videos

All are original creative proposals ranked by likely usefulness, not measured performance. Use 9:16, chunky 8-bit pixel art, near-black backgrounds, neon-green CRT glow, scanlines, chiptune, readable captions, and a 3–4-second end card. This follows the supplied style; no existing videos were available to audit. Every end card includes swarmpepe.xyz. Verify the mechanics before publishing instructional copy.

1. “27 hours. One permanent outcome.” Hook: “Your Pepe has a reveal window.” 24s beats: 0–3s a ghost flickers beside “27 HOURS”; 3–8s a clock ticks over a token silhouette; 8–15s split-screen: timely reveal becomes a colored Pepe, missed window stays a ghost; 15–20s show a legible deadline/status mockup labeled “concept”; 20–24s end card. Ending text: “Know your reveal deadline. Miss it: ghost forever.” Do not suggest all wallets share one countdown.

2. “Zero mint price. Maximum pixels.” Hook: “A free mint still needs gas.” 20s beats: 0–3s “MINT PRICE: 0 ETH”; 3–7s allowlist terminal checks a wallet; 7–12s a transaction travels to an Ethereum-shaped chip, with “network gas applies”; 12–16s silhouette appears and reveal-window reminder follows; 16–20s end card. Ending text: “Allowlisted wallets only. Check eligibility. Gas required.” Do not depict transaction submission as an instant reveal.

3. “The pixels live in the chain.” Hook: “Where does your Pepe actually live?” 24s beats: 0–4s zoom through a pixel eye; 4–10s enter an Ethereum circuit; 10–16s art data becomes the same Pepe in a second viewer; 16–20s display its token ID and “fully onchain”; 20–24s end card. Ending text: “Swarm Pepes. Art on Ethereum.” Use a real token and verified rendering path in production; avoid claiming universal permanence.

4. “Your Pepe clocks in.” Hook: “What could your Pepe help create?” 25s beats: 0–4s Pepe inserts a pixel work card; 4–10s swarm sprites gather around a creative brief; 10–17s they assemble one artwork; 17–21s actual contributors appear in arcade credits; 21–25s end card. Ending text: “Proposed: the holder workbench. Build with the swarm.” Replace “Proposed” with a real session date only once the utility pilot is funded and scheduled.

5. “Gold, crown, or ghost: enter the cast.” Hook: “Every Pepe gets a story.” 24s beats: 0–4s character-select grid; 4–10s Gold skin flashes “1%” and Crown hat “3%”; 10–16s common Pepes and ghosts assemble a stage; 16–20s each gets equal screen time; 20–24s end card. Ending text: “Show your Pepe. Write its next scene.” Percentages are supplied context; do not multiply them into combined odds or promise exact final trait counts.

Unanswered before execution: current minted supply, outstanding grants, holder distribution, verified ABI/source, timer origin and reveal caller requirements, whether windows are token-specific, actual trait-generation probabilities, IMD service budget, artwork reuse rights, partner interest, existing video examples and baseline engagement. These uncertainties limit execution readiness, not the usefulness of the proposed pilots. No price, revenue, conversion uplift, or partner participation is forecast as fact.