Skip to main content

BilliCat

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

BilliCat — a Meme project on the BNB Smart Chain network, token (symbol: BCAT).

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 meme token and a brand around the “Billex ecosystem” (DEX/wallet/NFT market), claimed on the official website.
  • Who it’s for: users who want to use (or wait for) the products of the Billex ecosystem.
  • Why onchain/token: the BCAT token exists as a BEP‑20 asset; claims about the usefulness of the token within the ecosystem require verification against Tier‑1 artifacts (contracts/docs/application).

How it works (very briefly)

  1. The user does: interacts with the token and (if available) uses the ecosystem products.
  2. The system does: operations with the token happen onchain on the BNB Smart Chain network.
  3. The user gets: the BCAT token; the claimed ecosystem functions (DEX/wallet/NFT market) require verification per Tier‑1.
  4. Where the blockchain is: onchain — the token contract (BEP‑20) and transactions on the BNB Smart Chain network.
  5. Token role (if any): the website claims that BCAT “powers” the ecosystem functions; confirmation of the real necessity of the token in the protocol is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name BilliCat
Also known as (aliases) BCAT, Polymoon
Logo (logo) ../assets/512_polymoon_logo.png
Token symbol (ticker) BCAT
Category Meme
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 0x47a9B109Cfb8f89D16e8B34036150eE112572435
Token model (token_type) —
Max supply 100,000,000 BCAT
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) meme token + DeFi + NFT ecosystem
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

BilliCat (BCAT) is a token on the BNB Smart Chain network. The official website describes the “Billex ecosystem” (an exchange, a non‑custodial wallet, an NFT marketplace) and claims that BCAT is used as an internal “currency/utility engine” for the ecosystem functions. Within this card, these claims are recorded as Tier‑1 claims, but without confirmation of onchain mechanics (other than the fact of the token’s existence and its parameters in the explorer).

Features/modules

  • BCAT token: a BEP‑20 contract on BNB Smart Chain.
  • Billex ecosystem (claimed): an exchange, a wallet, an NFT marketplace, staking/DAO (requires verification against artifacts).

Typical scenarios

  • Scenario 1: the user interacts with BCAT → operations are reflected onchain.
  • Scenario 2: the user tries to use the claimed ecosystem products → a check of availability and of the corresponding onchain contracts is needed.

Getting started (wallet/network)

  • What you need: a wallet with BNB Smart Chain support.
  • Network/chain: BNB Smart Chain.
  • Fees: BNB Smart Chain network fees (gas) for operations with the token.

Architecture/tech (non‑AI)

  • Components: the token contract (BEP‑20); other ecosystem contracts/applications are not established per Tier‑1.
  • Participant roles: token holders and network users.
  • Where logic runs: onchain — token transfers/balances; the rest of the logic (if any) is not established.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility (claimed): on the official website, BCAT is described as a token “for operations/utilities” in the Billex ecosystem.
  • Issuance/burn: max total supply 100,000,000 BCAT (per the token page data in the explorer).
  • Security/incentive mechanisms: not established (there are no Tier‑1 artifacts of staking/slashing/other protocol mechanisms).
  • Distribution and token issuance schedule: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: for users — typical risks of interacting with tokens (contract risks, phishing, fake applications), as well as the risk of a mismatch between the claimed utility and the actual implementation.

Project status and timeline

  • Current status: the token exists on BNB Smart Chain mainnet; the status of the “ecosystem” is not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: the token’s onchain activity is observable in the explorer; usage in the ecosystem products requires additional Tier‑1 artifacts.

AI component of the project

  • What is real AI here? per Tier‑1 sources, no confirmation of an AI component or AI intentions was found.
  • What is truly onchain? onchain — the BEP‑20 token on the BNB Smart Chain network (the token contract).
  • Why is a token needed? the website claims token utility in the ecosystem; confirmation of the protocol necessity of the token is not established.
  • Red flags (based on the information found): “utility/ecosystem” without verifiable onchain contracts and without an accessible application; mixing marketing promises with Tier‑1 evidence.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality no Tier‑1 data 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 claim of AI intentions was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without Tier‑1 mentions of AI we set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI features of the product are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of what exactly the AI does.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): AI demos/examples are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without an AI feature and without a Tier‑1 demo we set 0.
  • 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): AI quality metrics are not applicable (the AI feature is not established).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI architecture is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 tech description of the AI component.
  • 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 0x47a9B109Cfb8f89D16e8B34036150eE112572435
  • Evidence: Tier‑1 — https://bscscan.com/token/0x47a9B109Cfb8f89D16e8B34036150eE112572435
  • Why sufficient / why not (one line): The presence of a token contract in the explorer confirms the onchain component.
  • 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): In Tier‑1 sources, no confirmation of onchain 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: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality for the claimed products.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, BCAT.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x47a9B109Cfb8f89D16e8B34036150eE112572435
  • Why sufficient / why not (one line): The Tier‑1 explorer confirms the existence of the token.
  • 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): Not established (there are no Tier‑1 tech docs/contracts where the token is mandatory as payment).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): We do not consider website claims without confirmed onchain mechanics sufficient.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Not established (there is no Tier‑1 proof of staking/slashing as protocol mechanics).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without specific onchain contracts/docs we set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Not established (there is no Tier‑1 description of governance mechanics).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a provable governance process we set 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): Not established (a Tier‑1 analysis of alternatives is needed).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 comparison of replaceability we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bscscan.com/token/0x47a9B109Cfb8f89D16e8B34036150eE112572435 Onchain fact: the BilliCat (BCAT) token, the token contract; max total supply 100,000,000 BCAT.
Tier‑1 https://billicatcoin.com/ Claims about the Billex ecosystem and the role of the token (DEX/wallet/NFT market, staking/DAO — as a description).
Tier‑1 — No Tier‑1 source for claim “AI component/AI intentions” was found.

No comments to display

Back to top