Dungeon Crawler Pepe (DCP)

Token name: Dungeon Crawler Pepe. Token symbol: DCP.

CURRENT ORDER: Build, test and independently review the complete Dungeon Crawler Pepe game, contracts, backend and operating software for the production specification below. Publish complete source on public GitHub, build the browser frontend's static export, and provide a locally runnable integrated demonstration. This is the user's authorised BUILD-AND-REVIEW fallback, not a launch: do not deploy contracts, mint a token, seed a pool, enable real-money gameplay, create paid subscriptions or submit paid swarm work. Do not publish a live production site in this order. Use local/fork simulations and labelled test fixtures. Deliver working implementation, not just research or a design document. Independently review it and clearly record unresolved defects, funding and provisioning gaps; prepare a supported subsequent IMD launch plan preserving hands-off operation. The production requirements below remain the target, but actual mainnet deployment and external runtime provisioning await a separate reviewed launch.

ECONOMY: Ethereum mainnet (1), ordinary play off-chain. DCP/IMD preferred; DCP/ETH allowed with automatic IMD conversion, protected gas reserves and expenses funded. Single-sided DCP seed; no requester-funded pair liquidity. Total supply: 1,000,000,000 DCP with 18 decimals, minted once; no further minting, owner, pause or upgrade on the token; plain transfers. 10% swarm, 10-20% pool, 70-80% contract game reserve; initial proposal 20/10/70. Verify quoted pairing/allocation. POOL4 optional.

Verify current fees (docs 1.25%: 1% payer, 0.25% IMD). Verify treasury routing: initial factory.setRequester(uint64,address), permissionless claimFees/withdraw; prove both assets arrive. Fund reserve via supported remainderTo or one approved initial transfer of its exact allocation. No ongoing wallet forwarding, private keys or extra tax by default. Document LP ownership, collection, assets and depth; other pools need not pay. No wash trading.

Token seed is not cash; no extra budget committed. Cost and specify inference/gas/hosting bootstrap before the later launch; disclose subsidy/gaps, no assumed wallet access. Separate player custody/liabilities from operation. Choose sinks/burn/recycling, capped emissions/anti-farming; finite supply/sell pressure, fun with small prizes, no yield promises. Replenish IMD at runway thresholds through approved liquid routes with minimum output, manipulation-resistant prices and slippage/gas/spend caps. Batch dust; handle DCP fees explicitly. Failed conversions preserve funds. Model zero volume, shallow liquidity, price falls, rising costs and depleted reserves; essential operation before prizes.

TONE: Dungeon Crawler Pepe/DCP fixed; creative control of original world/cast/classes/combat/crafting/factions/equipment/seasons. Dungeon Crawler Carl intensity without copying plot, characters or dialogue. R-rated profanity, filthy jokes, grotesque monsters, outrageous violence, predatory sponsors and cosmic bureaucracy. Adults/non-graphic sexual comedy, unsanitised. Magical lightsaber strap-on is illustrative, NOT required starting gear. Make absurdity mechanical, with callbacks, consequences, recurring characters and emotional stakes; screenshot-worthy moments.

VARIETY: A small bounded daily world, fixed loot list or shared upgrade ladder is unacceptable. 100 players must not get the same upgrades or exhaust possibilities. Swarm-authored systems plus deep procedural generation: individual routes, encounters, branching quests, powers/modifiers/curses/trade-offs and build synergies. Shared events, not identical progression or merely renamed/stat-rolled loot. Expand mechanics/content continually, many viable builds, randomness reacting to choices/history. Bound rewards/costs, not creative breadth. Validate combinations; resist seed/reroll farming, verifiable randomness for valuable prizes. Caching must not produce identical sessions. Simulate 100+ players/several days; measure repetition/duplicate upgrades/build diversity/dominant strategies; fix convergence.

PLAY: Fast dark-mode desktop/mobile browser game, persistent characters/inventory/cross-device saves; long sessions, daily floors/quests/events, secrets, leaderboards, token/item rewards; consider parties/seasons. No ten-minute cap. Define death/resets/persistence, item ownership/trading and purchase consequences. Avoid pay-to-win; try before spending, no IMD NFT required. Browser/mobile wallets, replay-safe sign-in (connection is not authentication), account/network changes, approval/purchase/claim status. No seeds. Ordinary moves need neither transactions nor AI fees. Authoritative state, concurrency/retries/reorg safety, verified scores/claims; resist bots, multi-wallet farming and prompt injection. Preserve ownership/earned rewards.

OPERATION: Durable swarm memory/versioned rules; separate creation, independent review, tests and publication. Generate ahead, fallback content, preserve active encounters. No arbitrary code/treasury commands from player/generated text. Provision revenue-to-IMD-to-paid-work/topups, validation/publication, gameplay/state/rewards. Verify APIs/payment authority/prices. Give automated content work its own constrained payment identity. Contracts cannot initiate transactions/HTTP. Fund/provision keepers, schedules, isolated payment signers, backend/database/indexer/RPC/hosting, backups/failover and recovery. No temporary worker workspace, my PC or manual account setup; IPFS is not a backend/perpetual hosting.

Bounded/revocable authority, replaceable operators; no unrestricted withdrawals or founder admin. Document roles/holders, content versus financial upgrades, external operators and IMD-staff-only controls. No secrets/personal history in prompts/source/browser/public outputs; no anonymity claims. Bounded retries, duplicate-payment prevention, rollback, old content playable in outages; low-runway spending reduction and safe dormancy protecting claims. Show version/history/runway/spend/reserves/liquidity/outages. No perpetual funding/service guarantees.

DELIVERY FOR THIS BUILD: Prove fee/reserve routing and ownership in tests; deliver runtime code, provisioning/recovery automation and exact bootstrap costs/authority needed before the later launch. Identify unsupported sequencing and services explicitly; no founder chores. Test substantial play/saves/purchases/inventory/rankings/claims; 100-player variety; fee-to-treasury-to-paid-work; two unattended content cycles with durable state; operator loss/outages/bad content/empty budgets/treasury attacks. Independently test no overspending, duplicate claims, unauthorised minting/withdrawals or player-custody spending. Deliver source, runnable demo/static export, test/review evidence, deployment manifests, operating rules and a launch-readiness report. Future launch must deliver a live URL, verified contracts/pool and actually funded services. Success: entertaining, evolving adult game running without me.