FAQ.

That is the planned configuration, not a completed claim. The plan sends 100% of BF supply to the Clanker liquidity pool, with 0% team allocation, 0% presale, 0% creator vault and no developer buy. The final deployment transaction must be verified before the wording becomes definitive.

No team token allocation is planned. Creator compensation is intended to come from the disclosed 40% Creator Cut applied to Creator Rewards actually received, not from a preallocated BF bag.

It means the entire BF token supply is planned for the Clanker-created liquidity pool at launch. It does not mean 100% of trading fees go to BurnlyFans, and it is separate from the 40/20/35/5 Creator Reward split.

Forty percent of Creator Rewards received by BurnlyFans forms the Creator Cut. There is no guaranteed amount: compensation depends on final Clanker configuration, rewards actually collected and real BF trading activity.

They are intended to come from BF trading through the configured Clanker liquidity position and reward routing. The 1% figure used in examples is a planning assumption; actual net rewards depend on the verified launch configuration and Clanker-level fees.

Twenty percent of Creator Rewards received funds Burnback, 35% funds the weekly Fan Vault and 5% funds the monthly Top Fans pool. It is accurate to say 60% returns to BF and community mechanisms, but not that the entire 60% is paid directly to users.

The 40% Creator Cut is used at the creator's discretion. Potential uses include development, maintenance, infrastructure, operations, liquidity support, marketing, security work, audits, experiments, community drops and future expansion; no fixed sub-allocation is promised.

No. BurnlyFans does not pay users simply for holding BF. A wallet must voluntarily burn BF through the Burn Router to create Fan Power for the active cycle.

An eligible Burn Router transaction permanently sends BF to The Furnace and creates equal Fan Power for that Burn Cycle. Direct transfers to The Furnace remain burned but receive no Fan Power or ranking credit.

No. Burning is irreversible. The protocol has no recovery route from The Furnace.

No. The value of BF destroyed may exceed any ETH claimed, and rewards may be zero. Price, liquidity, Creator Rewards, total Fan Power and participation can all change.

It refers to proportional reward weight within the same cycle: more eligible BF burned creates more Fan Power. It is not a profit promise because the burn itself has value and every participant's relative percentage can change.

A fixed Fan Vault is shared across all eligible Community Fan Power. If total Fan Power grows faster than the vault, each burned BF represents a smaller fraction of the pool.

Participation does not divide rewards by wallet count; it adds burn weight. Existing users' relative shares fall when additional eligible BF is burned, unless the Fan Vault grows enough to offset it.

It compares a current estimated Friday Drop with a conservative estimated value of the BF considered for burning. It is a point-in-time scenario based on current vault and Fan Power inputs.

There is no deposit, annualized rate or guaranteed yield. BF is permanently destroyed, the cycle state changes, and the result is only a current estimate—not a recurring return.

Thirty-five percent of Creator Rewards actually received funds the active weekly Fan Vault. Eligible community burners share the community-distributable portion pro rata after finalization.

Creator Rewards and therefore Burnback, Fan Vault and Top Fans funding may fall, potentially to zero. None of the examples are forecasts or minimum distributions.

A zero-community cycle does not hand the vault to the protocol. The funded amount rolls into the next cycle under the V1 contracts.

Yes. Burnback purchases BF and sends it to The Furnace. That burn may create protocol weight, but the resulting Loop Cut is capped and can only buy and burn BF again.

No. Its proportional Loop Cut is hard-capped at 20% of the funded weekly Fan Vault. The protocol cannot withdraw that value for another purpose.

Friday Drop claims expire after 90 days. Unclaimed ETH and residual dust then route exclusively to Burnback for another BF buy-and-burn cycle.

No. The Hot 25 is a deterministic calendar-month ranking of eligible BF burned. Equal amounts use deterministic address ordering.

Only MONTH is the official V1 Top Fans reward ranking. Each occupied Hot 25 rank receives 4% of the monthly Top Fans pool.

No. Quarter, Year and All Time are community statistics only. They do not create additional V1 reward pools.

No. Creator, project and protocol wallets are intended to be excluded through the immutable deployment denylist. The exact final denylist must be verified at deployment.

Every occupied rank receives its fixed 4% allocation. Unoccupied allocations roll into the following month's Top Fans pool.

After deployment, the Verify view will link to the BF token, Burn Router, Furnace and other contracts on the Base explorer. Contract events and state remain authoritative.

The Recent Burns drawer derives production entries from indexed BurnRouter events. Each real entry links to its corresponding Base explorer transaction; simulated development events never use fake BaseScan links.

No. BF, its Clanker pool and the BurnlyFans protocol contracts are not deployed. All current balances, burns, leaderboards and reward values shown in development mode are samples.