cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-BURN-001

BurnedFi (BURN)

BNB Smart Chain · Token contract · Documentation reviewed

Documentary contract0x19c018e13cff682e729cc7b5fb68c8a641bf98a4

The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

This dossier examines the documented purpose and mechanisms of BurnedFi (BURN) on the BNB Smart Chain network. The goal is to understand the stated aims of this token as recorded in community-maintained registries, while clearly separating those claims from independent operational verification.

Established facts

The pinned Trust Wallet registry entry for BNB Smart Chain identifies BurnedFi with the symbol burn and the documentary contract address 0x19c018e13cff682e729cc7b5fb68c8a641bf98a4. This record specifies 18 decimal places, a technical term referring to the number of digits used to represent fractional amounts in the token system, which does not measure supply or value. The registry labels the entry as BEP20, indicating it follows the standard interface for fungible tokens on this network. The community-maintained description states that BurnedFi is a fair burning movement returning to fundamental decentralization. These statements are attributed registry claims, not independently verified issuer statements. The ERC-20 specification defines the standard interface requirements for such tokens, including functions for reading balances and transferring assets, but a wallet label establishes no independently checked compliance or actual deployed implementation.

Unknowns

Present independent control, beneficial ownership, usage patterns, client adoption, total supply, concentration of holdings, liquidity depth, and complete incident history remain unverified. No live network observation was performed to confirm current controllers or deployed bytecode behavior. The dossier may explain stated aims with attribution, but economic niche and scoring criteria remain unclassified.

Consequences

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Inclusion in a community-maintained registry does not imply a direct partnership with the listed projects or validate the safety and functionality of the smart contract. Without independent verification, the operational strength remains unproven.

Verdict

Operational strength remains unproven; unrated with 0% scoring coverage. No public admission of operational status or audit results has been established. The lack of evidence prevents any assessment of security, governance, or economic viability.

What would change it

Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this documentary baseline. Calibration and editorial review following such verification could establish a scored status.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured BNB Smart Chain record for BurnedFi

The pinned Trust Wallet BNB Smart Chain integration record names BurnedFi with symbol burn, documentary address 0x19c018e13cff682e729cc7b5fb68c8a641bf98a4 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BEP20 and active. Its community-maintained description states: "Burn: This is a fair burning movement, returning to the most fundamental decentralization of blockchain organizations." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: ec37bae72b0a197e63265de34ed1054aa2798f1b4dbeb736a696f0950b583074

Trust Wallet: pinned BNB Smart Chain directory context

The pinned Trust Wallet smartchain network-context record identifies the community registry directory for BNB Smart Chain. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 9888dd19b8ace07b4a705771770ab5140129ba43ec4ce6e95932dd63af204278

Trust Wallet Assets: README.md (bbe582d25a22)

The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

Ethereum ERC-20: pinned token interface specification

The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation