Add NewBlock hook

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-257/create-onnewblock-hook

Description

Adds a new block hook to the transaction manager and moves pruning and reveal not submitted logic to be triggered by new blocks instead of by transaction collector. This improves the separation of concerns by having these operations respond to time-based triggers rather than transaction events.

Key changes:

• Added NewBlock hook type to transaction manager
• Enhanced type safety for hook handlers using TypeScript generics
• Moved pruning logic and reveal not submitted from transaction collector to new block handler
• Added proper hook registration for new block events

Checklist

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.

• 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.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	d6af5a2
Status:	✅  Deploy successful!
Preview URL:	https://dce7bf21.happychain.pages.dev
Branch Preview URL:	https://gabriel-on-new-block.happychain.pages.dev

View logs

[GabrielMartinezRodriguez]

• Deploy randomness service #416 : 2 dependent PRs (#434 , #441 )
• Add config contract #404
• Randomness service: Improve performance and reliability #372
• Add transaction submission failure hook and error handling #366
• Increase default RPC timeout to 2000ms #365
• Add configurable HTTP polling interval for block monitoring #362
• Force initialization before using the TXM #361
• Script to monitor randomness service #325
• Script to easily launch the randomness service locally #324
• Submit drand numbers #318
• Random oracle contracts #307
• Only prune finalized randomness entries #305
• Add NewBlock hook #304 👈 (View in Graphite)
• Refactors the randomness service to be able to process pending commitments  #303
• Add SQLite persistence to randomness service #300
• Txm no longer receives Viem objects #298 : 1 other dependent PR (#299 )
• Add flush mechanism #289 : 1 other dependent PR (#297 )
• Allow run multiple txm simultaneously within the same service #285
• Added docs for txm #272
• Mutex in tx monitor #264
• Purge transactions #232
• Txm hooks #229
• Use kysely instead of mikro-orm #250
• master

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

[linear]

HAPPY-257 Create OnNewBlock hook

This hook will allow users to execute code on every new block without having to place that code inside the transaction collector or use another web3 client.

In addition, after implementing this hook, we will have to move the randomness-service prune database function to this new hook and mark as expired the randomness for which the commitment has been submitted but not revealed, and it has already expired

[norswap]

Just checking: the ordering of this with other block subscriptions doesn't matter, right?

[GabrielMartinezRodriguez]

Yes, it doesn't matter