PROJECT & GAME MANUAL

WHAT IS PLUMBERS VS TRENCHERS?

Plumbers vs Trenchers is an asynchronous faction game on Base Mainnet. A fixed collection of Plumber and Trencher NFTs can run missions, score points for a fourteen-day season, and be staked for a rarity-weighted share of WETH generated by canonical-pool trading activity.

The product has three connected layers: on-chain assets and reward vaults, a server-authoritative mission ledger, and public IPFS artwork/reward datasets. Ownership and claims settle on Base; mission availability and daily entitlement publication require the game service.

WHAT LIVES WHERE

• ON BASEToken supply, NFT ownership and rarity, mint burns, canonical swap fees, permanent liquidity, staking custody, staking claims, gameplay roots, and gameplay claims.
• GAME SERVICESIWE sessions, NFT energy, mission state, finalized-block results, season points, leaderboards, and cumulative reward proofs.
• PUBLIC STORAGE64×64 NFT images, token metadata, collection branding, daily entitlement datasets, proofs, and calculation artifacts.

START A SHIFT

1. 01
   CONNECT A WALLET

   Connect Rainbow or another supported wallet and switch to Base Mainnet. Keep a small amount of ETH for gas.

2. 02
   GET <REDACTED>

   Open Trade, request a fresh quote, review price impact and slippage, then buy through the canonical hooked WETH/<REDACTED> pool.

3. 03
   MINT AND REVEAL

   Burn 100,000 <REDACTED> per NFT. The NFT is issued immediately and its unique artwork is assigned by a later randomness callback.

4. 04
   SIGN IN TO PLAY

   Use Sign-In with Ethereum on Missions. This proves wallet control without spending gas and opens a time-limited game session.

5. 05
   RUN MISSIONS

   Select one to three eligible NFTs, a mission tier, and a tool strategy. Return after the timer and complete the result.

6. 06
   STAKE OR CLAIM

   Stake revealed NFTs for weighted WETH, or load the latest gameplay proof and claim the difference owed to your wallet.

Every on-chain approval, trade, mint, stake, unstake, and claim requires Base gas. SIWE signatures and read-only quotes do not transfer assets.

TOKEN, LIQUIDITY & TRADING

The project token is a standard ERC-20 with Permit support. Its one-billion supply is created once. There is no post-launch mint function, blacklist, wallet-transfer tax, or trading pause. NFT mint payments are burned, so total supply can decrease after launch.

As the final deployment transaction, activation deposits the full initial supply into a one-sided WETH/<REDACTED> Uniswap v4 position. The token becomes tradable immediately when that transaction confirms—there is no launch delay or trading ceiling. The starting target is $0.000003 per token, equivalent to a $3,000 starting fully diluted value, checked against a fresh ETH/USD oracle response. This is an initialization point—not a guaranteed price, floor, or future valuation.

HOW THE 3% FEE IS MEASURED

On a buy, the fee is taken from the WETH input. On a sell, the fee is taken from the WETH output. It is a canonical-pool hook fee, not an ERC-20 transfer tax: ordinary wallet transfers and NFT marketplace transfers do not trigger it.

The first-party DApp always requests a fresh canonical quote, applies the selected slippage limit, simulates the transaction, and warns on high estimated price impact. Selling may require an ERC-20 approval to Permit2 followed by a Permit2 approval to the Universal Router.

MINT, BURN & REVEAL

Mint with Permit uses an EIP-2612 typed-data signature and one mint transaction. Approve + Mint is the fallback and may require an approval transaction before the mint.

Once confirmed, consecutive NFT token IDs are issued immediately in a concealed state. One randomness request covers the full mint transaction, whether it contains one NFT or ten. The reveal popup opens from the confirmed mint event, tracks each token on-chain every four seconds, and updates every card when its metadata assignment arrives.

COLLISION-FREE RANDOM ASSIGNMENT

The contract draws metadata from an on-chain sparse Fisher–Yates pool. Each metadata ID can be used only once, and the fixed metadata ranges guarantee the exact final rarity totals. A batch uses the callback randomness, request identity, and each token ID to derive a separate draw.

• NO SAME-BLOCK REVEALA callback in the mint’s request block is rejected.
• PUBLIC RETRYIf unresolved for thirty minutes, any wallet may retry the whole request through the alternate operator.
• REVEALED TO STAKEAn unrevealed NFT has no rarity weight and cannot enter the staking vault.
• FROZEN METADATAThe production IPFS base URI and collection provenance can be frozen once and cannot be replaced afterward.

FACTIONS, RARITY & CREWS

Plumbers occupy the Common and Rare tiers. Trenchers occupy the Epic and Legendary tiers. The listed percentages are the exact share produced by the fixed integer counts.

Weight is used twice: it adds to a mission crew’s combined scoring weight and determines its relative share inside the staking vault. An 8× Legendary has eight times the weight of a 1× Common, but actual WETH still depends on the vault’s total active weight and incoming fee revenue.

CREW RULES

• SIZEOne to three distinct NFTs per mission.
• OWNERSHIPNFTs may be held in the wallet or staked. The game resolves beneficialOwner(tokenId) so staked NFTs remain playable.
• MIXED CREWSThe mission faction is the majority by NFT count. A one-Plumber/one-Trencher tie resolves to Plumbers.
• COMBINED WEIGHTAdd every selected NFT’s 1 / 2 / 4 / 8 weight. Faction does not replace rarity weight.

TEMPORARY DOWNLOAD BAY10 COLLECTION PNGs

ORIGINAL 64 × 64 · FOUR RARITIES

These ten samples are temporary downloads and can be removed from this manual without changing the collection or frozen metadata.

The collection signals a 2.5% ERC-2981 royalty to the deployment admin. This is a marketplace instruction, not an enforced transfer fee; a marketplace may choose not to pay it.

RUN MISSIONS

Mission state is server-authoritative and tied to a SIWE-authenticated wallet. The service checks current on-chain ownership or staking beneficial ownership before a mission begins and again when it completes.

ENERGY & ELIGIBILITY

Every NFT receives three energy each UTC calendar day. Starting a mission spends one energy from every NFT in the crew. An NFT with no energy or another active mission cannot be selected. Energy is recorded when the mission starts and is not refunded if the mission is later cancelled.

1. Connect on Base and sign the SIWE message. The signature does not spend gas.
2. Enter one to three distinct NFT IDs that you beneficially own.
3. Select Patch Job, Pressure Run, or Deep Trench.
4. Commit Cut, Seal, or Pump as the crew’s strategy.
5. Confirm the mission. The service stores its start block, a future result block, timer, crew, weight, faction, and idempotency key.
6. After the timer, complete the mission. Settlement waits until the result block has the configured Base finality confirmations.

A mission cannot start if its timer would end after the current season closes. A repeated start request with the same idempotency key returns the existing mission instead of spending energy twice.

HOW MISSION POINTS ARE CALCULATED

The hidden mission tool and RNG value come from the committed season seed plus a future finalized Base block hash, wallet, mission ID, and ordered NFT IDs. RNG ranges from 0.9000 to 1.1000. The final result is floored to a whole number of points.

TOOL MATCHUP

If your strategy equals the hidden mission tool, the modifier is 1.00. If it beats the tool, it is 1.25; if it loses, it is 0.75.

FOURTEEN-DAY FACTION SEASONS

Before play opens, the game publishes a commitment to a secret season seed. The unrevealed seed is combined with finalized Base block data for mission results. After the season, the seed is revealed so completed missions can be independently reproduced from their public inputs.

Raw population does not determine the winning faction. Active weight-days count the unique NFT weight that participated for a faction on each UTC day. Running the same NFT more than once in a day can earn more mission points, but that NFT’s weight is counted once in that day’s denominator.

• PLUMBERS WINTheir points per active weight-day are higher.
• TRENCHERS WINTheir points per active weight-day are higher.
• TIE / NO ACTIVITYNo winning faction is selected, and an undistributed faction reserve remains unallocated for later operations.
• LEADERBOARDThe public season view reports faction totals and up to the top one hundred wallets by completed mission points.

NFT STAKING VAULT

The staking vault takes ERC-721 custody but records the original staker. That address remains the NFT’s beneficial owner for mission eligibility. Only revealed NFTs can be staked because the contract must read their immutable rarity weight.

REWARD ACCOUNTING

Incoming staking WETH is added to a rolling 24-hour stream and synchronized into an accumulated-WETH-per-weight index. Each account earns continuously according to its active weight divided by total active weight. The vault never loops over every staker.

There is no staking warm-up, claim lock, or reward ceiling. WETH received while no NFT is staked remains queued. When active weight exists, the queued reserve starts streaming second by second over 24 hours. New swap revenue combines with the undistributed remainder and starts a fresh 24-hour window, preventing one wallet from instantly draining a pre-stake reserve.

24H ESTIMATED APY

The Stake page values the 100,000-token NFT mint cost through a fresh canonical <REDACTED>-to-WETH quote, applies the current per-weight 24-hour WETH run rate, and displays a daily-compounded annualized estimate for 1×, 2×, 4×, and 8× rarities.

1. Approve the staking vault for the NFT collection.
2. Enter one or more revealed NFT IDs and stake them.
3. Watch pendingWeth(address); the DApp refreshes it every four seconds.
4. Choose Claim WETH whenever the continuously accrued balance is non-zero, or unstake. Unstaking settles earned WETH before returning the NFT.

WETH REWARDS & CLAIM PATHS

The canonical hook routes every non-zero 3% swap fee before that swap finishes. Half goes to treasury; the rewards half is split 80/20 between NFT staking and gameplay. The receiving asset is WETH, not the project token.

CLAIM PATH A · NFT STAKING

Staking WETH arrives automatically at the vault, rolls into the 24-hour stream, and accrues through its weight accumulator. Open Stake or Claims, check the live amount, and submit Claim Staking at any time. The vault transfers only the already-accrued WETH directly to the connected wallet; claiming does not stop the remaining stream.

CLAIM PATH B · GAMEPLAY

Gameplay WETH arrives automatically at the distributor, but entitlements are calculated and published in daily cumulative Merkle datasets by a restricted root-publisher operation.

• 90% DAILYThe funded individual pool is divided among active wallets in proportion to their completed points for the publication day.
• 10% SEASON RESERVEAfter a season is finalized, its reserve is divided among wallets in the normalized winning faction in proportion to their completed season points.
• NO ACTIVITYIf there are no eligible points or finalized bonus, funds are not assigned by a new root and remain available to roll forward.
• FUNDING LIMITThe contract rejects any cumulative root that promises more WETH than the distributor balance plus amounts already claimed.

1. Sign in with the wallet that earned the points.
2. Open Claims and choose Load Proof to fetch the latest published cumulative entitlement.
3. Review the dataset URI and cumulative WETH amount.
4. Choose Claim Game. The contract verifies the current Merkle proof.
5. Only the difference above claimedCumulative(wallet) is transferred, preventing double claims.

A new root replaces the proof set but preserves each wallet’s cumulative total. Load a fresh proof before claiming. Claimed WETH can be held as WETH or unwrapped separately; the claim contracts do not automatically convert it to ETH.

CONTRACT ROLES & TRUST MODEL

Some protocol settings become permanent at activation; other operational roles remain because missions, randomness callbacks, incident response, and reward publication require them.

• PERMANENT FEE DESTINATIONSTreasury, staking, and gameplay recipients are locked and the splitter renounces ownership.
• PERMANENT LIQUIDITYThe canonical position NFT and rounding dust are held by a contract with no withdrawal method.
• DEPENDENCY PINNINGActivation checks the runtime code hashes of the official Base PoolManager, PositionManager, Quoter, Permit2, and Universal Router.
• SERVER AVAILABILITYThe game authority can delay or censor missions and root publication. Public datasets, seed reveal, finalized blocks, and on-chain claims improve auditability but do not make availability trustless.
• IPFS AVAILABILITYFrozen URIs cannot be edited. Long-term display depends on the pinned primary and archival copies remaining retrievable.
• SMART-CONTRACT RISKTests and fork rehearsals reduce risk but do not replace an independent security audit. Verify the published audit and current addresses before using real value.

COMMON QUESTIONS