Fix: Viem sends random undefined blocks

[GabrielMartinezRodriguez]

Description

Viem sends random undefined blocks during network problems, which causes unexpected behavior

Toggle Checklist

Checklist

Basics

• B1. I have applied the proper label & proper branch name (e.g. norswap/build-system-caching).
• B2. This PR is not so big that it should be split & addresses only one concern.
• B3. The PR targets the lowest branch it can (ideally master).

Reminder: PR review guidelines

Correctness

• C1. Builds and passes tests.
• C2. The code is properly parameterized & compatible with different environments (e.g. local,
  testnet, mainnet, standalone wallet, ...).
• C3. I have manually tested my changes & connected features.

< INDICATE BROWSER, DEMO APP & OTHER ENV DETAILS USED FOR TESTING HERE >

< INDICATE TESTED SCENARIOS (USER INTERFACE INTERACTION, CODE FLOWS) HERE >

• C4. I have performed a thorough self-review of my code after submitting the PR,
  and have updated the code & comments accordingly.

Architecture & Documentation

• D1. I made it easy to reason locally about the code, by (1) using proper abstraction boundaries,
  (2) commenting these boundaries correctly, (3) adding inline comments for context when needed.
• D2. All public-facing APIs & meaningful (non-local) internal APIs are properly documented in code
  comments.
• D3. If appropriate, the general architecture of the code is documented in a code comment or
  in a Markdown document.
• D4. An appropriate Changeset has been generated (and committed) for changes that touch npm published packages (currently packages/core and packages/react), see here for more info.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	db10c52
Status:	⚡️  Build in progress...

View logs

[GabrielMartinezRodriguez]

• Randomness monitor service #584
• Txm traces #521
• fix(txm): returned nonce queue order #578
• fix(txm): not process the same block multiple times #577
• Fix: Viem sends random undefined blocks #575 👈 (View in Graphite)
• fix(txm): heap out of memory #573
• Avoid initiating new attempts if the gas conditions persist unchanged #571
• Dynamic priority fee #570
• TXM: Rpc liveness #562
• fix(txm): nonce gap #561
• PoC: Add metrics to TXM #503
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[aodhgan]

so weird this can happen.. I see they are somewhat dangerously-widening casting to any here: https://github.com/wevm/viem/blob/main/src/actions/public/watchBlocks.ts#L172

looking through the docs and implementation for Viems watchBlocks there is also emitMissed
https://viem.sh/docs/actions/public/watchBlocks.html#emitmissed-optional
https://github.com/wevm/viem/blob/main/src/actions/public/watchBlocks.ts#L162

looking at the implementation it detects if the "latest" block number is not +1 from the last, and will send the missing blocks in the interval. this might be useful for us. wdyt? can be a another PR

[norswap]

Could be interesting but would need to be handled with caution as the blocks as used as a clock as well so we wouldn't want to trigger say the transaction monitor in rapid fire.

In fact, I think we don't otherwise need to see every block — but we should make sure. Can we enqueue an issue for this (= make sure it's okay if we miss block + document).