Txm hooks

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-112/txmanager-we-should-implement-a-system-to-notify-users-of-the-status

Description

Implemented a mechanism that allows originators to be notified when certain events occur. Currently, only the TransactionStatusChanged event is specified, which is triggered when a transaction's status changes. Additionally, this PR modifies the randomness service to reveal the commitment value only if the commitment transaction has succeeded

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.

This PR has been tested using the randomness service on localhost, interacting with the Anvil blockchain

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

[GabrielMartinezRodriguez]

• Add flush mechanism #289 : 2 dependent PRs (#297 , #298 )
• 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 👈 (View in Graphite)
• 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:	a520cec
Status:	⚡️  Build in progress...

View logs

[linear]

HAPPY-112 txmanager: We should implement a system to notify users of the status of their transactions

This system should notify users when certain events occur, for instance:

• Transaction success
• Transaction failure
• Transaction is being canceled

In addition, it might be a good idea to allow users to proactively check the status of their transactions

[norswap]

Should we just add "All" to TxmHookType? Seems like it would work nicely. We can also mandate type in addHook to be explicit then.