Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(alerts): Display the number of proofs in a batch from the created task #1722

Closed
wants to merge 4 commits into from

Conversation

PatStiles
Copy link
Contributor

@PatStiles PatStiles commented Jan 8, 2025

Display the number of proofs in a batch from the created task

Description

Currently the alert sender just sends the number of repetitions of sent proofs. This pr changes this to fetch the number of proof submitters in the batch from the proofSubmitters parameter of the createNewTask function call. This parameters contains the addresses of each submitted proof therefore the number of submitters corresponds to the number of proofs in the batch.

To Test:

  • start a local devnet
  • execute the alert script via ./alerts/sender_with_alert.sh ./alerts/.env
    You should observe that the correct number of proofs in a batch is displayed now and observe that if a second senders proofs are included in the batch the number of proofs are displayed. Adding additional task senders should increase the batch size.
16 Proofs in batch of size 16 submitted and verified. Spent amount: 0.000171417922653 ETH ($ 0.57) [ http://localhost:3000/batches/0x0a8dd28a8e7a38151a22b3f04315d17be3a583fdc5fc925d085084b4c8732b27 ]

Type of change

Please delete options that are not relevant.

  • New feature

Checklist

  • “Hotfix” to testnet, everything else to staging
  • Linked to Github Issue
  • This change depends on code or research by an external entity
    • Acknowledgements were updated to give credit
  • Unit tests added
  • This change requires new documentation.
    • Documentation has been added/updated.
  • This change is an Optimization
    • Benchmarks added/run
  • Has a known issue
  • If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
    • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
    • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

@PatStiles PatStiles changed the base branch from testnet to staging January 8, 2025 15:22
@PatStiles PatStiles marked this pull request as draft January 8, 2025 15:22
@PatStiles PatStiles self-assigned this Jan 9, 2025
@PatStiles PatStiles marked this pull request as ready for review January 9, 2025 16:55
@PatStiles PatStiles changed the base branch from staging to testnet January 9, 2025 16:55
Copy link
Collaborator

@JuArce JuArce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Point it to testnet as a hotfix

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All this changes are not related with the PR

@PatStiles PatStiles force-pushed the feat/number_proofs_in_sender_with_alert branch from 8325d76 to 1d8846a Compare January 9, 2025 17:01
@PatStiles
Copy link
Contributor Author

Closing in favor of #1727 as this branch was made off staging and carries with it some of the commits

@PatStiles PatStiles closed this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants