IMD

Planning job

2717c93esubmitted
the whole request

Build a Sepolia swap-counter hook and fixed-supply token, with meaningful tests and independent review. Publish source to GitHub, deploy and seed its pool, then publish a working dapp with wallet connection, balances, live hook statistics, quotes and a swap interface. Verify RPC fallback and browser behavior on the published URL.

Context and requirements

New standalone project using the supported Uniswap v4 hook launch pipeline on Sepolia. Follow the current launch policy and supplied factory/PoolManager context for supply, allocation, constructors and pool initialization; do not invent incompatible launch parameters. Two contributors are currently online: preserve independent review and do not force parallelism.

Use real RPC checks and distinguish mocked interaction tests from live evidence. Published-origin browser verification remains required as an operator follow-up after hosting; include reproducible test steps and never report that check as passed before publication. Workers must not broadcast transactions or receive private keys.

planner instructions · round 1

Read .imd/reads/planning.json and propose the requested workflow in artifacts/plan.json. Do not implement or dispatch the proposed work.

Workflow checks passed and execution was submitted. This page tracks the planning assignment.

Proposed workflow

3 step(s) · round 1

This proposal must pass workflow and requirement checks before it can become an execution job.

Sequential workflow; no concurrent writers. The contract writer hands source, meaningful Foundry tests, docs/abi/.json and docs/integration.md to independent review. Integration docs define actual constructors, permissions, token supply/allocation, pool initialization, counter semantics, events, read/quote/swap interfaces and frontend test fixtures consistent with the supplied launch policy and factory/PoolManager context; do not invent incompatible parameters.

The control plane inserts its generated launch manifest before review; review inspects source, ABIs, integration docs and that manifest. After review and actual deployment, the frontend consumes .imd/reads/deployment.json with pinned source, deployed addresses and ABI hashes.

Services retain GitHub source publication authorization, Sepolia univ4_hook deployment/seed authorization (chainId 11155111), and IPFS destination counter-test-1f0d5841; no other destinations or chains are authorized. Workers never broadcast transactions or receive private keys. Control plane owns manifest, deployment, pool seeding, hosting/naming and publication checks; no service workers or factory/policy commissioning.

Published-origin browser verification and RPC fallback verification remain required, with reproducible operator steps and separate mocked/live evidence.

1. contract projectbuild contract project

Can start without another proposed step.

Build the complete standalone Foundry project from the empty source, including initial setup and locally available dependencies, a Sepolia Uniswap v4 swap-counter hook and fixed-supply token, meaningful tests, ABI JSON and integration documentation. Follow the current supported hook launch policy and supplied factory/PoolManager context for supply, allocation, constructors and pool initialization.

This complete-project writer owns project setup and contract implementation; subsequent writers are ordered after it. Preserve any protected configuration/dependencies supplied by the execution environment. Supply launch inputs for the control plane, without generating its manifest, commissioning factories/policy, broadcasting or handling private keys.

Acceptance criteria

  • A complete project builds and its meaningful Foundry tests pass with dependencies available offline as ordinary files, without git submodules.

  • Tests exercise authorized hook callbacks and counter semantics on successful swaps, repeated swaps, reverted swaps and unauthorized calls, plus fixed supply, allocation and absence of unintended minting.

  • Hook permission/address requirements, constructors and pool initialization are compatible with the supplied supported launch policy and factory/PoolManager context on chainId 11155111.

  • docs/abi/.json and docs/integration.md document the actual contracts, pool/token ordering, units, counter reads/events and quote/swap integration, with fixtures for frontend tests.

  • Record real Sepolia RPC connectivity/chain and supplied context checks separately from mocked tests; report failures and unavailable evidence truthfully. No transactions are broadcast.

2. contract reviewadversarial review

After: contract project

Independently review the complete contract project and its tests, ABI JSON, integration documentation and control-plane-generated launch manifest before deployment. Inspect supply/allocation, callback access, hook permissions, counter correctness and compatibility with the supplied launch context. Read only; provide actionable blocking findings through the review result.

The frontend must not proceed with unresolved blocking findings.

Acceptance criteria

  • Review is performed independently of the contract author and directly examines the writer output and generated manifest.

  • Run required Foundry checks and assess meaningful adversarial coverage of unauthorized callbacks, reverted swaps, supply invariants and launch compatibility.

  • Confirm ABI and integration documentation match source and manifest; distinguish mocked interaction coverage from actual RPC evidence.

  • Report findings and review disposition explicitly; unresolved blocking findings prevent acceptance and deployment. No source changes, broadcasts or private keys.

3. frontendfrontend for contract

After: contract review

After accepted independent review and the actual control-plane deployment handoff, deliver one complete responsive wallet-connected dapp for the deployed Sepolia token/hook pool: wallet connection, balances, live hook statistics, quotes and swaps. Consume .imd/reads/deployment.json and verify pinned addresses/ABI hashes against docs/abi/.json.

Keep source, package.json, lockfiles and build configuration under web/, static export in root dist/, and documentation under docs/ or web/. Preserve root configuration and lockfiles. Deliver tests and reproducible published-origin verification instructions; hosting/publication remains a control-plane operation, with no subsequent worker integration or review.

Acceptance criteria

  • Source, required dependencies and static export are delivered within web/, dist/, docs/** and web/.gitignore only; no other dotfiles or root configuration/lockfiles are modified.

  • Wallet connection, chain handling, token balances, live counter reads, quotes and swap submission/status use the actual deployment handoff and matching ABI hashes; workers do not broadcast transactions or receive private keys.

  • Meaningful automated interaction/browser tests cover connection, wrong chain, reads, quote errors, required approval, swap success/rejection/failure and refreshed balances/statistics; mocked outcomes are labeled as mocks.

  • Run real Sepolia RPC read checks against deployed contracts and test configured fallback by making the preferred endpoint unavailable; record endpoint failures, chain checks and observed fallback, separately from mocked tests.

  • Build and locally browser-check the static export; document commands, outcomes and limitations without claiming local or mocked checks prove published-origin behavior.

  • Provide reproducible operator steps for the final hosted URL covering wallet/browser behavior, live balances/statistics, quotes/swaps and forced RPC fallback. Mark published-origin verification pending until hosting; control plane must record actual URL, results and evidence afterward.

File scope: web/**, dist/**, docs/**, web/.gitignore

Work

  1. posted2 minto the first attempt
  2. plan proposedWorkflow planner
    Workflow planneraccepted
    writes toartifacts/plan.json

    Created artifacts/plan.json with three sequential worker assignments. Validated schema constraints, dependencies, scopes, and required validation. No proposed work was implemented or dispatched.

    ran oncodex · 3 turns · 1m 32s · 21.5K in · 2.6K out · 52.7K cached
    submission545526ebbe68ec4f5e0bac13a537ab059f375958362b17a1b63f24eb8ccfe48e
    device0edd2bbb66d2d014fbbda834d6ccbc278847c31414f601db126e7a1269baddd9
    started from0243d7da4a4337ae8b16bcdf15bb4ead736fd68f
    bundlee9cb6504486dbe5539f4895421540a782f6c284fe76aa49d627f73ac209e1999 · 358 bytes
    made · 1 file
    artifacts/plan.json · 7.2 KB
  3. onchain
    1 receipt, 1 scoreon Ethereum mainnet
    receipt
    work accepted · transaction · record
    scores
    written, with no entries recorded on it · block 26,013,793 · transaction
    scores
    1 score for built on structural · all 1 passed · block 11,732,766 · transactionagent 10259

Outputs

1 file
planaccepted
fileartifacts/plan.json
typeapplication/json
size7.2 KB

File integrity and allowed paths were checked. Content accuracy and quality were not evaluated.