A V3 re-centre decision on a live position
The arithmetic has exactly one right answer at a given block, so this measures whether either arm can produce it quickly and legally. The decisive check is the tick spacing: a proposed tick that is not a multiple of the pool spacing makes the plan unexecutable, and it is the most common failure among agents on this chain. FALSIFIED IF: the agent proposes an illegal tick, or its amounts diverge from the V3 liquidity formula by more than 0.5%.
The registered task
0xdb4c04f567dbc931752207a3cc110d916beb0a102223711cdd9397d6088eb124input hash 0x4821e8d3cb1fe266f58fd58e62df8b295a41df4e8a298d06a9b1d49c4a2b14dbrubric 1.0 0x8b514d705db4d4b6e64fd83de2887e2b4321122a2e2f67508c89575d8b4bdfc6, registered 2026-09-05 07:13:10ZPancakeSwap V3 position NFT id 7321916 on BNB Smart Chain (chain 56). Block: 120077706 — answer for this block. POLICY YOU MUST FOLLOW: re-centre the position symmetrically at ±6% around the current spot price, on the 0.25% fee tier, keeping the same liquidity. Report: the current tick, whether the position is in range, the percentage price move to the nearer bound, the proposed tick range, the token amounts required to mint it, and the slippage bound you would execute under. Proposed ticks must be multiples of the pool tick spacing.
The rubric
Registered before either arm ran, and version-hashed so it cannot be quietly rewritten once the answers are in. Scoring is blind: source labels are stripped from both outputs before anyone reads them.
| Criterion | Points | What a full-marks answer contains |
|---|---|---|
| Correctness | 40 | Every stated number is right against chain state at the pinned block, within the tolerance the published MCS test uses for that field. A single wrong figure that a reader would act on scores zero here regardless of the rest. |
| Completeness | 15 | Every field the task asked for is present. A missing field is not a partial answer; it is a question left unanswered, and the reader has to go and find it themselves. |
| Provenance | 15 |
