Skip to content

Conversation

@Dentosal
Copy link
Member

@Dentosal Dentosal commented Oct 6, 2025

Follow-up to #3099, which should be merged first.

Description

This information is required for fraud proving, so the executor must expose them. This is a breaking change as public types gain new fields.

Checklist

  • Breaking changes are clearly marked as such in the PR description and changelog
  • New behavior is reflected in tests
  • The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

  • I have reviewed the code myself
  • I have created follow-up issues caused by this PR and linked them here

@Dentosal Dentosal self-assigned this Oct 6, 2025
@Dentosal Dentosal added the breaking A breaking api change label Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking A breaking api change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants