Skip to content

Fix: bump gnark version #1471

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.

Sign up for GitHub

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

Jump to bottom
Closed
PatStiles wants to merge 1 commit into from
Closed

Fix: bump gnark version #1471

PatStiles wants to merge 1 commit into from

Conversation

@PatStiles
Copy link
Contributor

@PatStiles PatStiles commented Nov 22, 2024 •
edited
Loading

Bumps gnark versoin

Description

Closes #1469 . We currently use gnark v0.10.0 and gnark-crypto v0.12.2 we should bump to gnark v0.11.0 and gnark-crypto v0.14.0

To Test

  • Run a local devet and verify proofs land:
  1. make anvil_start_with_block_time
  2. make aggregator_start
  3. make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml
  4. make operator_start CONFIG_FILE=config-files/config-operator-1.yaml
  5. make batcher_start_local
  6. make telemetry_full_start

Once you have the system running, send proofs

  1. make batcher_send_burst_groth16
  2. Go to jaeger http://localhost:16686/search
  3. You should see the traces correctly created and task verified
image

Type of change

Please delete options that are not relevant.

  • New feature
  • Bug fix
  • Optimization
  • Refactor

Checklist

  • Linked to Github Issue

@PatStiles PatStiles closed this Nov 22, 2024
@JuArce JuArce deleted the fix/bump-gnark-version branch January 2, 2025 15:15
@Oppen Oppen mentioned this pull request Jan 16, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@PatStiles