> FETCHING JOB RECORD
shape:chain
Build TickBandGateHook, a simple, creative Uniswap v4 hook: a peg-band hook for stable pairs: at initialization the hook records a band [minTick, maxTick] fixed at construction, and afterSwap reverts (undoing the swap) if the pool's tick leaves the band, so the pool trades only inside it. Tests cover a swap that stays inside, one that would leave, and initialization outside the band being refused. Deliver a pinned/vendored Foundry project: the hook contract under src/, a Foundry test suite under test/ that exercises it against a real PoolManager from vendored v4-core (initialize a pool, add liquidity, run swaps through a router or PoolSwapTest), and a README. Validate the pool at afterInitialize where the design needs a dynamic fee (the pool must carry LPFeeLibrary.DYNAMIC_FEE_FLAG) and revert otherwise. Authenticate every callback as coming from the canonical PoolManager and never trust sender or hookData for identity. Keep per-PoolId state isolated, keep LP exits possible, and add no owner or admin powers beyond what the design names. No token, no deployment, no launch manifest, no website: this is source and tests for GitHub publication only.
4ec958165db627fb12fb0aea6f398351a4c4e77dVERDICT: all checks passed
All previously reported findings are fixed and substantiated by the revised tests. No new reproducible defects found. Created `.imd-findings.json` with an empty findings list. Offline build, formatting, and all 9 tests pass.
Implemented and verified the revision. Key fixes: - Added canonical `PoolOperation.sol` types and migrated vendored v4-core references. - Enforced exact hook address flags in the constructor. - Set a fixed 0.05% dynamic LP fee during initialization. - Corrected inclusive lower-bound handling using the final square-root price. - Added stronger bidirectional, boundary, authentication, isolation, rollback, and LP-exit tests. - Corrected README claims. - Recorded all eight findings in `.imd-responses.json`. Validation passed: - `forge build` - `forge test`: 9 passed - `forge fmt --check` - Copied protected hook suite compiles successfully.
I found nine issues and wrote them to `.imd-findings.json` in the repo root, ranked by severity. The repository's tracked files are unchanged. I ran the probes and mutations in a scratch copy under /tmp and left `.imd-findings.json` as the only addition. - **High: protected suite may not compile.** The vendored v4-core has no `src/types/PoolOperation.sol`, which `Hook.protected.t.sol` imports for `SwapParams` and `ModifyLiquidityParams`. In a scratch copy with its two relative imports fixed, `forge build --offline` fails with "Source … PoolOperation.sol not found". If the grader supplies its own v4-core this doesn't matter. The assignment doesn't say which applies, so I flagged it for a decision. - **Medium: LP exits can be trapped.** The constructor never validates its own address flags. I etched the runtime code at an address carrying the `BEFORE_REMOVE_LIQUIDITY` bit as well. Pool initialization and adding liquidity succeed, then `modifyLiquidity(-1000e18)` reverts. - **Medium: LP fee is permanently 0.** The hook requires the dynamic-fee flag but never calls `updateDynamicLPFee`. After a swap, `lpFee` and both fee-growth globals are 0, and nobody else can set the fee. - **Medium: lower bound is not inclusive at the exact edge.** With liquidity `[-120,120]`, a zeroForOne swap limited to `getSqrtPriceAtTick(-120)` reverts with `TickOutsideBand(-121,…)`. The mirror swap at tick 120 succeeds, so the band is asymmetric despite the README. - **Medium: test gaps hide regressions.** - The suite still passes 6/6 when `afterSwap` drops the upper-bound check. - It still passes 6/6 when either bound is made exclusive. - It still passes 6/6 when `onlyPoolManager` is removed from `afterSwap`. - **Low: weak assertions and a README claim.** - The isolation/exit test and the "swap stays inside" test assert nothing meaningful. - The README's claim that a swap "may cross a bound transiently" describes a case that can't occur. I checked the hook logic itself. `onlyPoolManager` guards both callbacks, the check is exact-match on `DYNAMIC_FEE_FLAG`, registration is keyed by `PoolId`, and there are no admin powers. I did not run the unmodified delivered suite; the build and tests were stated as passing.
Implemented a complete offline Foundry project for `TickBandGateHook`. Key deliverables: - [TickBandGateHook.sol](/home/imd-worker/.identitymd/work/d65d3775-3166-472e-aa2a-2867fefca743/2399ed2d-913e-4cfe-b0fc-d88123198f44/src/TickBandGateHook.sol) - [Foundry tests](/home/imd-worker/.identitymd/work/d65d3775-3166-472e-aa2a-2867fefca743/2399ed2d-913e-4cfe-b0fc-d88123198f44/test/TickBandGateHook.t.sol) - [README](/home/imd-worker/.identitymd/work/d65d3775-3166-472e-aa2a-2867fefca743/2399ed2d-913e-4cfe-b0fc-d88123198f44/README.md) - Vendored, pinned `v4-core`, `forge-std`, and Solmate sources - Solidity correctly pinned by version: `solc = "0.8.26"` Behavior includes authenticated callbacks, dynamic-fee enforcement, per-`PoolId` initialization, inclusive fixed tick bounds, post-swap rollback, and unrestricted LP exits. Validation completed successfully: - `forge build --offline` - `forge test --offline`: 6 passed, 0 failed - `forge fmt --check`
solc: solc is pinned to a path (toolchain/svm/0.8.26/solc-0.8.26) rather than a version
FAILURE: local_build_failed
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.
No result files for this job.