Skip to main content

DAOBase

DAOBase — 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).

DAOBase — an AI/Other / Infra project (an AI‑powered DAO launcher + DAO aggregator), token (symbol: BEE).

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 service/platform that aggregates DAO data and helps create/manage communities (DAO launcher + analytics).
  • Who it’s for: creators of DAOs/communities and users who need analytics/rankings/governance tools.
  • Why onchain/token: onchain is needed for the BEE token (Base/BSC) and the claimed incentive/governance functions; in the Tier‑1 documentation, AI is mentioned as an “AI‑powered” characteristic of the product.

How it works (very briefly)

  1. The user does: explores the DAO ecosystem (leaderboards/analytics) and/or launches DAOs/tokens/assets and connects governance frameworks.
  2. The system does: aggregates data and provides governance/analytics tools and a reputation layer (per the docs).
  3. The user gets: an “all‑in‑one” interface for launching/managing/analyzing DAOs.
  4. Where the blockchain is: the BEE token and the smart contract infrastructure (the docs claim a Smart contract section).
  5. Token role: the ecosystem’s utility+governance token (per the token docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name DAOBase
Also known as (aliases) DAO BASE, ThePass (in the project’s links)
Logo (logo) —
Token symbol (ticker) BEE
Category AI/Other | Infra
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Base on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract Base: 0x1f1bA52c445755C92caFFe7B608B87dCDAf9d825; BSC: 0xDB6f1F098B55E36B036603c8e54663a8D907D6E1
Token model (token_type) utility (incentives + governance)
Max supply 1,000,000,000 BEE (total supply; per the docs)
Issuance —
Tokenomics (tokenomics, brief) the docs describe total supply/decimals/networks and the unlock logic (cliff + linear vesting by category)
Governance governance (as claimed)
Admins/keys —
Audit yes (there is a Security Audit section in the docs)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI-powered aggregator/launcher
Use‑case (use_case) DAO analytics + launcher
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 1 / 2
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, DAOBase is described as an “AI‑powered DAO launcher and aggregator”: a platform that aggregates the DAO ecosystem (leaderboards/analytics/insights) and provides tools for launching tokens/assets and integrating governance functions (treasury management, proposals, delegation, etc.).

The docs also claim reputation layer tools (for example, DAOBadgeX) and data coverage (mapped over 170,000 DAOs and governance participants; this claim is present in the docs, but as an aggregated metric without a methodology it should be treated with caution).

Features/modules

  • DAO aggregation/analytics: leaderboards, analytics and “deep insights”.
  • DAO launcher: launching tokens/assets and fair launch / fundraising mechanics (claimed).
  • Governance integration: treasury/proposals/delegation (claimed).
  • Reputation layer: DAOBadgeX and onchain reputation (claimed).

Typical scenarios

  • Scenario 1: a user explores DAO metrics/rankings → receives analytical reports/insights.
  • Scenario 2: a community creator launches DAO entities and connects governance tools.

Getting started (wallet/network)

  • What you need: web access to the product; for the BEE token — an EVM wallet.
  • Network/chain: Base and BNB Smart Chain (per the token docs).
  • Fees: gas of the respective network for onchain operations.

Architecture/tech (non‑AI)

  • Components: the product layer (aggregation/analytics), a set of onchain artifacts (the BEE token, NFT PASS/BadgeX, etc. per the structure of the docs), governance integrations.
  • Where logic runs: analytics/aggregation — offchain; onchain — the token and some of the tools (claimed).

Token/economics (expanded, no forecasts)

The Tier‑1 token docs state:

  • Networks: Base and BNB Smart Chain.
  • Total supply: 1,000,000,000 BEE.
  • Decimals: 18.
  • Contract addresses: Base and BSC contracts (and a bridge contract on Base is listed as a separate line).
  • Unlock logic: cliff + linear vesting for Team/Advisors and VC rounds; unlock rules for different categories (described in text).

Governance

  • Who makes decisions: governance mechanics are claimed; process details are not confirmed by Tier‑1 sources in this card.

Security and incidents

  • Security audit: the docs have a separate Security Audit section (links inside).
  • Incidents: —.

Project status and timeline

  • Current status: the documentation and website are available; the BEE token exists in the claimed networks.

AI component of the project

  • What is real AI here? In the Tier‑1 docs the project is claimed as “AI‑powered”, but it is not disclosed what exactly the AI does and where it runs (model/metrics/architecture are not described).
  • What is truly onchain? The BEE token on Base/BSC is confirmed by addresses; other onchain components require separate recording of addresses.
  • Why is a token needed? Per the docs: a utility and governance token, “powering product incentives, protocol governance, ecosystem collaboration”.
  • Red flags (based on the information found): the AI part is described at the level of the marketing label “AI‑powered” without artifacts (AI_1..AI_4 are not confirmed).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity low 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): DAOBase is claimed as an “AI‑powered DAO launcher and aggregator”.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): this is a Tier‑1 declaration of an AI direction, but without proof of a working AI component.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): it is not described what exactly the AI does (specific functions/modules/inputs‑outputs).
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): there is “AI‑powered”, but without specifics.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo of an AI function was found.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): the docs are a description, without a demonstration of an AI module.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): there are no metrics/benchmarks.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a technical description of the AI architecture is absent.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): there is no architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base (also BSC)
  • Addresses/identifiers: BEE (Base) 0x1f1bA52c445755C92caFFe7B608B87dCDAf9d825
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee ; https://basescan.org/token/0x1f1bA52c445755C92caFFe7B608B87dCDAf9d825
  • Why sufficient / why not (one line): the docs provide the contract address, and the explorer allows verifying it.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: the docs claim launch/governance/reputation tools, but without a link to specific contract addresses in this card.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): without addresses/contracts we set 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the aggregator/analytics can work offchain; onchain criticality is not proven.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase
  • Why sufficient / why not (one line): onchain is useful, but “breaks down without the blockchain” is not shown.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): DAOBase has a token, BEE (Base/BSC).
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee
  • Why sufficient / why not (one line): the token docs list the networks/addresses/parameters.
  • 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): the token docs contain no explicit statement that the service is paid for strictly in BEE (as a tariff).
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee
  • Why sufficient / why not (one line): the role is described as incentives/governance, without tariffs.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the token is claimed as a “product incentives” instrument.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee
  • Why sufficient / why not (one line): incentives are stated explicitly (albeit without details of the mechanics).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): the token is claimed as a governance token; changes to the unlock logic go through proposal‑based governance.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee
  • Why sufficient / why not (one line): governance is mentioned directly, including the rules for changing the distribution.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): no strict proof of the irreplaceability of BEE (why it cannot be implemented via a subscription/USDC) was found.
  • Evidence: Tier‑1 — https://docs.daobase.ai/daobase/community/about-daobase-token-bee
  • Why sufficient / why not (one line): the token’s role is described in general terms; the “only this way” argument is absent.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.daobase.ai/daobase positioning of DAOBase as an “AI‑powered DAO launcher and aggregator” and the list of capabilities
Tier‑1 https://docs.daobase.ai/daobase/community/about-daobase-token-bee total supply/decimals/networks and BEE contract addresses + the unlock logic
Tier‑1 https://basescan.org/token/0x1f1bA52c445755C92caFFe7B608B87dCDAf9d825 onchain page of the BEE token (Base)
Tier‑1 https://docs.daobase.ai/daobase/smart-contract/security-audit the existence of a Security Audit section
Tier‑2 https://coinmarketcap.com/currencies/daobase/ reference profile

No comments to display

Back to top