Department of More

Design specification, 2026-11-09. Ticker: DEPTMORE. Documents only; nothing has been deployed, hosted or published. [B0] denotes the assignment; [Rxx] denotes evidence catalogued in RESEARCH.md. All mechanisms, thresholds, scores and scenarios below are original design choices, not observations of a running product.

The idea

Department of More is a memecoin on Base whose company manufactures its own paperwork: a swap funds the office, the office opens more trading desks, and activity at those desks pays for more desks and a small, conditional market-buyback queue. Its mascot is a receipt printer feeding its receipt back into itself. The IMD swarm gets a deliberately ridiculous first-company story: it automated the work, then created an entire department to process the automation. Holders file an onchain complaint asking for less paperwork and receive a stamped rejection to screenshot. The joke is the actual money path: "Every swap creates more paperwork." There are no holder fee payments, redeemable points or claims on the vault.

Problem, why now, and the offer

The problem is participation that ends at the first screenshot. A trader can recognize a meme without having a reason to revisit its workings; a holder can see volume without seeing where the launch-side fees went. Those are design hypotheses, not measured claims about every trader. Department of More turns both into a continuing, inspectable joke: new desk receipts, budget receipts, a complaint registry, and publicly visible queues when nothing can safely execute.

The timing has concrete context. Zora documents posts becoming tradable coins; Clanker documents launching from a social cast. Base's chain publications celebrate onchain participation and now describe markets spanning more asset classes. [R01, R02, R03, R04] This design borrows the recognizable habits of posting, collecting proof of attendance and checking the next launch, while making its own repetitive administrative behavior the target of the joke. It does not assert that particular traders, projects or people behaved badly.

The distinctive offer is a company whose expanding org chart is a set of actual liquidity positions. A holder's screenshot says "LESS PAPERWORK: DENIED" beside a verifiable case number. A new pool is a new department; a dormant queue is "OUT OF TONER." Neither needs a chart or a financial claim to be funny. The picture works before the mechanism is explained.

For IMD, this is a public demonstration of agents producing a coherent brand, constrained contracts and inspectable operations. For the swarm, it is a concrete artifact and the specified 10% launch allocation, not a claim that agents have previously operated a large company. The only prior Base deployment stated in the brief is a test counter. [B0] Show deployment and operation receipts when they exist; do not invent a track record. "Company" describes this operating project, not an equity interest conferred by the token.

Three concepts considered

Scores are editorial judgments, each out of 10. The flywheel score covers fee capture, asset diversity, execution, cold start and abuse resistance. The meme score covers immediate recognition, original visual, ritual and repeatable jokes. Both receive equal weight.

Concept	Picture and different player mechanism	Flywheel /10	Meme /10	Total /20
Department of More	A printer consumes its own receipt. Fee-funded desks generate new receipts; mature holders file rejected complaints. Attendance has no financial rights.	9	9	18
Reply All Forever	One envelope spawns an inbox at each asset pool. Traders voluntarily relay a receipt to another consenting participant; completed relay chains form the public board.	7	8	15
Emergency Meeting	A conference table keeps adding chairs. Holders call an onchain meeting to request the next funded desk, with an attendance quorum.	6	7	13

Reply All Forever lost because repeated invitations can become unwanted messaging and its envelope does not show where the budget goes. Emergency Meeting lost because a quorum can stop the joke during quiet periods; removing the quorum makes the ritual less distinctive. Department of More needs neither invitations nor a crowd to keep its records usable. Its score is not a claim that trading demand is assured.

Fixed launch facts

These are requirements from [B0], not parameters open to governance.

Item	Exact design
Chain and launch pair	Base, chain 8453; DEPTMORE paired with native ETH.
Token	1,000,000,000 tokens; 18 decimals; plain transfers; no transfer tax; no owner mint after launch; no automatic burn in the token.
Liquidity allocation	35%, or 350,000,000 tokens, seeds the launch liquidity pool.
Swarm allocation	10%, or 100,000,000 tokens, goes to the swarm, the agents who build it.
Developer allocation	55%, or 550,000,000 tokens, goes in one transfer to the developer wallet. This is not split by the distributor.
Developer's subsequent manual step	The developer personally sends 50% of the original supply, or 500,000,000 tokens, to 0x000000000000000000000000000000000000dEaD and keeps 5%, or 50,000,000 tokens. Show this as pending until the transfer is observed. The token does not enforce or schedule it.
Launch trading fee	1.25% of every trade: 1% of trade notional, which is 80% of the fee, to the launching side; 0.25% of trade notional to the network.
Additional hook fee	0%. No extra surcharge, no fee ramp and no transfer fee.

Both specified burn mechanisms are transfers to the full dead address above. They do not invoke a token burn function or reduce ERC-20 totalSupply. Track the developer transfer and vault market purchases separately; unrelated transfers to that address are neither of those counters. No quantity or schedule of vault buybacks is guaranteed.

The launching side supplies 5 ETH of launch-pool seed capital, separately from token distribution. This is a chosen launch requirement, not a claim that funds have been received. Deployment gas is also a launching-side expense. Neither creates another token allocation. Recipient addresses are deployment inputs supplied by the launching side in the later launch job; this document invents none.

Money, custody and execution decisions

The token is a simple fixed-supply ERC-20. All registry, fee accounting, liquidity and buyback behavior belongs to separate contracts. The token, locker, vault, collector, hook and registry are non-upgradeable; no proxy administrator can replace their limits. Uniswap v4 supports native ETH and pool hooks; those capabilities do not themselves implement this design. [R12, R13]

Use a permanent launch LP locker and a separate vault. The locker holds the initial full-range ETH position and has no principal-withdrawal path. Its fee collector sends the required 80% fee share to the vault and 20% to the network recipient, in each collected currency. The vault owns the satellite LP positions. Only the locker or vault can add liquidity to the official pools, so third-party LP ownership cannot silently dilute the promised fee routing. Anyone may swap. Anyone may make an unrelated pool; a plain-transfer token cannot force that pool to fund this vault.

Use the same 1.25% pool fee and 80/20 launch-side/network division on every official satellite as well. This deliberately avoids making a cheaper official bypass. The hook surcharge remains 0% everywhere. An implementation must verify the total charge and recipients in both swap directions, including underlying protocol charges; do not import another launcher's defaults. Current Clanker fee documentation is evidence of a cultural pattern, not a compatible fee specification. [R02]

Keep three disjoint ledgers:

• Launch income: the launch pool's 1% share. Allocate 95% to new liquidity and 5% to an operating reserve inside the vault. The reserve only pays bounded execution costs; unused amounts remain visible in the vault.
• LP rewards: the vault's satellite fee share after the network's 0.25% has been separated. Allocate 20% to a market-buyback queue and 80% back to liquidity. Nothing goes to token holders or the developer.
• Principal: LP inventory and unspent allocations. Removing or migrating a satellite position never turns principal into LP rewards. Assets can only remain in the vault or enter an approved position.

Fees can arrive in either token of a pair. Preserve DEPTMORE fee inventory for liquidity where possible. For a reward batch, value the entire collected fee basket with the guarded reference described below, reserve 20% of that value from its non-DEPTMORE assets for buybacks, and assign the remaining basket to liquidity. If quote assets cannot cover the full 20%, leave that batch unsettled until a later collection supplies them; do not send fee-received DEPTMORE directly to the dead address. The split applies to settled batches, with pending inventory separately visible. This avoids pretending that receipt of a token fee was a market purchase.

Buybacks convert the earmarked quote inventory to ETH if necessary, buy DEPTMORE through the launch market, and transfer the actual bought amount to the dead address in the same transaction. The 20% is a spending allocation including that route's trading costs, not a promised token amount. The other 80% is a liquidity spending allocation including its execution costs.

Vault-origin swaps pay the same fees. Attribute their fee recirculation separately, never to external volume, player attendance or new earned rewards. Internally recovered fees return to their originating spending ledger; the network portion and external route costs leave it. An execution receipt reconciles gross input, assets added, fees recovered, external costs and any unspent remainder. No recursive "fees on our fees" growth is included in the model.

Keepers call public collect, settle, add-liquidity and buyback functions. Contracts do not wake themselves. The swarm may run a keeper, but anyone can execute the same allowed transaction. After a successful batch, a single reimbursement is the lesser of metered execution gas multiplied by the transaction gas price, $2 equivalent and 0.25% of batch notional, paid from the operating reserve. This does not promise reimbursement of all transaction overhead or data-availability costs. There is no discretionary keeper tip. If the reserve or a willing caller is absent, the batch waits; positions and balances persist.

The desks and who chooses them

The developer chooses the following immutable pair list and allocation policy before launch. There is no holder pair vote and no later power to add a surprise asset. The contracts open and deepen approved desks when gates pass, without a manual approval step. A holder's complaint is theater, not a treasury instruction.

Desk	Pair	Share of new satellite LP spending	Reason
Reception	DEPTMORE / native ETH	Initial launch position only	The required launch market and reference for market purchases.
Petty Cash	DEPTMORE / native USDC	70%	Dollar reference and a documented native asset on Base. [R05]
Heavy Filing	DEPTMORE / cbBTC	25%	A separate Bitcoin reference and observed Base trading routes; custody remains a risk. [R07, R17]
Archive	DEPTMORE / VNXAU	5%	A gold reference with a documented Base token and a real VNXAU/USDC market. Small allocation reflects thinner routes and issuer dependence. [R08, R17]

The economic drivers are dollar cash, Bitcoin and physical gold, alongside ETH at reception. This is a deliberately less correlated set than several ETH wrappers. No source here proves a zero-correlation matrix; crypto assets can move together and gold can move with them. "Independent prices" means external reference markets can move differently, not statistical independence or protection from losses. Every position still contains DEPTMORE.

Use full-range, unlevered positions. No borrowing, narrow-range harvesting, LP incentive token farming or holder deposits into the vault. Each newly created satellite needs at least $500 equivalent of deposited inventory, approximately half in DEPTMORE and half in its paired asset at entry. Buy the required DEPTMORE from the market or use legitimately collected token fees; there is no extra launch allocation. Once open, deepen in $50 inventory increments, carrying dust forward. Allocate spending 70/25/5 before batching. A desk below its opening threshold accumulates its own allocation instead of fragmenting into dust pools.

Acquiring the two assets can take several guarded transactions before the atomic LP deposit. Staged assets remain tagged principal for that desk. Cap each acquisition swap at the lesser of $250 equivalent and 0.1% of the route pool's quote-side inventory, with the same minimum-output checks as buybacks. Thus a $500 opening requirement does not force a single large purchase through the thin launch market. The $50 top-up increment describes deposited inventory, not a minimum individual acquisition swap. If a stage cannot execute, keep both its unspent budget and already acquired assets visible.

Require at least 6 hours of usable observations and an external quote-asset route with at least $75,000 equivalent of pool inventory reconstructed from onchain state, plus an onchain executable quote meeting the impact limits. An indexer's reported liquidity never passes the contract gate by itself. The gold desk also has a hard 10% cap on cumulative satellite acquisition cost; its normal 5% allocation stays below it. These are spending limits, not a promise that market-value weights stay fixed. If a gate fails, that desk's allocation stays idle; the other desks continue.

Pin the external reference routes to the three chain-checked pools in RESEARCH.md. Read their cumulative observations through immutable adapters, and have the launch hook record cumulative ticks for the new ETH market. The execution reference for a satellite combines that launch-market reference with its counterpart's USDC route and the WETH/USDC route. Treat USDC as the dollar accounting unit for thresholds; actual dollar equivalence is a scenario assumption, not a peg guarantee. Require observation coverage for each window and a latest recorded observation no older than 15 minutes. Anyone can checkpoint cumulative observations without trading. Missing history or an unsupported observation interface disables the affected desk, rather than authorizing a guessed feed or a manually supplied quote. The later implementation must verify those interfaces before enabling the desk.

EURC was researched and has Base markets, but adding another issuer-linked fiat desk before these three are useful would fragment the budget. [R06, R17] Tokenized stocks are excluded: the chain's B20 documentation describes transfer restrictions, pause and seizure controls, and issuer-operated adjustments. [R09, R10] That additional integration and issuer-freeze surface is not worth a fourth satellite for this meme. Gold still has issuer risk; its small gated allocation is an explicit tradeoff, not an assertion that it is permissionless physical gold.

The developer can pause new vault spending immediately and propose resumption with a 48-hour timelock; anyone can execute the matured resumption subject to the guards. The developer cannot withdraw principal, change the fee split, change the reward split, change the pair list or pause token transfers. A failed asset stays quarantined in the vault; no promise is made that a frozen asset can be recovered. Expose all pause and resumption events.

One flywheel diagram

flowchart TD
  T[Traders and arbitrageurs] -->|A| P[Official ETH market and satellite desks]
  P -->|B| F[1.25% trading fee]
  F -->|C| N[0.25% of trade to network]
  F -->|D: launch market| L[1% of trade to launch-income ledger]
  F -->|E: satellite markets| R[1% of trade to vault LP-reward ledger]
  L -->|F: 95%| P
  L -->|G: 5%| O[Vault execution reserve]
  R -->|H: 80%| P
  R -->|I: 20%| Q[Conditional market purchase then dead-address transfer]
  P -->|J: reference-market gaps| T
  P -->|K: receipts| S[Complaint stamps and public desk records]
  S -->|L: voluntary attention| T

Every arrow is accounted for below. "Without new money" means no net new funding enters the system after launch; holders may still circulate existing inventory. It never means unlimited activity.

Arrow	Who pays or supplies it	Trigger	Can it continue without new money?
A	Trader supplies input assets and gas.	Voluntary swap.	Existing inventory can trade, but willingness and capacity are finite.
B	Trader pays the stated pool fee.	Executed swap.	Only while swaps continue.
C	Fee payer funds the network recipient.	Fee collection.	Existing accrued fees can be collected once; no new swap means no new fee.
D	Launch-market traders fund the vault's launch ledger.	Launch fees collected.	Accrued inventory persists; the ledger cannot replenish itself.
E	Satellite traders fund the vault's LP rewards.	Satellite fees collected.	Conditional on real trades, including external arbitrage.
F	Vault spends 95% of launch income; caller fronts gas.	Pair threshold and execution guards pass.	Previously accumulated budgets can fund finite batches.
G	Launch-market fee payers fund execution overhead.	Launch income allocation.	Existing reserve pays finite work, then waits.
H	Vault spends 80% of settled LP rewards.	A desk reaches its next spending increment.	Previously collected fees can be reused once, not multiplied.
I	Vault spends the 20% reward allocation; market sellers provide tokens.	A permitted batch buys tokens and atomically sends them to the dead address.	Only until earmarked funds are exhausted; execution can be zero.
J	Arbitrageur supplies inventory and gas; LP inventory bears rebalancing.	External references diverge sufficiently to clear all route costs.	Possible using existing capital while references move; impossible as a perpetual source in a static closed market.
K	Executed contracts emit records; holder pays complaint gas.	A real action produces a receipt, or an eligible holder files.	Existing holders can keep filing at their own gas expense; records already exist.
L	Participants supply attention; a new trader funds any resulting swap.	Someone voluntarily responds to a receipt or joke.	Attention may continue, but conversion to trading is an unproven hypothesis.

Chosen loop in ten steps

1. Seed the required ETH launch pool, lock its LP principal and record the exact launch distribution.
2. A voluntary swap pays 1.25%; the required 1% launching share accrues to the vault, with 0.25% for the network.
3. The vault reserves 5% of launch income for execution and queues 95% for desks.
4. Once observed references and minimum capital exist, it opens the USDC, cbBTC and VNXAU desks under the fixed 70/25/5 policy.
5. Each position emits a desk receipt. Holders can inspect its assets, fees and pending allocation.
6. Divergent external references can motivate arbitrage across desks; a round trip through two official pools faces two 1.25% fees plus other costs. Small differences will simply be left alone.
7. Satellite fees are collected; the vault's share stays in its separate LP-reward ledger.
8. Settle eligible reward baskets: 80% funds more liquidity; 20% queues market purchases whose actual token output is sent to the dead address.
9. Eligible holders file complaints and screenshot the stamped record; early and active participants receive factual attendance labels only.
10. Visible receipts and the running joke may attract voluntary visits and trades. If they do not, spending batches become less frequent and existing positions remain.

Roles, motives and visible powers

Role	Reason to participate	Can do	Can verify onchain
Early buyer	A permanent First Shift attendance label, without an allocation bonus.	Buy through the identified launch route during the first 24 hours and open a file.	Launch time, own trade, fee payment and later qualification.
Holder	Recurring complaint theater and inspecting what the company actually did.	Escrow 1 DEPTMORE, mature the file for 7 days, file complaints and withdraw the same escrowed token after maturity.	Escrow, maturity, stamps, positions and vault queues.
Active trader	A recognizable attendance record rather than a size contest.	Opt into signed attribution through the registry-compatible router; trade normally elsewhere without registry credit.	At most one credited trading day per UTC day; no volume ranking.
Arbitrageur	Independently evaluate executable cross-market discrepancies.	Quote and trade any official pool; optionally execute vault work.	Pool state, fee schedule, reference observations and route costs. No outcome is promised.
Developer	Ship a coherent launch and protect its operation.	Supply seed ETH; receive the fixed 55%; perform the manual 50% transfer; retain 5%; choose the initial whitelist; exercise the bounded pause role.	Distribution, manual-transfer evidence, timelocks and all administrative actions.
Swarm	A verifiable building and operating record, plus its fixed 10% allocation.	Build, review and run a permissionless keeper. Its allocation is not represented as vested or locked.	Its receipt, deployed code and successful or skipped execution events.
IMD	A reproducible company-launch demonstration and the specified network fee stream.	Operate the network recipient and inspect the launch; no extra power over the vault is implied.	Network fee receipts and the same public records as everyone else.

The holder ritual and player rules

Call openFile to escrow exactly 1 DEPTMORE in a separate registry. After 7 days, call fileComplaint with the fixed category LESS PAPERWORK. The contract emits a case number and the immutable response MORE PAPERWORK REQUIRED. The screen renders "LESS PAPERWORK: DENIED" with the wallet, transaction hash, filing day and desk count at that block. Screenshot it. A file can receive one complaint stamp per UTC day while its escrow remains; withdrawal after maturity is always available and ends eligibility. Historical stamps remain historical.

First Shift requires a verified market buy in the first 24 hours and a subsequently matured file; there is no presale or private early-buy entitlement in this design. Active attendance requires one attributed official-pool swap of at least $20 reference notional that day, plus a mature file. A compatible router authenticates the account and binds attribution to the actual swap; never infer the trader from tx.origin or blindly trust arbitrary hook data. Bad or unavailable reference data means no attendance credit, not a blocked ordinary swap. Vault transactions receive no attendance.

The public table sorts by filing day and case number, not balance or volume. Labels are nontransferable registry data, not minted reward assets. They never unlock token distributions, fee rebates, an airdrop, a treasury claim or financial voting power. The hypothesized budget effect is repeated voluntary attention and some voluntary trades; the design does not pay people to manufacture volume.

Numbers: an explicit scenario, not a forecast

V is total external daily volume across all official pools, counted once per pool leg. Assume 80% at the launch market and 20% across existing satellites; arbitrage legs count as trades, not additional unique users. All three satellites already exist for this steady-state table. No new pools are counted. Assume sufficient quote-denominated rewards to settle the baskets, stable reference accounting during each batch, successful guards, a willing keeper and at least $25,000 equivalent of quote-side launch inventory for the modeled purchases. That depth is a scenario input, not a valuation of the 5 ETH seed. The satellite volume fraction is an assumption, not an estimated causal multiplier.

Amounts are USD equivalents for arithmetic, not token quotations; assume one USDC corresponds to one USD in these scenarios. One week is 7 days; one month is 30 days. The liquidity spending envelope reserves 2% for conversion, fees and execution difference; net added inventory is 98% of that envelope. This allowance is an assumption and actual spending must pass guards. Buyback spend includes its route fees. Gas comes from the separate 5% reserve. Changes in existing inventory value and impermanent loss are excluded from the cash-flow table, not assumed absent.

Metric	V = $10,000/day	V = $500,000/day
Total pool fee, 1.25% V	$125/day	$6,250/day
Network, 0.25% V	$25/day	$1,250/day
Total vault receipts, 1% V	$100/day	$5,000/day
Of that: launch-income budget, 1% of 80% V	$80/day	$4,000/day
Of that: satellite LP rewards, 1% of 20% V	$20/day	$1,000/day
Operating reserve, 5% of launch income	$4/day	$200/day
Buyback spending, 20% of LP rewards	$4/day average	$200/day average
Liquidity spending, 95% of launch income + 80% of LP rewards	$92/day	$4,600/day
Net new LP inventory after assumed 2% execution cost	$90.16/day	$4,508/day
Weekly net inventory available before $50 batching	$631.12	$31,556
Weekly pools opened / existing pools deepened	0 / 2	0 / 3
Weekly inventory actually placed in $50 increments	$550	$31,450
Monthly net inventory available before $50 batching	$2,704.80	$135,240
Monthly pools opened / existing pools deepened	0 / 3	0 / 3
Monthly inventory actually placed in $50 increments	$2,600	$135,200

At low volume, weekly allocations are $441.784 / $157.78 / $31.556 for USDC / cbBTC / VNXAU. They place $400 / $150 / $0; the remainder waits. The month is computed from a fresh zero-dust starting balance, not by adding it to the weekly row. Repeated top-ups to one pair are not counted as new pools.

The buyback queue has a $10 minimum. In the low scenario, $4/day can mean a $12 batch every third day and $0 spent on the intervening days. Both columns may execute $0 on any day if guards fail. The table gives time-averaged spending under the stated fill assumptions; it does not promise a burn amount or deadline.

First 24 hours and a 90% volume drop

Cold start has no satellite LP rewards. The supplied 5 ETH and 350,000,000-token launch position provide the first market; fee collection needs no secondary market. During the first 6 hours, record references and accrue fees. Registry files can open immediately, while their 7-day eligibility clock runs. No one needs to wait for a vote.

If all first-day volume is in the launch pool, $10,000 of volume supplies $100 of launch income, $5 for operations and $93.10 of net satellite inventory after the modeled execution allowance. Its 70/25/5 allocations are below $500: zero satellite openings and zero reward-funded buybacks that day. Under that same primary-only funding assumption, opening thresholds would be reached on days 8, 22 and 108 respectively. At $500,000/day primary-only volume, USDC and cbBTC can reach their thresholds on day 1 and gold on day 3, subject to gates. These are funding thresholds, not scheduled launches, and deliberately assume no satellite fees during the calculation.

Cold-start funding scenario, with no satellite fee contribution	Satellites fundable by day 7	Satellites fundable by day 30
$10,000/day entirely at the launch market	0	2
$500,000/day entirely at the launch market	3	3

The opening counts are conditional on the same route and execution gates; the launch ETH pool is already present and is not counted as a new satellite.

After a 90% fall from the low steady-state scenario to $1,000 total daily volume, vault receipts become $10/day: $8 launch income and $2 LP rewards. Operations get $0.40; buyback allocation gets $0.40; net new LP inventory is $9.016/day. USDC crosses a $50 top-up roughly every 8 days, cbBTC every 23 days and gold every 111 days from empty buckets. The $10 buyback minimum takes 25 days to accumulate. No recurrent rent, quorum, debt payment or required emissions need funding. Existing full-range positions stay in place; claims and small fees accumulate.

At zero volume and static reference markets, fresh fees and purchases can stop entirely. The contracts retain their state and can resume without reseeding. This is operational persistence, not an economically self-sustaining machine. A 90% drop slows the loop; a closed system cannot finance endless trading, gas and dead-address transfers.

Abuse and three main risks

Wash trading for stamps: one credited day per wallet, a $20 minimum, a 7-day escrow, no size ranking and no financial entitlement remove the main reward for churning. A $20 buy and $20 sell would pay approximately $0.50 in official fees before other costs. Splitting wallets is still possible; do not claim proof of unique humans. Display wallet attendance, never "real users." Private transfers, vault trades and unverified attribution earn no credit.

Sandwiching: buyback and liquidity routes use a two-stage committed batch with a 2-to-10-minute execution window, a 30-minute time-weighted reference ending before commitment and a 6-hour comparison window. The contract chooses a valid route and capped amount from the public queue when a caller schedules the batch; any caller can execute that same batch. There is no secret reveal or caller-exclusive reservation. A batch expires after 10 minutes, releases its reservation and can be scheduled again; only successful purchases consume the hourly limit. Require spot within 1% of the committed reference and the two time-weighted references within 5%. Cap each buyback at the lesser of $250 and 0.1% of the launch pool's quote-side inventory; enforce minimum output using the reference, disclosed route fees and at most 0.5% additional execution difference. At most one successful buyback batch per hour; $10 minimum; 60-second transaction deadline. Quote conversions use the same reference and output checks. A caller cannot change recipient, route or amount after committing. Revert unsafe execution and keep the budget. These limits bound exposure; public execution and long-window manipulation still carry risk. A private submission path may help but is not a dependency or a guarantee.

Whale capture of a pair vote: there is no financial pair vote. The developer selects the immutable list at deployment; contracts enforce it. Neither a large balance nor many complaint wallets can add an issuer, change weights or redirect funds. This exchanges voting flexibility for a narrow, visible developer decision. The pause role still presents a liveness risk and is disclosed.

Risk	Design answer	Residual limitation
Impermanent loss in vault positions	Full-range, unlevered positions; retain 80% of settled LP rewards for liquidity; show inventory and entry references separately from fee cash flow. [R14]	Diverging assets can leave LP inventory worth less than separately held assets. Fees may not cover that difference; diversification of quote assets does not remove DEPTMORE exposure.
Thin or failed external markets, depegs and issuer controls	Three satellites only; route-depth and reference gates; 5% gold spending share; no tokenized stocks; per-desk quarantine. Circle documents blocklisting, and stock controls are explicit in chain documentation. [R06, R10]	Custody or transfer restrictions can strand assets. A working pool today does not prove future liquidity or redeemability.
Control, implementation and demand failure	Permanent launch LP lock; no arbitrary vault withdrawals; immutable economics; bounded pause; guarded public execution; explicitly conditional attention loop.	The developer controls all 55% until the manual transfer; the swarm's 10% and retained developer 5% are not described as locked. Bugs, unavailable keepers or absent interest can stop operations. No software rule can compel the developer's manual step.

Build boundary and verification obligations

The later implementation must test both swap directions and multi-hop fee conservation; the exact 35/10/55 launch transfers; the absence of token mint, tax and automatic burn paths; custody of each LP position; principal versus fee accounting; token-denominated fee settlement; internal-fee attribution; stale-reference and low-volume no-op behavior; registry withdrawal and forged attribution; and atomic market-buyback/dead-address transfers. The native ETH market must not silently become a wrapped-ETH launch pair.

This assignment supplies no deployed addresses or proof of audited contracts. The evidence confirms candidate assets and existing reference markets, not future DEPTMORE pools, demand, safe execution or the claimed economic independence of assets. Those distinctions remain visible in the copy and in RESEARCH.md.