Skip to content

Conversation

varun-doshi
Copy link

@varun-doshi varun-doshi commented Jul 10, 2025

TITLE

Description

Fixes #1983
add new() to VerificationData

Type of change

Please delete options that are not relevant.

  • Refactor

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 crates/docs/examples
    • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

@varun-doshi
Copy link
Author

Should I go ahead and apply this function to applicable places in the codebase?

@JuArce JuArce changed the base branch from testnet to staging July 15, 2025 14:59
Copy link
Contributor

@MauroToscano MauroToscano left a comment

Choose a reason for hiding this comment

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

Now that we have this new, it should actually be used when instantiating the data. You can pull changes in staging, do that, and we can merge it

@varun-doshi
Copy link
Author

Now that we have this new, it should actually be used when instantiating the data. You can pull changes in staging, do that, and we can merge it

Done!

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.

feat(sdk): add new() to VerificationData
2 participants