brickpaper

A token that defends itself and backs itself.

Revenue flows in. Most becomes claimable WETH backing. A large share becomes buy-and-burn firepower for crashes. Nobody presses a button, and the important rules cannot be changed at all.

The machine is code.

01

Introduction

BRICK is a meme token with a machine behind it. Every unit of revenue is split automatically between three destinations: a Vault of WETH any holder can claim against by burning BRICK, a Wall that buys BRICK on the open market during real crashes and destroys what it buys, and the team. The rules live in immutable smart contracts. Adjustable parameters sit behind a 24 hour public timelock; the core promises are not adjustable at all.

to the vault
55%
Claimable WETH backing for every holder.
to the wall
35%
Buy-and-burn ammunition for crashes.
to the team
10%
Operations and development.
02

The entities

There are four moving parts. Everything in the system is a relationship between them.

$BRICK
The ERC-20 token
Burned by the Wall and by claims. Supply only goes down.
The Wall
A pot of WETH with one legal move
Buys BRICK during 30%+ crashes, burns 100% of it. Cannot be withdrawn.
The Vault
The WETH backing every BRICK
Leaves in exactly one way: a holder burns BRICK for their share. No admin key.
The Router
The allocation engine
Splits all incoming revenue 55 / 35 / 10. Anyone can trigger distribution.
system flow
REVENUEcreator fees + ETHROUTER55 / 35 / 10VAULT · 55%claimable backingWALL · 35%buys + burns in crashesTEAM · 10%operations
03

The revenue split

Revenue comes from BRICK's trading venue: creator fees earned on trading are routed straight to the machine, and anyone can top it up with ETH directly. Either way the money hits the same engine and splits 55 / 35 / 10 into Vault, Wall, and team.

Distribution is permissionless: once revenue accumulates, anyone can trigger the split. The team cannot sit on funds, and the ratios are enforced by the contract, not by policy.

04

The Wall

The Wall is WETH with one legal move: buy BRICK during a serious drawdown and burn all of it. Burned tokens are permanently destroyed. There is no code path for anyone, including the team, to withdraw the Wall's money.

When it fires. The Wall compares price to Established Territory, a slow-moving reference built from time-averaged market data, so a single manipulated trade cannot move it. Below a 30% drawdown the Wall starts firing, and it fires harder the deeper the crash, peaking around the 80 to 90% zone. Past 90% it deliberately eases off to preserve ammunition instead of emptying itself into a collapse.

Velocity. A crash in one hour is scarier than the same drop over a week. Fast drops can scale a shot up to at most 2x. Speed can never make the Wall fire when the drawdown gate says no, and never breaks the caps below.

base shot
0.60%
of Wall balance
max shot
2.50%
hard per-shot cap
daily budget
6%
per rolling day
cooldown
30m
between shots
impact cap
~4%
of pool liquidity

The caps exist so the Wall survives long wars instead of blowing its budget on the first bad candle. Even the automation that proposes shots is untrusted: the contract re-checks every rule onchain before spending a single wei.

05

The Vault

The Vault holds the WETH that backs every circulating BRICK. Money leaves it in exactly one way: a holder burns BRICK and takes their proportional share. No admin key, no pause button, no borrowing by the Wall. An emergency switch must never become a way to freeze or seize holder backing, so there isn't one.

Backing per brick is the Vault's WETH divided by the redeemable supply. It is the floor amount one BRICK can always be exchanged for through the contract, and three forces push it in one direction only:

revenue in
+WETH
55% of all revenue lands in the Vault.
wall burns
−supply
Fewer BRICK dividing the same Vault.
claim fees
+ratio
The 1% fee stays in, everyone else gains.

Nothing in the mechanism can push the ratio down.

06

Burn & claim

Any holder can burn BRICK at any time for their share of the Vault. The formula is V × B / S: Vault balance, times BRICK burned, divided by redeemable supply.

worked example

The exchange is atomic: burn and payout happen in one transaction against the state right before your burn. The fee is fixed at deploy time and cannot be raised behind your back.

07

Guarded launch & timelock

Guarded launch. Young markets have thin liquidity, and a full-size Wall shot into a thin pool would move price too much. So the Wall starts with base shot and daily budget halved. Lifting guarded launch is one-way and goes through the timelock: the training wheels cannot come off silently, and can never be re-imposed to fake scarcity.

Timelock. Every adjustable parameter is owned by a 24 hour timelock. No parameter changes without a full day of public notice onchain. And the biggest promises are not parameters at all:

  • Vault money can never fund the Wall.
  • Wall money can never reach the team.
  • Everything the Wall buys must be burned.
  • The claim formula is fixed forever.
08

Honest risks

The Vault is a claimable backing mechanism, not a promise that market price cannot fall. Price is set by traders and can trade below, or far above, backing per brick. The Wall softens crashes with real buy-and-burn pressure but is capped by design and cannot stop a determined market. Backing grows only as fast as real revenue arrives. And like all smart contract systems, the code can contain bugs despite careful design.

What the contracts do guarantee is mechanics: your right to burn BRICK for your share of the Vault cannot be paused, frozen, or taken away by anyone.