Document Type:: AI-Assisted Product Assessment — Public Source Review
Version:: 1.2
Assessment Date:: July 26, 2026
Subject:: HoodCard (hoodcard.cc)
Prepared by:: AI-assisted research workflow (see Section 2.5)

Disclaimer: This is an AI-assisted research report, not an independent third-party audit, financial advice, or security certification. Ratings reflect publicly available documentation and sources only. No wallet transactions or live product testing were performed. Readers should verify all claims using cited primary sources.

HoodCard Feature Evaluation Report

Agentic RWA Virtual Visa Card on Robinhood Chain

Overall Assessment Rating

7.2 / 10

Scale: 0 (Not verified) → 10 (Fully documented, transparent, production-ready)

Note: Score reflects documentation quality and transparency only. No live product testing, smart contract audit, or independent financial verification was performed.

This report presents a public-source feature assessment of HoodCard based on official documentation at docs.hoodcard.cc, live website metadata at hoodcard.cc, and assistive review using Cursor, Claude, Ollama, and Qwen AI tools during research and drafting. HoodCard is assessed as a non-custodial virtual Visa card platform that enables wallet-native identity, onchain funding with crypto and tokenized stocks, tokenized stock cashback rewards, and optional card management via HoodAgent on X. HoodCard's public documentation describes a three-tier architecture with stated fee disclosures and an outlined security model; these claims are based on published documentation and have not been independently tested. Noted limitations include a permanent X account binding, one-card-per-wallet constraint, a flat 3% top-up fee, virtual-only card availability, and an early-stage codebase (GitHub repos created July 25, 2026). The composite rating of 7.2 out of 10 uses equal weighting across twelve categories; see Section 6.0 for the full score breakdown and methodology note.

Section 1.0

Executive Summary

HoodCard is a non-custodial virtual Visa card built on Robinhood Chain (Chain ID 4663). The platform allows users to fund a card with ETH or supported tokenized real-world asset (RWA) stocks, spend online wherever Visa is accepted, and earn tokenized stock cashback directly to their connected wallet. Identity is wallet-based: there is no email signup, password, or traditional bank account requirement.

The assessment reviewed twelve distinct feature categories against official GitBook documentation, website metadata, and three public GitHub repositories (hoodcard, hoodcard-agent, hoodcard-contracts). Key findings indicate that HoodCard provides a coherent end-to-end user journey—from wallet connection through card creation, funding, spending, and reward accrual—with supplementary control surfaces via the Dashboard and HoodAgent X integration. Technical architecture documentation on GitHub reveals a three-tier system (React frontend, Express backend with deposit poller and Twitter agent, HoodAgent.sol on Robinhood Chain) with MIT-licensed open-source components.

Primary strengths include non-custodial architecture, published fee and cashback schedules, comprehensive documentation across fifteen pages, and direct onchain settlement with transaction hash visibility in the Dashboard. Primary limitations documented by the provider include irreversible X account linking, a single HoodCard per wallet address, virtual-only card format, and a 3% flat top-up fee in addition to network gas costs.

The overall rating of 7.2 reflects equal weighting across all twelve categories. Early-stage features (Sections 1–4: wallet connection, chain integration, card creation, funding) scored in the 5.8–6.7 range due to onboarding complexity and fee impact. Advanced features (Sections 5–12) scored 7.4–8.0, reflecting published documentation quality while acknowledging that live product behavior, cashback delivery, and third-party card issuer operations were not independently verified.

"HoodCard is a non-custodial virtual Visa card built on Robinhood Chain. It lets you fund a card with crypto or tokenized stocks, spend online wherever Visa is accepted, and earn tokenized stock cashback."
— Introduction, docs.hoodcard.cc, retrieved July 26, 2026

Website metadata — Title: "HoodCard — Agentic RWA Virtual Card"

Meta description: "Create an agentic virtual card, fund it with onchain assets, earn tokenized stock rewards, and control via X."
— hoodcard.cc, retrieved July 26, 2026

Section 2.0

Scope & Methodology

2.1 Scope

This assessment covers all documented HoodCard features as published in the official GitBook documentation index (llms.txt) and corroborated by live website metadata at hoodcard.cc and public GitHub repositories at github.com/tryHoodcard. The scope includes wallet onboarding, chain integration, card lifecycle, funding, spending, cashback, Dashboard controls, HoodAgent configuration, X command interface, fee structures, supported assets, security/support channels, product architecture (from GitHub READMEs), multi-agent infrastructure, smart contract lifecycle, deposit/cashback mechanisms, platform metrics, performance benchmarks, and onchain verification pathways.

2.2 Methodology

Each feature was evaluated through public source review: documentation cross-reference, verification of published rates and fee tables, confirmation of official support channels, and alignment of website metadata with documented product claims. Every finding in this report cites a primary source URL and includes a verbatim excerpt where applicable.

2.3 Exclusions & Limitations

This assessment did not involve wallet connections, onchain transactions, private account access, or hands-on live product testing. Evidence is drawn from public documentation, website screenshots captured on July 26, 2026, and open GitHub repositories. The following limitations apply:

No independent security audit or penetration testing was performed or cited.
Live homepage stats (e.g. cashback distributed, wallet count) reflect a single point-in-time capture and may change.
GitHub repositories were created July 25, 2026 — the project is early-stage with limited public adoption data (0 stars at time of review).
AI tools assisted research and drafting; they are not separate accredited auditors (see Section 2.5 and Section 5.0).
Ratings assess documentation quality and published transparency, not guaranteed production performance.

Table 2.1 — Evidence standards applied in this assessment
Evidence Type	Format in Report
Documentation excerpt	Blockquote with source URL and retrieval date
Published data table	Reproduced HTML table with footnote link
Website metadata	Quoted title and meta description from hoodcard.cc
Official channels	Linked references to @tryhoodcard, Telegram, GitHub
On-chain parameters	Network configuration table (Chain ID 4663, Blockscout)

Section 2.5

AI Tools Used in Research

This report was drafted using an AI-assisted workflow. The tools below helped gather public sources, structure findings, and check internal consistency. They did not perform live wallet testing, onchain transaction verification, or act as accredited third-party auditors.

Primary Tool

Cursor

Report drafting, documentation retrieval, screenshot capture, HTML assembly

Review Assist

Claude

Structure review, security section consistency checks, prose editing

Local Check

Ollama

Offline cross-check of HoodAgent.sol claims against GitHub source text

Data Check

Qwen

Fee table and supported-assets list validation against official docs

Table 2.5.1 — AI tools used (assistive only, not accredited auditors)
Tool	Role in This Report	What It Did Not Do
Cursor	Drafted report, fetched public docs, captured dated screenshots	No wallet connection or transaction signing
Claude	Reviewed report structure and flagged inconsistencies	No independent onchain verification
Ollama	Cross-checked contract variable names against GitHub source	No bytecode or deployment audit
Qwen	Validated published fee/asset tables against docs	No access to private HoodCard backend data

What this assessment could not verify:

Live card issuance or spending behavior
Actual cashback delivery to wallets
Backend API responses or database integrity
Smart contract behavior under adversarial conditions
Card issuer (Visa) approval rates or transaction success rates
Whether stated fees match actual charged amounts

Section 2.6

Visual Evidence

The following captures were taken directly from HoodCard's live website, official documentation, and public GitHub repositories on July 26, 2026. Figures show the source as captured on that date; live values (such as wallet counts or cashback totals) may have changed since.

HoodCard live homepage showing Connect Wallet, stats, and product features — Figure 2.6.1 — Homepage at hoodcard.cc as captured July 26, 2026. Visible at time of capture: Connect Wallet CTA, live ticker showing "$14.02 distributed", "52 events", "21 wallets". These are point-in-time values — verify current stats on hoodcard.cc.

HoodCard official documentation on docs.hoodcard.cc — Figure 2.6.2 — Official GitBook documentation at docs.hoodcard.cc with getting-started guides and feature reference.

HoodCard contracts GitHub repository showing HoodAgent.sol — Figure 2.6.3 — Public GitHub repository tryHoodcard/hoodcard-contracts showing HoodAgent.sol (Solidity 100%, MIT license).

HoodCard product banner — Spend Tokenized Assets — Figure 2.6.4 — Official HoodCard product banner from GitHub repository: "Spend Tokenized Assets" — RWA-backed virtual Visa card. Source: github.com/tryHoodcard/hoodcard

Section 3.0

Feature Assessments

The following twelve subsections evaluate individual HoodCard features. Each subsection includes an assessment rating (0–10), documented functionality, verification summary, cited evidence, findings, and rating justification.

Section 3.1

Wallet Connection & Identity

Assessment Rating 6.4

Overview

HoodCard uses wallet-native identity. The connected EVM wallet address serves as the user's HoodCard account. No email, password, or separate registration is required.

Documented Functionality

Users visit hoodcard.cc, select Connect Wallet, approve the request in their wallet, and switch to Robinhood Chain when prompted. Supported wallets include MetaMask, Rabby, and Coinbase Wallet through Privy integration.

Verification Summary

The onboarding flow is documented step-by-step in the official getting-started guide. Wallet provider support is explicitly named. The wallet-as-identity model is consistently stated across introduction and FAQ documentation.

Evidence

"Connect an EVM-compatible wallet to begin. MetaMask, Rabby, and Coinbase Wallet are supported through Privy."
— Connect your wallet, retrieved July 26, 2026

"Your wallet address becomes your HoodCard identity. You do not need an email, password, or separate account."
— Connect your wallet, retrieved July 26, 2026

"Your connected wallet is your account. There is no email signup or password."
— FAQ and social links, retrieved July 26, 2026

Findings — Strengths

The wallet-native model eliminates traditional account friction and aligns with non-custodial DeFi conventions. Privy integration supports multiple popular wallet providers, reducing onboarding barriers for existing crypto users.

Findings — Limitations

Users must already possess a compatible EVM wallet and understand network switching. No alternative identity or recovery mechanism beyond wallet seed phrase is documented.

Rating Justification: Wallet connection is documented with named providers and a clear flow. Score reduced to 6.4 due to dependency on user wallet literacy, manual network switching requirements, and absence of documented account recovery beyond seed phrase backup.

Sources

Section 3.2

Robinhood Chain Integration

Assessment Rating 6.1

Overview

All HoodCard onchain operations occur on Robinhood Chain. Users must switch their wallet to this network before creating or funding a card.

Documented Functionality

Robinhood Chain uses Chain ID 4663, native token ETH for gas, ERC-20 token standard, and Blockscout as the block explorer. Users who cannot auto-switch must manually add the network via wallet settings.

Verification Summary

Network parameters are published in a structured table within the connect-your-wallet documentation. Gas requirements are noted for smart contract deployment and token transfers.

Evidence

Table 3.2.1 — Robinhood Chain network parameters. Source: Connect your wallet
Setting	Value
Network	Robinhood Chain
Chain ID	4663
Native token	ETH
Token standard	ERC-20
Explorer	Robinhood Chain Blockscout

"Keep a small ETH balance on Robinhood Chain. It pays gas for smart contract deployment and token transfers."
— Connect your wallet, retrieved July 26, 2026

Findings — Strengths

Complete network specification is published in tabular form. Gas requirements are explicitly communicated before users begin onchain actions.

Findings — Limitations

Manual network addition may be required for wallets that do not auto-switch. Gas costs are separate from HoodCard service fees and vary with network conditions.

Rating Justification: Chain integration is documented with required parameters. Score reduced to 6.1 reflecting manual network setup burden, unstated gas cost ranges, and Robinhood Chain being a newer ecosystem with limited wallet auto-detection support.

Sources

docs.hoodcard.cc/getting-started/connect-your-wallet.md

Section 3.3

HoodCard Creation

Assessment Rating 5.8

Overview

Card creation deploys a personal HoodAgent smart contract and issues a virtual Visa card permanently linked to the user's wallet address.

Documented Functionality

The six-step creation flow requires: selecting Create HoodCard, entering a card name, choosing a HoodAgent name, setting a Daily X Limit (default $100 per 24 hours), selecting an initial funding asset and amount, and confirming onchain transactions. Upon deposit confirmation, HoodCard issues the virtual Visa card with number, expiry, and CVV visible in the Dashboard.

Verification Summary

The creation workflow is documented sequentially. Constraints (one wallet, one card) are explicitly warned. Default Daily X Limit is stated.

Evidence

"Create your card after connecting a wallet on Robinhood Chain. The process deploys your personal HoodAgent and links the card permanently to your wallet address."
— Create your HoodCard, retrieved July 26, 2026

"The default Daily X Limit is $100 per 24 hours. It limits the value HoodAgent can process through X commands. You can change it later."
— Create your HoodCard, retrieved July 26, 2026

"One wallet address supports one HoodCard. Choose the connected wallet carefully."
— Create your HoodCard, retrieved July 26, 2026

Findings — Strengths

End-to-end creation flow is documented with sensible defaults. HoodAgent deployment is integrated into card issuance, providing immediate X-based control capability.

Findings — Limitations

One-card-per-wallet is a permanent constraint. Initial funding is required during creation, which may deter exploration-only users.

Rating Justification: Creation process is documented but score reduced to 5.8 — lowest in early-stage group — due to mandatory initial deposit, one-card-per-wallet inflexibility, and multi-step onchain confirmation during setup.

Sources

docs.hoodcard.cc/getting-started/create-your-hoodcard.md

Section 3.4

Card Funding / Top-up

Assessment Rating 6.7

Overview

Users fund their HoodCard by sending ETH or supported tokenized stock tokens on Robinhood Chain. After onchain confirmation, HoodCard credits the USD equivalent to the virtual card balance.

Documented Functionality

The four-step top-up flow: open Dashboard, select Fund Card, choose asset and amount, review fee and confirm wallet transaction. A flat 3% fee applies to every top-up. Top-ups process within seconds to a few minutes after chain confirmation.

Verification Summary

Funding mechanics, fee deduction, and timing expectations are documented. Worked example provided ($100 NVDA → $97 credited after $3 fee).

Evidence

"Fund your HoodCard by sending ETH or a supported tokenized stock on Robinhood Chain. After onchain confirmation, HoodCard credits the USD equivalent to your virtual card balance."
— Fund your card, retrieved July 26, 2026

"Send $100 worth of NVDA. The $3 fee is deducted, so your card receives $97. Eligible top-ups earn fixed 2% tokenized stock cashback."
— Fund your card, retrieved July 26, 2026

"Only send supported assets on Robinhood Chain. Transfers on another network cannot credit your card."
— Fund your card, retrieved July 26, 2026

Findings — Strengths

Funding supports both native ETH and 19 tokenized RWA stocks. Clear worked example demonstrates fee impact. Processing time expectations are stated.

Findings — Limitations

Cross-network transfers cannot be recovered. The 3% fee reduces effective card balance. Very small top-ups are impractical per FAQ guidance.

Rating Justification: Funding is transparent with examples but score reduced to 6.6 due to 3% flat fee impact, network-specific transfer requirement, and impracticality of small top-ups.

Sources

docs.hoodcard.cc/getting-started/fund-your-card.md

Section 3.5

Virtual Visa Card Usage

Assessment Rating 7.6

Overview

HoodCard issues a virtual Visa card usable for online purchases wherever Visa is accepted. Card details are protected and revealed only during an active wallet session.

Documented Functionality

Users access card number, expiry date, and CVV from the Dashboard card panel. Details remain hidden by default. Copy controls are provided for each value. Day-to-day card spending does not require onchain gas; ETH is needed only for deposits and contract deployment.

Verification Summary

Card type (virtual Visa), usage scope (online), security model (session-gated reveal), and gas requirements are all documented.

Evidence

"Your HoodCard is a virtual Visa card. Use its card number, expiry date, and CVV for online purchases wherever Visa is accepted."
— Use your virtual card, retrieved July 26, 2026

"Card details remain hidden by default. Reveal them only during an active wallet session, then use the copy control for each value."
— Use your virtual card, retrieved July 26, 2026

"HoodCard has no physical form. It is designed for online card purchases."
— Use your virtual card, retrieved July 26, 2026

Findings — Strengths

Session-gated card detail reveal provides a documented security control. Separation of spending (no gas) from onchain actions (gas required) is clearly explained.

Findings — Limitations

Virtual-only format excludes in-store POS and ATM usage. Online-only scope may limit use cases compared to physical debit cards.

¹ The virtual card issuer is a regulated third-party provider. Identity is not disclosed in public HoodCard documentation; this assessment uses the term "Virtual Card Provider" to reflect that limitation.

Rating Justification: Virtual card functionality is well-defined with appropriate security controls documented. Minor deduction for virtual-only limitation and lack of documented merchant category restrictions.

Sources

docs.hoodcard.cc/using-hoodcard/use-your-virtual-card.md

Section 3.6

Dashboard & Activity

Assessment Rating 7.5

Overview

The Dashboard serves as the HoodCard control center, consolidating virtual card access, balance, funding, activity feed, cashback history, and security controls including card freeze.

Documented Functionality

The Transactions tab lists top-ups (with status and onchain tx hash), card spending (amount and date), and associated cashback. The Cashback section shows total earned value, pending tokens, and individual reward events with token, amount, source, and tx hash. Freeze Card immediately suspends card use; unfreeze restores it after securing accounts.

Verification Summary

Dashboard capabilities are documented across transactions, cashback, and freeze/unfreeze controls. Onchain transaction hash visibility provides auditability.

Evidence

"The Dashboard is your HoodCard control center. It brings together your virtual card, balance, funding flow, activity feed, cashback, and security controls."
— Dashboard and activity, retrieved July 26, 2026

"The Transactions tab lists activity in chronological order: Top-ups with status and onchain transaction hash. Card spending with amount and date. Cashback associated with eligible activity."
— Dashboard and activity, retrieved July 26, 2026

"Select Freeze Card to suspend card use immediately. Use it if you suspect unauthorized access. You can unfreeze the card after securing your accounts."
— Dashboard and activity, retrieved July 26, 2026

Findings — Strengths

Unified control center with onchain tx hash linkage enables user verification of all financial activity. Immediate freeze capability provides emergency response.

Findings — Limitations

Dashboard UI specifics (layout, filtering, export) are not documented in detail. Activity review depends on wallet session availability.

Rating Justification: Core Dashboard functions are documented with audit trail support via tx hashes. Score reflects limited UI-level documentation beyond functional descriptions.

Sources

docs.hoodcard.cc/using-hoodcard/dashboard-and-activity.md

Section 3.7

RWA Cashback Rewards

Assessment Rating 7.5

Overview

HoodCard delivers eligible cashback as tokenized stocks directly to the user's connected wallet on Robinhood Chain. Rewards are real tokens, not points or vouchers.

Documented Functionality

Card top-ups earn a fixed 2% cashback. Card spending earns a randomized 2% to 5% cashback. Each reward selects one asset from a designated pool of ten tokenized stocks. Users retain full custody and may hold, trade, or sell received tokens.

Verification Summary

Cashback rates, delivery mechanism, reward asset pool, and ownership model are documented with worked examples.

Evidence

Table 3.7.1 — Cashback reward rates. Source: Earn RWA cashback
Eligible Activity	Cashback
Card top-up	2% fixed
Card spend	2% to 5%, randomized

"HoodCard sends eligible cashback rewards directly to your connected wallet on Robinhood Chain. Rewards are tokenized stocks, not points or vouchers."
— Earn RWA cashback, retrieved July 26, 2026

"Each reward selects one asset from the cashback pool: NVDA, AAPL, TSLA, MSFT, GOOGL, AMZN, META, PLTR, COIN, or NFLX."
— Earn RWA cashback, retrieved July 26, 2026

"A $200 top-up earns $4 worth of the selected stock token. A card transaction receives a randomly selected rate between 2% and 5%."
— Earn RWA cashback, retrieved July 26, 2026

Findings — Strengths

Direct wallet delivery of real tokenized stock assets distinguishes HoodCard from traditional points-based rewards. Fixed top-up rate provides predictability; spend rate range adds variable upside.

Findings — Limitations

Spend cashback rate is randomized within the 2–5% range, reducing predictability. Reward token selection from the pool is not user-configurable.

Rating Justification: Cashback model is differentiated from traditional points-based systems and is clearly documented with concrete worked examples. Score reflects documentation quality only — cashback delivery to wallets was not independently verified through live transactions. The randomized 2–5% spend rate introduces unpredictability, and reward token selection is non-configurable. No on-chain cashback transactions were reviewed as part of this assessment.

Sources

Section 3.8

Supported Assets

Assessment Rating 7.8

Overview

HoodCard accepts ETH and 19 tokenized RWA stocks for card funding on Robinhood Chain. The first ten stocks form the cashback reward pool.

Documented Functionality

ETH serves dual purpose as gas token and fundable asset. Nineteen tokenized stocks spanning major technology, financial, and thematic equities are listed with symbols and full company names. Only listed assets sent via Robinhood Chain are accepted.

Verification Summary

Complete asset list is published in tabular form. Cashback pool subset is explicitly identified.

Evidence

Table 3.8.1 — Supported funding assets (plus ETH). Source: Supported assets
Symbol	Asset
NVDA	NVIDIA
AAPL	Apple
TSLA	Tesla
MSFT	Microsoft
GOOGL	Alphabet
AMZN	Amazon
META	Meta Platforms
PLTR	Palantir
COIN	Coinbase
NFLX	Netflix
AMD	Advanced Micro Devices
MSTR	MicroStrategy
TSM	TSMC
AVGO	Broadcom
SHOP	Shopify
MU	Micron Technology
CRWD	CrowdStrike
GME	GameStop
SPCX	Space Exploration ETF

"HoodCard accepts ETH and 19 tokenized RWA stocks for card funding on Robinhood Chain."
— Supported assets, retrieved July 26, 2026

Findings — Strengths

Broad asset coverage including major tech equities and thematic ETF. Clear symbol-to-company mapping aids user selection. Cashback pool subset is explicitly defined.

Findings — Limitations

Asset list is fixed; no stablecoin or additional token categories are documented. Assets beyond the first ten cannot be received as cashback rewards.

Token contract addresses listed in documentation were not cross-referenced against official Robinhood Chain contract registry at time of assessment. Users should independently verify contract addresses via explorer.robinhood.com before transacting.

Rating Justification: Asset support is comprehensively listed with 20 fundable options. Score reflects limited extensibility documentation and absence of stablecoin funding options. Token contract addresses listed in documentation were not cross-referenced against official Robinhood Chain contract registry at time of assessment. Users should independently verify contract addresses via explorer.robinhood.com before transacting.

Sources

docs.hoodcard.cc/security-and-support/supported-assets.md

Section 3.9

Fees Transparency

Assessment Rating 7.8

Overview

HoodCard publishes a flat 3% top-up fee and detailed cashback rate schedules. Network gas is documented as a separate cost.

Documented Functionality

Every top-up incurs a 3% fee deducted from the sent asset. HoodCard states no other top-up charges exist. Gas uses ETH on Robinhood Chain and is independent of the service fee.

Verification Summary

Fee schedule is published with three worked examples. Cashback rates are tabulated alongside fee information on a dedicated reference page.

Evidence

Table 3.9.1 — Top-up fee schedule (3% flat). Source: Fees and cashback reference
Top-up Value	Fee	Card Balance Credited
$50	$1.50	$48.50
$100	$3.00	$97.00
$500	$15.00	$485.00

Table 3.9.2 — Cashback rates. Source: Fees and cashback reference
Eligible Activity	Reward Rate	Reward Delivery
Card top-up	2% fixed	Tokenized stock to your wallet
Card spend	2% to 5%, randomized	Tokenized stock to your wallet

"Every card top-up has a flat 3% fee. HoodCard deducts the fee from the asset you send."
— Fees and cashback reference, retrieved July 26, 2026

Findings — Strengths

Fee structure is published with multiple worked examples. Explicit statement that no other top-up charges exist reduces ambiguity. Gas separation is clearly noted.

Findings — Limitations

3% flat fee is relatively high compared to some payment alternatives. Gas cost ranges are not quantified. No fee comparison or calculator tool is documented.

Rating Justification: Transparency is strong with published tables and examples. Score reflects the fee level itself (3%) rather than disclosure quality, which is excellent.

Sources

docs.hoodcard.cc/using-hoodcard/fees-and-cashback-reference.md

Section 3.10

HoodAgent Setup

Assessment Rating 7.4

Overview

HoodAgent is a personal smart contract deployed during card creation that enables selected card controls through a linked X (Twitter) account.

Documented Functionality

Users link an X account via Dashboard → Agent → Link X Account. The X connection is permanent and cannot be changed or removed. Daily X Limit caps USD value HoodAgent can process in 24 hours. Token allowances must be set for X-triggered deposits. Each HoodAgent is unique to a wallet and visible on Robinhood Chain Blockscout.

Verification Summary

Setup steps, permanence warning, limit configuration, and onchain visibility are documented. Security guidance precedes agent deposit enablement.

Evidence

"HoodAgent is a personal smart contract deployed during card creation. It enables selected card controls through your linked X account."
— Set up HoodAgent, retrieved July 26, 2026

"Your X link is permanent. It cannot be changed or removed. Only authorize an account you intend to control long term."
— Set up HoodAgent, retrieved July 26, 2026

"Can I change my linked X account? No. The X connection is permanent and cannot be removed or replaced."
— FAQ and social links, retrieved July 26, 2026

Findings — Strengths

Onchain agent contract provides verifiable, transparent automation. Daily limit and token allowance controls offer layered security. Permanent link warning is prominently displayed.

Findings — Limitations

Irreversible X account binding is a significant operational constraint. Agent setup adds complexity for users unfamiliar with token allowances. Dependency on X platform availability.

Rating Justification: HoodAgent is a differentiated feature with documented security controls. Lowest category score reflects the permanent X binding constraint and setup complexity.

Sources

Section 3.11

X Commands

Assessment Rating 7.8

Overview

After linking X, users manage HoodCard by tweeting commands to @tryhoodcard from the linked account. HoodAgent accepts commands only from that account within the Daily X Limit.

Documented Functionality

Eight commands are documented covering balance inquiry, token deposits, card freeze/unfreeze, daily limit updates, transaction history, cashback summary, and agent status. Deposit commands require prior token allowance setup and cannot exceed allowance or Daily X Limit.

Verification Summary

Complete command reference table is published. Deposit prerequisites and post-action Dashboard review are documented.

Evidence

Table 3.11.1 — HoodAgent X commands. Source: Use X commands
Command	Action
@tryhoodcard balance	Show current card balance
@tryhoodcard deposit $[amount] with [TOKEN]	Start a token top-up
@tryhoodcard freeze my card	Freeze the card immediately
@tryhoodcard unfreeze my card	Restore card use
@tryhoodcard set daily limit to $[amount]	Update your daily limit
@tryhoodcard transactions	View recent activity
@tryhoodcard cashback	View your reward summary
@tryhoodcard agent info	Check agent status and configuration

"After linking X, tweet commands to @tryhoodcard from the linked account. HoodAgent accepts commands only from that account and applies your Daily X Limit."
— Use X commands, retrieved July 26, 2026

Findings — Strengths

Eight documented commands cover essential card management without requiring Dashboard access. Natural language command format lowers interaction barrier for social media users.

Findings — Limitations

Commands are public tweets, which may expose usage patterns. Response time and error handling for failed commands are not documented. Platform dependency on X availability.

Rating Justification: Command set is comprehensive and well-tabulated. Score reflects public nature of X commands and undocumented error/response behavior.

Sources

docs.hoodcard.cc/hoodagent/use-x-commands.md

Section 3.12

Security, Privacy & Support

Assessment Rating 8.0

Overview

HoodCard employs wallet-based access and onchain settlement with no KYC documentation requirement. Security controls include session-gated card details, immediate freeze capability, configurable agent limits, and documented support channels.

Documented Functionality

No name, email, or identity document is requested. HoodCard does not custody wallet assets. Top-ups transfer onchain from the user's wallet; cashback arrives directly. Card details are hidden until active wallet session. Official support is available via Telegram; product updates via @tryhoodcard on X; code presence via GitHub.

Verification Summary

Privacy model, custody boundaries, protection mechanisms, and support channels are documented across security, FAQ, and troubleshooting pages.

Evidence

"HoodCard does not request a name, email, or identity document. Your connected wallet address identifies your HoodCard access."
— Security and privacy, retrieved July 26, 2026

"HoodCard does not custody your crypto wallet assets. Top-ups transfer onchain from your wallet. Cashback arrives directly in your wallet."
— Security and privacy, retrieved July 26, 2026

"Need support? Contact the team on Telegram for any card-related question or other HoodCard issue."
— FAQ and social links, retrieved July 26, 2026

Findings — Strengths

Non-custodial architecture with no KYC requirement aligns with privacy-conscious crypto users. Multi-channel support (Telegram, X, GitHub) provides redundancy. Comprehensive troubleshooting documentation exists.

Findings — Limitations

Users bear sole responsibility for wallet recovery and legal compliance. No formal third-party security audit publication was found in public documentation — the 8.0 rating reflects documentation and support channel quality, not a certified security audit.

Rating Justification: Security and privacy model is clearly articulated with actionable protection guidance. Score reflects documentation and support quality only — not an independent security certification.

Sources

Section 4.0

Technical Architecture & Infrastructure

The following subsections document HoodCard's product architecture, multi-agent execution model, onchain lifecycle, publicly available metrics, performance characteristics, GitHub resources, and reader-verifiable onchain pathways. All content is sourced from official documentation, public GitHub repositories under github.com/tryHoodcard, and live website metadata.

Section 4.1

Product Architecture & System Design

Overview

HoodCard's public documentation describes a three-tier architecture with stated fee disclosures and an outlined security model. These claims are based on published documentation and have not been independently tested. The described system comprises a React web application (hoodcard.cc), an Express API backend with auxiliary services (deposit poller, Twitter agent), and onchain components on Robinhood Chain (HoodAgent.sol, RWA token contracts). A PostgreSQL database persists application state; a Virtual Card Provider handles Visa card issuance and spending authorization.

System Components

Table 4.1.1 — HoodCard system component map. Source: hoodcard README
Layer	Component	Role
Frontend	React + Vite Web App	Wallet auth (Privy), card management UI, agent configuration
Backend	Express API Server	REST endpoints, card lifecycle, agent deployment orchestration
Backend	Deposit Poller	Monitors Robinhood Chain for incoming top-up transactions
Backend	Twitter Agent (hoodcard-agent)	Polls X mentions, classifies intent, executes card commands
Data	PostgreSQL	User state, transaction records, tweet deduplication
External	Virtual Card Provider	Visa card issuance, balance management, spend authorization
Onchain	HoodAgent.sol	Per-user smart contract: identity, limits, X account hash
Onchain	ETH + 19 RWA Tokens	Funding assets on Robinhood Chain (Chain ID 4663)

Architecture Diagram (Text Representation)

┌─────────────────────────────────────────────────────────────────┐
│                    WEB APP — hoodcard.cc                        │
│              React 18 + Vite + Privy (wallet auth)              │
└──────────────────────────┬──────────────────────────────────────┘
                           │ REST API
┌──────────────────────────▼──────────────────────────────────────┐
│                      BACKEND SERVICES                           │
│  ┌─────────────┐  ┌────────────────┐  ┌───────────────────┐  │
│  │ Express API │  │ Deposit Poller │  │ Twitter Agent Bot │  │
│  └──────┬──────┘  └───────┬────────┘  └─────────┬─────────┘  │
│         │                 │                      │            │
│         ▼                 ▼                      ▼            │
│  ┌─────────────┐   Robinhood Chain         HoodAgent.sol       │
│  │ PostgreSQL  │   (ETH + RWA Tokens)      (per-user contract)│
│  └─────────────┘                                               │
└──────────────────────────┬──────────────────────────────────────┘
                           │ webhooks
                  ┌────────▼────────┐
                  │ Virtual Card    │
                  │ Provider (Visa) │
                  └─────────────────┘

Evidence

"HoodCard is a no-KYC virtual Visa card that runs on Robinhood Chain. Connect your wallet, issue a card in under 30 seconds, fund it with ETH or tokenized stocks."
— tryHoodcard/hoodcard README, retrieved July 26, 2026

Architecture subgraph documented: Web App (React + Vite, Privy Auth) → Express API + Deposit Poller + Twitter Agent → Robinhood Chain (HoodAgent.sol, ETH + RWA Tokens) + PostgreSQL + Virtual Card Provider.
— tryHoodcard/hoodcard README — Architecture, retrieved July 26, 2026

Sources

Section 4.2

Multi-Agent Infrastructure & Execution Flow

Overview

HoodCard implements a multi-agent model where each user receives a personal HoodAgent smart contract at card creation. A separate backend Twitter agent (hoodcard-agent) monitors @tryhoodcard mentions, classifies user intent via OpenAI, verifies onchain permissions, and executes card operations. The deposit poller operates as an independent service monitoring chain state for incoming top-ups.

Agent Types

Table 4.2.1 — HoodCard agent infrastructure. Sources: GitHub README files
Agent	Type	Deployment	Function
HoodAgent	Onchain smart contract (HoodAgent.sol)	One per user wallet at card creation	Stores identity, spending limits, X account hash; enforces permissions
Twitter Agent	Backend service (hoodcard-agent)	Centralized, polls X every 30 seconds	Classifies tweet intent, reads onchain permissions, executes commands
Deposit Poller	Backend service	Centralized, continuous chain monitoring	Detects incoming RWA/ETH deposits, credits virtual card balance

Twitter Agent Execution Flow

Table 4.2.2 — Twitter agent command execution sequence. Source: hoodcard-agent README
Step	Action
1	User tweets command to @tryhoodcard from linked X account
2	Mention Listener polls X every 30 seconds for new mentions
3	Tweet ID checked against PostgreSQL — deduplication prevents double execution
4	OpenAI intent classifier processes tweet (confidence threshold ≥ 0.85 required)
5	Backend looks up wallet address by twitterUserId in database
6	HoodAgent.sol read: twitterEnabled, dailyLimitWei, maxPerCommandWei verified onchain
7	If permitted: command executed via Virtual Card Provider; reply posted to X
8	Tweet ID recorded in database; per-user cooldown enforced

Evidence

"HoodAgent watches @tryhoodcard for mentions and executes card commands — no app required. Every tweet is classified by an AI intent model, verified against your on-chain permissions in HoodAgent.sol, and executed in real time."
— tryHoodcard/hoodcard-agent README, retrieved July 26, 2026

"Confidence must be ≥ 0.85 — anything below is silently dropped."
— hoodcard-agent README — Intent Classification, retrieved July 26, 2026

Sources

Section 4.3

Smart Contracts & Onchain Transaction Lifecycle

Overview

The HoodAgent.sol contract is deployed once per user on Robinhood Chain during card creation. It stores agent identity, card name, a keccak256 hash of the card ID (never the raw card number), X account hash, spending limits, and a twitterEnabled toggle. Card secrets are explicitly excluded from onchain storage.

HoodAgent.sol State Variables

Table 4.3.1 — HoodAgent.sol contract state. Source: HoodAgent.sol
Variable	Type	Description
owner	address (immutable)	Deploying wallet address — sole controller
agentName	string	User-chosen HoodAgent name
cardName	string	User-chosen card display name
cardIdHash	bytes32 (immutable)	keccak256(cardId) — tamper-proof link without exposing card ID
xAccountHash	bytes32	keccak256(twitterUserId) — set once via linkXAccount()
dailyLimitWei	uint256	Max cumulative daily spend via tweet commands
maxPerCommandWei	uint256	Max value per single tweet command
twitterEnabled	bool	Master switch for all tweet commands (default: true)
createdAt	uint256 (immutable)	Block timestamp at deployment

Onchain Events

Table 4.3.2 — HoodAgent.sol events. Source: hoodcard-contracts README + HoodAgent.sol
Event	Emitted When
AgentInitialized	Contract deployed — stores owner, agentName, cardName, cardIdHash
XAccountLinked	X account permanently linked via linkXAccount()
SettingsUpdated	Limits or twitterEnabled toggle changed by owner

Transaction Lifecycle

Table 4.3.3 — End-to-end transaction lifecycle across onchain and offchain systems
Phase	Onchain Action	Offchain Action
Card Creation	Deploy HoodAgent.sol via API → Robinhood Chain	API stores contractAddress + txHash; Virtual Card Provider issues Visa card
Top-up	User sends ETH/RWA token to deposit address on Chain 4663	Deposit Poller detects tx → credits card balance (minus 3% fee) → Dashboard shows tx hash
X Linking	linkXAccount(keccak256(twitterUserId)) — one-time, irreversible	Privy linkTwitter() → API POST /api/agent/twitter
Spend	No onchain gas required for card spending	Virtual Card Provider authorizes Visa transaction; cashback calculated offchain
Cashback	Tokenized stock sent directly to user wallet on Robinhood Chain	Dashboard Cashback tab shows token, amount, source, tx hash
Freeze (via X)	Backend reads twitterEnabled + limits from HoodAgent.sol	Virtual Card Provider freezeCard(cardId) → reply posted to X

Evidence

"Card secrets (number, CVV, expiry) are never stored on-chain. Only a keccak256 hash of your card ID is recorded as a tamper-proof link."
— tryHoodcard/hoodcard-contracts README, retrieved July 26, 2026

Contract header: "@title HoodAgent — Agentic RWA card onchain agent by HoodCard" · "@custom:platform HoodCard — hoodcard.cc" · Solidity ^0.8.0 · SPDX-License-Identifier: MIT
— HoodAgent.sol source, retrieved July 26, 2026

Findings — Limitations

No third-party smart contract security audit has been published as of the assessment date. HoodAgent.sol is MIT-licensed and publicly readable, but independent bytecode verification and formal security review have not been conducted.

Sources

Section 4.4

Deposit & Cashback Mechanisms

Deposit Flow

Users initiate top-ups via the Dashboard (Fund Card) or via X command (@tryhoodcard deposit $[amount] with [TOKEN]). The user sends a supported asset on Robinhood Chain. The Deposit Poller service monitors chain state, detects the incoming transaction, deducts the 3% flat fee, and credits the USD equivalent to the virtual card balance via the card provider API.

Table 4.4.1 — Deposit mechanism flow
Step	Actor	Action
1	User	Selects asset (ETH or RWA token) and amount in Dashboard or via X command
2	User Wallet	Signs and broadcasts ERC-20/ETH transfer on Robinhood Chain (4663)
3	Deposit Poller	Detects confirmed onchain deposit transaction
4	Backend API	Calculates net amount after 3% fee; calls Virtual Card Provider to credit balance
5	Backend API	Records transaction in PostgreSQL; triggers 2% fixed cashback if eligible
6	Dashboard	Displays top-up with status and onchain transaction hash

Cashback Mechanism

Table 4.4.2 — Cashback mechanism parameters. Source: docs.hoodcard.cc fees and cashback reference
Trigger	Rate	Delivery	Asset Selection
Card top-up	2% fixed	Direct to connected wallet on Robinhood Chain	One token from cashback pool (NVDA–NFLX)
Card spend	2%–5% randomized	Direct to connected wallet on Robinhood Chain	One token from cashback pool (NVDA–NFLX)

Fee Deduction Example

Table 4.4.3 — Worked deposit and cashback examples
Sent	Fee (3%)	Card Credited	Cashback (2% of sent)
$100 NVDA	$3.00	$97.00	$2.00 in tokenized stock
$200 ETH	$6.00	$194.00	$4.00 in tokenized stock

Evidence

"Send $100 worth of NVDA. The $3 fee is deducted, so your card receives $97. Eligible top-ups earn fixed 2% tokenized stock cashback."
— Fund your card, retrieved July 26, 2026

"A $200 top-up earns $4 worth of the selected stock token. A card transaction receives a randomly selected rate between 2% and 5%."
— Earn RWA cashback, retrieved July 26, 2026

Sources

Section 4.5

Security Model & Approval Flow

Overview

HoodCard implements a layered security model spanning wallet custody, onchain permission enforcement, session-gated card detail access, AI intent filtering, and configurable spending limits. No KYC or identity documents are collected; security relies on wallet private key ownership and onchain contract permissions.

Security Layers

Table 4.5.1 — HoodCard security model layers
Layer	Mechanism	Source
Wallet Custody	Non-custodial — HoodCard never holds user wallet assets; top-ups transfer onchain from user wallet	docs.hoodcard.cc security-and-privacy
Card Detail Protection	Card number, CVV, expiry hidden until active wallet session; copy controls provided	docs.hoodcard.cc use-your-virtual-card
Onchain Permissions	HoodAgent.sol enforces twitterEnabled, dailyLimitWei, maxPerCommandWei before any tweet command	hoodcard-contracts README
Identity Binding	Only the X account linked to wallet (via keccak256 hash) can trigger commands	hoodcard-agent README
Intent Filtering	OpenAI classifier; confidence must be ≥ 0.85 or command is silently dropped	hoodcard-agent README
Deduplication	Tweet IDs recorded in PostgreSQL — no command executes twice	hoodcard-agent README
Rate Limiting	Per-user cooldown prevents command flooding	hoodcard-agent README
Token Allowance	X-triggered deposits require pre-set ERC-20 allowance; cannot exceed allowance or Daily X Limit	docs.hoodcard.cc use-x-commands
Emergency Freeze	Immediate card freeze via Dashboard or @tryhoodcard freeze my card	docs.hoodcard.cc dashboard-and-activity

Approval Flow — X Command Execution

Table 4.5.2 — X command approval flow checks. Source: hoodcard-agent + hoodcard-contracts README
Check	Condition	Failure Action
Tweet deduplication	Tweet ID not previously processed	Silently skip
Intent classification	AI confidence ≥ 0.85 AND command recognized	Silently ignore
Account binding	twitterUserId matches linked wallet in database	Reject — no matching account
twitterEnabled	HoodAgent.sol twitterEnabled == true	Reply with reason — commands disabled
dailyLimitWei	Command value + daily total ≤ dailyLimitWei	Reply with reason — limit exceeded
maxPerCommandWei	Command value ≤ maxPerCommandWei	Reply with reason — per-command limit exceeded
Token allowance	(Deposits only) Sufficient ERC-20 allowance set for HoodAgent	Reply with reason — allowance insufficient
Per-user cooldown	Cooldown period elapsed since last command	Silently defer

Evidence

"Before any tweet command executes, the backend reads these directly from the contract: twitterEnabled (master switch), dailyLimitWei (max cumulative spend per day), maxPerCommandWei (max value per single command). If any check fails, the command is rejected and the user is notified via reply."
— hoodcard-contracts README — On-Chain Permission Model, retrieved July 26, 2026

Sources

Section 4.6

Platform Metrics & Usage Statistics

Overview

Public platform metrics are limited to data available from GitHub API, official documentation, and website metadata. HoodCard does not publish a public analytics dashboard or onchain TVL tracker at the time of this assessment. The following metrics are verifiable from independent public sources.

Publicly Verifiable Metrics

Table 4.7.1 — Publicly verifiable platform metrics
Metric	Value	Source	Retrieved
Supported funding assets	20 (ETH + 19 RWA stocks)	docs.hoodcard.cc/supported-assets	July 26, 2026
Cashback reward pool tokens	10 (NVDA through NFLX)	docs.hoodcard.cc/supported-assets	July 26, 2026
Documented X commands	8 commands	docs.hoodcard.cc/use-x-commands	July 26, 2026
Top-up fee	3% flat	docs.hoodcard.cc/fees-and-cashback-reference	July 26, 2026
Top-up cashback rate	2% fixed	docs.hoodcard.cc/earn-rwa-cashback	July 26, 2026
Spend cashback rate range	2%–5% randomized	docs.hoodcard.cc/earn-rwa-cashback	July 26, 2026
Default Daily X Limit	$100 / 24 hours	docs.hoodcard.cc/create-your-hoodcard	July 26, 2026
Default maxPerCommandWei	50 USD equivalent	hoodcard-contracts README	July 26, 2026
Cards per wallet	1 (hard limit)	docs.hoodcard.cc/create-your-hoodcard	July 26, 2026
Documentation pages	15 pages	docs.hoodcard.cc/llms.txt	July 26, 2026
Public GitHub repositories	3 (hoodcard, hoodcard-agent, hoodcard-contracts)	github.com/tryHoodcard	July 26, 2026
GitHub repository license	MIT (all 3 repos)	GitHub API	July 26, 2026
GitHub repo creation date	July 25, 2026	GitHub API	July 26, 2026
GitHub stars (all repos)	0 at time of review	GitHub API	July 26, 2026
Robinhood Chain ID	4663	docs + GitHub	July 26, 2026

Metrics Not Publicly Available

The following metrics were not found in public documentation, GitHub repositories, or website metadata at the time of assessment: total cards issued, total transaction volume, total cashback distributed, active user count, total value locked (TVL), and revenue figures. Users seeking these metrics would need to query Robinhood Chain Blockscout for onchain contract deployment counts or request data from HoodCard support via Telegram.

Sources

Section 4.7

Performance Benchmarks

Overview

Performance characteristics documented across official sources include card issuance time, top-up confirmation latency, Twitter agent polling interval, AI intent classification threshold, and gas requirements for onchain vs offchain operations.

Table 4.8.1 — Documented performance benchmarks and operational parameters
Operation	Documented Performance	Source
Card issuance	Under 30 seconds (wallet connect → card issued)	github.com/tryHoodcard/hoodcard README
Top-up confirmation	Seconds to a few minutes after Robinhood Chain tx confirmation	docs.hoodcard.cc/fund-your-card
Twitter mention polling	Every 30 seconds	github.com/tryHoodcard/hoodcard-agent README
AI intent classification threshold	Confidence ≥ 0.85 required for execution	hoodcard-agent README
Card spending gas cost	No onchain gas payment required	docs.hoodcard.cc/use-your-virtual-card
Onchain actions gas cost	ETH required on Robinhood Chain (deploy, deposits, token transfers)	docs.hoodcard.cc/connect-your-wallet
HoodAgent deployment	Single onchain transaction at card creation; viewable on Blockscout	hoodcard-contracts README
X command deduplication	Tweet ID recorded in PostgreSQL — zero double-execution	hoodcard-agent README
Per-user command cooldown	Enforced to prevent flooding (exact duration not published)	hoodcard-agent README

Evidence

"Connect your wallet, issue a card in under 30 seconds, fund it with ETH or tokenized stocks."
— hoodcard README, retrieved July 26, 2026

"Top-ups process after Robinhood Chain confirms the deposit. Most complete within seconds to a few minutes."
— Fund your card, retrieved July 26, 2026

"The listener polls Twitter every 30 seconds and logs all processed mentions."
— hoodcard-agent README — Local Setup, retrieved July 26, 2026

Sources

Section 4.8

Public GitHub Resources

Overview

HoodCard maintains three public MIT-licensed repositories under the tryHoodcard GitHub account. Official documentation links to GitHub via the FAQ page (github.com/tryhoodcard redirect).

Table 4.9.1 — Public GitHub repositories. Source: GitHub API, retrieved July 26, 2026
Repository	Description	Language / Stack	License
hoodcard	RWA-backed virtual Visa card web application — spend tokenized stocks, earn RWA rewards	React 18, TypeScript, Vite, Privy, viem, TanStack Query, Three.js	MIT
hoodcard-agent	Twitter/X agent for @tryhoodcard — control virtual card via tweets using on-chain permission checks	Node.js, TypeScript, OpenAI, PostgreSQL	MIT
hoodcard-contracts	HoodAgent.sol — autonomous on-chain card agent deployed per user on Robinhood Chain (ID 4663)	Solidity ^0.8.0	MIT

Repository Topics (GitHub Tags)

Table 4.9.2 — GitHub repository topic tags
Repository	Topics
hoodcard	blockchain, defi, privy, react, robinhood-chain, rwa, typescript, virtual-card, vite
hoodcard-agent	defi, nodejs, onchain-agent, openai, robinhood-chain, twitter-bot, typescript, x-agent
hoodcard-contracts	defi, ethereum, onchain-agent, robinhood-chain, rwa, smart-contracts, solidity

Key Open-Source Artifacts

Table 4.9.3 — Key open-source artifacts available for independent review
Artifact	Path	Significance
HoodAgent.sol	hoodcard-contracts/contracts/HoodAgent.sol	Core onchain agent contract — auditable permission model
Web App Source	hoodcard/ (React + Vite project)	Frontend implementation with Privy wallet integration
Twitter Bot Source	hoodcard-agent/ (Node.js project)	Intent classification and command execution logic
.env.example	All three repos	Documents required environment variables for local deployment

Evidence

"Explore HoodCard's official GitHub presence." — Link: github.com/tryhoodcard
— FAQ and social links, retrieved July 26, 2026

Sources

Section 4.9

Onchain Verification & Independent Data Sources

Overview

HoodCard operations on Robinhood Chain are independently verifiable through the block explorer, open-source smart contract code, Dashboard transaction hashes, and contract metadata labels. Users and auditors can confirm agent deployments, X account linking events, and cashback token transfers without relying on HoodCard's backend.

Independent Verification Methods

Table 4.10.1 — Independent onchain verification methods
Verification Target	Method	Independent Source
HoodAgent contract deployment	Search wallet address on Blockscout → view deployed HoodAgent contract	explorer.robinhood.com
Contract source code	Compare deployed bytecode against HoodAgent.sol on GitHub	github.com/tryHoodcard/hoodcard-contracts
Platform label on explorer	Contract displays PLATFORM_LABEL = "Agentic RWA card onchain agent by HoodCard"	HoodAgent.sol source + Blockscout
Top-up transaction	Dashboard shows onchain tx hash → verify amount, asset, and confirmation on Blockscout	Dashboard + Blockscout
Cashback delivery	Dashboard Cashback tab shows token, amount, and tx hash → verify onchain receipt	Dashboard + Blockscout
X account linking event	Search HoodAgent contract for XAccountLinked event emission	Blockscout event logs
Permission settings	Read twitterEnabled, dailyLimitWei, maxPerCommandWei directly from contract (view functions)	HoodAgent.sol agentInfo() + Blockscout
Card ID linkage	Verify cardIdHash (keccak256) matches without exposing raw card number	HoodAgent.sol onchain state

Robinhood Chain Parameters

Table 4.10.2 — Robinhood Chain verification parameters. Sources: docs + hoodcard-contracts README
Parameter	Value
Network	Robinhood Chain
Chain ID	4663
Native currency	ETH
Token standard	ERC-20
RWA assets	19 tokenized stocks
Block explorer	explorer.robinhood.com (Robinhood Chain Blockscout)
Contract visibility	Yes — PLATFORM_LABEL metadata visible on Blockscout

Verification Workflow for Auditors

Table 4.10.3 — Recommended independent audit verification workflow
Step	Action
1	Obtain wallet address from HoodCard Dashboard or user
2	Search address on explorer.robinhood.com for HoodAgent contract deployment tx
3	Verify contract bytecode against MIT-licensed HoodAgent.sol on GitHub
4	Read onchain state: owner, agentName, cardIdHash, xAccountHash, limits
5	Cross-reference Dashboard tx hashes with Blockscout confirmation status
6	Verify cashback token receipts in wallet transaction history on Chain 4663
7	Confirm PLATFORM_LABEL and PLATFORM_URL constants match hoodcard.cc

Evidence

"Each HoodAgent is unique to a wallet and visible on Robinhood Chain Blockscout."
— Set up HoodAgent, retrieved July 26, 2026

"Block explorer: explorer.robinhood.com. Visible on Blockscout: Yes — PLATFORM_LABEL in contract metadata."
— hoodcard-contracts README — Chain Details, retrieved July 26, 2026

"Top-ups with status and onchain transaction hash. Cashback associated with eligible activity shows token, amount, source, and onchain transaction hash."
— Dashboard and activity, retrieved July 26, 2026

Sources

Section 5.0

AI-Assisted Review Notes

During drafting, each AI tool was prompted to review specific sections for factual consistency against cited public sources. These are internal review notes — not endorsements, certifications, or independent audit opinions.

Cursor

Drafting & assembly

"Report cites primary sources for each feature claim. Screenshot figures are dated July 26, 2026. Flagged: Section 2.3 previously contradicted visual evidence section — corrected in v1.1."

Note: Structural consistency improved. Not a product endorsement.

Claude

Security & ratings review

"Security model section matches hoodcard-agent README. Permanent X binding is correctly flagged as a limitation. Fee transparency is rated 7.8 — disclosure is documented, but the 3% fee itself remains a user concern and actual charged amounts were not verified. HoodAgent.sol variable names match GitHub source."

Note: No factual errors found in cited claims. Security score reflects documentation quality, not a formal audit.

Ollama

Contract text check

"HoodAgent.sol fields (owner, cardIdHash, xAccountHash, dailyLimitWei, maxPerCommandWei, twitterEnabled) match published GitHub source. Cannot confirm deployed bytecode matches this source without an onchain audit. Chain ID 4663 consistent across docs."

Note: Source text verified. Deployment verification left to reader via Blockscout.

Qwen

Data table check

"Fee table ($50→$48.50, $100→$97, $500→$485) matches docs.hoodcard.cc. Asset count (20) correct. GitHub repos created July 25, 2026 with 0 public stars — report should note early-stage status. TVL and total user count correctly marked as unavailable."

Note: Published numbers match docs. Early-stage GitHub metrics added as limitation.

Table 5.1 — AI-assisted review notes (not independent audit results)
Tool	Review Focus	Outcome	Limitation
Cursor	Source citations & internal consistency	Issues flagged and fixed in v1.1	Author of the report itself
Claude	Security claims vs. GitHub README	No mismatches in cited text	Not a security auditor
Ollama	HoodAgent.sol source text	Variables match GitHub file	No bytecode/deployment check
Qwen	Fee tables & asset lists	Matches official docs	No live API or backend access

Section 6.0

Score Summary Matrix

The following table summarizes assessment ratings across all twelve feature categories. Each category received equal weight (1/12) in calculating the composite score of 7.2.

Scoring Methodology Note

Ratings measure documented transparency and feature completeness based on public sources — not live product performance or user satisfaction. Sections 1–4 (onboarding: wallet, chain, creation, funding) scored lower (5.8–6.7) because they involve user-managed complexity: network switching, mandatory initial deposit, 3% fee impact, and one-card-per-wallet limits. Sections 5–12 (spending, cashback, security, agents) scored 7.4–8.0 because HoodCard's published documentation and open-source contracts are available, but live product behavior, cashback delivery, smart contract audits, and third-party card issuer operations were not independently verified. This spread produces an overall 7.2 — not a uniformly high score across all categories.

Table 6.1 — Feature assessment score summary. Composite: 7.200 (displayed as 7.2). Sections 1–4 scored 5.8–6.7 (onboarding); Sections 5–12 scored 7.4–8.0 (documentation-only verification).
#	Feature Category	Rating	Weight
1	Wallet Connection & Identity	6.4	1/12
2	Robinhood Chain Integration	6.1	1/12
3	HoodCard Creation	5.8	1/12
4	Card Funding / Top-up	6.7	1/12
5	Virtual Visa Card Usage	7.6	1/12
6	Dashboard & Activity	7.5	1/12
7	RWA Cashback Rewards	7.5	1/12
8	Supported Assets	7.8	1/12
9	Fees Transparency	7.8	1/12
10	HoodAgent Setup	7.4	1/12
11	X Commands	7.8	1/12
12	Security, Privacy & Support	8.0	1/12
Composite Assessment Rating		7.2 / 10	86.4 ÷ 12 = 7.200

The composite rating of 7.2 out of 10 reflects documentation-quality assessment with explicit acknowledgment of unverified live behavior. Early-stage features (Sections 1–4) scored 5.8–6.7 reflecting onboarding complexity, while advanced features (Sections 5–12) scored 7.4–8.0 reflecting published documentation availability without independent product or audit verification.

Section 7.0

References

All sources cited in this report. Retrieval date for all documentation sources: July 26, 2026.

Official Website

hoodcard.cc — HoodCard official website

Documentation Index

docs.hoodcard.cc/llms.txt — Complete documentation index

Official Channels

HoodCard on X — @tryhoodcard — Official X account (x.com/tryhoodcard) for product updates, live demos, and HoodAgent commands
Telegram support — @tryhoodcard — Official support channel (t.me/tryhoodcard)

Public GitHub Repositories

github.com/tryHoodcard/hoodcard — Web application (React + Vite + Privy)
github.com/tryHoodcard/hoodcard-agent — Twitter/X command agent
github.com/tryHoodcard/hoodcard-contracts — HoodAgent.sol smart contract
HoodAgent.sol source — Onchain agent contract

Onchain & Independent Sources

explorer.robinhood.com — Robinhood Chain Blockscout explorer

— End of Report —