BRICK · trading activity becomes permanent onchain structure

How the machine runs

STEP 1

A swap pays the hook 2%

Every swap in the official pool pays 2% on the ETH side. Both directions, and both exact-input and exact-output, so there is no shape of trade that avoids it.

The fee is taken by the hook itself rather than by the token, which is why a transfer between two wallets costs nothing.

FEE_BPS = 200

STEP 2

It accumulates in the pot

The fee sits in the hook as WETH and does nothing until there is enough of it to be worth spending. Nothing can take it out in the meantime.

There is no withdraw function on the contract, for any address, including the one that deployed it.

pot += fee

STEP 3

At 0.10 ETH anyone can trigger it

Once the pot reaches the threshold, any address may call layBrick(). There is no allowlist, no keeper role and no privileged caller.

Whoever calls it is paid 1.2% for the gas they spent. That is the whole of what they get.

BRICK_THRESHOLD = 0.10 ether

STEP 4

The pot splits four ways

One hundred bricks, one per percent. Thirty-five become liquidity, twenty-seven go to the quarry, and the rest funds operations with the caller’s 1.2% carved out of it.

The four numbers are constants. Nothing in the contract can change them.

LP 35% · BURN 27% · OPS 36.8% · KEEPER 1.2%

1 brick = 1% of a pot

35Permanent liquidity 27The quarry 38Operations, incl. 1.2 keeper

STEP 5

The liquidity has no way out

The 35% is added as a position the hook itself owns, and the remove-liquidity path reverts for every caller that tries it, the deployer included.

It is not locked for a period. There is no path, so there is nothing to unlock.

revert FloorIsPermanent()

STEP 6

The trade that filled it earns the brick

The brick is credited to the swap that carried the pot over the threshold, not to whoever won the race to trigger it.

Triggering is permissionless and pays, so a bot wins that race every time. It takes the ETH. It does not take the record.

wall[idx].mason

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 allocation

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 Open the quarry

Burning BRICK for a share of the fee

Mining is destruction

You mine by destroying BRICK. The tokens go to the grave and never come back, and in the same transaction circulating supply falls, and that is the only input to the accounting ratio this protocol is built on. There is nothing to unstake.

Paid from fees, not emission

Each epoch's miners split 27% of one masonry pot, pro-rata to the BRICK they destroyed. That ETH was collected from real trades. No supply is minted to pay it, no schedule halves it, and no miner is paid out of another miner's loss.

You mine into the next brick

An epoch is paid by the brick after the one that closes it. The delay is the point: the pot is public and anyone can trigger masonry, so without it a large holder could burn at the last second and take a slice they knew the size of.

Epoch: The window your burn is counted in. It closes when the next brick is laid, and everything destroyed inside it shares one slice.
The course: Every burn in one epoch, laid side by side. Your width is your share of that slice, and it shrinks as other people join.
Settling: The brick after the one that closed your epoch. Only then does the ETH become claimable.
The grave: 0x…dEaD, where destroyed BRICK goes. There is no path back, for anyone, including the protocol.

Cut the face

Every miner in the open epoch holds a slab of it, sized by the BRICK they destroyed. When the next brick is laid, that course settles and its ETH becomes claimable.

Preview

Rate · ETH per 1,000 BRICK destroyed

·awaiting deployment

Epoch fillof its 3× ceiling

Open epoch·

BRICK destroyed this epoch·

Miners this epoch·

Settling next·

Slice per masonry event0.027 ETH, split across the epoch

Maximum payout3× what you destroyed, priced at settlement

Destroy BRICK

BRICK

Connect a wallet to see what a cut would earn.

Irreversible. Burned BRICK cannot be recovered by anyone, including the protocol. Your epoch settles once two further bricks are laid, so payout depends on continued trading through the pool.

Settled · claimable

·ETH

Pull-based, and it never expires. An epoch you never got round to claiming is still claimable in full a year later. The contract has no sweep and no deadline.

Hover or tap a slab Slab width is proportional to BRICK destroyed

If nobody mines

The 27% runs the original buy-and-burn: the protocol buys BRICK from the pool and sends it to the grave. An epoch with no miners behaves exactly as the protocol did before the quarry existed.

If an epoch is thin

Payout is capped at three times the pool-price value of the BRICK destroyed, priced when the epoch settles rather than when you burned. A lower price at settlement means a lower ceiling. Whatever the cap declines goes to the same buy-and-burn, and destroying one BRICK cannot capture a whole slice.

Epoch	Destroyed	Miners	Paid	Rate / 1k	Your claim
No epochs have settled. Mining begins when the pool does.

Mining is optional and speculative. It does not mint a token, an NFT or a position, grants no governance rights, and is not a yield product.

An epoch pays a pro-rata share of the 27% slice, in real ETH from trades that already happened. What it pays depends on how much the pool traded and how much BRICK was burned into the same epoch, so commit only what you intend to burn.

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%.

Four different things, often confused

Implied liquidity price

Cumulative ETH credited to permanent liquidity, divided by circulating supply. Credited ETH only increases and supply only falls, so this figure cannot decrease. It is an accounting ratio, not a redemption right. No holder can exchange BRICK for that ETH, because it sits in a position the hook cannot remove. The contract calls it impliedLiquidityPriceWei() and not a floor, deliberately.

Active liquidity

What the position actually holds right now. The LP is full-range, so its composition shifts with price. It is not the same number as the one above.

Market price

What the pool will trade at. Set by supply and demand. Nothing in the contract sets, defends, or targets it.

Protocol guarantees

Two, both enforced in code: liquidity added by the hook cannot be removed by any address, and burned supply cannot return. Everything else is a consequence, not a promise.

How the metrics work

How the numbers are defined, and what is still open

Guarantees

Two protocol rules enforced in code

Liquidity added by the hook cannot be removed, 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

Implied liquidity price

The implied liquidity price is a transparent on-chain metric: 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.
Test suite	124 of 124 passing, including the mainnet-fork launch rehearsal against the canonical PoolManager and six stateful invariants over 96,000 random operation sequences
In-house review	Adversarial review complete, published at deployment, including known open items
Third-party audit	Not started. No audited language should be used until one is complete.

Questions

Does every BRICK trade pay the fee?

No. A pool is identified by its two tokens, its fee tier, its tick spacing and its hook. The hook governs the one pool it is bound to, not the token. Any address can create a second BRICK/WETH pool with no hook attached, and trades routed through that pool pay nothing to the protocol. What nobody can do is point a second pool at this hook: beforeInitialize rejects every caller but the launcher, so the hook governs one pool and only one, permanently. This is not hypothetical: one recent v4 launch has 242 pools, of which 233 carry no hook. What protects fee capture in practice is depth, not permission. Routers send orders to the pool with the best price, and the protocol pool's liquidity is permanent and grows with every masonry event, while a rival pool would need someone to fund and maintain it at a loss. The claim this site makes is therefore "trades in the protocol pool pay 2%", and nothing stronger.

Can the liquidity be removed?

No. It is held by the hook contract and the remove-liquidity path reverts for every caller, including the deployer and the hook itself. There is no emergency withdraw function. This is verified against the real PoolManager on a mainnet fork.

How does the team make money?

62% of every pot is spent on the token: 35% into liquidity that cannot be removed, 27% on destroying supply: paid to the miners who burned BRICK in the settling epoch, or spent buying BRICK and sending it to a dead address when no one mined. The remaining 36.8% is paid in ETH to a fixed operations address, after the 1.2% execution reward is carved out for whoever triggered the event. That fee is the team's only revenue: there is no token allocation, no vesting schedule and no unlock, because the entire supply seeds the pool at deployment. A team holding none of the supply and taking a disclosed, fixed share of fees cannot quietly sell into you, which is the failure mode a token allocation exists to enable.

How does mining work?

Mining is optional and speculative. You burn BRICK for a pro-rata share of the 27% slice of a masonry pot, about 0.027 ETH at a full pot, paid in real ETH from trades that already happened. The payout is capped at three times the pool-price value of what you burned. What you receive depends on how much the pool trades and how many others mine the same epoch, so commit only what you intend to burn. The ETH is real, the split is a constant nobody can change, and an unclaimed epoch never expires.

What if an epoch is never funded?

An epoch is funded by the next masonry event, and the claim never expires, so an epoch funded a year later still pays in full. Mining commits BRICK for a share of future fees rather than a deposit you can withdraw, so treat it as a commitment, not a balance.

Why proof-of-burn instead of a round-based game?

Because the wager version pays winners out of losers, and this protocol's only claim is that its accounting ratio rises by construction. Proof-of-burn is that claim made callable: the BRICK goes to the grave, circulating supply falls, and the ratio rises in the same transaction. There is also no randomness to relay. A round-based game needs a beacon or a VRF to be live or the protocol stops turning, and this one needs nothing but the pool.

What happens to the 27% if nobody mines?

It buys BRICK from the pool and sends it to a dead address, exactly as the protocol did before the quarry existed. The same applies to any part of the slice the payout ceiling declines. This is deliberate: the worst case for the mining layer is the behaviour of the version without it, so adding it cannot leave holders worse off.

Is there a team allocation or unlock?

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

What does the implied liquidity price actually mean?

Cumulative ETH credited to permanent liquidity divided by circulating supply. It cannot decrease. It is not redeemable and it does not set market price. See the four definitions under Mechanics.

Who can trigger a masonry event?

Any address, once the pot reaches 0.10 ETH. There is no allowlist and no privileged caller, and whoever calls it earns a 1.2% reward of the pot. The team also runs a keeper as a backstop, so masonry events fire reliably even when network gas is high.

Where are the full limitations written down?

Under Limitations. Every plate expands to the technical detail, including what is still open. The complete in-house review, with the findings that remain unresolved, is published alongside the source at deployment.

What if the operations address stops working?

Nothing halts. The payout is attempted without reverting, so a failed transfer cannot block masonry events. The failure is recorded as an event.

Trading activity becomes permanent onchain structure.

What trading activity builds

How the machine runs

A swap pays the hook 2%

It accumulates in the pot

At 0.10 ETH anyone can trigger it

The pot splits four ways

The liquidity has no way out

The trade that filled it earns the brick

The wall, and who holds it

Build the wall

What a masonry event leaves behind

Nothing is random

Quarried bricks

The mason’s mark

Masons

What the contract enforces

Burning BRICK for a share of the fee

Mining is destruction

Paid from fees, not emission

You mine into the next brick

Cut the face

Where every fee goes

Implied liquidity price

Active liquidity

Market price

Protocol guarantees

How the metrics work

Two protocol rules enforced in code

Implied liquidity price

Review status

Read the code

Questions