# Department of More: one-page copy

Copy specification only. Read sections from top to bottom on a phone. Braced fields are required chain-derived values, never sample statistics. Fixed percentages and durations below describe the specified rules; verify the deployed configuration before presenting a live interface. Until verified deployment records exist, show the prelaunch state and disable transaction actions. Evidence keys resolve in RESEARCH.md; mechanism details resolve in CONCEPT.md.

## Hero

Department of More

DEPTMORE

Every swap creates more paperwork.

The swarm opened an office. The office keeps requesting more office.

A memecoin on Base. Trading fees fund more trading desks. You can file a complaint. The complaint creates paperwork.

Primary button: Inspect the department

Secondary button, before launch: Trading has not opened

Secondary button, after verified launch: Review a swap

Department status: {onchain: deployment verification, launch-pool initialization and vault pause state}

Open desks: {onchain: initialized official pool count with nonzero vault or locker liquidity}

## What it is

An office with a very serious circular problem.

The IMD swarm designs and launches the token, then leaves a public record of what its contracts do. A swap funds the office. The office opens trading desks. Activity at those desks creates fees and another stack of receipts.

The picture is a receipt printer eating its own receipt. The receipts are real contract records. The office is the joke.

DEPTMORE has plain transfers. No transfer tax. No owner mint after launch. No automatic burn inside the token. [B0]

## The flywheel: budget

Your trade has been assigned a budget code.

Every trade in an official pool pays 1.25%: 1% of the trade goes to the launching side's vault and 0.25% goes to the network. The launching side receives 80% of that fee. Additional hook fee: 0%.

Of the launch market's vault income, 95% funds liquidity and 5% stays in the vault for bounded execution costs. Unused operating money stays visible. Transfers and unrelated pools do not pay this trading fee.

Launch-market fees received by the vault: {onchain: cumulative launch-income receipts by asset}

Network fees paid: {onchain: cumulative network fee transfers by asset}

Execution reserve: {onchain: operating-reserve balances by asset}

## The flywheel: vault and desks

We have opened a department to investigate why we keep opening departments.

Reception is the DEPTMORE / ETH launch market. New vault liquidity is allocated across Petty Cash, paired with USDC; Heavy Filing, paired with cbBTC; and Archive, paired with VNXAU. Their spending shares are 70%, 25% and 5% respectively.

USDC, cbBTC and VNXAU have documented Base assets and existing reference markets. These new DEPTMORE desks open only after their funding and execution conditions pass. [R05, R07, R08, R17]

A dollar asset, Bitcoin reference and gold reference can move differently. Those differences may prompt arbitrage trades between desks. They do not manufacture money. All of the desks also contain DEPTMORE, and their inventory can lose value.

The developer chooses the pair list before launch. Contracts enforce the list and the spending rules. Complaint stamps do not vote on the treasury. Tokenized stocks are excluded because their issuer controls add restrictions the department does not need. [R10]

Vault inventory: {onchain: spendable, reserved and pending vault balances, separately for each asset}

Reception - DEPTMORE / ETH

- State: {onchain: launch pool initialized status, pool identifier and permanent locker address}
- Assets in its position: {onchain: launch LP token and native ETH inventory}
- Trading fee: {onchain: verified launch pool effective swap fee and additional hook fee}

Petty Cash - DEPTMORE / USDC

- State: {onchain: USDC desk queued, open or paused status and pool identifier}
- Assets in its position: {onchain: vault-owned DEPTMORE and USDC LP inventory}
- Next allocation: {onchain: USDC desk unspent allocation and opening or top-up threshold}

Heavy Filing - DEPTMORE / cbBTC

- State: {onchain: cbBTC desk queued, open or paused status and pool identifier}
- Assets in its position: {onchain: vault-owned DEPTMORE and cbBTC LP inventory}
- Next allocation: {onchain: cbBTC desk unspent allocation and opening or top-up threshold}

Archive - DEPTMORE / VNXAU

- State: {onchain: VNXAU desk queued, open or paused status and pool identifier}
- Assets in its position: {onchain: vault-owned DEPTMORE and VNXAU LP inventory}
- Next allocation: {onchain: VNXAU desk unspent allocation and opening or top-up threshold}

For every open satellite, also show:

- Fee record: {onchain: that pool's verified effective fee, collected vault LP fees and pending fees by asset}
- Last completed action: {onchain: that pool's latest vault execution event, timestamp and transaction hash}

If a desk is waiting: OUT OF TONER. Its allocation is still here.

If data cannot be verified: RECORDS UNAVAILABLE. Show no replacement figures.

## The flywheel: rewards split

Some paperwork goes to the shredder. Most orders another desk.

The vault keeps its satellite LP fees. Of each settled reward batch, 20% funds a market-buyback queue and 80% funds liquidity. These are vault allocations, not payments to holders.

When execution conditions pass, the vault spends the queued share to buy DEPTMORE on the market and sends the actual bought tokens to 0x000000000000000000000000000000000000dEaD. If the batch is too small or execution is unsafe, it waits. A day can have no purchase and no dead-address transfer.

Pending LP fee inventory: {onchain: unsettled satellite fee basket by asset}

Buyback budget waiting: {onchain: earmarked market-buyback balances by asset}

Tokens bought on the market by the vault: {onchain: cumulative DEPTMORE output of executed vault buybacks}

Bought tokens sent to the dead address: {onchain: cumulative DEPTMORE transferred by those buyback executions to 0x000000000000000000000000000000000000dEaD}

Last buyback receipt: {onchain: latest completed market-buyback input, output, timestamp and transaction hash}

These counters exclude the developer's manual transfer and unrelated dead-address transfers. The token's total supply does not decrease when tokens are sent to that address.

## The flywheel: players

Please take a number. Then complain about the numbers.

Escrow 1 DEPTMORE to open a file. After 7 days, submit LESS PAPERWORK. Receive MORE PAPERWORK REQUIRED onchain. Screenshot the card that says LESS PAPERWORK: DENIED.

One complaint stamp per UTC day while your mature file remains open. Withdraw your escrowed token after maturity whenever you choose. The stamp is a record, not a financial reward.

First Shift records a qualifying buy in the first 24 hours followed by a mature file. Active attendance records at most one qualifying trading day per day, with a $20 reference-notional minimum. More volume does not improve your label. There is no airdrop, fee rebate or treasury vote attached to these records.

Button: Open a file

After maturity: File for less paperwork

Your escrow: {onchain: registry escrowed DEPTMORE balance}

Your file is ready: {onchain: registry maturity timestamp and current eligibility}

Your case: {onchain: complaint serial number, filing day and transaction hash}

Your attendance: {onchain: verified First Shift flag and credited trading days}

Screenshot card:

LESS PAPERWORK: DENIED

Case {onchain: complaint serial number}

Desk count at filing: {onchain: official desk count recorded in the complaint event}

Receipt: {onchain: complaint transaction hash}

MORE PAPERWORK REQUIRED

Button: Save this receipt

## Distribution

The allocation form. Read the whole form.

Supply design: 1,000,000,000 DEPTMORE, with 18 decimals, on Base, chain 8453. [B0]

- 35% - 350,000,000 tokens seed the liquidity pool.
- 10% - 100,000,000 tokens go to the swarm, the agents who build it.
- 55% - 550,000,000 tokens go in one transfer to the developer wallet.

From that developer allocation, 50% of the original supply, or 500,000,000 tokens, is designated for the developer's later manual transfer to 0x000000000000000000000000000000000000dEaD; the remaining 5%, or 50,000,000 tokens, is kept by the developer. This is a manual action, not an automatic token feature. Until confirmed, the developer controls the whole 55%. The retained allocation and swarm allocation are not described as locked. [B0]

Verified total supply: {onchain: DEPTMORE totalSupply with decimals}

Launch allocation receipts: {onchain: observed initial liquidity allocation, swarm transfer and single developer transfer amounts and transaction hashes}

Developer manual-transfer status: {onchain: pending or confirmed from developer-origin DEPTMORE transfers to the full dead address}

Developer manual-transfer amount: {onchain: verified developer-origin amount sent to the dead address for the planned manual action}

This manual-transfer record is separate from the vault's market-buyback record. No future vault transfer amount or timing is assured.

## How to buy

Read before signing. That is technically paperwork.

1. Select Base, chain 8453, in your wallet and keep ETH available for the trade and gas.
2. Compare the full token address and official ETH pool identifier below. A ticker alone is not identification.
3. Enter an amount. Review the 1.25% pool fee, the 0% additional hook fee, the minimum token output and gas estimate. Cancel if the quote or transaction is unclear.
4. Confirm only the transaction you reviewed. After it settles, inspect the receipt. The complaint registry is optional and uses a separate, explicit escrow transaction.

Token: {onchain: verified DEPTMORE contract address}

Official ETH pool: {onchain: registered launch pool identifier and hook address}

Your ETH available: {onchain: connected wallet native ETH balance}

Trade input: {onchain: wallet-simulated transaction input amount}

Minimum tokens received: {onchain: simulated quote minimum DEPTMORE output after fees and chosen execution limit}

Estimated gas: {onchain: wallet transaction simulation gas estimate}

Before launch: Trading has not opened. No token address has been published in this design.

## Risks

The office is absurd. The costs are real.

You can lose the money you spend. Liquidity can be thin, and you may be unable to complete a sale on acceptable terms. Vault LP positions can suffer impermanent loss relative to holding their component assets separately. Fees may not cover it. [R14]

Stablecoin and gold issuers, custodians and external markets introduce failure and transfer-restriction risks. Stocks are excluded, but other paired assets still have issuer dependence. [R06, R07, R08, R10]

Contracts can contain bugs. Reference checks can fail. Keepers may stop calling. The developer can pause vault spending and controls the manual transfer of its allocation. A quiet department can remain quiet. The vault holds its own assets; DEPTMORE holders have no right to redeem them or receive its fees.

Button: Inspect balances and controls

Current controls: {onchain: pause status, pending resumption timestamp, fixed pair list and recipient configuration}

## Footer

Department of More / DEPTMORE

Every swap creates more paperwork.

Designed for the IMD swarm. Chain: Base.

Memecoin participation, not company equity. Records are the receipts; slogans are the joke.

Record block: {onchain: block number and timestamp used for all displayed balances and counters}

If records are stale, say so. Do not replace missing records with marketing numbers.