Akedo
Akedo — 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).
Akedo — an AI/Agents | Gaming | Infra project on BNB Smart Chain: a multi‑agent AI framework that allows creating games “no‑code” via text prompts (based on LLMs), and an ecosystem where the created content can be published/played/monetized. Token: AKE (BEP‑20).
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 platform where you can “assemble a game” from text and templates, and then publish and earn from the content.
- Who it’s for: game/content creators and players who want a UGC ecosystem with fast creation.
- Why onchain/token: the token is needed as the currency for prompts/publishing, staking and the distribution of protocol fees; the wallet’s onchain footprint is used for content personalization (per the whitepaper).
- What you can actually touch (Tier‑1): https://play.akedo.fun/
How it works (very briefly)
- The user does: chooses a template and writes a prompt (setting/map/rules/story).
- The system does: a set of AI agents classifies the task, refines the prompt, breaks it down into sub‑tasks and generates/tests the code/game elements (described in the AI Framework).
- The user gets: a finished game/content (maps/mechanics/NPCs/story) and can publish it in the ecosystem.
- Where the blockchain is:
AKEis a BEP‑20 token on BNB Smart Chain; AI personalization may use the wallet’s onchain “footprints” (a scan of assets/history) per the whitepaper. - Token role (if any): payment for prompts and publishing, staking (a share of protocol fees), LP mechanics and in‑game transactions (per the tokenomics).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Akedo |
| Also known as (aliases) | AKEDO Games; Akedo.AI; $AKE; Adodo Nodes |
| Logo (logo) | ../assets/135_akedo_logo.png |
| Token symbol (ticker) | AKE |
| Category | AI/Agents | Gaming | Infra |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | 2025 (roadmap: beta/public versions by quarters of 2025) |
| Project status (status) | active |
| Token (standard) | BEP-20 |
| Token contract | 0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db |
| Token model (token_type) | utility (governance) |
| Max supply | 100,000,000,000 AKE (total supply) |
| Issuance | issuance/unlocks over 4 years (per the tokenomics) |
| Tokenomics (tokenomics, brief) | AKE is needed for prompts and publishing; 33% of protocol fees — stakers, 33% — burn, 33% — revenue |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — (in the whitepaper: “game veterans”, without a verifiable lineup) |
| Funding (investors/funding) | — |
| AI component (ai_component) | multi-agent LLM (game generation + testing) |
| Use‑case (use_case) | no-code game creation from prompts |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 2 / 2 / 3 |
| Last verified | 2026-02-05 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://learn.akedo.fun |
| Docs | https://akedo-1.gitbook.io/akedo-whitepaper |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://akedo-1.gitbook.io/akedo-whitepaper |
| Roadmap | https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/roadmap |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db |
| App / Demo | https://play.akedo.fun/ |
| Node marketplace | https://agentnodes.akedo.fun/ |
| X | https://twitter.com/akedofun |
| Discord | — |
| Telegram | https://t.me/akedoglobal |
| Medium | https://medium.com/@akedo.fun |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/akedo |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/akedo/ |
General project overview
In Tier‑1 sources, Akedo describes itself as a multi‑agent AI framework for “Autonomous Content Creation”: the user provides a prompt, and a system of specialized AI agents (LLMs) jointly generates game elements and code, tests them in simulation and iteratively fixes them. The product part is positioned as a platform where you can create games from text, publish, play and monetize them in a “dynamic content ecosystem”.
The onchain layer is used as an economic and identity layer: the AKE token (BEP‑20) is claimed as the “primary currency” for prompts/publishing/in‑game scenarios, and the “On‑Chain Personalizer” section describes content personalization based on the wallet’s verifiable onchain footprints (BNB Chain).
Features/modules
- Multi‑agent AI creation: generation of maps/rules/balance/story and code via a set of LLM agents (AI Framework).
- Game templates: creation starts with choosing a template (RPG dungeon/adventure/survival/narrative, etc.).
- Play ecosystem: a library of games (first‑party + UGC), categories, incentives/points.
- Monetization: publishing, advertising/Revenue Sharing, tokenization of “game tokens” and “game collection tokens” (per the whitepaper).
- Nodes/compute (Adodo Nodes): nodes for earn/yield and (claimed) provision of compute power to the network.
Typical scenarios
- Scenario 1 (creator): chooses a template → writes a prompt → AI agents generate the game → the creator publishes the game (pays/uses
AKE) → receives a share of revenue/incentives. - Scenario 2 (player): plays UGC games → earns points/tokens → spends them on in‑game items/boosters/access.
- Scenario 3 (node operator): participates via an Adodo Node → receives yield/points and (per the whitepaper) can connect compute for AI processing and receive additional rewards.
Getting started (wallet/network)
- What you need: access to the Akedo web product (website/Play), an account (if required) and an EVM‑compatible wallet for onchain actions.
- Network/chain: BNB Smart Chain (for
AKEand onchain footprints in personalization). - Fees: BNB gas for onchain operations (token transfers/interactions, if applicable).
Architecture/tech (non‑AI)
- Components: the web platform (creation/play), AI orchestration (multi‑agent), the
AKEtoken contract (BSC), the node layer (Adodo nodes) and the in‑game economy/tokenization (per the whitepaper). - Participant roles: creators, players, node operators, token stakers.
- Where logic runs: generation/simulation — offchain; onchain — the token/economy and “footprints” for personalization (a scan of wallets/history).
- Dependencies: BNB Chain RPC/wallets, offchain AI infrastructure (LLM agents).
Token/economics (expanded, no forecasts)
- Token utility: AI creation (payment for prompts and game publishing), staking (a share of protocol fees), LP provision (pairs of new tokens with
AKE), in‑game scenarios and game tokenization. - Protocol necessity drivers: per the Tier‑1 tokenomics, “Users need to use $AKE to prompt and publish games”;
AKEis described as the main currency of the ecosystem. - Who pays fees: creators/players who use paid actions (prompts/publishing/in‑game transactions).
- Where fees go: per the tokenomics: 33% of protocol fees — platform revenue, 33% — stakers, 33% — burn.
- Issuance/burn: total supply 100B; there is a burn of a share of protocol fees (per the tokenomics).
- Security/incentive mechanisms: staking rewards; fee distribution as incentives; the node layer and creator/player rewards (at the level of distribution/descriptions).
- Distribution and token issuance schedule: the tokens are distributed by category (community/investors/ecosystem/early contributors/advisors/LP/airdrop) and unlocked on a schedule (4 years).
- Treasury: Ecosystem & Growth allocation (per the tokenomics) — management details are not disclosed.
Governance
- Who makes decisions: — (the Tier‑1 mechanics of governance via the token are not explicitly described in the available sections).
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: — (no Tier‑1 audit reports were found).
- Bug bounty: —.
- Incidents: —.
- Threat model: risks of “AI‑generated code/content” (quality/security), risks of the token economy/payment layers, risks of abuse of incentives.
Project status and timeline
- Current status: an active product/ecosystem (Tier‑1: description of creation/play + public product domains), the token exists on BSC.
- Key releases/milestones: 2025 Q1 beta, 2025 Q2 public version (per the roadmap).
- Roadmap: 2025 Q1–Q4: beta → public → expansion of templates → creators campaign.
Ecosystem/integrations
- Integrations: BNB Smart Chain (onchain footprints and the token), the node layer (Adodo nodes).
- Partners: — (within this card we do not record them without Tier‑1 contractual confirmation).
- Where it’s actually used: the creation/play mechanics are described in the Tier‑1 whitepaper and on the website.
AI component of the project
- What is real AI here? a multi‑agent LLM system generates game elements and code, simulates/tests and iteratively fixes them (Agent 1–5; task classification/breakdown/codegen/simulation/scrutiny).
- What is truly onchain? the
AKEtoken (BEP‑20), plus the wallet’s onchain footprints (BNB Chain) as an input to content personalization. - Why is a token needed? payment for prompts/publishing, staking (a share of protocol fees), the in‑game economy and LP pairs for game tokens.
- Red flags (based on the information found): AI‑washing (low) (there is a Tier‑1 technical description of the multi‑agent pipeline); onchain‑washing (medium) (the criticality of the blockchain is not proven by a replacement test); token‑washing (medium) (the utility is described, but the actual “mandatory” nature of payment in
AKEand the implementation of the burn/fee split should be double‑checked).
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | medium | 2 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): the AI component is described as a working architecture and product, not only as an “intent”.
- Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/akedo-framework; https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/creation
- Why sufficient / why not (one line): there is a Tier‑1 description of the AI pipeline and the game creation mechanics → the intent flag is not needed.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): a multi‑agent LLM system generates game elements and code (map/mechanics/balance/story), then simulates and checks the result.
- Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/akedo-framework; https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/creation
- Why sufficient / why not (one line): the Tier‑1 technical description records the agent roles and the task→code→simulation→scrutiny steps.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): there are public “TRY NOW” product entry points for creation/play (app endpoint), confirming the existence of a demo artifact.
- Evidence: Tier‑1 — https://learn.akedo.fun/; https://play.akedo.fun/
- Why sufficient / why not (one line): the website leads to “TRY NOW”, and a separate app domain exists as a product endpoint.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): the available Tier‑1 sources contain no quantitative metrics/benchmarks of generation quality.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the agent roles and pipeline (task classification/breakdown/codegen/simulation/scrutiny) and the modular AI infrastructure are described.
- Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/akedo-framework; https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/modular-ai-infrastructure
- Why sufficient / why not (one line): there is a Tier‑1 architectural description of how the multi‑agent system and the modules work.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers:
AKEBEP‑20:0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db - Evidence: Tier‑1 — https://bscscan.com/token/0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db
- Why sufficient / why not (one line): BscScan confirms the network, the contract and the max supply of the token.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: AI personalization based on verifiable onchain footprints (asset holdings/tx history/DID metrics) and asset‑gated features.
- Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/on-chain-personalizer
- Why sufficient / why not (one line): the Tier‑1 section describes the use of the wallet’s onchain footprint as an input to content/feature generation.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the core game generation could work offchain; there is no Tier‑1 proof that “without the blockchain it breaks down”.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): the criticality of the onchain layer is not proven by a replacement test → 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token,
AKE(BEP‑20), on the BNB Smart Chain network. - Evidence: Tier‑1 — https://bscscan.com/token/0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db
- Why sufficient / why not (one line): the onchain token page confirms the existence of the token and its parameters.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 1
- Claim (one line):
AKEis needed for prompts and game publishing (pay‑per‑prompt and pay‑to‑publish). - Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/tokenomics
- Why sufficient / why not (one line): the Tier‑1 tokenomics explicitly sets payment for prompts/publishing via
AKE. - Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): staking
AKEgives a share of protocol fee revenue; part of the fees goes to stakers, part — to burn. - Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/tokenomics
- Why sufficient / why not (one line): the tokenomics describes staking and the distribution of protocol fees (stakers/revenue/burn).
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the role of
AKEin governance is not confirmed in the available Tier‑1 sections. - Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no clear Tier‑1 wording about the token’s governance mechanics → 0.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): the Tier‑1 tokenomics describes
AKEas the mandatory token for prompts/publishing, and also as the base asset for fee distribution/staking. - Evidence: Tier‑1 — https://akedo-1.gitbook.io/akedo-whitepaper/tokenomics; https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/nodes-assets
- Why sufficient / why not (one line): if the protocol requires
AKEfor key actions, replaceability does not follow from Tier‑1 sources → TK_4 = 0. - Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://akedo.fun/ | Tier‑1 product description: a multi‑agent AI framework for autonomous content creation (games in ~2 minutes from a prompt). |
| Tier‑1 | https://learn.akedo.fun/ | Tier‑1 product page with “TRY NOW” and a description of the specialized AI agents. |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper | Tier‑1 whitepaper: description of Akedo, the agents (World Builders/Rule Designers/Balancers/Storytellers) and the “Why crypto” motivation. |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/akedo-framework | Tier‑1 technical description of the multi‑agent pipeline (task→codegen→simulation→scrutiny). |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/modular-ai-infrastructure | Tier‑1 architecture of the modules and the transparency/traceability of AI operations (logging/versions). |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/ai-framework/on-chain-personalizer | Tier‑1 onchain logic: personalization based on BNB Chain onchain footprints (scan wallet, asset‑gated features). |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/tokenomics | Tier‑1 tokenomics: total supply 100B, distribution, utilities (pay‑per‑prompt/publish, staking fee share, burn). |
| Tier‑1 | https://bscscan.com/token/0x2c3a8Ee94dDD97244a93Bc48298f97d2C412F7Db | Tier‑1 onchain fact: the AKE contract (BEP‑20) and max total supply 100B. |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/roadmap | Tier‑1 roadmap 2025 Q1–Q4. |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/creation | Tier‑1: description of the game creation process from a prompt (templates, multi‑agent collaboration). |
| Tier‑1 | https://akedo-1.gitbook.io/akedo-whitepaper/explore-akedo/nodes-assets | Tier‑1: Adodo Nodes, the role of compute and AKE as the main asset of the ecosystem. |
No comments to display
No comments to display