From af386725a65376f9533dc794abe12e7aa6e7107f Mon Sep 17 00:00:00 2001 From: Michael Taylor Date: Sun, 27 Sep 2026 10:08:00 -0700 Subject: [PATCH 1/2] chore: open lane for #3421 Co-Authored-By: Claude Sonnet 5 From 802ae49e2d26ac07fa87638bf81880731fe02e0f Mon Sep 17 00:00:00 2001 From: Michael Taylor Date: Sun, 27 Sep 2026 10:08:58 -0700 Subject: [PATCH 2/2] refactor(rewards): rename chain_peak_height binding to chain_peak Both members of read_chain_peak's (u64, u64) return are u64, so the misleading name would let a future construction/destructure swap go unseen by the compiler. Rename before rewriting around these lines for #3421 (gate finding on PR #629). Co-Authored-By: Claude Sonnet 5 --- crates/dig-node-service/src/rewards/chain_port.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/dig-node-service/src/rewards/chain_port.rs b/crates/dig-node-service/src/rewards/chain_port.rs index ff768927..20eaf3a8 100644 --- a/crates/dig-node-service/src/rewards/chain_port.rs +++ b/crates/dig-node-service/src/rewards/chain_port.rs @@ -180,14 +180,14 @@ where // a height the rest of the report was never read against -- a plausible number beside // possibly-stale data, with nothing erroring. Both reads MUST succeed or the whole call // refuses; see `ChainPortError::ChainPeakUnavailable`'s doc for why `0` is never a stand-in. - let chain_peak_height = read_chain_peak(source)?; + let chain_peak = read_chain_peak(source)?; report_from_snapshot( &snapshot, launcher_id, comment, first_epoch_start, - chain_peak_height, + chain_peak, ) }