brick
Docs · Mechanics

Dev pay and courses

Creators choose Direct pay (onchain, trustless) or Courses escrow (server held, released as the wall grows).

A creator picks how they get paid before launch. Direct is enforced by Meteora. Courses escrow is held and released by the BRICK server, and the launch form says so before the creator signs.

Direct

  • The creator's share is written into the coin's DBC config as creatorTradingFeePercentage and, after graduation, as a creator owned permanently locked LP position.
  • The creator claims it themselves from the Meteora programs. BRICK never holds it.
  • Trustless: no BRICK server or key is involved.

Courses escrow

The creator's share goes to the BRICK fee wallet instead and is released one course at a time, only when the wall grows.

CourseReleased when
Course 1The coin graduates.
Course n (2 and later)Cumulative SOL compounded into the pool reaches (n minus 1) x 25% of the pool's SOL reserve measured right after migration.
  • The metric is cumulative compounded SOL (the wall), not market cap or current reserves, so it cannot be pushed up by a single buy and does not fall when price falls.
  • At each course, all escrow accrued so far is released to the creator wallet. Escrow that accrues later waits for the next course.
  • No wall growth, no further release.

Forfeiture

Forfeiture applies only when the creator explicitly consents to it at launch. If the creator's declared wallets together sell more than the threshold shown at launch (a percentage of their peak combined holdings), all unreleased escrow is forfeited to builders and joins the next reward epoch.

Not trustless

Escrow is held by the BRICK server, not by a Solana program. Only wallets the creator declared as linked are watched. A creator can hold tokens in undisclosed wallets, and those cannot be detected reliably. A server observed sell cannot stop funds already in the creator's control from being spent.