Burnify.AI

Burnify.AI — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Burnify.AI — a project on the BNB Smart Chain network (BEP‑20), token (symbol: BURNIFYAI).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

What it is: per the project’s claim — a buyback/burn protocol that can be integrated into BEP‑20 contracts.
Who it’s for: teams that want to add buyback/burn mechanics to a token/contract (per the project’s claim).
Why onchain/token: onchain — the token (BEP‑20) and related public contract data; per the project’s claim, the protocol is linked to buyback/burn mechanics.
What you can actually touch (Tier‑1): the Telegram notification bot @BurnifyAI_Bot and instructions for integrating the protocol with “1 line of code” (GitBook).

How it works (very briefly)

The user does: integrates the protocol into a BEP‑20 contract (per the project’s claim).
The system does: per the project’s claim, executes “targeted buybacks” and burn mechanics triggered by AI.
The user gets: buyback/burn operations as part of the contract mechanics (per the project’s claim).
Where the blockchain is: onchain — the token and its contract; details of the protocol logic require re‑checking.
Token role: the token utility is not established per Tier‑1 sources (other than tokenomics: supply and buy/sell tax; and Tier‑1 claims about buyback/burn mechanics).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Burnify.AI
Also known as (aliases)	BurnifyAI
Logo (logo)	—
Token symbol (ticker)	BURNIFYAI
Category	AI/Other \| DeFi
Primary chain (chain)	BNB Smart Chain
Type	EVM
Network status	mainnet
Consensus (consensus)	PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date)	—
Project status (status)	active
Token (standard)	BEP-20
Token contract	0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea
Token model (token_type)	utility (buyback + burn)
Max supply	100 000 000 BURNIFYAI
Issuance	—
Tokenomics (tokenomics, brief)	Total supply 100 000 000; buy tax 5%, sell tax 5% (Tier‑1 Tokenomics).
Governance	—
Admins/keys	—
Audit	yes (Coinsult; the link is in `links_*`)
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	AI buyback/burn triggers
Use‑case (use_case)	buyback/burn protocol for BEP-20
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://burnify.ai
Docs	https://burnify-ai.gitbook.io/
GitHub	—
Releases / Changelog	—
Whitepaper	https://burnify-ai.gitbook.io/
Roadmap	https://burnify-ai.gitbook.io/burnify.ai/roadmap
Security advisories	—
Explorer	https://bscscan.com/token/0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea
App / Demo	https://t.me/BurnifyAI_Bot
X	https://twitter.com/BurnifyAI
Discord	—
Telegram	https://t.me/BurnifyAI
Medium	—
Audit report(s)	https://github.com/Coinsult/solidity/blob/main/Coinsult_BurnifyAI_0x36...3EEa_Audit.pdf
Bug bounty	—
CoinGecko (profile, reference)	—
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/burnifyai/

General project overview

Per the Tier‑1 documentation, Burnify.AI describes a buyback protocol for BEP‑20 contracts, where buyback triggers are claimed to be “AI‑backed”. Tier‑1 sources claim AI buyback triggers, but do not provide verifiable details of the AI part (model/metrics/architecture) — so AI conclusions remain conservative.

Features/modules

Integration of the buyback protocol into a BEP‑20 contract (per the project’s claim).
AI triggers for buybacks (per the project’s claim).
Burn mechanics and a buyback system (per the project’s claim).

Typical scenarios

Scenario 1: a team adds the protocol to a contract and enables buyback/burn mechanics (per the project’s claim).
Scenario 2: participants observe buyback/burn events onchain (requires separate verification through transactions/events).

Getting started (wallet/network)

What you need: a BNB Chain wallet; access to the documentation/integration instructions.
Network/chain: BNB Smart Chain (BEP‑20).
Fees: BNB Smart Chain onchain fees; other fees — not established per Tier‑1 sources.

Architecture/tech (non‑AI)

Components: the BEP‑20 token contract; documentation; audit report (Tier‑1 links).
Participant roles: users/integration teams.
Where logic runs: onchain — the token; protocol integration logic — requires re‑checking against the code/contracts.
Dependencies: BNB Smart Chain RPC; the rest — not established.

Token/economics (expanded, no forecasts)

Token utility: not described per Tier‑1 sources as mandatory “utility in the product”, other than tokenomics parameters and the claimed buyback/burn logic.
Protocol necessity drivers: per Tier‑1 sources, it is not established where exactly the token is mandatory as “payment/access” (additional verification of contracts/docs is needed).
Who pays fees: not established.
Where fees go: not established.
Issuance/burn: total supply and buy/sell tax are given in Tier‑1 Tokenomics; the detailed mechanics of actual burn require verification through contracts/events.
Security/incentive mechanisms: not established.
Distribution and token issuance schedule: not established.
Treasury: not established.

Governance

Who makes decisions: not found per Tier‑1 sources.
How protocol parameters change: not found.
Where decisions are discussed/made: not found.
Keys/multisig: not found.

Security and incidents

Audits: an audit (Coinsult) is listed — the link is in links_*.
Bug bounty: not found per Tier‑1 sources.
Incidents: not found per Tier‑1 sources.
Threat model: requires separate verification: whether the audit matches the current contract, the presence of proxies/upgrades, the actual operation of buyback/burn.

Project status and timeline

Current status: mainnet (BEP‑20 token on BNB Smart Chain).
Key releases/milestones: not found per Tier‑1 sources.
Roadmap: listed in the project docs; details require re‑checking.

Ecosystem/integrations

Integrations: not established per Tier‑1 sources.
Partners: not found per Tier‑1 sources.
Where it’s actually used: not established.

AI component of the project

What is real AI here? A Tier‑1 source claims that the buyback mechanics are “AI‑backed/AI‑triggered”, but the specifics of the AI part (model/metrics/architecture) are not confirmed by Tier‑1 technical artifacts.
What is truly onchain? The token on BNB Smart Chain and its contract are confirmed onchain.
Why is a token needed? Tier‑1 sources record tokenomics parameters and claim buyback/burn mechanics, but do not provide an unambiguous formalization of the token utility as “payment/access/governance”.
Red flags (based on the information found): “AI‑backed” without verifiable artifacts of the AI part; whether the audit matches and the actual buyback/burn logic in the contracts require re‑checking.

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	medium	2
Onchain necessity	low	1
Token necessity	low	0
Evidence	Tier‑1 present	3

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

AI_0 (decision): 0
Claim (one line): Tier‑1 describes AI buyback triggers as part of the protocol (this is more than intent).
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): AI_0 applies to “intent only”; here there is a description of the use of AI in the mechanics (without details).
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): Per the Tier‑1 claim, AI is used for “targeted buybacks” triggers (push/reversal buybacks).
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/ ; https://burnify-ai.gitbook.io/burnify.ai/abstract
Why sufficient / why not (one line): The documentation describes the purpose of the AI part (buyback triggers), but without technical details.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 1
Claim (one line): There are reproducible “product surfaces”: a Telegram notification bot and instructions for integrating the protocol with “1 line of code” (Tier‑1).
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/burnify.ai/our-telegram-bot ; https://burnify-ai.gitbook.io/burnify.ai/how-to-use-burnify.ai
Why sufficient / why not (one line): These are verifiable instructions/tools for integration and observing events; they do not prove the existence/quality of an AI model (AI_3/AI_4 remain 0).
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: not found per Tier‑1 sources.
Context (version/date/how measured): not found.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): There are no quantitative metrics/benchmarks of the AI part.
Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

AI_4 (decision): 0
Claim (one line): The architecture/versions of the AI module are not confirmed by Tier‑1 technical artifacts.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): 1 requires technical details, which are absent.
Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

OC_1 (decision): 1
Chain: BNB Smart Chain
Addresses/identifiers: 0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea
Evidence: Tier‑1 — https://bscscan.com/token/0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea
Why sufficient / why not (one line): The token contract is verifiable via the onchain explorer.
Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

OC_2 (decision): 0
What useful logic is onchain: Tier‑1 describes onchain integration through a separate protocol contract (address in the integration instructions), but the full set of contracts/logic requires separate verification.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/burnify.ai/how-to-use-burnify.ai
Why sufficient / why not (one line): There is a Tier‑1 mention of an onchain integration address and an example; without a systematic description of contracts/events we conservatively set 0.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: the criticality of onchain for a key property of the protocol is not proven by Tier‑1 sources.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): There is no explicit argument “without the blockchain the property breaks down”.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a token on the BNB Smart Chain network.
Evidence: Tier‑1 — https://bscscan.com/token/0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea
Why sufficient / why not (one line): The token contract is observable via the explorer.
Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 0
Claim (one line): Payment for the service with the token is not confirmed by Tier‑1 sources.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): There is no description of pay‑per‑use with the token as a mandatory mechanism.
Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

TK_2 (decision): 0
Claim (one line): Incentives/collateral/penalties via the token are not confirmed by Tier‑1 sources.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): The available materials contain no specific scheme of incentives/staking/slashing.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): Governance use of the token is not confirmed per Tier‑1.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): There is no description of DAO/governance.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): The replaceability of the token is not established per Tier‑1 sources.
Evidence: Tier‑1 — https://burnify-ai.gitbook.io/
Why sufficient / why not (one line): 1 requires an explicit argument that the token is secondary and replaceable.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://burnify-ai.gitbook.io/	Tier‑1 description of “AI backed buyback protocol”, positioning and a high‑level description of the mechanics.
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/abstract	Tier‑1 description of the protocol’s goals and mention of the AI approach (without metrics/architecture).
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/tokenomics	Tokenomics: total supply 100 000 000; buy/sell tax 5%/5%.
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/our-telegram-bot	Telegram notification bot for buyback mechanics events and connection instructions.
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/how-to-use-burnify.ai	Instructions for integrating the protocol with “1 line of code” and a link to sample code (BscScan).
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/the-mechanism	Tier‑1 high‑level description of the integration mechanism and contract requirements.
Tier‑1	https://bscscan.com/token/0x36f6f2f2a9a0672e40c1531ddb7421ade65b3eea	Onchain fact of the BEP‑20 token contract on the BNB Smart Chain network.
Tier‑1	https://github.com/Coinsult/solidity/blob/main/Coinsult_BurnifyAI_0x36...3EEa_Audit.pdf	Smart contract audit (public report).
Tier‑1	https://burnify-ai.gitbook.io/burnify.ai/roadmap	Roadmap; Tier‑1 mentions the ticker $BURNIFYAI.