BRICK · trading activity becomes permanent onchain structure

A hook with a job to do

One loop · four outputs · onchain

Most token fees leave the market through a treasury, marketing wallet, or team multisig.

BRICK keeps a portion of trading activity inside the system.

Fees are directed toward liquidity that remains in the pool and supply that is permanently removed. Trading activity creates measurable onchain outputs. It does not guarantee a market price, liquidity level, or return.

Each completed pot is split by fixed contract rules: 35% liquidity · 27% burn/mining · 36.8% operations · 1.2% caller reward.

Together, liquidity and burn/mining represent 62% of the pot. The remaining 38% is split between operations and the permissionless caller reward. A visible onchain route for every completed pot.

The usual model

feetreasury / marketing / team

the fee leaves the trading system

BRICK

feeliquidity + permanent supply reduction

protocol-owned, and it stays in the pool

Trade → accumulate → trigger → route

Every swap pays a 2% fee in ETH. It collects in the hook until the pot is full, then anyone can trigger a masonry event that spends it by fixed rules that no address can change or redirect.

Collect

A 2% swap fee enters the pot. Wallet transfers are free.

Accumulate

The pot grows until it reaches the 0.10 ETH threshold.

Trigger

Anyone can call the event, permissionlessly, for a 1.2% reward.

Route

35% liquidity · 27% burn/mining · 36.8% operations · 1.2% caller.

The pot, built into the design

35% 27% 36.8%

Liquidity 35% Burn / mining 27% Operations 36.8% Caller reward 1.2%

Each completed pot follows the published allocation.

The footingprotocol-owned liquidity

Full-range LP owned by the hook. The remove-liquidity path reverts for every address.

The quarrysupply destruction

Buys BRICK and burns it, or pays the miners who burned their own. Supply only falls.

The yardoperations, one fixed address

Paid in ETH to a fixed address. The team holds no tokens, so this is its only revenue.

The mason’s feewhoever lays the brick

Paid to whoever calls layBrick(), carved from operations. The four total 100%.

The mechanism in full, step by step, is in the documentation.

The wall, and who holds it

Masonry history renders here once deployed.

Build the wall

Every BRICK holder is represented in the monument. Your brick's area reflects your current BRICK balance relative to total supply. Split a balance across multiple wallets and the total represented area does not increase.

Connect your wallet to highlight your brick.

Simulated

Holder brick

Live, balance-proportional visual representation. Updates when you buy, sell, transfer, or split BRICK across wallets. Not permanent.

Masonry brick

Permanent monument growth. The monument grows by one structural brick when layBrick() is successfully triggered. It never shrinks.

Hover or tap a brick Area is proportional to balance · live state, not permanent

The holder wall above is a visual representation of current balances. Drawing your brick there does not mint anything, create a separate token, grant governance rights, or change the masonry accounting. It is a picture of who holds what, right now. The collection in §02 is the separate thing that is minted, and it is minted from masonry events, not from balances.

What a masonry event leaves behind

Each masonry event creates one fully on-chain SVG brick. Its traits come from the event itself: the BRICK removed, the caller, the triggering trade, and the event index. No server, no IPFS, no external dependency. The image is generated by a contract and read straight off the chain.

Events laid0

Minted0

Unclaimed0

Mint costGas only

Nothing is random

The fire is read off the BRICK that event destroyed. The protocol spends a near-fixed amount of ETH on each buy-and-burn, so the tonnage it buys falls as the price rises. An early brick is coarse and heavy, a late one dense and small. A brick carries the market it was made in. Scarcity comes out of history, not a rarity table.

Quarried bricks

When the quarry’s miners claim the burn slice, no clay is cut. Those bricks are struck through and unfired, and they exist only because somebody chose to destroy their own BRICK into that epoch.

The mason’s mark

A lattice glyph walked from the mason’s address, struck into the frog: the recessed panel a brick is moulded with and stamped in. One per hand, and never chosen by the person carving it. Anyone may pay the gas to mint a brick; it always goes to the trader who earned it.

Every masonry event mints a fully on-chain brick. These are specimen renders of the two types.

Specimen · fired

Specimen · raw clay

Specimen · quarried

What the contract enforces

Powers that do not exist

no owner
no mint()
no pause
no blacklist
no upgrade path
no transfer tax
no withdraw function
no team token allocation

Technical details · the full trust surface, and how to verify each

Every row below is enforced by code you can read, and the right-hand column shows exactly where to check it.

ControlPositionVerify

Owner / adminNone Brick.sol has no Ownable, no onlyOwner, no roles

MintImpossible no mint function exists; supply fixed at 1,000,000

Upgrade pathNone no proxy, no delegatecall, no implementation slot

Fee2%, fixed FEE_BPS is a constant, with no setter on the hook

Team allocationZero whole supply enters the pool at launch; no vesting contract

Team revenue36.8% of each pot OPS_BPS, paid in ETH automatically each event to one immutable address

Operations recipientImmutable set once at deploy, no setter; the deployer cannot redirect it afterward. Intended: a multisig

Operations powersNone over the protocol the ops address only receives ETH; it cannot pause, upgrade, change fees or touch liquidity, no such function exists

Liquidity withdrawalReverts beforeRemoveLiquidity reverts for every caller, deployer included

Opening the poolLauncher only beforeInitialize rejects every caller but the launcher, so no second pool can use this hook

Deployer powersbindPool, seedFloor both one-shot, both inert after launch, neither moves funds

Pause / blacklistNeither exists no pause modifier, no transfer hook on the token

Independent auditNot done in-house review complete, published at deployment

Inspect the hook Inspect the token Read the docs

Where every fee goes

Eligible swaps pay a 2% fee on the ETH side. Fees accumulate inside the hook until the balance reaches 0.10 ETH, about 5 ETH of trading through the pool. Any address can call layBrick() and receive a 0.0018 ETH execution reward. The remaining balance is processed by the fixed allocation rules below. Nothing forces that volume to exist: the protocol builds at exactly the rate the pool is used, and at no volume it does not build at all.

Parameters

Parameter	Value
Execution function	`layBrick()`
Fee applies to	Every swap in the protocol pool, both directions and both exactness modes
Fee can change	No. `FEE_BPS` is a constant with no setter.
Threshold	0.10 ETH
Caller reward	0.0018 ETH (1.2% of the threshold)
Chain	Ethereum mainnet
Pair	WETH / BRICK. An ERC-20 leg, so explorers and aggregators index the pool correctly

The footingprotocol-owned liquidity

Added as full-range LP owned by the hook. The remove-liquidity path reverts for every address.

The quarrysupply destruction

Paid to the miners who destroyed BRICK in the settling epoch. Whatever they do not take buys BRICK and sends it to a dead address instead. Either way circulating supply only decreases.

The yardoperations, one fixed address

Paid in ETH to a fixed address set at deployment. The team holds no tokens, so this is its only revenue.

The mason’s feepaid to whoever lays the brick

Paid to whoever calls layBrick(). Deducted from the operations share, so the four figures total 100%.

Allocation percentages describe the distribution of each 0.10 ETH pot at the moment a masonry event executes. They are fixed constants in the contract and total 100%.

The contract does not set or target a market price. It reports one accounting metric, ETH in permanent liquidity divided by circulating supply, and nothing more. The full definitions, the quarry, and the metrics are in the documentation.

How the metrics work

How the numbers are defined, and what is still open

Guarantees

Two protocol rules enforced in code

The hook-owned liquidity removal path reverts, and burned BRICK cannot return to circulation.

These two rules hold regardless of market conditions, and the removal path reverts for every address including the deployer. Everything else is a consequence rather than a guarantee. Outside liquidity providers cannot add to or rebalance the managed position, and founding liquidity cannot be withdrawn by anyone, including whoever provided it.

Metric

Accounting metric

This is an accounting measure, not a guaranteed market price or redemption value: cumulative ETH credited to the hook-owned liquidity divided by circulating supply.

It is not a redemption price, a market-price guarantee, or a promise of value. Credited ETH only increases and circulating supply only falls, so the figure cannot decrease. But the liquidity is full-range, so what the position holds at any moment varies with price. brickStats() returns every input, so the figure can be recalculated independently.

Review status

The in-house adversarial review is complete. It has not been published yet, and no independent third-party audit has been done.

124 of 124 tests pass, including a full launch rehearsal that deploys, binds, funds and seeds against the canonical PoolManager on a fork of Ethereum mainnet. The adversarial in-house review is complete and written down: findings, fixes, and the items still open. The source, the tests and the review notes publish at deployment, alongside the addresses that make every claim on this page checkable. No independent third-party audit has been completed, and no audited language is used until an external review is finished.

Read the code

Item	State
Deployment	Not deployed. No token, pool, bricks or on-chain history exist yet.
Token address	Does not exist yet
Hook address	Does not exist yet
Chain	Ethereum mainnet
Pair	WETH / BRICK. An ERC-20 leg, so explorers and aggregators index the pool correctly
Supply	1,000,000 BRICK, fixed at deployment
Opening configuration	Target opening FDV 21 ETH (a launch-time parameter, not yet committed on-chain). The launch is single-sided: the pool opens holding every BRICK and no ETH, so no capital is committed at launch and nothing is bought. Buyers walk the price up through the founding range, and the ETH they pay accumulates inside it.
Third-party audit	Not started. No audited language should be used until one is complete.

Questions

Can the liquidity be removed?

No. It is held by the hook and the remove-liquidity path reverts for every caller, the deployer included. There is no withdraw function. Verified against the real PoolManager on a mainnet fork.

Is there a team allocation or unlock?

No. The full 1,000,000 supply is minted once and seeded into the pool. No vesting, no treasury wallet, no mint function.

How does the team make money?

Only the fee. 36.8% of each pot is paid in ETH to a fixed operations address. The team holds no tokens, so it cannot sell into you.

Who can trigger a masonry event?

Any address, once the pot is full. No allowlist, no privileged caller; whoever calls it earns a 1.2% reward. A keeper backstops it so events fire reliably.

Every mechanism in full, plus the quarry, the metrics and the code, in the documentation.

The rules are public. The event is permissionless. The record stays on-chain.

Every trade adds to protocol-owned liquidity and permanently reduces BRICK supply, by fixed rules no address can change. The machine runs on its own, in public, on Ethereum.

BRICK does not set, defend, or guarantee a market price, a liquidity level, or a return. Its accounting metrics are not the same as market value.

Where this stands

Nothing is deployed. There is nothing to buy yet, and anyone offering you a BRICK contract address today is selling you something else.

The token address, the hook address, the source and the review all land on this page on launch day, together, because they are only worth anything to you as a set. Until then every figure here is a model and says so.

Follow @brickonchain The deployment transaction is posted there first

Every swap lays a brick.