Quack AI
Quack AI (Q) — 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).
Quack AI — an AI/Other | Infra project/stack for AI automation of governance + onchain execution (Q402/x402), with the Q token (ERC‑20 / multi‑chain per the tokenomics).
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: an “AI Autonomy” stack for governance and action execution, with the Q402 (x402) protocol for gasless and policy‑aware onchain execution.
- Who it’s for: DAOs/protocols/teams that need governance automation and action execution; developers integrating Q402.
- Why onchain/token: onchain — to validate/log delegated execution and governance actions; the Q token — for governance/delegation and rewards (per the tokenomics).
- What you can actually touch (Tier‑1):
app.quackai.ai(airdrops / chat / governance entry points) and the open‑source Q402 repository with examples (examples/bsc-testnet).
How it works (very briefly)
- The user/DAO does: creates/filters a governance proposal or sets execution parameters (policy/limits).
- The system does: the AI layer (proposal engine + scoring + delegation) helps with preparation/evaluation; Q402 forms a “sign‑to‑pay / delegated execution” flow via an EIP‑712 witness + EIP‑7702 delegated execution.
- The user gets: a more automated governance cycle + the option of gasless onchain settlement (the facilitator sponsors gas).
- Where the blockchain is: delegated transactions/execution (receipts/logs) and delegation/accounting of actions are recorded onchain (per the docs).
- Token role: $Q is used for governance/delegating decisions to AI agents and for receiving rewards (per the tokenomics).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Quack AI |
| Also known as (aliases) | Q402 | x402 | $Q |
| Logo (logo) | ../assets/44_quack-ai_logo.svg |
| Token symbol (ticker) | Q |
| Category | AI/Other | Infra |
| 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 | 0xc07e1300dc138601fa6b0b59f8d0fa477e690589 |
| Token model (token_type) | utility (rewards + governance) |
| Max supply | 10,000,000,000 (10B) |
| Issuance | fixed cap |
| Tokenomics (tokenomics, brief) | TGE circulating ~16.16%; full unlock timeline 37 months |
| Governance | — |
| Admins/keys | owner + minter (per the contract code) |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | Backers are listed on the website (logos; the terms require precise verification) |
| AI component (ai_component) | AI governance intelligence + delegation scoring |
| Use‑case (use_case) | AI governance automation + gasless execution |
| DecAI Fit — AI thesis fit | 6/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 3 / token_score 2 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://quackai.ai/ |
| Docs | https://quackai.gitbook.io/docs |
| GitHub | https://github.com/quackai-labs |
| Releases / Changelog | — |
| Whitepaper | https://quackai.gitbook.io/docs/appendices/whitepaper-version |
| Roadmap | https://quackai.gitbook.io/docs/roadmap/futureplans |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xc07e1300dc138601fa6b0b59f8d0fa477e690589 |
| App / Demo | https://app.quackai.ai/ |
| X | https://twitter.com/QuackAI_AI |
| Discord | — |
| Telegram | https://t.me/quackai_Community |
| Medium | https://medium.com/@quackai |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/quack-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/quack-ai/ |
General project overview
Quack AI describes itself as an “AI Autonomy Stack”: a set of layers where AI models help prepare/evaluate governance decisions, while onchain execution is done via Q402 (a production implementation of x402) — sign‑to‑pay and delegated execution for EVM networks based on EIP‑712 (typed witness) and EIP‑7702 (delegated execution).
In practice this looks like a combination of:
- Governance intelligence (an AI proposal engine + scoring + delegation of votes to AI agents),
- Execution fabric (Q402: gasless settlement/execution of actions, where gas is paid by the facilitator),
- Dev stack (SDK/middleware/facilitator service + integration examples).
Features/modules
- Proposal Engine (AI, Tier‑1 docs): reading/parsing data, summarization, classification and filtering of proposals.
- Delegation & AI Scoring (AI, Tier‑1 docs): AI delegation and a scoring model; there is a “delegation contract” as onchain accounting of delegation.
- Q402 / x402 execution layer (Tier‑1 docs + GitHub): the gasless “approve → transfer” is replaced with a single‑signature flow; there is middleware and a facilitator service.
- Facilitator network (Tier‑1 docs): relay/gas sponsorship + receipts and an incentive model (reward in $Q).
- App (Tier‑1):
app.quackai.aias the public entry point to airdrop/chat/governance.
Typical scenarios
- Scenario 1 (governance automation): a DAO forms a proposal → the AI proposal engine summarizes/structures it → the system evaluates/ranks → the user votes themselves or delegates to an AI agent.
- Scenario 2 (gasless execution): a developer integrates Q402 → users authorize an action with a single signature → the facilitator performs onchain settlement and sponsors gas → a verifiable onchain audit trail remains.
- Scenario 3 (app flow): the user goes to
app.quackai.ai, checks the airdrop/uses the chat/proceeds to governance actions (within the available interface).
Getting started (wallet/network)
- What you need: an EVM wallet; for developers — the GitBook + the Q402 repository (SDK/middleware/facilitator) and an environment (env vars/RPC).
- Network/chain: the $Q token is multi‑chain (Ethereum + BNB Chain per the tokenomics); Q402 targets EVM networks with EIP‑7702 support (BNB Chain is marked as Active).
- Fees: onchain operations require gas; in the Q402 flow, gas can be sponsored by the facilitator (gasless for the user per the description).
Architecture/tech (non‑AI)
- Components: the $Q token contract (ERC‑20), a client SDK (signatures/headers), middleware (validation of “402 payment required”), a facilitator service (verify/settle), onchain execution (delegated execution), an audit/receipt layer.
- Participant roles: users/delegators, AI agents (decision agents), facilitator operators/relayers, integrating developers.
- Where logic runs: AI reasoning and decision preparation — offchain; critical actions/execution/accounting of delegation and receipts — onchain (EVM).
- Dependencies: EVM networks (BNB/Ethereum are claimed), RPC, the infrastructure of facilitator nodes/services.
Token/economics (expanded, no forecasts)
- Token utility: governance + delegating decisions to AI agents + access to AI tooling + rewards (per the tokenomics overview).
- Protocol necessity drivers: the tokenomics describes $Q as the ecosystem’s core governance/utility token; in the execution layer, the facilitator economy uses rewards in $Q (per the facilitator incentives description).
- Who pays fees: in ordinary transactions — the user/operator; in the Q402 flow, gas is paid by the facilitator (gasless for the user per the docs).
- Where fees go: — (not explicitly established per Tier‑1).
- Issuance/burn: maximum supply 10B (fixed cap per the tokenomics); burn mechanics were not extracted as Tier‑1 from the reviewed sources.
- Security/incentive mechanisms: incentives for facilitators and participants (rewards); compliance/policy checks before execution (per the docs).
- Distribution and token issuance schedule: token allocation by category + cliffs/vesting; TGE circulating ~16.16%, full unlock 37 months (Tier‑1).
- Treasury: there is a “Treasury” category in the tokenomics, but the specific onchain control/multisig was not extracted from the reviewed sources.
Governance
- Who makes decisions: governance processes are described as onchain governance (Tier‑1); the specific mechanism (Snapshot/Timelock/multisig) requires additional Tier‑1 confirmation.
- How protocol parameters change: via governance proposals and (in the vision) automated execution via Q402 (per the docs).
- Where decisions are discussed/made: the “Vote in Governance” entry point in the app (Tier‑1); links to a formal governance forum/snapshot were not extracted from the reviewed sources.
- Keys/multisig: — (not extracted as Tier‑1).
Security and incidents
- Audits: — (not found in the reviewed sources).
- Bug bounty: —.
- Incidents: — (not established).
- Threat model: risks in the facilitator implementation (sponsor keys, whitelist), correctness of policy checks, risks of the EIP‑7702 dependency (actual support by networks), centralized AI reasoning components.
Project status and timeline
- Current status: the public website/docs/repositories are active; the
app.quackai.aiapplication is available; Q402 is positioned as a production implementation of x402 (Tier‑1). - Key releases/milestones: the x402 BNB rollout is described as the “first production deployment” (Tier‑1 docs).
- Roadmap: Q1–Q4 2026 plans (Reasoning Proof MVP, Simulation Network, Treasury agents, Agent Constitution Framework and others) in the GitBook Future Plans (Tier‑1).
Ecosystem/integrations
- Integrations: Q402 is claimed to be compatible with standard ERC‑20 and EVM networks with EIP‑7702; dev integration via SDK/middleware/facilitator (Tier‑1).
- Partners: the website has a “Backed By Builders” block with logos; the exact terms/format of participation require re‑checking.
- Where it’s actually used: as a dev stack for gasless execution and governance automation (per the docs) + the public app entry.
AI component of the project
- What is real AI here? Tier‑1 describes an AI layer for governance: a proposal engine (parsing/summarization/classification) and AI scoring/delegation models that help evaluate proposals and delegate decisions to “decision agents”.
- What is truly onchain? Tier‑1 describes Q402 as onchain delegated execution (EIP‑712 + EIP‑7702) with receipts/an audit trail and onchain accounting of delegation (delegation contract).
- Why is a token needed? $Q is described as a governance/utility token for onchain governance, delegating decisions to AI agents, access to AI tooling and rewards; the reward model for facilitators also uses $Q.
- Red flags (based on the information found): dependence on the actual support of EIP‑7702 by networks (and on the correctness of the implementation), absence of confirmed audits/bug bounty in the reviewed sources; some of the AI promises about “bias‑free/verifiable intelligence” require separate verification with artifacts/metrics.
DecAI Fit component summary
- DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | high | 3 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
- Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
- Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): the AI layer parses/summarizes/classifies governance proposals and computes scoring/indices for delegating decisions to AI agents.
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/governance-intelligence/gap, https://quackai.gitbook.io/docs/governance-intelligence/fatigue
- Why sufficient / why not (one line): Tier‑1 describes specific AI functions (proposal engine + scoring framework), not just a marketing label.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): there is a public application,
app.quackai.ai, and the open‑source Q402 repository with a Quick Start and integration examples (includingexamples/bsc-testnet). - Evidence: Tier‑1 — https://app.quackai.ai/, https://github.com/quackai-labs/Q402
- Why sufficient / why not (one line): the existence of the app + a repository with examples/guides provides a reproducible artifact “to touch”.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/governance-intelligence/fatigue
- Why sufficient / why not (one line): Tier‑1 has no quantitative metrics of “AI decision quality” (accuracy/benchmarks) as a formal part of the protocol.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the documentation describes the Q402/x402 architecture (EIP‑712 witness + EIP‑7702 delegated execution, facilitator network) and dev flows (SDK/middleware/facilitator).
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/x402-execution-layer/proposalgeneration, https://github.com/quackai-labs/Q402, https://quackai.gitbook.io/docs/developer-suite/q402-sign-to-pay-protocol
- Why sufficient / why not (one line): there is a technical description of protocol‑level execution and of the repository/integration structure.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum mainnet (token explorer)
- Addresses/identifiers: token Q (ERC‑20): 0xc07e1300dc138601fa6b0b59f8d0fa477e690589
- Evidence: Tier‑1 — https://etherscan.io/token/0xc07e1300dc138601fa6b0b59f8d0fa477e690589
- Why sufficient / why not (one line): the onchain facts of the token/contract are verifiable in the explorer.
- Conflict note (if any): the tokenomics claims multi‑chain (including BNB) with the same address; within this card we record the contract via Etherscan.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: delegated execution of Q402 transactions (receipts/logs/audit trail) and onchain accounting of vote delegation (delegation contract).
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/x402-execution-layer/proposalgeneration, https://quackai.gitbook.io/docs/governance-intelligence/fatigue
- Why sufficient / why not (one line): Tier‑1 describes a specific onchain function beyond “there is a token”.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 1
- “Replace the blockchain” test: without onchain execution/receipts, the verifiability of “verifiable, auditable settlement” and the trustless execution of delegated actions are lost.
- Evidence: Tier‑1 — https://quackai.ai/q402, https://quackai.gitbook.io/docs/x402-execution-layer/proposalgeneration
- Why sufficient / why not (one line): the claimed value of Q402 is directly tied to onchain delegated execution and the audit trail.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, $Q (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0xc07e1300dc138601fa6b0b59f8d0fa477e690589
- Why sufficient / why not (one line): the onchain fact of the token/contract is verifiable.
- 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): we do not record here a direct Tier‑1 statement of “payment with the $Q token for the service” (there is a more general wording about access/utility).
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/tokenomics/overview
- Why sufficient / why not (one line): “enables access” does not equal explicit payment with the token; we remain conservative.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): $Q is used as a reward token for participants (community/airdrop) and for the facilitator economy (rewards for settlement/accuracy/compliance).
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/tokenomics/allocation, https://quackai.gitbook.io/docs/x402-execution-layer/aivoting, https://quackai.gitbook.io/docs/tokenomics/releaseschedule
- Why sufficient / why not (one line): Tier‑1 directly describes the distribution/rewards and the incentive model.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): $Q is described as a governance token that allows participation in onchain governance and delegating decisions to AI agents.
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/tokenomics/overview, https://app.quackai.ai/
- Why sufficient / why not (one line): the tokenomics overview explicitly calls $Q a governance/utility token and links it to governance/delegation.
- 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 (no strict comparison with alternatives).
- Evidence: Tier‑1 — https://quackai.gitbook.io/docs/tokenomics/overview
- Why sufficient / why not (one line): Tier‑1 describes the role of the token, but does not prove irreplaceability.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://quackai.gitbook.io/docs/tokenomics/overview | $Q as a governance/utility token (multi‑chain), max supply 10B, the link to governance/delegation/access and rewards. |
| Tier‑1 | https://etherscan.io/token/0xc07e1300dc138601fa6b0b59f8d0fa477e690589 | Onchain facts of the Q ERC‑20 token: contract and onchain parameters. |
| Tier‑1 | https://quackai.gitbook.io/docs/tokenomics/allocation | Token allocation by category (community/airdrop/treasury/team/investors/liquidity) + vesting schemes. |
| Tier‑1 | https://quackai.gitbook.io/docs/tokenomics/releaseschedule | Release schedule: TGE circulating ~16.16%, full unlock 37 months, cliffs. |
| Tier‑1 | https://quackai.gitbook.io/docs/roadmap/futureplans | Roadmap 2026: reasoning proof, simulation network, treasury agents, unified agent economy. |
| Tier‑1 | https://quackai.gitbook.io/docs/governance-intelligence/gap | Proposal engine: parsing/summarization/classification/filtering of governance proposals. |
| Tier‑1 | https://quackai.gitbook.io/docs/governance-intelligence/fatigue | Delegation & AI scoring: scoring framework and delegation contract (onchain accounting of delegation). |
| Tier‑1 | https://quackai.gitbook.io/docs/x402-execution-layer/proposalgeneration | Q402 architecture: delegated execution + receipts/audit registry, x402 BNB rollout and claimed results. |
| Tier‑1 | https://quackai.gitbook.io/docs/x402-execution-layer/aivoting | Facilitator network and incentive model (rewards in $Q) for sponsored relays. |
| Tier‑1 | https://quackai.gitbook.io/docs/developer-suite/q402-sign-to-pay-protocol | Q402 sign‑to‑pay: gasless, Permit2‑compatible, policy limits; a link to the open‑source repo and examples. |
| Tier‑1 | https://github.com/quackai-labs/Q402 | Open‑source: Quick Start, architecture, examples (examples/bsc-testnet), SDK/middleware/facilitator. |
| Tier‑1 | https://app.quackai.ai/ | Public app entry (airdrops/chat/governance entry) as “what you can touch”. |
| Tier‑2 | https://www.coingecko.com/en/coins/quack-ai | Profile/context (not proof). |
| Tier‑3 | — | — |
No comments to display
No comments to display