Add transaction submission failure hook and error handling

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-282/hook-to-notify-the-library-user-about-issues-before-submitting-their

Description

• Creating a new TransactionSubmissionFailed hook to capture submission failures
• Adding error logging for transaction submission failures in the randomness service

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

Correctness

• C1. Builds and passes tests.

• C2. The code is properly parameterized & compatible with different environments.

• C3. I have manually tested my changes & connected features.

• C4. I have performed a thorough self-review of my code after submitting the PR.

Architecture & Documentation

• D1. I made it easy to reason locally about the code.
• D2. All public-facing APIs & meaningful internal APIs are properly documented.
• D3. If appropriate, the general architecture is documented.

[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 👈 (View in Graphite)
• 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
• 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.

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	2c9bf41
Status:	✅  Deploy successful!
Preview URL:	https://dd973ade.happychain.pages.dev
Branch Preview URL:	https://gabriel-txm-submission-faile.happychain.pages.dev

View logs

[linear]

HAPPY-282 Hook to notify the library user about issues before submitting their transactions.

We want to notify users about potential issues that may occur before submitting their transactions, such as problems encountered when simulating a transaction. These issues could result in the transaction remaining indefinitely in our database while attempting to be included, without notifying the user.

Another good idea would be to implement a system that allows users to modify the parameters of such transactions to resolve these issues, for example, by changing the call data. Additionally, it should also be possible for users to remove these transactions.

[norswap]

Seems like a good idea to also pass the cause from the AttemptSubmissionErrorCause enum (and export that publicly) so that might enable finer-grained reaction to this without needing to parse the description.