feat(randomness): drand prune

[GabrielMartinezRodriguez]

Description

Prune the drand repository every 20 seconds to avoid having thousands of drands in memory, which causes delays when trying to submit drands

• Include all relevant context (but no need to repeat the issue's content).
• Draw attention to new, noteworthy & unintuitive elements.

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.

< INDICATE BROWSER, DEMO APP & OTHER ENV DETAILS USED FOR TESTING HERE >

< INDICATE TESTED SCENARIOS (USER INTERFACE INTERACTION, CODE FLOWS) HERE >

• 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 are documented in the docs.
  Public APIS and 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.
• D4. An appropriate Changeset has been generated (and committed) with make changeset for
  breaking and meaningful changes in packages (not required for cleanups & refactors).

[GabrielMartinezRodriguez]

• feat(randomness): drand prune #693 👈 (View in Graphite)
• feat(txm): transactions with value #647 : 1 other dependent PR (#661 )
• Txm transactions support arbitrary calldata #596
• feat(randomness): submit drands asap #590
• 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:	15884ab
Status:	✅  Deploy successful!
Preview URL:	https://a61aaecd.happychain.pages.dev
Branch Preview URL:	https://gabriel-drand-prune.happychain.pages.dev

View logs

[aodhgan]

this change is already in master

[norswap]

Seems like a git bug — I've seen happen quite a bit recently, I usually fix it by restacking and resubmitting.

[aodhgan]

uh oh dodgy rebase

[aodhgan]

think this had some funky rebase/merge conflict resolution, since a bunch of allowing transaction values to be non-zero is included. either worth trying to resolve or re-opening with just the specific intentional changes (drand pruning)
also changes contracts/package.json which it shouldnt etc.

[norswap]

think this had some funky rebase/merge conflict resolution, since a bunch of allowing transaction values to be non-zero is included. either worth trying to resolve or re-opening with just the specific intentional changes (drand pruning) also changes contracts/package.json which it shouldnt etc.

As mentionned on other comment, Github sucking — restacked and resubmitted, removes all that cruft.