Docs · Trust
Supported features
Every requested mechanic, whether it is supported now, how, and what you have to trust.
This is the capability matrix. A feature is only called onchain when an existing Solana program enforces it. Server managed features say so. The live state of each feature, including dry run, is on the status page.
| Requested feature | Supported now | Protocol method | Onchain enforceable | Trust assumption | Limitation |
|---|---|---|---|---|---|
| One signature launch | Yes | Meteora DBC createConfigAndPool, wallet signed | Yes | Server builds and simulates the transaction; the creator reviews and signs it | A first buy adds a second transaction |
| Fixed supply, no mint or freeze | Yes | DBC TokenAuthorityOption Immutable | Yes | None | None |
| $10k start, $45k graduation | Yes | Per coin DBC config from live SOL/USD at launch | Yes | SOL/USD price API at launch time | Fixed in SOL after launch, dollar values drift with SOL |
| Graduation to a Meteora pool | Yes | DBC migration to DAMM v2 at the quote threshold | Yes | None | Triggered by the curve reserve; run by Meteora migration keepers |
| LP locked forever | Yes | DAMM v2 permanent lock, 100% of migrated liquidity (75/25 partner and creator on Direct, 100% partner on escrow) | Yes | None, provable via permanent_locked_liquidity | Locked positions still earn claimable fees for their owner |
| The wall (50% compounding) | Yes | DAMM v2 Compounding mode, compoundingFeeBps 5000 | Yes | Meteora operators can change compounding_fee_bps via update_pool_fees | Counts contributions; price and reserves can still fall |
| Rising price floor | No | None | No | Not offered | No existing program can guarantee it |
| Cure (time decay fee) | Yes | DBC fee scheduler, linear or exponential | Yes | None | UI max 50% start, program max 99% |
| Courses (market cap steps) | Yes | DBC flat fee, then DAMM v2 market cap fee scheduler | Yes | Meteora holds a pool fee update instruction | Levels reverse if price falls; schedule expires; end fee below curve fee |
| Masons (holder heavy split) | Yes | Fixed DBC fee, larger holder share of controlled proceeds | Partly | BRICK server pays holders | Holder payouts are server managed |
| Load bearing (volatility fee) | Yes | DBC and DAMM v2 dynamic fee | Yes | None on the curve; Meteora fee update instruction on the pool | Surcharge capped at 20% of base; measures price movement, not volume |
| Creator Direct pay | Yes | DBC creatorTradingFeePercentage and creator locked LP | Yes | None, the creator claims it | No release schedule |
| Creator Courses escrow | Pending | BRICK fee wallet, released per course of compounded SOL | No | BRICK server holds and releases funds | Pending operator keys and activation. Forfeiture needs explicit consent; only declared wallets are watched |
| Builders rewards | Pending | Time weighted balances, rank multipliers, SOL payouts every 24h | No | BRICK server holds funds and sends payouts | Pending operator keys and activation. Caps, dry run and kill switches apply |
| Brickyard buyback and burn | Pending | Jupiter swap with mint allowlist, then SPL Token burn | Partly | BRICK server runs the swap and burn | Pending until the BRICK mint is configured |
| Fee ledger and reconciliation | Yes | Indexed claims and allocations reconciled with onchain transfers | No | BRICK indexer | Every movement links to its signature for independent checking |
Not offered
- A guaranteed price floor or a floor that only rises. No existing program can guarantee it, so BRICK does not claim it.
- Trustless holder rewards, trustless dev escrow or trustless forfeiture. These would need a custom program; BRICK deploys none.
- Detection of undeclared creator wallets.