brick
Docs · Mechanics

Fee flows

The complete allocation table for every plan and pay mode, from gross trading fee to each destination.

Not every fee unit reaches BRICK. Meteora keeps its share, the creator may take a direct share onchain, and after graduation the pool compounds half of what is left. The BRICK server only splits what it actually claims into its fee wallet.

Terms

TermMeaning
Gross feeWhat a trader pays as the trading fee of a swap.
Protocol shareKept by Meteora: 20% of curve fees, and the pool's protocol fee percent on DAMM v2 (20% on migrated pools).
Post protocol feeGross minus the protocol share. Split onchain between the creator and BRICK.
Controlled proceedsWhat BRICK actually claims into its fee wallet, minus execution costs. Only this is split by the server.
ResidualControlled proceeds that are not allocated to a destination. Held in the BRICK fee wallet as a reserve and shown, never hidden.

Allocation table

Rendered directly from the allocation module that the launch config builder and the fee ledger use. Gross share is a share of the phase's whole trading fee. Controlled share is a share of BRICK controlled proceeds, and those always sum to 100%.

Curve phasebefore graduation
DestinationRecipientGross shareControlled shareEnforced by
Meteora protocolMeteora20%n/aOutside BRICK control
CreatorCreator wallet, claimed onchain by the creator24%n/aOnchain, immutable
BuildersBRICK fee wallet, paid to holders every 24h22.4%40%BRICK server
BrickyardBRICK fee wallet, spent on BRICK buyback and burn16.8%30%BRICK server
Platform opsBRICK fee wallet16.8%30%BRICK server
Total100%100%
Graduated pool phaseDAMM v2, after graduation
DestinationRecipientGross shareControlled shareEnforced by
Meteora protocolMeteora20%n/aOutside BRICK control
The wallPool reserves, added by DAMM v2 on every swap40%n/aOnchain, Meteora governed
CreatorCreator wallet, claimed onchain by the creator10%n/aOnchain, Meteora governed
BuildersBRICK fee wallet, paid to holders every 24h15%50%BRICK server
BrickyardBRICK fee wallet, spent on BRICK buyback and burn6%20%BRICK server
Unallocated residualBRICK fee wallet, held as reserve9%30%BRICK server
Total100%100%

Meteora protocol share used here: 20% on the curve and 20% on migrated DAMM v2 pools (the live value is read from each pool). Wall compounding: 50% of the post protocol pool fee.

Rounding

Each claim is split with integer lamport math: every destination gets floor(amount x bps / 10000) and the rounding dust goes to the residual line, so the parts always sum to exactly the amount claimed. Execution fees and a small reserve for future transaction fees are taken off before the split.

Custody

The BRICK partner wallet is the DBC fee claimer on every config and owns the partner side locked LP positions. It claims fees and the server splits them. Every job that moves funds passes one gate before sending: the global dry run switch (on by default), a per job kill switch (off by default, changed from the operator console with a signed confirmation and an audit entry), the operator key being configured and matching the partner wallet, a per run spend cap, and a simulation of the transaction. Every claim and allocation is listed on the wall with signatures.