feat(coprocessor): allow skipping verify proof requests during GW catchup

[antoniupop]

This is needed when spinning up a coprocessor as the keygen/crsgen events can be quite far back and we don't necessarily want to replay all verify proof requests since genesis if we don't have the precise location of these events.

[antoniupop]

@claude /pr-review

[claude]

Claude finished @antoniupop's task in 1m 45s —— View job

---

[AUTOMATED]

PR Review: feat(coprocessor): allow skipping verify proof requests during GW catchup

• Gather context and read changed files
• Analyze changes for bugs, correctness, and design issues
• Validate findings
• Post final review

---

Summary

This PR adds a --replay-skip-verify-proof CLI flag to the gateway listener that, when enabled during replay/catchup mode, skips VerifyProofRequest events. This is useful when bootstrapping a new coprocessor, where keygen/crsgen events may be far in the past and replaying all verify proof requests since genesis is undesirable.

Changes are clean and well-structured across 5 files: CLI arg definition, config propagation, core logic, default value, and helm chart documentation.

---

Issue Found (Confidence: 90/100)

Bug: Skip applies to ALL input_verification_address events, not just VerifyProofRequest

In gw_listener.rs (lines 198-202), the skip is placed before the event is decoded and matched:

if log.address() == self.input_verification_address {
    if replay_from_block.is_some() && self.conf.replay_skip_verify_proof {
        debug!(log = ?log, "Skipping VerifyProofRequest during replay");
        continue;  // ← skips ALL events from this address
    }
    if let Ok(event) = InputVerification::InputVerificationEvents::decode_log(&log.inner) {
        match event.data {
            InputVerification::InputVerificationEvents::VerifyProofRequest(request) => { ... }
            _ => { error!(log = ?log, "Unknown InputVerification event"); }
        }
    }
}

The continue at line 201 skips the entire input_verification_address log processing, meaning any event type emitted by this contract (not just VerifyProofRequest) would be silently skipped during replay. The log message says "Skipping VerifyProofRequest" but it hasn't actually verified that the event is a VerifyProofRequest.

Currently this may be safe if VerifyProofRequest is the only event emitted by that contract, but it's fragile — if additional event types are added to the InputVerification contract in the future, they would be silently dropped during replay with no warning.

Suggested fix: Move the skip inside the match arm, after the event has been decoded:

if log.address() == self.input_verification_address {
    if let Ok(event) = InputVerification::InputVerificationEvents::decode_log(&log.inner) {
        match event.data {
            InputVerification::InputVerificationEvents::VerifyProofRequest(request) => {
                if replay_from_block.is_some() && self.conf.replay_skip_verify_proof {
                    debug!(log = ?log, "Skipping VerifyProofRequest during replay");
                    continue;
                }
                self.verify_proof_request(db_pool, request, log.clone()).await
                    .inspect(|_| { verify_proof_success += 1; })
                    .inspect_err(|e| {
                        error!(error = %e, "VerifyProofRequest processing failed");
                        VERIFY_PROOF_FAIL_COUNTER.inc();
                    })?;
            },
            _ => { error!(log = ?log, "Unknown InputVerification event"); }
        }
    } else {
        error!(log = ?log, "Failed to decode InputVerification event log");
    }
}

Fix this →

---

Nits

1. PR title typo: "guring" → "during"

2. Nit: default_value_t = false in gw_listener.rs line 88 — for bool fields in clap, you can simply omit the default_value_t since bool defaults to false already. Using #[arg(long, help = "...")] would suffice. Non-blocking.

---

What looks good

• ✅ The replay_from_block.is_some() guard ensures the skip only applies during replay mode and not during normal operation
• ✅ After replay finishes (*replay_from_block = None at line 274), the guard correctly deactivates the skip
• ✅ Helm chart documentation is properly updated with the new flag as a commented-out option
• ✅ Chart version bumped appropriately (0.8.1 → 0.8.2)
• ✅ Default value of false is sensible — opt-in behavior
• ✅ Config propagation is clean through CLI → ConfigSettings → listener

---

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 9797b44.

🟢 All jobs passed!

But CI Insights is watching 👀

[antoniupop]

@Mergifyio queue

[mergify]

Merge Queue Status

Rule: main

---

• ✅ Entered queue — 2026-02-18 15:09 UTC
• ✅ Checks started · on draft merge queue: embarking main (16d7577) and #2005 together #2008
• 🚫 Left the queue — 2026-02-18 16:13 UTC · at 9797b449fe3dac4bef6c94218d88be741108d2e4

This pull request spent 1 hour 4 minutes 27 seconds in the queue, including 3 minutes 4 seconds running CI.

Required conditions to merge

• check-success = run-e2e-tests / fhevm-e2e-test
• any of [🛡 GitHub branch protection]:
  • check-neutral = coprocessor-cargo-test/cargo-tests (bpr)
  • check-skipped = coprocessor-cargo-test/cargo-tests (bpr)
  • check-success = coprocessor-cargo-test/cargo-tests (bpr)
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• any of [🛡 GitHub branch protection]:
  • check-success = common-pull-request/lint (bpr)
  • check-neutral = common-pull-request/lint (bpr)
  • check-skipped = common-pull-request/lint (bpr)
• any of [🛡 GitHub branch protection]:
  • check-skipped = coprocessor-cargo-listener-tests/cargo-tests (bpr)
  • check-neutral = coprocessor-cargo-listener-tests/cargo-tests (bpr)
  • check-success = coprocessor-cargo-listener-tests/cargo-tests (bpr)
• any of [🛡 GitHub branch protection]:
  • check-success = coprocessor-dependency-analysis/dependencies-check (bpr)
  • check-neutral = coprocessor-dependency-analysis/dependencies-check (bpr)
  • check-skipped = coprocessor-dependency-analysis/dependencies-check (bpr)
• any of [🛡 GitHub branch protection]:
  • check-skipped = gateway-contracts-deployment-tests/sc-deploy (bpr)
  • check-neutral = gateway-contracts-deployment-tests/sc-deploy (bpr)
  • check-success = gateway-contracts-deployment-tests/sc-deploy (bpr)
• any of [🛡 GitHub branch protection]:
  • check-skipped = kms-connector-tests/test-connector (bpr)
  • check-neutral = kms-connector-tests/test-connector (bpr)
  • check-success = kms-connector-tests/test-connector (bpr)

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ coprocessor-cargo-test/cargo-tests (bpr)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[antoniupop]

@Mergifyio queue

[mergify]

Merge Queue Status

Rule: main

---

• ✅ Entered queue — 2026-02-19 09:42 UTC
• ✅ Checks passed · on draft merge queue: embarking main (290e19f), #2010 and #2005 together #2012
• ✅ Merged — 2026-02-19 12:37 UTC · at 9797b449fe3dac4bef6c94218d88be741108d2e4

This pull request spent 2 hours 54 minutes 29 seconds in the queue, including 1 hour 53 minutes 19 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • feat(coprocessor): allow skipping verify proof requests during GW catchup #2005
• check-success = run-e2e-tests / fhevm-e2e-test
• any of [🛡 GitHub branch protection]:
  • check-success = common-pull-request/lint (bpr)
  • check-neutral = common-pull-request/lint (bpr)
  • check-skipped = common-pull-request/lint (bpr)
• any of [🛡 GitHub branch protection]:
  • check-success = coprocessor-cargo-listener-tests/cargo-tests (bpr)
  • check-neutral = coprocessor-cargo-listener-tests/cargo-tests (bpr)
  • check-skipped = coprocessor-cargo-listener-tests/cargo-tests (bpr)
• any of [🛡 GitHub branch protection]:
  • check-success = coprocessor-cargo-test/cargo-tests (bpr)
  • check-neutral = coprocessor-cargo-test/cargo-tests (bpr)
  • check-skipped = coprocessor-cargo-test/cargo-tests (bpr)
• any of [🛡 GitHub branch protection]:
  • check-success = coprocessor-dependency-analysis/dependencies-check (bpr)
  • check-neutral = coprocessor-dependency-analysis/dependencies-check (bpr)
  • check-skipped = coprocessor-dependency-analysis/dependencies-check (bpr)
• any of [🛡 GitHub branch protection]:
  • check-skipped = gateway-contracts-deployment-tests/sc-deploy (bpr)
  • check-neutral = gateway-contracts-deployment-tests/sc-deploy (bpr)
  • check-success = gateway-contracts-deployment-tests/sc-deploy (bpr)
• any of [🛡 GitHub branch protection]:
  • check-skipped = kms-connector-tests/test-connector (bpr)
  • check-neutral = kms-connector-tests/test-connector (bpr)
  • check-success = kms-connector-tests/test-connector (bpr)

[antoniupop]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed

[antoniupop]

@Mergifyio requeue

[mergify]

requeue

☑️ Command requeue ignored because it is already running from a previous command.