More Paperwork / STAPLR

More Paperwork is a memecoin on Base whose mascot is a coral stapler manufacturing its own workload. A trade funds the Receipt Department; the department puts that budget into token pools against different assets; differences between those markets can invite more trades, creating more receipts. The IMD swarm builds and launches the company it jokes about. Holders file Form NTHNG onchain and screenshot the administration they have voluntarily joined. The central joke is visible in one picture: a stapler feeding a loop of receipts back into its own mouth, with three desks on the loop. The mechanism performs the joke rather than merely decorating a financial product.

Problem, timing and distinctive offer

Problem: traders face scattered pools and opaque creator-fee destinations; holders have little to do together except refresh a chart. This is a design diagnosis, not a measured claim about every trader. This concept offers a legible fee destination, a public treasury workload and a recurring, deliberately pointless filing ritual. It does not solve the financial risk of holding a memecoin.

Why now: Zora describes posts becoming tradeable coins [R1]; Clanker's own repository describes social requests deploying tokens on Base [R2]. The chain also has native USDC, a BTC representation and newly announced tokenized gold, while stocks introduce explicit compliance controls [R4-R8]. Those are facts about available ingredients. Our inference is that a company whose bureaucracy grows with trading will land better than another mascot with a vague treasury story. No claim about current launch counts, insider behavior or any real person's conduct is needed.

Culture fit: social coin creation supplies the absurdity; existing social-token tipping supplies evidence that small repeated actions can become part of a token's identity [R1-R3]. Our invented punchline is that every attempt to finish a transaction generates another department. The target of the sarcasm is our own machine and its unnecessary administration. The offer is a memecoin with receipts for what the fee-funded machine actually did, plus a ritual that requires neither repeat trading nor a reward expectation.

IMD gets a public, inspectable example of agents coordinating a company launch, with contract events that can be independently reconciled. The swarm gets its specified allocation for building the work and a memorable authorship story. The assignment says its earlier launch was only a test counter; this is requester-provided context [B1], not externally verified history. The token conveys no equity, treasury redemption or right to an IMD payment. IMD gets no extra launch allocation or vault withdrawal privilege.

Visual identity

The single visual is a coral stapler on warm cream, with a white receipt looping back through its jaws and a thick charcoal outline. Use the same square SVG as a 1:1 avatar and a 32 px icon. The stapler silhouette and paper loop carry the idea without words or fine detail; the delivered SVG has no lettering, gradients, faces, external assets or borrowed logos. At larger campaign sizes, the receipt can carry the three desk illustrations described in BRAND.md. They are not required to recognize the small icon.

Three concepts considered

Scores are editorial judgments, 1 to 5; equal weight per column. Flywheel columns test mechanism legibility, participation and resilience. Meme columns test instant recognition, ritual and visual distinctiveness. All three use the fixed launch facts below.

Concept	One-picture joke	Loop	Roles	Resilience	Instant joke	Ritual	Icon	Total / 30
More Paperwork	Stapler creates receipts that fund more desks and more receipts	5	5	4	5	5	5	29
Please Hold	Telephone queue collects fees to install more hold lines	4	4	4	4	5	4	25
Reply All Department	An envelope breeds inboxes whose replies fund more inboxes	4	4	3	5	4	4	24

More Paperwork wins because a receipt is simultaneously the joke, the onchain evidence and the thing a holder can screenshot. Please Hold's queue makes a busy market look broken and suggests a service awaiting fulfillment. Reply All Department has a good first gag but a less legible explanation for asset pairs; multiplying inboxes also encourages spam as the behavior to imitate. Neither alternative needs its own ticker or brand system.

Fixed launch specification [B1]

Item	Required design
Chain and launch pair	Base, chain 8453; STAPLR / native ETH
Supply	1,000,000,000 STAPLR, 18 decimals
Token behavior	Plain transfers; no transfer tax; no owner mint after launch; no automatic burn in the token
Initial liquidity allocation	35% = 350,000,000 tokens seeds the liquidity pool
Swarm allocation	10% = 100,000,000 tokens to the agents who build it
Developer allocation	55% = 550,000,000 tokens in one transfer to the developer wallet
Subsequent developer action	Developer later manually sends 50% of the original supply = 500,000,000 tokens to 0x000000000000000000000000000000000000dEaD and keeps 5% = 50,000,000 tokens
Launch-pool trading fee	1.25% of every trade: 1% of trade notional, or 80% of the fee, to the launching side; 0.25% of trade notional to the network
Launching-side recipient	Vault contract, including every unit of the launching side's fee share
Additional hook fee	0%

The developer's manual transfer is a required later action, never represented as already done. Until its transaction is visible, the developer controls the full 55%. Tokens sent to the dead address remain in ERC-20 totalSupply: transfers to that address do not call a token burn function. Report the developer transfer and vault purchases separately. Neither mechanism has a stated effect on market value.

Only the specified recipients receive launch tokens. The developer supplies the seed ETH separately, with its amount set at deployment; no vault tokens, liquidity incentives or ritual tokens are minted. This document chooses no wallet addresses. Developer, swarm and network recipients are explicit deployment settings verified before launch and immutable afterward. No assumed recipient or substitute address is authorized.

Chosen mechanism and decisions

The launch pool has a fixed 1.25% LP fee, expressed as 12,500 millionths in v4. An immutable seed-position locker is its sole liquidity provider. All of its collected fees pass through an immutable 80 / 20 splitter to the vault and configured network recipient, in the currency actually collected. Anybody can trigger collection; nobody can redirect it. The hook restricts primary-pool liquidity additions to that locker and prohibits principal removal. Swaps remain open. These are pool restrictions, never token-transfer restrictions. V4 liquidity callbacks support such restrictions [R9]. This avoids silently assuming that v4's own protocol fee equals the assignment's network share.

The launch configuration requires the underlying v4 protocol fee to be zero. The hook checks it before swaps and fails closed if governance later changes it: the 1.25 / 1 / 0.25 split cannot be silently diluted or supplemented. This is a disclosed external dependency [R9], not a claim that a hook can control v4 governance. A later implementation must verify this condition on Base before initializing the pool. A changed protocol fee is an exceptional halt requiring a new reviewed design, not permission to change the fixed facts. No extra hook charge, sniper charge, transfer charge or special first-block fee exists.

Satellite desks are new full-range v4 pools: STAPLR / USDC, STAPLR / PAXG and STAPLR / cbBTC. Each charges 0.30%, with 0% additional hook fee. The vault is their sole LP; other liquidity providers can use other pools. The primary 1.25% fee and its distribution remain unchanged. Satellite fees belong entirely to the vault, subject to any external protocol deduction; recorded rewards always mean fees actually received, never assumed gross fees. Satellite pools and wallets outside this system cannot be forced to route fees to the vault because transfers are plain.

The launch ETH desk plus USD, gold and BTC desks create differing quote-asset exposures. ETH and BTC can be strongly correlated; none of these assets is statistically guaranteed to be uncorrelated. USD and gold broaden the drivers, but every pair still shares STAPLR risk. "Different reference markets" is the defensible claim; "uncorrelated portfolio" is not [R4-R7; inference]. Arbitrage is conditional on discrepancies exceeding all route fees, gas and execution costs. A path through two 0.30% desks already has approximately 0.60% pool fees before other costs; paths through the launch desk cost more. Opening a pool does not manufacture demand.

Pair selection: the developer chooses the above whitelist, exact verified Base asset addresses, routes and feeds before initialization. It is frozen at launch; there is no holder pair vote, no arbitrary-call executor and no later whitelist expansion. Anyone can execute scheduled actions within those bounds. The developer can quarantine a desk immediately, but can restore it only after a public 48-hour delay. Automatic health checks still apply. Quarantined desks receive no new money; their allocation waits in the vault, rather than moving to another recipient. No governance token balance changes these permissions.

Stocks are excluded. The chain's B20 technical description explicitly supports transfer policies, pauses and seizure [R8]. For this joke, that integration and freeze surface is not worth adding. Gold is not free of issuer risk either: PAXG's issuer reserves freezing and upgrade powers [R7]. We accept a bounded gold desk because it adds a distinct reference asset. Bootstrap permits exactly USD 1,000 per desk, with no deepening until all three open; this temporarily concentrates spending in the first one or two desks. After bootstrap, each desk receives at most one third of each new liquidity allocation; unspendable allocations remain queued. This cap limits new spending, not market-value drift or loss. If gold never passes its gates, the existing first desk remains at its bootstrap size and the rest waits. USDC has issuer-blocking and depeg risk [R4]. cbBTC introduces custody dependency [R5]. There is no claim that excluding stocks makes the remaining assets censorship-proof.

Budget policy: reserve 5% of newly collected launching-side fees for gas, conversion costs and keeper reimbursement; earmark the remaining 95% for liquidity. Unused operations money stays in the vault, with no developer salary or sweep. Reimburse only successful work, actual gas up to 1 gwei effective gas price and a fixed 500,000-gas ceiling per action, plus documented conversion fees within the available operations bucket. No keeper tip or failed-transaction reimbursement. A caller can choose not to execute at that cap.

Rewards policy: 25% of the vault's realized satellite LP fees funds market purchases of STAPLR sent atomically to 0x000000000000000000000000000000000000dEaD; 75% returns to satellite liquidity. We choose 25 / 75 because the gag needs an observable disposal tray while most collected fees continue funding desks. The 1% launch fee is not itself split 25 / 75. Principal, donations and operating reserves are never labeled LP rewards. No payments go to holders. Any token-denominated LP fees first sell into quote currency; the buyback bucket then buys tokens on the market. Merely moving fee tokens to the dead address does not satisfy this purchase requirement. Costs can make small batches impractical.

The hook records trades and observations; the vault collects, accounts, converts and supplies liquidity. Keepers call contracts; contracts do not wake themselves. Registry filings create no entitlement. All financial actions use allowlisted routers and exact pool identifiers, bounded approvals, minimum outputs, reentrancy guards and no arbitrary external calls. Contracts are non-upgradeable; the developer has no withdrawal or fee-setting function. This is a proposed specification, not audited or deployed software.

The loop in ten steps

1. The developer funds the seed ETH and the specified token allocation seeds the locked launch desk. The hook begins recording market observations.
2. A launch-desk trade pays 1.25%; its LP fees accrue to the seed locker, claimable through the fixed splitter. Token transfers elsewhere remain untaxed.
3. Anyone collects. The vault receives the launching side's 1% and credits 5% of that receipt to operations and 95% to liquidity. The network receives its 0.25%.
4. After the safety window and funding threshold, anyone executes the next desk opening. The queue is USDC, then PAXG, then cbBTC. Each needs USD 1,000 of total paired liquidity, bought using accumulated budget; no extra launch tokens are diverted.
5. Each opening purchases STAPLR and its quote asset in approximately equal marked value. Existing fee tokens may supply the STAPLR leg. After all three desks open, new liquidity is allocated equally, with a USD 100 minimum addition per desk. Bootstrap purchases are liquidity acquisition, not buybacks.
6. Independent asset moves and ordinary token orders can leave quotes inconsistent. Arbitrageurs choose whether a route is worth executing and pay its fees. Nothing obliges them to trade.
7. Anyone harvests realized satellite LP fees into separately tracked reward balances. Those fees stay in the vault: 25% to the buyback bucket, 75% to liquidity.
8. A safe, sufficiently funded buyback purchases STAPLR and transfers its actual output to the dead address in the same transaction. A failed safety check leaves the budget queued.
9. Equal-weight desk additions use accumulated liquidity buckets. Successful harvests and additions emit receipt events; a holder can file Form NTHNG without trading again.
10. Receipts become voluntary screenshots; people may become curious and make new trades, returning to step 2 or step 6. Attention is a possible social link, never a contract guarantee.

One diagram, with the cost and trigger on every arrow

N means this arrow can execute using already funded assets, without a new capital contribution. C means it is conditional on market activity, counterparties or a volunteer. Neither means perpetual motion. Gas reimbursement is included only while the operations reserve can pay it.

[LAUNCH TRADE]
  | A: trader pays 1.25%; swap triggers accrual; C
  v
[SEED LOCKER + 80/20 SPLITTER]
  | B: accrued fees pay; anyone collects; N, caller needed
  |---- Bn: accrued fees pay network 0.25%; same collection; N
  v
[VAULT: launching-side 1%; operations 5% / liquidity 95%]
  | C: vault budget pays both asset legs and costs;
  |    USD 1,000 opening or USD 100 deepening threshold + health gates; N
  v
[USD / GOLD / BTC DESKS]
  | D: arbitrageur supplies trade inputs and gas;
  |    actionable quote discrepancy or ordinary order; C
  v
[SATELLITE TRADES]
  | E: trader pays 0.30%; swap then harvest; N from finite trader inventory
  v
[REALIZED LP FEES IN VAULT]
  | F: 75% pays paired-liquidity additions; thresholds + health gates; N
  |--------------------------------------------------> [DESKS]
  | G: 25% pays market purchase; safe batch threshold; N
  v
[PURCHASE OUTPUT SENT TO DEAD ADDRESS]
  | H: no token payment; operation gas comes from its bounded reserve;
  |    a real successful operation updates receipt counters; C
  v
[PUBLIC RECEIPTS + VOLUNTARY HOLDER FILINGS]
  | I: poster pays own gas/time; viewer supplies trade input and gas;
  |    voluntary screenshot and new order; C
  +--------------------------------------------------> [LAUNCH OR SATELLITE TRADE]

Arrow H updates counters automatically with the successful operation; filing is a separate voluntary transaction paid by the holder, without vault reimbursement. No money flows from the dead address. It is not a source of funding. Primary fees can also produce receipts without any buyback. Arrow E can persist for a while with recycled trader inventory; neither trader inventory nor vault principal is inexhaustible. Arbitrage spends inventory and transfers losses; it does not create money. With zero new net capital, changing external markets can still prompt trades, but no arrow promises continuing activity. With no counterparties and no usable reserve, execution stops safely. "Slows instead of dying" means no forced liquidation or recurring bill, not everlasting activity.

Players, permissions and visible reasons to participate

Role	Why participate	Can do	Can see onchain
Early buyer	Be present for the first absurd filing shift	Buy normally; opt into a first-day stamp during the first 24 hours	Launch timestamp, own swap and first-day registry event; same fee as anyone else
Holder	Belong to the joke without trading to maintain a streak	File Form NTHNG once per epoch with a current balance of at least 1 STAPLR	Filing events, real collection counters, pending manual developer transfer
Active trader	Trade an instrument and attach a public receipt to a real trade	Opt into one qualifying trade stamp per seven-day epoch	Actual fee paid, validated attribution, no notional leaderboard
Arbitrageur	Execute routes when market discrepancies justify the full costs	Route freely through the desks; decline uneconomic routes	Pool state, fee rates, depth, vault transaction bounds
Developer	Complete the launch design and its visible operating constraints	Configure before launch; perform manual 50% transfer; quarantine within the fixed rules; keep specified 5% afterward	Single initial 55% transfer, manual dead-address transaction, all controls and remaining balances
Swarm	Build a company whose operation is independently inspectable	Build, review, publish receipts voluntarily, and hold or transfer its specified 10%	Its allocation, contract events and fee accounting; no exclusive keeper path
IMD	Demonstrate agent coordination with public evidence	Observe, document and maintain optional interfaces; no special vault authority	Same public balances, events and registry as everyone else

The first-day stamp is earned only after a real launch-desk trade plus an explicit registry call; it allocates no tokens. Active stamps require at least USD 1 of actual launch fee paid, measured with the configured quote-asset feed, and a signed intent bound to chain, pool, nonce, recipient, amount and deadline through the designated gateway. Other routers may trade but receive no attributed stamp. No trust is placed in arbitrary hookData for trader identity. Keeper operations and vault-owned trades never earn stamps. The public table is alphabetical by address with yes/no epoch stamps, not volume rankings. These are cosmetic records, not transferable assets, fee rebates, multipliers, raffle entries or future distribution criteria. The developer cannot later attach vault spending or voting power to them.

Numbers: transparent budget arithmetic, not activity forecasts

USD is an accounting unit, not an assumed token value. A week is 7 days and a month is 30 days. V is external launch-pool daily volume, excluding vault purchases, conversions and reinvestment trades. For the mature illustration only, assume additional external satellite volume S = 20% of V, all three satellites already open, the vault owns 100% of their LP, no protocol deduction, no asset-value movement and successful execution. Actual satellite volume can be zero. USD marks use configured external quote feeds and a guarded STAPLR TWAP; they are not a reliable liquidation value.

Gross launching budget B = 0.01 V. Realized satellite fees R = 0.003 S. Operations earmark O = 0.05 B. Liquidity allocation L = 0.95 B + 0.75 R. Buyback purchase-input allocation Q = 0.25 R. B + R = O + L + Q; there is no double counting. Gas, route fees and slippage consume the operations bucket in this simplified model; if the bucket cannot cover them, execution waits. Daily buyback figures below are allocation rates; actual spending is batched and can be zero on a given day.

Mature-state assumption / allocation	V = USD 10,000 / day	V = USD 500,000 / day
Launch fee paid by external traders / day	125	6,250
Network share / day	25	1,250
Vault launching budget B / day	100	5,000
Assumed satellite external volume S / day	2,000	100,000
Realized satellite LP fees R / day	6	300
Operations earmark O / day	5	250
Buyback input Q / day, before execution	1.50	75
Liquidity allocation L / day	99.50	4,975
Liquidity allocation / week	696.50	34,825
Pools opened / week; pools deepened / week	0; 3	0; 3
Liquidity allocation / 30-day month	2,985	149,250
Pools opened / month; pools deepened / month	0; 3	0; 3

Three means distinct pools touched, not three new pools every period. At the low case, a weekly addition is approximately USD 232.17 per desk; at the high case it is approximately USD 11,608.33. Both clear the USD 100 addition minimum. Unspent rounding stays in its bucket. No fees from an unopened pool are assumed. For a conservative opening-only comparison, set R = 0 throughout, even after opening:

Start with zero satellites, constant primary V	USD 10,000 / day	USD 500,000 / day
New-liquidity budget after operations / week	665	33,250
New desks opened by day 7	0	3
New-liquidity budget after operations / day 30	2,850	142,500
New desks opened by day 30	2	3
Budget after opening cost by day 30	850 queued for desk 3	139,500 for deepening
Buyback spending in this zero-rewards comparison	0	0

The seed ETH desk is already open and is not counted as a new satellite. Under these conservative assumptions, low-case openings become eligible on days 11, 22 and 32; high-case openings become funded on day 1, subject to safety gates and execution limits. The remaining USD 850 is reserved for the third desk, not also counted as deepening. These are threshold calculations, not promised opening dates. Issuer controls or missing viable routes can delay a particular desk indefinitely.

Cold start and a 90% volume drop

First 24 hours: initialize the primary desk and locker with the specified token allocation and developer-supplied ETH. Begin a 2-hour observation window. First-day and holder filings work immediately; no airdrop countdown exists. No satellites start pre-funded and no LP rewards exist until they actually trade. Keepers can collect primary fees immediately, but swaps by the vault wait for the observation window, feed checks and sufficient liquidity. At low-case volume the first day's USD 95 liquidity budget stays queued. At high-case volume USD 4,750 can fund the three USD 1,000 desks if safe routing is available; remaining money is earmarked equally for later additions. The interface must show a closed or quarantined gold desk honestly rather than replace it with an unverified wrapper.

After a 90% drop from the low mature case, V = USD 1,000, B = USD 10, assumed S = USD 200, R = USD 0.60, O = USD 0.50, L = USD 9.95 and Q = USD 0.15 per day. Three USD 100 additions need approximately 31 days to accumulate. A USD 10 buyback input batch needs approximately 67 days, if costs and safety allow. A drop from the high case similarly scales every modeled flow by one tenth. Existing full-range positions remain; no leverage, salary, rent, minimum payout or liquidation deadline consumes them. There is no compulsory rebalance just because time elapsed. Operations money accumulates rather than paying idle keepers. With no LP fees, buybacks have no new funding; with no trades anywhere, no new fee budget exists. The system becomes idle without a forced unwind.

Execution safety and abuse

Wash trading for points: no volume score and no monetary reward. A wallet can receive at most one active stamp per epoch. A wash trader still pays the full launch fee and gas, including at least USD 1 in qualifying fee, for a binary cosmetic mark. Vault actions and related gateway self-routes are excluded from stamp accounting. Sybil wallets can still manufacture decorative marks; do not pretend an address cap proves unique humans. Because stamps control neither money nor pair selection, that remaining exploit cannot redirect the vault. Holder filing needs no trade, removing pressure to churn a position to participate.

Sandwiching and manipulated marks: no predictable, unlimited daily market order. Each market swap is capped to the smallest of the funded bucket, USD 100 equivalent and 0.10% of the chosen execution pool's marked quote-side reserve per slice, with a minimum slice of USD 10. At most one vault market-swap slice per block and a 60-second gap between slices. Cap checks are aggregated across callers. Liquidity acquisition can accumulate assets over many swap slices before a USD 1,000 opening; the deposit itself is not a market swap and is exempt from that swap-size cap. Revalue acquired inventory before depositing; insufficient paired value stays queued. Each buyback, conversion and acquisition uses a 30-minute time-weighted STAPLR reference built from hook observations, at least 2 hours of observation history and contemporaneous quote-asset feeds. Require spot within 1% of reference and minimum output within 0.50% of the reference after disclosed pool fees. The 0.50% tolerance excludes known fees, so a 1.25% fee is not itself a failed slippage test. Reject an action if its size would violate the output bound; leave its bucket untouched.

Feeds must have positive answers, valid round completion, updates within twice their documented heartbeat and a healthy Base sequencer feed with a 1-hour recovery grace period. Gold execution also requires two fresh feed updates at least 30 minutes apart; a stale reference during a market closure queues gold spending. Quotes are not freshness checks by themselves. Require at least USD 20,000 marked primary-pool liquidity and USD 50,000 on each external quote-conversion route used; the newly created satellite's own price cannot certify its initialization. Small new satellites can open using the established primary reference plus an independently checked external asset route. Routes, feed addresses and heartbeats are deployment settings published before initialization, not guessed in this document.

Private submission can be attempted but is not a protection assumption. Tight outputs, small slices and ability to skip limit extraction; they do not eliminate sandwiches or sustained TWAP manipulation. If depth or feed integrity fails, wait. At USD 1.50/day buyback allocation, the USD 10 minimum alone implies batches rather than daily purchases. At high volume, the slice cap permits more calls, paid only within the operations reserve. Contract time gates describe the future program; this assignment waits on no clock.

Whale capture of pair voting: there is no pair vote to capture. We explicitly choose developer selection over a token vote. No amount of STAPLR or registry activity can add a quote asset, alter the split, withdraw principal or appoint a recipient. The cost is initial developer selection risk and no rapid permissionless addition of a new asset. Frozen whitelist, public initialization and limited quarantine authority make that tradeoff inspectable. Any informal popularity poll is nonbinding and must never be presented as governance.

Three principal risks and the design response

Risk	Why it matters	Response and remaining limitation
Impermanent loss and adverse selection	Vault LP inventory can become less valuable than simply retaining the two assets; arbitrage can extract value from stale quotes. Sharing STAPLR across all desks concentrates risk.	Full-range unlevered positions, USD 1,000 bootstrap limits, one-third new-spending caps after bootstrap and no forced rebalancing reduce operational fragility. Compare current inventories with deposited-asset benchmarks publicly. Fees are not assumed to offset losses; principal can be depleted economically.
Issuer, reference and contract failure	Stablecoin depeg/blocking, BTC custody, gold freezes, stale feeds, hook defects or v4 fee governance can block use or lose funds [R4-R9].	No stocks, no leverage, bounded routes, independent checks, per-desk quarantine and a primary-fee fail-closed check. Audit and adversarial simulations are later build requirements. Freezing cannot be undone by this vault; disabled routing can mean an indefinite pause.
Demand exhaustion and concentrated launch holdings	Attention can disappear; until the manual transfer the developer holds 55%, afterward 5%; the swarm has 10%. Neither holder controls nor rituals create buyers.	Show actual balances and manual-transfer status, lock seed LP principal, batch small work and incur no fixed operating bill. Allocations are liquid unless their owners separately choose otherwise; do not imply a vesting lock. There is no guaranteed activity, buyback execution or capital recovery.

Evidence, uncertainty and completion boundary

[B1] means fixed facts or context supplied in this assignment. [R1]-[R13] resolve to the titled source records in RESEARCH.md. All other mechanism parameters are design decisions; dollar tables are explicitly conditional arithmetic. No deployment, hosting, publication, token sale or contract audit has happened in this job.

The later builder must bind authentic recipients and verified Base assets, feeds and pool IDs through deployment configuration; these are intentionally configurable launch inputs, not unknown values filled with stand-ins. Available gold execution depth, live v4 protocol-fee settings and real keeper costs are not established by this document. Each has a defined execution gate rather than an assumed favorable answer. Ticker search found no STAPLR collision within the stated coverage, not a proof that no unindexed token exists. Recheck before launch; a discovered collision requires renaming the design, not silently using an already taken ticker.