Infrastructure built to scale.

HoodStack is a Robinhood Chain-native developer infrastructure stack for accounts, transaction orchestration, gas sponsorship, token utilities, chain data, automation, and production application development.

CA: 0x690145b6952fbe1eb90b5b98dffd6cd7622ce538

Website · X · GitHub · Security

HoodStack is an independent developer infrastructure project and is not affiliated with, endorsed by, sponsored by, or operated by Robinhood Markets, Inc. or its affiliates. Robinhood and Robinhood Chain are trademarks of their respective owners.

Early access. The table below is the authoritative record of what is implemented. Everything else in this document describes intended architecture.

The Data module is enabled and backed by a live API; every other module is preview until its implementation ships. Sign-in, projects, API keys, and the gateway are working end to end.

Not yet audited. No token has launched and no token contract has been deployed. Use test keys for production-critical flows until mainnet readiness is announced. Do not use this to secure funds you cannot afford to lose.

HoodStack is broader than wallet-as-a-service. Wallet infrastructure is one layer.

Identity - authentication · embedded accounts · passkeys · recovery · identity linking · device and session management

Execution - transactions · batch execution · simulation · smart accounts · session keys · delegated execution · contract calls

Gas - sponsorship · paymaster policies · budgets · analytics · abuse controls

Assets - token utilities · canonical asset registry · stock-token metadata · balances and allowances · transfers and approvals · asset verification

Connectivity - chain data · webhooks · event streams · RPC routing · transaction history · indexed activity

Automation - agent accounts · agent policies · workflows · scheduled execution · treasury automation · subscription permissions

Security - spending policies · contract and recipient allowlists · risk checks · audit logs · security events · emergency controls

Developer platform - TypeScript, React, and server SDKs · CLI · REST API · playground · dashboard · examples · OpenAPI

Network coordination - usage credits · developer capacity · gas entitlements · operator bonding · agent collateral · ecosystem incentives · governance · token utility

Every module has a permanent route from the first release. Implementation grows behind stable interfaces - see ADR 0006.

Requires Node 20.11+ and pnpm 10+.

git clone https://github.com/hoodstack/hoodstack.git
cd hoodstack
pnpm install
pnpm build
pnpm test
pnpm typecheck
pnpm lint

Run the platform application locally:

pnpm --filter @hoodstack/platform dev
# http://localhost:3000

Copy .env.example to .env for local configuration. .env is gitignored, and .env.example contains placeholders only.

import {
  robinhoodTestnet,
  assertChainMatches,
  assertWriteAllowed,
  getExplorerTxUrl,
} from "@hoodstack/network";

// Reject a wallet on the wrong network before anything is signed.
assertChainMatches(await wallet.getChainId(), robinhoodTestnet);

// Mainnet writes are closed by default; enabling them is an explicit act.
assertWriteAllowed(robinhoodTestnet, { allowMainnetWrites: false });

getExplorerTxUrl(robinhoodTestnet, txHash);

Chain definitions extend viem's Chain, so they pass directly to createPublicClient, wagmi, or any viem-compatible tooling.

Testnet is the default everywhere. Testnet ETH is available from the faucet.

Public RPC endpoints are rate-limited and shared. They are fine for local development; in production HoodStack refuses to fall back to them rather than degrade silently under load.

HoodStack does not operate RPC infrastructure, a bundler, paymaster liquidity, an indexer, or MPC/HSM custody. Each is a third party behind an adapter that normalizes it into stable interfaces.

Planned: ui, accounts, auth, transactions, gas, tokens, data, webhooks, usage, credits, sdk, server, react, cli, database, logging, testing.

Directories are created when their contents are actually built, rather than committed empty.

• System overview - layers, dependency graph, request path
• Architecture decisions - ADRs 0001-0006
• Threat model
• Key management
• Incident response
• Responsible disclosure
• Module activation

Phase 1 (current) - platform, dashboard, versioned API, testnet account abstraction, transactions and simulation, gas policies, tokens, data, webhooks, usage and credits, SDKs, CLI, documentation, examples. Completed before any token launch.

Phase 2 - token staking for developer capacity, gas entitlement adapter, advanced session keys, programmable spending policies, team roles, agent accounts and budgets, React Native SDK.

Phase 3 - infrastructure operator network, bonded bundlers and paymasters, simulation and security marketplaces, agent reputation, enterprise organizations, compliance adapters.

Phase 4 - decentralized execution marketplace, cross-chain accounts, intent-based execution, governance activation, selective multi-chain expansion.

Robinhood Chain remains HoodStack's primary identity throughout.

Report vulnerabilities privately - see SECURITY.md. Do not open a public issue for a security problem.

HoodStack has not been audited and makes no claim to be bank-grade, military-grade, unhackable, battle-tested, or institutional-grade.

Properties the codebase is built around: no key custody and no ability to move user funds; tenant isolation; no server secret reachable from a browser bundle; chain ID validated before signing and before submission; non-idempotent operations never retried automatically; fail-closed gating; errors that never carry stack traces, SQL, credentials, or tenant data across a trust boundary.

Contribution guidelines are being written alongside M3. Until then, open an issue before starting substantial work.

HoodStack is an independent project, not affiliated with Robinhood Markets, Inc.

• HoodStack does not provide brokerage services.
• HoodStack does not provide investment advice.
• Asset availability may depend on jurisdiction.
• Developers remain responsible for their own legal and compliance obligations.
• Token utility documentation is technical architecture, not an offer.
• The HoodStack token has not launched. Any claim otherwise is not from us.

Apache-2.0