Skip to main content

FluxBot

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

FluxBot — an AI/Agents \| DeFi project on the Solana network, token (symbol: FLUXB).

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 Telegram bot/interface for trading and operations on the Solana network (buy/sell, balances, transfers).
  • Who it’s for: users who want to trade and perform basic onchain operations via a Telegram UI.
  • Why onchain/token: onchain — execution of swap/transfer and accounting; the FLUXB token is described in the docs (supply/tax/reflections).
  • What you can actually touch (Tier‑1): the Telegram bot @fluxbeam_bot + AI Assistant commands (for example “Buy 5 USD of …”).

How it works (very briefly)

  1. The user does: sends commands in the Telegram bot (including “conversational” AI Assistant commands).
  2. The system does: executes onchain operations on Solana (buying/selling tokens, transfers, balance checks) and shows the result in the Telegram UI.
  3. The user gets: the executed onchain operation and its status/result.
  4. Where the blockchain is: the Solana network.
  5. Token role: FLUXB is described as a token with a supply and a tax/reflections; its role as a “mandatory access token” for the bot is not established per the available sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name FluxBot
Also known as (aliases) FLUXB, FluxBeam
Logo (logo) ../assets/565_fluxbot_logo.png
Token symbol (ticker) FLUXB
Category AI/Agents | DeFi
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) SPL
Token contract FLUXBmPhT3Fd1EDVFdg46YREqHBeNypn1h4EbnTzWERX
Token model (token_type) —
Max supply 500,000,000 FLUXB (total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Tax 3%: 50% holders, 25% LP, 25% team/ops (per the docs).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI assistant for trading/translation teams
Use‑case (use_case) Telegram bot for on-chain operations (Solana)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

FluxBot is described in the Tier‑1 documentation as a Telegram UI for trading and basic onchain operations on the Solana network. Separately, an “AI Assistant” layer is claimed, which allows sending “conversational” commands (for example, “Buy 5 USD of …”, “Swap 1 SOL to FLUXB”, “What is my SOL balance”) and getting the supported operations executed.

The documentation also has a separate page about the FLUXB token (mint address, supply, tax/reflections and distribution).

Features/modules

  • Telegram UI for trading/operations: buy/sell, balances, transfers.
  • AI Assistant: “natural language” commands for the supported operations (per the docs).
  • FLUXB token: supply/tax/reflections (per the docs).

Typical scenarios

  • Scenario 1: a user writes “Buy 5 USD of …” → the bot executes the token purchase and shows the result.
  • Scenario 2: a user writes “Transfer 1 SOL to …” → the bot forms and sends an onchain transfer.

Getting started (wallet/network)

  • What you need: Telegram + a deposit/balance on the Solana network (per the docs, “make your first deposit”).
  • Network/chain: Solana mainnet.
  • Fees: Solana network fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: the Telegram bot (UI/logic), Solana onchain infrastructure and tokens; offchain command execution and transaction sending.
  • Participant roles: users of the bot.
  • Where logic runs: the interface/command layer — offchain; execution of operations and accounting — onchain (Solana).
  • Dependencies: Solana RPC/infrastructure; Telegram.

Token/economics (expanded, no forecasts)

  • Token utility: the docs describe reflections (3% tax) and the distribution of reflections/fees.
  • Who pays fees: users pay Solana network fees for transactions.
  • Issuance/burn: total supply 500,000,000 FLUXB (per the docs).
  • Incentive mechanisms: reflections and distribution of part of the service fees to holders (per the docs).

Governance

  • Who makes decisions: — (not established per the available sources).
  • How protocol parameters change: — (not established per the available sources).
  • Where decisions are discussed/made: — (not established per the available sources).
  • Keys/multisig: — (not established per the available sources).

Security and incidents

  • Audits: — (not found).
  • Bug bounty: — (not found).
  • Incidents: — (not established).
  • Threat model: custody/key risks (the bot), DEX/swap route risks, token risks; details not established.

Project status and timeline

  • Current status: mainnet
  • Key releases/milestones: — (not found per the available sources)
  • Roadmap: — (not found per the available sources)

Ecosystem/integrations

  • Integrations: Telegram, Solana ecosystem.
  • Partners: — (not established)
  • Where it’s actually used: — (not established)

AI component of the project

  • What is real AI here? The documentation describes an “AI Assistant” that accepts free‑form commands and performs the supported actions (buy/sell, balances, transfers).
  • What is truly onchain? swap/transfer operations and balance accounting on the Solana network; the FLUXB token mint is given in the docs.
  • Why is a token needed? The docs describe the supply and reflections (3% tax and distribution); whether the token is mandatory for access to the bot is not established per the available sources.
  • Red flags (based on the information found): custody/key security in the Telegram bot; absence of public audits per the available sources.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is described as functionality (AI Assistant), not only as intent/roadmap.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/basic-tutorials/how-to-use-our-ai-assistant
  • Why sufficient / why not (one line): given the description of the AI Assistant functions, we use AI_1/AI_2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the AI Assistant accepts “conversational” commands and launches the supported operations (buy/sell, balances, transfers).
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/basic-tutorials/how-to-use-our-ai-assistant
  • Why sufficient / why not (one line): the Tier‑1 docs list example commands and the list of supported actions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the FluxBot Telegram bot is available, where the AI Assistant commands can be used.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/fluxbot/get-started ; https://t.me/fluxbeam_bot
  • Why sufficient / why not (one line): the Tier‑1 docs give a link to the bot and the “get started” steps.
  • 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 — https://docs.fluxbot.xyz/
  • Why sufficient / why not (one line): there are no quantitative quality metrics for the AI Assistant in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): no tech description/architecture of the AI Assistant was found per the available sources.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/
  • Why sufficient / why not (one line): the docs contain user‑level instructions without the architecture/versions of the model.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: the FLUXB token mint: FLUXBmPhT3Fd1EDVFdg46YREqHBeNypn1h4EbnTzWERX
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): the Tier‑1 docs directly give the mint address.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: execution of swap/transfer operations on the Solana network (via the Telegram UI) — it does not boil down to “token issuance”.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/basic-tutorials/how-to-use-our-ai-assistant
  • Why sufficient / why not (one line): the docs list buy/sell/transfer operations as supported actions.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality in terms of trustless/anti‑censorship was found (per the available sources).
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/
  • Why sufficient / why not (one line): without an explicit “replacement test” we set 0 (conservatively).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, FLUXB.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): the docs give the mint address and the parameters 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): per the available sources, no Tier‑1 confirmation was found that FLUXB is a mandatory payment token for the service.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): the docs describe the tax/reflections and the distribution of fees, but not “payment for the service with FLUXB”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the 3% tax and “reflections” are distributed to holders/LP/operational expenses; part of the service fees is distributed to holders.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): the docs describe the reflections scheme and the distribution.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): a governance role of the token is not established per the available sources.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): the docs contain no explicit description of governance via the token.
  • 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 the available sources.
  • Evidence: Tier‑1 — https://docs.fluxbot.xyz/faq/fluxb-token
  • Why sufficient / why not (one line): there is no Tier‑1 “replacement test”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.fluxbot.xyz/ Tier‑1 product documentation (FluxBot = Telegram UI for trading/operations).
Tier‑1 https://docs.fluxbot.xyz/basic-tutorials/how-to-use-our-ai-assistant AI Assistant: examples of “conversational” commands and the list of supported actions (buy/sell, balances, transfers).
Tier‑1 https://docs.fluxbot.xyz/fluxbot/get-started Link to the Telegram bot @fluxbeam_bot and the starting steps.
Tier‑1 https://docs.fluxbot.xyz/faq/fluxb-token FLUXB mint address + supply + tax/reflections and distribution.
Tier‑1 https://solscan.io/token/FLUXBmPhT3Fd1EDVFdg46YREqHBeNypn1h4EbnTzWERX Onchain explorer for the FLUXB token mint (Solana).
Tier‑2 https://www.coingecko.com/en/coins/fluxbot Profile (for reference; not Tier‑1).

No comments to display

Back to top