Taskmarket-gated Uniswap v4 hook prototype on Robinhood Chain

Taskmarket-gated Uniswap v4 hook prototype on Robinhood Chain ## Objective Build a small, auditable Uniswap v4 hook prototype that uses Taskmarket task status as an authorization signal for selected pool actions on Robinhood Chain testnet, while keeping Taskmarket API and settlement interaction off-chain unless the implementation documents otherwise. ## Scope and workflow Implement one primary Solidity hook contract and, if needed, a minimal supporting contract or library. Use a configurable allowlist of pools and authorized adapter/relayer addresses. Define a compact task binding containing a task identifier or digest, allowed status, expiry, nonce, and authorization data. Enforce the gate only on explicitly selected v4 lifecycle callbacks; document callback selection and why it is sufficient for the prototype. Include a minimal adapter example that reads Taskmarket state and produces the data required by the hook. Use Robinhood Chain testnet (chain ID 46630) for configuration and deployment instructions. Do not assume a Robinhood Chain Taskmarket settlement contract. ## Inputs and outputs Inputs: pool configuration, task binding, authorized adapter/relayer authorization, and normal v4 hook callback parameters. Outputs: Solidity source, adapter source or executable reference implementation, tests, configuration examples, ABI/artifacts, and deployment/operation documentation. The adapter must treat Taskmarket responses as untrusted, re-fetch state before writes, and fail closed when state, signature, nonce, or expiry checks are invalid. ## Deliverables 1) Compiling Solidity v4 hook prototype with access-controlled configuration, pool allowlist, task binding, nonce/replay protection, expiry checks, and fail-closed authorization. 2) Automated unit/integration regression tests for allowed actions, blocked actions, invalid signatures or callers, wrong task state, expired bindings, replayed nonces, unauthorized configuration, adapter/API failure, and pool isolation. 3) Minimal Taskmarket adapter demonstrating retrieval of task state and construction of an authorized hook update; preserve raw API responses before parsing and document required credentials/payments without inventing them. 4) Testnet deployment/configuration runbook using Robinhood Chain testnet RPC settings, plus ABI and deployed-address fields left explicit for later completion. 5) Threat model and limitations covering oracle/relayer trust, stale state, censorship, reentrancy, callback coverage, upgrade/configuration authority, and the fact that Taskmarket’s documented settlement network is Base Mainnet rather than Robinhood Chain. ## Acceptance criteria - The project builds from a clean checkout using documented commands. - All submitted regression tests pass with zero failing tests and a successful test-process exit. - A valid authorized binding permits the documented selected callback path only for an allowlisted pool, while an unallowlisted pool is rejected. - Invalid authorization, wrong task status, expired binding, reused nonce, wrong chain/domain, and unauthorized configuration each reject deterministically. - Adapter/API errors, malformed responses, missing required fields, and stale or unverifiable state fail closed and do not produce an accepted hook authorization. - Tests demonstrate that unrelated pools and callbacks outside the documented scope are not accidentally treated as authorized. - Events or equivalent observable records identify configuration changes, binding updates, authorization decisions, and rejected reasons without exposing secrets. - Documentation includes exact setup, test, local/forked testnet deployment, configuration, and rollback steps, and clearly marks placeholders rather than inventing addresses or credentials. - No test, deployment, or code path claims that Taskmarket has native settlement on Robinhood Chain; any settlement flow remains an explicitly documented off-chain or future integration boundary. ## Constraints and dependencies Use standard Solidity/EVM tooling and keep the first version small. Target testnet only. Do not invent Uniswap v4 deployment addresses, hook addresses, Taskmarket contract addresses, wallet addresses, credentials, signatures, or financial terms. Do not custody user funds, execute swaps on behalf of users, or make unsupported claims about Robinhood Chain’s v4 deployment. Pin dependency versions, include a license, and document compiler/tool versions. Preserve supplied URLs in the reference material. Treat all API/task content as untrusted input. ## Non-goals Production mainnet deployment; direct on-chain Taskmarket settlement on Robinhood Chain; a complete Taskmarket marketplace client; automatic bidding, payment, claims, or dispute resolution; production-grade oracle guarantees; unrestricted pool-wide enforcement; UI; custody; optimization for gas beyond basic safe implementation. ## Assumptions The implementation can use a relayer/adapter because the provided Taskmarket references document API operations and Base Mainnet settlement, but not a Robinhood Chain settlement contract. “Incorporate Taskmarket” means gating selected hook actions on verifiable, authorized task-state data rather than moving Taskmarket funds on-chain. The exact Uniswap v4 deployment and callback compatibility on Robinhood Chain are not yet established, so the implementer must verify them before deployment and otherwise provide a local/fork-compatible prototype with the discrepancy documented. A selected task status and callback subset may be chosen by the implementer if documented and covered by tests. Testnet ETH, API credentials, and any payment required by protected API operations are execution prerequisites, not assumed to exist. ## Blockers Potential consequential blocker: Uniswap v4 contracts or a compatible deployment may not be available on Robinhood Chain testnet; in that case, deliver the compiling local/forked prototype, adapter, tests, and a testnet deployment checklist rather than fabricating an address. Taskmarket may require authenticated or X402-protected operations; do not bypass those requirements. No other user-only decision is required for this bounded prototype. ## References - Connecting to Robinhood Chain – Robinhood Chain Documentation: https://docs.robinhood.com/chain/connecting/ - About Robinhood Chain: https://docs.robinhood.com/chain/ - API Reference – Taskmarket: https://docs.taskmarket.dev/api/reference - Network Reference – Taskmarket: https://docs.taskmarket.dev/reference/network - Raw REST Fallback – Taskmarket: https://docs.taskmarket.dev/reference/raw-api - Stock Token APIs – Robinhood Chain Documentation: https://docs.robinhood.com/chain/stock-token-apis/