Random oracle contracts

[GabrielMartinezRodriguez]

Linked Issues

• closes https://linear.app/happychain/issue/HAPPY-243/drand-contract

Description

This PR aims to add the remaining logic to make the Random oracle contracts fully functional. The pending logic includes the submission of DRAND randomness and the implementation of a mechanism to combine our commitment/reveal contract with DRAND randomness.

More context:

• Notion design document
• Drand protocol used
• Official drand signature verification example

Key changes:

• Implemented the Drand verification contract.
• Implemented Random contract to combine Drand and RandomCommitment functionalities.
• Added two new environment variables.
• Renamed the Random contract to RandomCommitment.
• RandomCommitment now uses blocks instead of timestamps
• Created a folder to house the three random-related contracts.
• RandomCommitment and Drand are abstract contracts, which are extended by the Random contract.

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 (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 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:	d6eaecb
Status:	✅  Deploy successful!
Preview URL:	https://37bc8364.happychain.pages.dev
Branch Preview URL:	https://gabriel-drand-contract.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 👈 (View in Graphite)
• 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-243 Drand Contract

Currently, we have only created the Random contract, which is used to submit random commitments. Now, we need to create the Drand contract, which is designed to submit randomness generated by https://drand.love. This randomness will then be combined with the submitted random commitments to produce a random number every two seconds