AiONE
AiONE — 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).
AiONE — an AI/Other | Infra project on the BNB Smart Chain network, token (symbol: AiONE).
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: a token on the BNB Smart Chain network; claimed to be an AI integration platform in the explorer (intent).
- Who it’s for: users who need an AI service/integration (per the project’s claim).
- Why onchain/token: onchain records the token contract and transfers; the token utility is not established per Tier‑1.
How it works (very briefly)
- The user does: sends/receives the token or checks the contract.
- The system does: executes token transactions on the BNB Smart Chain network.
- The user gets: a change in the token balance.
- Where the blockchain is: the token contract and token transactions.
- Token role (if any): the role/utility of the token in the product is not established per Tier‑1 sources.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AiONE |
| Also known as (aliases) | AiONE |
| Logo (logo) | ../assets/770_aione_logo.svg |
| Token symbol (ticker) | AiONE |
| Category | AI/Other | Infra |
| 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) | — |
| Token (standard) | BEP-20 |
| Token contract | 0x4634d58982138e93c951c1485d25bc619cbd1f75 |
| Token model (token_type) | — |
| Max supply | 100,000,000,000 AiONE |
| Issuance | — |
| Tokenomics (tokenomics, brief) | max total supply is given in the explorer. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI integration platform |
| Use‑case (use_case) | AI services/APIs |
| DecAI Fit — AI thesis fit | 1/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://ai.one/ |
| Docs | — |
| GitHub | https://github.com/aionelab/AiONE |
| Releases / Changelog | — |
| Whitepaper | https://ai.one/whitepaper.pdf |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0x4634d58982138e93c951c1485d25bc619cbd1f75 |
| X | https://twitter.com/aionelab |
| Discord | https://discord.com/invite/HDcDbjUUhY |
| Telegram | https://t.me/aionelab |
| Medium | https://medium.com/@aionelab |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/aione/ |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/aione/ |
General project overview
AiONE is a token on the BNB Smart Chain network. In the token description in the explorer, the project claims “AI integration platform … suite of AI services, APIs, and tools”, but no Tier‑1 demos/examples or technical description of the AI part were found (so the AI assessment is limited to intent).
Features/modules
- AI integration platform (claimed in the explorer; no details/demos).
- the AiONE token on the BNB Smart Chain network (BEP‑20).
Typical scenarios
- Scenario 1: a user sends/receives the token → the balance changes.
- Scenario 2: a user checks the token contract in the explorer → sees the token parameters and the verified contract code.
Getting started (wallet/network)
- What you need: an EVM wallet and BNB for network fees (gas).
- Network/chain: BNB Smart Chain.
- Fees: BNB Smart Chain network fees for transactions.
Architecture/tech (non‑AI)
- Components: the token contract on the BNB Smart Chain network; verified contract source code in the explorer.
- Participant roles: users (holders/senders), BNB Smart Chain network validators.
- Where logic runs: onchain (token contract and transactions); AI logic/backend are not confirmed.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 sources.
- Protocol necessity drivers: not established.
- Who pays fees: users for transactions.
- Where fees go: to validators/the network (per BNB Smart Chain rules).
- Issuance/burn: —.
- Security/incentive mechanisms: —.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: the main risks are typical for tokens on EVM networks; specific measures/audits are not established.
Project status and timeline
- Current status: mainnet (the token is observable on the BNB Smart Chain network).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: EVM wallets; the BscScan explorer.
- Partners: —.
- Where it’s actually used: onchain activity is visible via the explorer (see links_*).
AI component of the project
- What is real AI here? AI positioning is claimed in the explorer (AI integration platform, suite of AI services/APIs), but no Tier‑1 proof of operation (demos/metrics/architecture) was found.
- What is truly onchain? The token contract and verified contract source code on the BNB Smart Chain network.
- Why is a token needed? The token exists onchain, but its necessity/utility is not established per Tier‑1 sources.
- Red flags (based on the information found): AI intent without demos/metrics; onchain may boil down to token issuance; token utility is not disclosed by Tier‑1; possible brand confusion between “AI One”/“AiONE”.
DecAI Fit component summary
- DecAI Fit: 1/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 present | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): AI positioning is claimed in the explorer: “AI integration platform … suite of AI services, APIs, and tools”.
- Evidence: Tier‑1 — https://bscscan.com/token/0x4634d58982138e93c951c1485d25bc619cbd1f75
- Why sufficient / why not (one line): this is a Tier‑1 declaration of AI intent, but without proof of working AI features.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): What exactly the AI component does is not established (no Tier‑1 details of the features).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a Tier‑1 description of specific AI features, we record 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demo/example of AI features was found per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no verifiable demo → 0.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Tier‑1 metrics/benchmarks are absent → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of the AI part was not found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no Tier‑1 tech description → 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers: token contract 0x4634d58982138e93c951c1485d25bc619cbd1f75
- Evidence: Tier‑1 — https://bscscan.com/token/0x4634d58982138e93c951c1485d25bc619cbd1f75
- Why sufficient / why not (one line): the explorer confirms the network, address and token parameters.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 on contracts/logic other than the token was found.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established what breaks down without onchain (other than token accounting).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 argument/proof of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, AiONE, on the BNB Smart Chain network.
- Evidence: Tier‑1 — https://bscscan.com/token/0x4634d58982138e93c951c1485d25bc619cbd1f75
- Why sufficient / why not (one line): the token and its contract are displayed in 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 established (no Tier‑1 found).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a Tier‑1 description of utility, we record 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Token‑based incentives/collateral/penalties are not established (no Tier‑1 found).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 description of the token as an incentive/collateral.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): Governance via the token is not established (no Tier‑1 found).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without Tier‑1 governance mechanics, we record 0.
- 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 without a description of utility (no Tier‑1 found).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data to prove replaceability/irreplaceability.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://bscscan.com/token/0x4634d58982138e93c951c1485d25bc619cbd1f75 | The AiONE token and its contract on the BNB Smart Chain network; AI positioning in the token description; max total supply; verified contract source code. |
| Tier‑1 | https://github.com/aionelab/AiONE | A repository with smart contracts/scripts (a Tier‑1 code artifact). |
| Tier‑1 | — | No Tier‑1 source for claim “AI demo/examples and metrics” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “onchain logic other than the token” was found. |
| Tier‑1 | — | No Tier‑1 source for claim “necessity of the token (utility)” was found. |
| Tier‑2 | https://ai.one/ | Project website (context; requires reconciliation with the token description). |
| Tier‑2 | https://coinmarketcap.com/currencies/aione/ | Token profile (context). |
| Tier‑2 | https://www.coingecko.com/en/coins/aione/ | Token profile (context). |
| Tier‑2 | https://twitter.com/aionelab | Official announcements (context). |
| Tier‑2 | https://t.me/aionelab | Official Telegram (context). |
| Tier‑2 | https://medium.com/@aionelab | Blog (context). |
No comments to display
No comments to display