- BurnedFi (BURN) research overview
- Historical market behavior
- YearBull metric interpretation
- Market structure and supply
- Key risks and limits
- Primary sources and review scope
- BurnedFi Explained: How BURN, BUILD and the Burn-to-Earn Model Fit Together
- What BurnedFi is
- The burn mechanism
- BURN, BUILD and the application layer
- Supply, ownership and contract controls
- Trading and user dependencies
- How to assess the project
- Key takeaways
- Risks and open questions
- YearBull Rank timeline
BurnedFi (BURN) research overview
BurnedFi (BURN) is tracked by YearBull under the source identifier burnedfi. Source categories place the asset in the Meme Coins universe, with additional labels including BNB Chain Ecosystem, Meme. Category labels describe market context; they do not prove project activity, adoption, or investment quality.
Market structure and supply
Observed market capitalization is about $30.53 million and reported 24 hour volume is about $19.7 thousand. That volume equals 0.06% of market capitalization in the dated snapshot. Current circulating supply is 12,281,750. The recorded maximum supply is 21,000,000. Circulating supply changed -0.8% across the available historical window. Reported volume and supply fields can change through source revisions, issuance, burns, migrations, or venue coverage.
Key risks and limits
Attention driven demand, holder concentration, shallow liquidity, contract controls, and abrupt changes in venue support can dominate price behavior. Historical metrics describe the available YearBull record; they do not predict future returns. Contract addresses, network support, custody, and venue availability should be verified before use.
Primary sources and review scope
YearBull methodology | Official project website | Technical documentation or whitepaper. Identity, categories, supply, and historical market fields were reviewed from locally stored source records on 2026-09-12. The live analytical snapshot may be newer than this editorial review.
BurnedFi Explained: How BURN, BUILD and the Burn-to-Earn Model Fit Together
BurnedFi is a BNB Chain token built around permanent BURN reductions, a separate BUILD token and a dividend-oriented application. Its design combines automatic transaction mechanics with a more complex burn-and-mint process that depends on the project’s app and liquidity markets.
What BurnedFi is
BurnedFi is a BEP-20 token on BNB Chain with the symbol BURN and the contract address 0x19c018e13cff682e729cc7b5fb68c8a641bf98a4. The contract’s maximum supply is 21 million tokens, and its source code is verified on BscScan under the contract name burnedFi. Public records place the token’s launch and early listings in late 2023 and 2024, although the reviewed materials do not establish a clearly documented founding team or legal entity.
The burn mechanism
The project’s central idea is that BURN is meant to become scarcer through programmed destruction. An exchange announcement describing the token says that 0.25% of the supply is burned every hour, or up to 6% per day, and that voluntary burns can accelerate the process. That description should be treated as a project or listing claim rather than as proof that the stated rate has operated continuously. The reviewed block-explorer record confirms the token contract and verified code, but does not by itself demonstrate the long-term effect of every advertised burn mechanism.
BURN also carries a transaction-tax design. The same listing announcement describes a 1% buy or sell tax, with tax revenue directed to a reward pool. CertiK’s token scan independently displayed a 1% buy tax and 1% sell tax at the time of its review. Tax behaviour can still depend on the contract, trading venue and transaction route, so users should check the live contract and pool before treating the rate as permanent.
BURN, BUILD and the application layer
BurnedFi’s more distinctive feature is a two-token process. Project descriptions say users can send or burn BURN through a decentralised application and receive BUILD as proof of the burn. The resulting BUILD position is then associated with liquidity mining and potential BNB distributions. A third-party market description gives a similar outline: users purchase BURN, use the application to burn it, receive BUILD and participate in a system that advertises BNB dividends.
This means BURN’s practical role is not limited to being a transferable meme token. It is also the input to a burn-and-build workflow. The economic result depends on several moving parts: the conversion rules between BURN and BUILD, the availability of the application, the funding and operation of the reward pool, the liquidity-mining contracts and the value of BNB distributions. The reviewed sources do not provide enough independently verifiable documentation to establish that the advertised yield or conversion outcome is guaranteed, fixed or sustainable.
Supply, ownership and contract controls
BscScan reports a verified, exact-match source contract with a 21 million maximum supply. CertiK’s scan reports that it did not detect a mint function, blacklist, honeypot restriction, self-destruct function or privileged ability to modify balances, and it identifies the owner address as renounced. These are useful contract-level observations, but they do not amount to a full audit of the wider BurnedFi application or every contract that may interact with BURN.
The contract also uses external calls, according to CertiK’s scan. That matters because a token can have limited owner powers while the broader user experience still depends on separate application contracts, liquidity pools, reward logic or front-end infrastructure. Ownership renunciation reduces one category of administrative control; it does not remove integration, oracle, liquidity or operational risks.
Trading and user dependencies
The main observable market route reviewed was a BURN/USDT pool on PancakeSwap V2. The pool page identifies the BURN contract and shows that trading occurs against USDT on BNB Chain. This makes PancakeSwap liquidity and the condition of the underlying pool practical dependencies for buying or selling, even if BURN is also available through centralised venues.
CertiK’s project profile reported more than 100,000 holders but also showed a major-holder ratio of roughly one-third of supply. That combination can create a misleading impression of distribution: a high wallet count does not necessarily mean that ownership or effective liquidity is broad. Users also need BNB for network fees and must distinguish the verified token contract from similarly named assets or unofficial application links.
How to assess the project
BurnedFi is best understood as a speculative BNB Chain token wrapped around a burn-and-build application concept. The contract-level record provides evidence for the token address, maximum supply, verified code and several reported controls. The larger economic proposition—automatic supply reduction, BUILD issuance, liquidity mining and BNB rewards—depends on application contracts and project-operated mechanisms that were not fully inspectable in the reviewed official pages. That distinction is central when evaluating the asset: verified token code is not the same as independently verified product performance.
Key takeaways
- BURN is a verified BEP-20 token on BNB Chain with a 21 million maximum supply.
- The project describes automatic burns and a 1% buy-and-sell tax, while CertiK’s scan reported the same tax rate at review time.
- The intended application workflow burns BURN to issue BUILD and links BUILD to liquidity mining and possible BNB distributions.
- Ownership renunciation and the absence of several reported token-level controls do not eliminate risks in external application contracts or liquidity pools.
- Holder counts should be read alongside concentration data; CertiK reported that major holders controlled roughly one-third of supply.
- The project’s reward and conversion claims require more independently inspectable documentation than was available in the reviewed sources.
Risks and open questions
- The advertised burn rate and long-term reduction in circulating supply were not independently established from the reviewed on-chain records.
- The sustainability, funding and withdrawal rules of the BNB reward pool are unclear from the available documentation.
- BURN users may face external-contract, liquidity-pool and front-end risks beyond the verified token contract itself.
- Major-holder concentration can increase volatility and the effect of large transfers or liquidity changes.
- The reviewed materials do not clearly identify a responsible legal entity, governance process or publicly documented upgrade-control framework.
- A 1% transfer tax can affect execution costs, especially when combined with slippage, exchange-specific deductions or application fees.
YearBull Rank timeline
Current YearBull Rank for burnedfi: #5189.
Rank change (reference points).
Reading rule: a smaller rank number indicates stronger placement.
- 7d window (2026-09-22): #6568 → #5189 (up by 1379).
- 30d window (2026-08-30): #4531 → #5189 (down by 658).
Downside posture: the same move can be stable in one market and fragile in another.
Venue angle: a broader footprint often smooths the rank trajectory.
Liquidity context: a quiet tape can still re-rank the pack.
Market phase: recent movement can fit a transition rather than a clean trend.
YearBull Rank is a comparative index on YearBull that helps contextualize a coin’s position versus others over time. Lower rank numbers indicate stronger placement in the current snapshot. It is a context signal for relative placement, not an outcome forecast.

