Skip to main content

PaLM AI

PaLM AI — 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).

PaLM AI — an AI/Assistants project: a suite of multi‑platform AI bots/assistants (Telegram/X/Discord/etc.) + an onchain token PALM on Ethereum with a tax model and “revenue share” (per the docs).

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: AI assistants/bot solutions for various platforms (including custom/whitelabel ones for businesses) + a set of “holder utilities”.
  • Who it’s for: users (chatbots/assistants) and businesses/projects (custom bots/integrations).
  • Why onchain/token: the PALM token is a funding mechanism (3% tax) and a mechanism for distributing “revenue share” to holders (per the docs); the AI logic runs offchain.
  • What you can actually touch (Tier‑1): a description of the “free‑to‑use” assistants and deployment examples/screenshots in the GitBook docs (see links_* → App / Demo).

How it works (very briefly)

  1. The user does: uses a bot/assistant on the chosen platform or orders a custom solution.
  2. The system does: performs AI functions (dialogue/code/integrations, etc. — per the project’s description) and handles deployment/configuration via automated pipelines (per the docs).
  3. The user gets: an AI assistant and/or a custom bot service.
  4. Where the blockchain is: onchain — the PALM token and its tax/liquidity logic; “revenue share” is distributed to holders (per the description in the docs).
  5. Token role (if any): holding PALM is used for access to utilities and participation in revenue share; there is also LP‑staking (per the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name PaLM AI
Also known as (aliases) $PALM; PaLMAI
Logo (logo) ../assets/171_palm-ai_logo.png
Token symbol (ticker) PALM
Category AI/Assistants | AI/SaaS
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xf1df7305E4BAB3885caB5B1e4dFC338452a67891
Token model (token_type) utility (fee-mechanism)
Max supply 100,000,000 PALM
Issuance fixed (the docs describe a burn of 22.5% of the supply)
Tokenomics (tokenomics, brief) 3% buy/sell tax (1% dev, 1% marketing, 1% staking/liq — per the docs); 20% burn at launch + additional burn
Governance — (the docs state “there is no DAO”)
Admins/keys the token is Ownable; there are functions to manage trading/fee/maxTx/maxWallet (see the contract)
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) cross-platform AI assistants/bots
Use‑case (use_case) AI bots for users + businesses
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

PaLM AI describes itself as a project at the intersection of AI technologies and blockchain: multi‑platform AI bots/assistants (including free‑to‑use ones as a showcase) plus custom/whitelabel solutions for businesses and projects. The documentation emphasizes “multiplatform integration” and automated deployment/management pipelines (including docker‑management) for custom solutions.

The onchain part is represented by the PALM token on Ethereum with a tax model, LP‑staking and a claimed revenue share program for holders.

Features/modules

  • AI assistants and bots: on various platforms; “conversation, coding, image gen” are mentioned (in the project’s descriptions).
  • Custom/whitelabel solutions: configuration and deployment via automated pipelines (per the docs).
  • Revenue Share: per the docs, 50% of the revenue from the business model is distributed to holders in ETH “at unannounced intervals”.
  • LP‑staking: staking of LP tokens for rewards in PALM (per the docs).
  • Holder utilities: some features are available only to PALM holders (per the docs).

Typical scenarios

  • Scenario 1 (user): uses an AI bot on Telegram/another platform → receives answers/help.
  • Scenario 2 (business): orders a custom bot → receives a whitelabel solution and deployment.
  • Scenario 3 (holder): holds PALM → gets access to utilities and participates in revenue share/LP‑staking.

Getting started (wallet/network)

  • What you need: for the token/onchain part — an EVM wallet; for the AI bots — the corresponding platform (Telegram, etc.).
  • Network/chain: Ethereum (PALM).
  • Fees: Ethereum gas for operations with PALM; 3% buy/sell tax per the tokenomics (per the docs).

Architecture/tech (non‑AI)

  • Components: offchain AI services/bot infrastructure + the onchain PALM token (ERC‑20) with tax/liq logic.
  • Participant roles: bot users, clients of custom solutions, token holders, the team.
  • Where logic runs: the AI part — offchain; tokenomics and trading/tax mechanics — onchain (Ethereum).
  • Dependencies: Telegram/other platforms, Ethereum and DEX liquidity.

Token/economics (expanded, no forecasts)

  • Token utility: the docs claim holder utilities and participation in revenue share; also LP‑staking.
  • Protocol necessity drivers: the AI bots can be used without the token; the token is needed for the onchain economy (tax, utilities, staking, revenue share).
  • Who pays fees: traders/token holders; per the docs there is a 3% buy/sell tax.
  • Where fees go: per the docs: 1% dev, 1% marketing, 1% staking/liq; the contract contains addresses for the fee recipient/marketing.
  • Issuance/burn: total supply 100M; the docs claim a 20% burn at launch + additional burn up to 22.5% of the total.
  • Security/incentive mechanisms: LP‑staking (per the docs) + the tax model; the contract has functions to manage trading/fees/limits (this is a centralization risk if ownership is not renounced).
  • Distribution and token issuance schedule: the docs indicate 75% for liquidity, 5% reserved, 22.5% burned (see Tokenomics).
  • Treasury: revenue share is distributed in ETH to holders per the business model (per the docs; specific addresses/contracts are not described).

Governance

  • Who makes decisions: the team/product operator (the docs explicitly state that there is no DAO).
  • How protocol parameters change: via updates of the offchain service/bots and via the token’s admin parameters (fees/limits/trading) within ownership (see the contract).
  • Where decisions are discussed/made: official channels (see links_*: X/Telegram/Website/Docs).
  • Keys/multisig: not disclosed in Tier‑1 sources; the token contract contains admin functions (a centralization risk while ownership is retained).

Security and incidents

  • Audits: — (no public Tier‑1 audit reports were found in the reviewed sources).
  • Bug bounty: —.
  • Incidents: — (no public postmortems/incidents were found in the reviewed sources).
  • Threat model: dependence of the AI service on offchain infrastructure; the risk of the token’s admin functions (fees/limits/trading) in case of compromise/abuse of ownership; risks of the tax model/liquidity.

Project status and timeline

  • Current status: active (AI bots/assistants + the PALM token on Ethereum mainnet; see links_*).
  • Key releases/milestones: —.
  • Roadmap: https://palmai.tech/roadmap

Ecosystem/integrations

  • Integrations: Telegram/multi‑platform bots (offchain) + Ethereum (token, DEX liquidity).
  • Partners: — (not listed in the reviewed Tier‑1 sources).
  • Where it’s actually used: as a suite of AI bots/assistants and custom solutions (see Docs/Website in links_*).

AI component of the project

  • What is real AI here? AI assistants/bot solutions for various platforms and use cases (per the GitBook and the contract metadata).
  • What is truly onchain? the PALM ERC‑20 token with buy/sell tax and admin functions; trading infrastructure/DEX.
  • Why is a token needed? funding/utility: a trading tax for dev/marketing/liq + holder utilities and a claimed revenue share for holders.
  • Red flags (based on the information found): token‑washing (the AI product can exist without the token); key risk — ownership/admin functions of the token (fees/limits/trading), needs to be monitored onchain.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity low 0
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 modules are described as existing/operational (bots/assistants), so the intent flag is not used.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): the docs describe products/execution, not just plans.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the project builds multi‑platform AI assistants/bots and custom solutions for users/businesses.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals ; https://docs.palmai.tech/
  • Why sufficient / why not (one line): the Tier‑1 documentation describes AI product functionality.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the contract and the docs list public channels/a bot (Telegram bot) and descriptions of showcase “free-to-use” assistants.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf1df7305E4BAB3885caB5B1e4dFC338452a67891#code ; https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): this indicates the existence of a product/demo beyond promises.
  • 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.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): quality metrics/benchmarks are not published.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a description of “Google AI tools + in-house algorithms” without specifics on models/versions/architecture.
  • Evidence: Tier‑1 — https://docs.palmai.tech/
  • Why sufficient / why not (one line): there are not enough technical details for a verifiable description.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: PALM token: 0xf1df7305E4BAB3885caB5B1e4dFC338452a67891
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf1df7305E4BAB3885caB5B1e4dFC338452a67891
  • Why sufficient / why not (one line): the token contract and the max total supply of 100,000,000 are confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: in the confirmed sources, specific onchain modules other than the token are not provided with addresses/contracts.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): “on-chain utilities” are described at the level of an idea/plan without addresses/contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the AI bots/assistants can function as a Web2 service; the blockchain is not critical for the AI functions.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): onchain acts as a funding/utility model, not as a technical necessity for AI.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, PALM.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xf1df7305E4BAB3885caB5B1e4dFC338452a67891 ; https://docs.palmai.tech/whitepaper/tokenomics
  • Why sufficient / why not (one line): the token and its supply are confirmed by the explorer and the docs.
  • 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): Tier‑1 does not describe mandatory payment for the AI service in PALM (rather — utilities and revenue distribution models).
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): the “payment token” function is not confirmed.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): there is LP‑staking (rewards in PALM) and “revenue share” for holders (in ETH).
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals ; https://docs.palmai.tech/whitepaper/tokenomics
  • Why sufficient / why not (one line): the docs describe staking and a revenue distribution program for holders.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via the token is not described; the docs state “there is no DAO”.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): the absence of a DAO/voting ⇒ flag 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the AI product can be monetized without the token (subscriptions/fiat); the token model is the chosen funding/utility method.
  • Evidence: Tier‑1 — https://docs.palmai.tech/whitepaper/fundamentals
  • Why sufficient / why not (one line): the description of the business model (including a company for Web2 payments) makes the token not strictly necessary.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.palmai.tech/whitepaper/fundamentals Description of the AI product, execution/pipelines, revenue share and the absence of a DAO
Tier‑1 https://docs.palmai.tech/whitepaper/tokenomics Total supply 100M, 22.5% burn, 3% buy/sell tax and the tax distribution
Tier‑1 https://etherscan.io/token/0xf1df7305E4BAB3885caB5B1e4dFC338452a67891 The PALM contract, max total supply 100,000,000, parameters and admin functions

No comments to display

Back to top