PaladinAI
PaladinAI — 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).
PaladinAI — an AI/Other project on the Ethereum network, token (symbol: PALAI).
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: per the Tier‑1 whitepaper — a DeFi product/“intelligence layer” with a real‑time AI firewall and an “autonomous engine” for swap execution/routing.
- Who it’s for: DeFi users who value execution security/automation (per the Tier‑1 whitepaper).
- Why onchain/token: onchain records issuance and circulation of the PALAI token; the Tier‑1 whitepaper records supply and tax, but token utility in the form of payment/staking/governance is not disclosed as mandatory.
How it works (very briefly)
- The user does: uses a wallet and sends/receives the token.
- The system does: processes token transactions on the Ethereum network.
- The user gets: a confirmed transaction and a balance change.
- Where the blockchain is: token issuance/accounting and transactions take place onchain (Ethereum).
- Token role (if any): the token exists; the Tier‑1 whitepaper records supply and tax, but the specific mechanics of token necessity in the product require clarification.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | PaladinAI |
| Also known as (aliases) | — |
| Logo (logo) | — |
| Token symbol (ticker) | PALAI |
| Category | AI/Other |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2 |
| Token model (token_type) | utility (treasury funding; tax) |
| Max supply | 100 000 000 PALAI |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Total supply 100 000 000; tax 5/5 (Tier‑1 whitepaper). |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI firewall + autonomous engine |
| Use‑case (use_case) | AI-assisted DeFi swap execution/protection |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.paladinai.xyz/ |
| Docs | https://whitepaper.paladinai.xyz |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://whitepaper.paladinai.xyz/ |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2 |
| X | https://twitter.com/PaladinAIETH |
| Discord | — |
| Telegram | https://t.me/PaladinAI |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/paladinai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/paladinai/ |
General project overview
PaladinAI is a project with a token on the Ethereum network and a Tier‑1 whitepaper. In the whitepaper, the project describes an “intelligence layer”, a real‑time AI firewall and an autonomous engine for swap execution/routing/protection. Onchain artifact: the token contract on Ethereum; Tier‑1 technical details/AI quality metrics are not presented.
Features/modules
- The token on the Ethereum network (the onchain address is available via the explorer).
- Public project materials (Website/Whitepaper).
Typical scenarios
- Scenario 1: a user sends/receives the token → receives a confirmed transaction on Ethereum.
Getting started (wallet/network)
- What you need: an EVM wallet.
- Network/chain: Ethereum.
- Fees: Ethereum network fees (gas) for onchain operations.
Architecture/tech (non‑AI)
- Components: the token (ERC‑20) on the Ethereum network; project materials (Website/Whitepaper).
- Participant roles: users.
- Where logic runs: operations with the token are processed onchain (Ethereum).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not disclosed as a mandatory product mechanic per Tier‑1 sources (other than supply/tax parameters and “use of treasury”).
- Protocol necessity drivers: not established per Tier‑1 sources.
- Who pays fees: users pay Ethereum network fees for transactions.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: —.
- Key releases/milestones: —.
- Roadmap: not found (links_* has
—).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? The Tier‑1 whitepaper claims a real‑time AI firewall and an autonomous engine (purpose: security/automation of swap execution).
- What is truly onchain? Onchain records token issuance/circulation on the Ethereum network; the token address is available via the explorer.
- Why is a token needed? Tier‑1 records supply/tax and “use of treasury”, but the utility role of the token in the protocol (payment/staking/governance) is not established.
- Red flags (based on the information found): an AI label without Tier‑1 artifacts; unestablished token utility.
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 | 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): A Tier‑1 declaration of AI intent (roadmap) is not established in a separate document.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): The Tier‑1 links contain no separate roadmap/roadmap section; there are only descriptions in the whitepaper.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The Tier‑1 whitepaper claims a real‑time AI firewall and an autonomous engine for protection/automation of swap execution.
- Evidence: Tier‑1 — https://whitepaper.paladinai.xyz/
- Why sufficient / why not (one line): Tier‑1 states the purpose of the AI part (without metrics and a tech description).
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): Demos/examples of the AI component in operation are not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmed AI component, so an AI demo is not applicable.
- 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: an AI component 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 an AI component is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no confirmed AI component.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum.
- Addresses/identifiers: token contract 0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2.
- Evidence: Tier‑1 — https://etherscan.io/token/0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2
- Why sufficient / why not (one line): There is an onchain artifact (the token address) in a public explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established per Tier‑1 sources (other than the existence of the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no Tier‑1 artifacts of useful onchain logic other than the token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established per Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 formulation that passes the “replace the blockchain” test.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The token exists on the Ethereum network.
- Evidence: Tier‑1 — https://etherscan.io/token/0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2
- Why sufficient / why not (one line): The existence of the token is confirmed by an onchain address in the explorer.
- 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): It is not established that the token is used as payment for the service.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of the token’s role as payment was found.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): It is not established that the token is used in mechanisms of incentives/collateral/penalties.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of token incentives was found.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): It is not established that the token is used in governance.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 confirmation of token governance was found.
- 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 Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 justification of the replaceability/irreplaceability of the token.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.paladinai.xyz/ | Official project website (navigation to Tier‑1 materials). |
| Tier‑1 | https://whitepaper.paladinai.xyz/ | Project whitepaper (Tier‑1 material): description of AI firewall / autonomous engine. |
| Tier‑1 | https://whitepaper.paladinai.xyz/paladin-ai/usdpalai | Tier‑1 tokenomics: ticker $PALAI, total supply 100 000 000, tax 5/5, use of treasury. |
| Tier‑1 | https://etherscan.io/token/0x3cb48aeb3d1abadc23d2d8a6894b3a68338381c2 | Onchain: token contract on the Ethereum network (the address is confirmed in the explorer). |
| Tier‑1 | — | A Tier‑1 demo/accessible product surface (App/Demo) was not found in the current sources. |
| Tier‑1 | — | No Tier‑1 description of token utility in the protocol (payment/staking/governance) was found. |
No comments to display
No comments to display