Skip to content

Conversation

@tsite
Copy link
Collaborator

@tsite tsite commented Nov 14, 2025

risc0 can be used as an alternative to sp1

Ticket

What does this PR do?

  • Summary:
    • <Provide a brief description of what this PR implements, the problem it solves, or the feature it introduces. Include relevant context as needed.>
  • Key Changes:
    • < List out major code changes or functionality modifications in bullet points.>
  • <Goal of this section: someone reads this in a few months and at-a-glance understands why this change got made + what it is>

Breaking changes?

  • Yes/No:
    • <Does this PR introduce any breaking changes (API/config/schema) for node operators?>
    • <If yes, explain the breaking change, its impact, and applicable upgrade steps.>

Metrics changes?

  • Yes/No:
    • <Does this PR introduce any changes to metrics that might affect our dashboards or alerts?>
    • <If yes, explain the metric(s) what are added/removed/updated>

Anything interesting?

  • < Optional>
  • < Did you use something fancy or new to you that teammates may not have seen before? Help your reviewer by explaining it here and link any references you used>

Documentation

  • < Optional>
  • <Do we have a repo doc where this feature is already documented? If not, can you add a relevant README.md or update an existing one?>

How can this PR be tested?

  • <Do existing tests cover the change? Do you need to add any (unit, e2e, CI) tests?>
  • <If you had to test this locally, share the steps to reproduce the behavior here. Ideally, include your testing in CI>

@tsite tsite force-pushed the risc0 branch 4 times, most recently from 6b6d3b2 to a16c16e Compare November 15, 2025 01:19
risc0 can be used as an alternative to sp1
@tsite tsite force-pushed the risc0 branch 2 times, most recently from 22f0dde to 7f415ee Compare November 24, 2025 20:05
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.

2 participants