Skip to main content

Griffain

Griffain (—) — 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).

Griffain — an AI/Agents product (an agent network + an “agent engine” for actions, including onchain), a token on the Solana network (mint — see the passport; the ticker is not confirmed by Tier‑1 sources).

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 where the user creates and manages a “personal agent” and also uses “special agents”; the key idea is that agents with a wallet can turn intent into onchain actions.
  • Who it’s for: users who want to delegate actions and automations (including onchain) to an agent and get access to the “agent network”.
  • Why onchain/token: the onchain part is the environment for executing actions via a wallet (signing and transactions); for the Griffain token, the mint address is confirmed in Tier‑1, but no Tier‑1 utility/necessity of the token was found.
  • What you can actually touch (Tier‑1): the Griffain documentation and the project’s public page.

How it works (very briefly)

  1. The user gets access (invite‑only) and creates a personal AI agent.
  2. The user creates an agent wallet and gives the application the right to sign and send transactions on their behalf (per the docs).
  3. The agent accepts requests and chooses actions from the available set (per the docs), including onchain actions.
  4. Where the blockchain is: signing and execution of actions via the wallet/transactions — onchain; the agent’s “brain” itself and orchestration — offchain.
  5. Token role: the existence of the token is confirmed by the mint address, but the token’s role in the product is not confirmed by Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Griffain
Also known as (aliases) Griffain Agent Engine; “The Agent Engine”
Logo (logo) ../assets/105_griffain_logo.png
Token symbol (ticker) —
Category AI/Agents
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) invite-only
Token (standard) SPL
Token contract KENJSUYLASHUMfHyy5o4Hp2FdNqZg1AsUPhfH2kYvEP
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) LLM agents + tool-based actions
Use‑case (use_case) agent wallet for on-chain actions
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Griffain describes itself as an “Agent Engine” and emphasizes that it is hard for AI agents to “act” on the regular internet: every website has its own accounts and APIs, and for actions involving money an agent needs a payment layer. As the “body” for an agent, the project proposes using a crypto wallet (private key → transaction signing), because onchain actions have a single interface (“sign and send a transaction”).

On the product side, Griffain (per the docs):

  • access is currently invite‑only and requires purchasing an access pass;
  • after gaining access, you can create a wallet for an AI agent;
  • there are personal agents (the user manages instructions/memory) and special agents (specialized agents provided by Griffain).

Features/modules

  • Access pass / invite‑only: restricted access to the product.
  • Agent wallet management: creating/managing the agent’s wallet, the ability to sign transactions.
  • Personal Agents: configuration of instructions and memory; in the future — delegation of tasks to special agents (per the docs).
  • Special Agents: a set of specialized agents for individual tasks (per the docs: examples are listed).
  • Actions / toolset: agents act via an explicitly defined set of actions; hallucination risks when going beyond the capabilities are noted.

Typical scenarios

  • Scenario 1 (agent+wallet): a user formulates a task → the agent chooses an action → signs/sends a transaction → the result is onchain.
  • Scenario 2 (delegation): a personal agent receives a complex request → delegates it to a special agent (per the roadmap/description of the approach) → collects data/makes a decision → performs the action.
  • Scenario 3 (search+action): the agent searches for relevant information via the available actions → then performs an onchain action.

Getting started (wallet/network)

  • What you need: an access pass (invite‑only), a Griffain account, then creation of an agent wallet.
  • Network/chain: Tier‑1 indicates the Solana ecosystem (Solana explorer/solscan link from the project card).
  • Fees: onchain network fees for transactions; payments for access (access pass) and pricing are possible (the docs contain a link to a pricing page, but without Tier‑1 details).

Architecture/tech (non‑AI)

  • Components: the Griffain web application, the “agent” layer (LLM + actions), the agent’s wallet (private key + signing), interaction with onchain via transactions.
  • Participant roles: the user, personal agent, special agents, the blockchain network (validators/nodes), external data sources (if actions use them).
  • Where logic runs: reasoning/orchestration — offchain; the final “sign+send” actions and their effect — onchain.
  • Dependencies: RPC access to the network; wallet/signing; security of key storage (critical).

Token/economics (expanded, no forecasts)

  • Token utility: no Tier‑1 utility of the project’s token (payment/staking/governance) was found; only the mint address is confirmed.
  • Protocol necessity drivers: —
  • Who pays fees: users pay network fees for onchain actions.
  • Where fees go: network fees — to validators/the network (typically); on the Griffain service’s internal fees — no Tier‑1 data.
  • Issuance/burn/distribution: — (no Tier‑1 found).
  • Incentive mechanisms: —.
  • Treasury: —.

Governance

  • Who makes decisions: — (no Tier‑1 found).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: — (no Tier‑1 found in links_*).
  • Bug bounty: —.
  • Incidents: — (no Tier‑1 postmortems found).
  • Threat model (brief): compromise of the agent wallet key; erroneous/hallucinating agent actions; risks of delegating signing rights.

Project status and timeline

  • Current status: invite‑only; the product is “booting up the network…” on the main page.
  • Key milestones: —.
  • Roadmap: — (no Tier‑1 roadmap page in links_*).

Ecosystem/integrations

  • Integrations: onchain actions via the wallet; communication channels (Telegram) per links_*; the “agent network” and a set of special agents.
  • Partners: —.
  • Where it’s actually used: no specific Tier‑1 integrations/cases recorded.

AI component of the project

  • What is real AI here? LLM‑based “agents” that choose actions from a set of capabilities; personal agents are managed by the user (instructions/memory), special agents are specialized for tasks.
  • What is truly onchain? the agent wallet signs and sends transactions; the effects of actions take place on the blockchain.
  • Why is a token needed? the Tier‑1 role of the project’s token (beyond the existence of the mint) is not confirmed.
  • Red flags (based on the information found): AI‑washing — medium (no technical description/metrics); onchain‑washing — medium (onchain matters as the environment for actions, but there are no own protocol contracts); token‑washing — high (no Tier‑1 token utility). What to double‑check: tokenomics/utility, the access model and pricing, key security and signing permissions.

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 no Tier‑1 data on utility 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): AI agents are the current functionality, not only intent.
  • Evidence: Tier‑1 — https://griffain.com/docs, https://griffain.com/blog/the-agent-engine
  • Why sufficient / why not (one line): there is a description of working agents/architecture, so intent‑only does not apply.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the agent accepts requests, chooses an action from the list of capabilities, can perform onchain actions.
  • Evidence: Tier‑1 — https://griffain.com/docs, https://griffain.com/blog/the-agent-engine
  • Why sufficient / why not (one line): Tier‑1 describes the agent’s behavior and capabilities at the product level.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there are public docs describing the scenarios (access pass, wallets, personal/special agents) and a blog description of the architecture.
  • Evidence: Tier‑1 — https://griffain.com/docs, https://griffain.com/blog/the-agent-engine
  • Why sufficient / why not (one line): the product is described sufficiently to confirm “there is agent functionality” (even if access is restricted).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): no Tier‑1 quality metrics/benchmarks were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is a high-level description of an “agent of agents”, but no technical description of models/versions/the inference stack.
  • Evidence: Tier‑1 — https://griffain.com/blog/the-agent-engine
  • Why sufficient / why not (one line): insufficient for technical verification of the AI component.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: mint KENJSUYLASHUMfHyy5o4Hp2FdNqZg1AsUPhfH2kYvEP
  • Evidence: Tier‑1 — https://explorer.solana.com/address/KENJSUYLASHUMfHyy5o4Hp2FdNqZg1AsUPhfH2kYvEP?cluster=mainnet
  • Why sufficient / why not (one line): there is a specific onchain identifier (mint) in the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: no Tier‑1 own protocol contracts/programs of Griffain (other than the token) are confirmed.
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): the product and onchain actions via the wallet are described, but not a Griffain protocol onchain.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without onchain, the single “sign+send” interface and the onchain effect disappear, but the AI agent as a product could live in web2 automations; criticality is not proven by Tier‑1.
  • Evidence: Tier‑1 — https://griffain.com/blog/the-agent-engine
  • Why sufficient / why not (one line): Tier‑1 argues convenience/universality rather than strict impossibility without a blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token (the mint address is listed in links_*).
  • Evidence: Tier‑1 — https://explorer.solana.com/address/KENJSUYLASHUMfHyy5o4Hp2FdNqZg1AsUPhfH2kYvEP?cluster=mainnet
  • Why sufficient / why not (one line): the onchain identifier 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): no Tier‑1 confirmation that the token is used to pay for the service was found.
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): the docs talk about the access pass/access, but do not describe a token payment.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): no Tier‑1 data on staking/incentives/collateral via the token was found.
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): there is no description.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): no Tier‑1 description of a governance role of the token was found.
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): there is no description.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability/irreplaceability of the token was not assessed due to the absence of Tier‑1 utility.
  • Evidence: Tier‑1 — https://griffain.com/docs
  • Why sufficient / why not (one line): insufficient data.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://griffain.com/docs invite‑only access, wallet management, personal/special agents, the ability to perform onchain actions
Tier‑1 https://griffain.com/docs what you can touch: public documentation and the described usage scenarios
Tier‑1 https://griffain.com/blog/the-agent-engine explanation of the motivation “wallets give agents a body”, high‑level architecture of the agent engine
Tier‑1 https://explorer.solana.com/address/KENJSUYLASHUMfHyy5o4Hp2FdNqZg1AsUPhfH2kYvEP?cluster=mainnet confirmation of the token’s mint address on Solana
Tier‑1 — No Tier‑1 source for claim “tokenomics/token utility (payment/staking/governance)” was found.

No comments to display

Back to top