Burnsome.cro

Burnsome.cro is a Cronos-chain service/smart contract where users send CRO that is permanently sent to the Cronos burn address, while a small portion is retained in the contract for management and maintenance. The contract tracks activity per address and exposes a badge level that third parties can verify and use to give the user benefits.

Each burn transaction forwards 97.5% of the received CRO to the official burn address. The remaining 2.5% stays in the contract to cover management cost, maintenance, and ongoing development. This split is enforced by the smart contract.

The dApp can support burning for your own address and (optionally) for a beneficiary address. In that case, the beneficiary address receives the burn credit and the badge progression.

There are 10 levels (1–10) based on how much CRO is burned by an address during the configured tracking period of 90 days in the contract. If an address meets the requirement for a level, the badge reflects that level.

The level is determined by the total amount of CRO burned by an address within the defined tracking period (90 days). The level is actually calculated based on the USD value of the CRO burned. Specific thresholds for each level are listed below. (It doubles every level)

• Level 1: $0.20
• Level 2: $0.40
• Level 3: $0.80
• Level 4: $1.60
• Level 5: $3.20
• Level 6: $6.40
• Level 7: $12.80
• Level 8: $25.60
• Level 9: $51.20
• Level 10: $102.40

Yes. If an address burns less CRO than the current level requires within the tracking period of 90 days, the level can drop accordingly. However, once an address reaches level 1, it will never return to level 0 again.

Levels are computed over a fixed rolling window defined by the smart contract and is a fixed multi-day window of 90 days. The exact logic is documented in the contract and/or docs page.

Third parties can call the contract’s read functions for your address. The contract returns a level number and a URI to an image representing that level. This makes it simple to integrate into airdrops, rebates, allowlists, boosts, and other benefits.

No. The contract returns a URI (an HTTP/HTTPS URL) that points to the image file hosted off-chain. This keeps on-chain costs low while keeping the badge state verifiable on-chain (the returned level and URI are derived from contract state).

An EOA (externally owned account) is a normal wallet address. A contract address is a deployed smart contract. The dApp can show additional context for contract addresses (such as known names) and may display rankings or other contract-focused insights alongside standard burn/badge info.

“Known Names” are human-friendly labels stored in the contract for addresses (especially useful for contracts). If a name is not set (see also next question), the UI shows “Unknown” so the row is still visible and consistent, while keeping the address as the source of truth.

The UI resolves a contract’s displayed name in this order:

1. Known Name (stored on-chain in the Burnsome.cro contract)
2. Cronos Explorer public name tag (a public label from the explorer, often used for tokens)
3. Verified contract name (the contract name from Cronos Explorer verification data)

If none of these are available, the UI will show “Unknown”. The address remains the canonical identifier.

A public name tag is an explorer-provided label that helps users recognize popular addresses. In many cases, token contracts return a recognizable token name and symbol (for example: “TokenName (TKN)”). These tags are informative, but they are not stored on-chain in the Burnsome.cro contract.

If a contract is verified on the Cronos Explorer, the verification record includes a contract name (for example: “BurnsomeCro”). Burnsome.cro can use that verified name as a fallback when no on-chain Known Name exists and no public name tag is available.

For reliability and abuse prevention, the Burnsome.cro UI only treats this as a display hint—the address is always the source of truth.

Only the owner or explicitly authorized addresses can add/update known names. This prevents malicious relabeling and keeps the naming directory reliable for integrators. If you think your contract address should have a known name, use the Contact page to request it.

Yes. After the Top list is loaded, searching can match either the address or (part of) the known name, so you can find entries like “burnsome.cro” or other labeled contracts quickly.

No. Burns send funds to a burn address and are intended to be permanent. Always verify the amount and destination in your wallet confirmation screen before you approve a transaction.

You will pay standard Cronos network gas fees for the transaction. Gas fees are separate from the burned CRO amount and depend on network conditions.

Projects can use the on-chain badge level as an eligibility signal (airdrops, discounts, multipliers, allowlists, etc.). To request listing in the Perks directory, use the Contact page and select “Request ‘Perks’ listing” with your details.

Burning CRO typically does not require token allowance approvals (unlike ERC-20 transfers), because CRO is the native currency. Your wallet will still require transaction confirmation for each burn.

Any wallet that supports Cronos (EVM) and can connect to the dApp should work. If your wallet supports WalletConnect or injected EVM providers, you can generally interact with Burnsome.cro. If you're on a mobile device and the wallet does not popup, try using the in-app browser.

The contract does not enforce minimums. Even small burns can be valid, but levels may require meeting specific totals within the tracking period. However, keep in mind that gas fees may make very small burns less economical.