Add config contract

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-320/always-execute-the-randomness-service-transactions-first-in-the-block

Description

This PR creates a new smart contract that is queried by the node every block to obtain the randomness contract address. The node then retrieves the randomness contract owner to prioritize all transactions from this wallet at the beginning of the block. This ensures that the reveal randomness transaction is included first, making the randomness available for all transactions in the block.

This allows us to modify the randomness contract address and the randomness contract owner without having to relaunch the sequencer, which would otherwise cause a small downtime and require us to request assistance from the Caldera team.

Toggle Checklist

Checklist

Basics

• B1. I have applied the proper label & proper branch name
• 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

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

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	823c0fe
Status:	✅  Deploy successful!
Preview URL:	https://30ea6a8d.happychain.pages.dev
Branch Preview URL:	https://gabriel-config-contract.happychain.pages.dev

View logs

[GabrielMartinezRodriguez]

• Deploy randomness service #416 : 2 dependent PRs (#434 , #441 )
• Add config contract #404 👈 (View in Graphite)
• 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
• 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-320 Always execute the randomness service transactions first in the block

[norswap]

It might make sense to separate this from random eventually (if we add other addreses here), but for now this is good.

[norswap]

Just needs a restack.