Hooked Protocol
Hooked Protocol — 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).
Hooked Protocol — an Infra | Education | Onboarding project on the BNB Smart Chain network that builds an “on‑ramp layer” for mass onboarding into Web3: Learn‑and‑Earn products (the pilot dApp Wild Cash) + infrastructure (identity/wallet/onchain data). Token: HOOK (BEP‑20).
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: “learn & earn” products and onboarding infrastructure to move users from Web2 to Web3.
- Who it’s for: new Web3 users, communities/projects that want to educate and onboard an audience.
- Why onchain/token: onchain is used to record actions/identity and interactions on BNB Chain; the
HOOKtoken is an economic/utility asset (governance, gas/fee model, incentives, access).
How it works (very briefly)
- The user does: goes through game/learning mechanics (quiz‑to‑earn, etc.) in Hooked products.
- The system does: issues tasks/rewards, conducts onchain interactions (per the whitepaper — on BNB Chain), forms onchain behavioral data.
- The user gets: a “first experience” of Web3, a wallet/identity (Hooked SBT) and access to ecosystem mechanics.
- Where the blockchain is: interactions and behavioral data are tied to BNB Chain; the
HOOKtoken is a BEP‑20 contract. - Token role (if any): the whitepaper claims governance/incentives/a gas role in the future rollup layer and access to NFTs/privileges.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Hooked Protocol |
| Also known as (aliases) | Hooked; Wild Cash; HOOK |
| Logo (logo) | ../assets/133_hooked-protocol_logo.bin |
| Token symbol (ticker) | HOOK |
| Category | Infra | Education | Onboarding |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | 2022-12 (TGE/first HOOK releases per the issuance schedule) |
| Project status (status) | active |
| Token (standard) | BEP-20 |
| Token contract | 0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0 |
| Token model (token_type) | utility (governance) |
| Max supply | 500,000,000 HOOK (Total fully diluted supply) |
| Issuance | fixed max supply + issuance/unlock schedule (per the whitepaper) |
| Tokenomics (tokenomics, brief) | distribution (Private Sale / Launchpad / Community / Treasury / Team) and schedule; utility: governance + gas token (for the planned rollup) + access |
| Governance | governance is claimed in the whitepaper (details of the onchain process are not disclosed) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | positioning only (AI-enhanced education) |
| Use‑case (use_case) | Learn + Earn onboarding in Web3 |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 2 / 3 |
| Last verified | 2026-02-05 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://hooked.io/ |
| Docs | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper |
| Roadmap | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-roadmap |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0 |
| X | https://twitter.com/HookedProtocol |
| Discord | https://discord.gg/2aWBxMKRFf |
| Telegram | https://t.me/HookedProtocolOfficial |
| Medium | https://medium.com/hookedprotocolofficial |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/hooked-protocol |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/hooked-protocol/ |
General project overview
In the Tier‑1 whitepaper, Hooked Protocol describes its goal as an “on‑ramp layer for massive Web3 adoption”: the project tries to lower the barrier to entry into Web3 through learning and game mechanics (Learn & Earn) and through onboarding infrastructure (identity/wallet/data). The pilot product is Wild Cash (Quiz‑to‑Earn and gamified learning), which, per the whitepaper, was used as a gateway for attracting and educating users.
From the blockchain perspective, Hooked describes that interactions take place on BNB Chain, and also mentions “rollup applicability” as a future base layer for consolidating data/assets. The roadmap additionally claims a Hooked AI direction (AI‑enhanced education) as a development plan, but there is no Tier‑1 confirmation of a working AI component (demos/architecture/metrics) in the available sources.
Features/modules
- Wild Cash (pilot dApp): Quiz‑to‑Earn and game‑based learning mechanics for onboarding.
- Gamified learning framework: a learning system based on “experience‑based” and “curiosity‑based” practices.
- Onboarding infra: Hooked SBT (soulbound identity), Hooked Wallet (wallet), on‑chain interactions on BNB Chain (as a source of behavioral data).
- Ecosystem layer (roadmap): a marketplace/ecosystem of applications + middleware and infrastructure; the role of the rollup approach as a scalable layer.
Typical scenarios
- Scenario 1 (newcomer): completes quizzes/game tasks → receives rewards/experience → starts using the wallet and onchain functions.
- Scenario 2 (community member): invites friends (referral mechanics) → participates in community growth → receives rewards/status elements.
- Scenario 3 (ecosystem partner): uses the onboarding infrastructure/data and access to the Hooked audience (at the level of the claimed ecosystem layer).
Getting started (wallet/network)
- What you need: access to the Hooked ecosystem products (website/app) and basic Web3 readiness (a wallet; the whitepaper mentions Hooked Wallet).
- Network/chain: interactions are described as taking place on BNB Chain.
- Fees: BNB network fees (gas) for onchain operations; the whitepaper claims a future role of
HOOKas the gas token for the Hooked application rollup.
Architecture/tech (non‑AI)
- Components: user products (Wild Cash and others), an identity layer (SBT), a wallet, onchain interactions on BNB Chain; the described middleware/infrastructure.
- Participant roles: users/community members, partner applications/businesses, ecosystem participants.
- Where logic runs: learning/game mechanics — in the applications (offchain); recording of interactions and data — onchain (BNB Chain) per the whitepaper.
- Dependencies: BNB Chain infrastructure (RPC/wallets/explorer), the
HOOKtoken (BEP‑20).
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1): governance, the claimed role of gas token for the Hooked application rollup and an access role (NFTs/privileges).
- Protocol necessity drivers: per the whitepaper, the token is a “governance platform token”; use as a gas token in the ecosystem layer is envisaged.
- Who pays fees: users/applications for onchain actions; in the future — via the gas token model on the rollup (per the whitepaper).
- Issuance/burn: Total supply 500M
HOOK; the distribution and unlock schedule are described. - Incentive mechanisms: the whitepaper mentions staking incentives as holding rewards (without conditions within the available pages).
- Distribution and token issuance schedule: Private Sale 20%, Launchpad 5%, Community 25%, Ecosystem/Treasury 30%, Team 20% + a detailed month‑by‑month schedule.
- Treasury: Ecosystem / Treasury 30% (the mechanics of managing the funds are not disclosed by Tier‑1 sources within this card).
Governance
- Who makes decisions: the whitepaper claims a governance role for
HOOK(implementation details/voting mechanics are not disclosed at the smart contract level). - How protocol parameters change: —.
- Where decisions are discussed/made: — (in this card we record only the existence of the claim in the whitepaper).
- Keys/multisig: —.
Security and incidents
- Audits: — (no Tier‑1 audit reports were found in the available sources).
- Bug bounty: —.
- Incidents: —.
- Threat model: onboarding UX risks (social engineering), token smart contract risks, quality/centralization risks of the offchain Learn&Earn logic.
Project status and timeline
- Current status: active (the token exists on BNB Chain; the whitepaper describes a working pilot product, Wild Cash).
- Key releases/milestones: Q3 2022 — launch of Wild Cash (per the whitepaper); Dec‑22 — TGE/start of the HOOK issuance schedule (per the emissions table).
- Roadmap: includes AI‑enhanced education and integration of the “Hooked AI SDK” (Tier‑1 roadmap).
Ecosystem/integrations
- Integrations: BNB Chain (on‑chain interactions), identity (SBT), wallet layer (Hooked Wallet — per the whitepaper).
- Partners: — (within this card we do not record marketing lists without Tier‑1 confirmation of integrations).
- Where it’s actually used: Learn & Earn onboarding (Wild Cash) as the pilot product per the whitepaper description.
AI component of the project
- What is real AI here? the Tier‑1 roadmap claims plans for “Hooked AI” and AI‑enhanced education, but there is no public Tier‑1 confirmation of a working AI component (demos/architecture/metrics) → we record it as AI intent.
- What is truly onchain? the
HOOKtoken (BEP‑20) and the claimed onchain interactions/data on BNB Chain (whitepaper). - Why is a token needed? per the whitepaper — a governance token, the claimed gas token for the Hooked application rollup and an access role (NFTs/privileges), plus part of the incentives.
- Red flags (based on the information found): AI‑washing (low‑medium) (there is a Tier‑1 roadmap, but no demos/metrics); onchain‑washing (medium) (much of the logic may remain offchain); token‑washing (medium) (part of the utility is tied to the future rollup layer).
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): the roadmap claims “Hooked AI” and plans for AI‑enhanced education / an AI SDK.
- Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-roadmap
- Why sufficient / why not (one line): the roadmap is Tier‑1, but these are exactly plans; without demos/architecture/metrics → intent only.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): the available Tier‑1 sources contain no specific description of a working AI function (what exactly the model/agent does).
- Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-roadmap
- Why sufficient / why not (one line): there is only an intent of “AI‑enhanced experiences” without a description of an implemented AI component → 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no public Tier‑1 demo of Hooked AI functions was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 link to a specific AI demo/example → 0.
- 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): there are no quantitative quality metrics for the AI part in Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a technical description of AI models/versions/architecture was not found in Tier‑1 sources.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no repo/docs describing an AI architecture → 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers:
HOOKBEP‑20:0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0 - Evidence: Tier‑1 — https://bscscan.com/token/0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0
- Why sufficient / why not (one line): BscScan confirms the network and the token contract.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: onchain interactions and behavioral data on BNB Chain; identity via a Soulbound Token (SBT).
- Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/build-the-on-ramp-layer/web3-onboarding-solutions
- Why sufficient / why not (one line): the whitepaper describes the SBT/wallet and “engaging all protocol interactions on BNB Chain”.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: learn‑and‑earn and the onboarding UX could also work centrally; there is no Tier‑1 proof that “without the blockchain it breaks down”.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): the criticality of the onchain layer is not substantiated by a Tier‑1 replacement test → 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token,
HOOK(BEP‑20). - Evidence: Tier‑1 — https://bscscan.com/token/0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0
- Why sufficient / why not (one line): the onchain token page 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): 1
- Claim (one line):
HOOKis claimed as the gas token for economic activity in the Hooked application rollup/ecosystem of dApps. - Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/token-utility
- Why sufficient / why not (one line): the Tier‑1 token utility explicitly describes the gas token role (payment for onchain activities).
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line):
HOOKis claimed as the basis for staking incentives / holding rewards. - Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/token-utility
- Why sufficient / why not (one line): the Tier‑1 utility description directly mentions “staking incentives as holding rewards”.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line):
HOOKis claimed as the governance token for proposals/votes in the ecosystem. - Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/token-utility
- Why sufficient / why not (one line): the Tier‑1 document directly speaks of a “Governance platform token”.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): part of the claimed utility (
gas tokenfor the planned rollup layer, access) looks replaceable at the design level and depends on whether the rollup is actually launched. - Evidence: Tier‑1 — https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/token-utility; https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-roadmap
- Why sufficient / why not (one line): most of the strong utility is tied to future components (rollup/ecosystem) → replaceability is not ruled out → TK_4 = 1.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/introduction-to-hooked-protocol/overview | Tier‑1 description: Hooked builds an on‑ramp layer, Learn & Earn, the pilot Wild Cash. |
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/build-the-on-ramp-layer | Tier‑1: the launch of Wild Cash as a gateway and gamified learning as the foundation. |
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/build-the-on-ramp-layer/web3-onboarding-solutions | Tier‑1: Hooked SBT identity, Hooked Wallet, and the statement about onchain interactions on BNB Chain. |
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-roadmap | Tier‑1: AI intent (Hooked AI, AI‑enhanced education, AI SDK). |
| Tier‑1 | https://bscscan.com/token/0xa260E12d2B924cb899AE80BB58123ac3fEE1E2F0 | Tier‑1 onchain fact: the HOOK token (BEP‑20), the contract and max supply 500M. |
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/token-utility | Tier‑1: HOOK utility (governance, gas token for the rollup, access, staking incentives). |
| Tier‑1 | https://hooked-protocol.gitbook.io/hooked-protocol-whitepaper/hooked-tokenomics/hook/emissions-and-distribution | Tier‑1: HOOK distribution (Private/Launchpad/Community/Treasury/Team) and the unlock schedule; total supply 500M. |
No comments to display
No comments to display