Closed lispc closed 1 month ago
This PR can work well with deployed curie provers ( >= v0.11.4).
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Has the version in params/version.go been updated?
params/version.go
Does this PR have the breaking-change label?
breaking-change
@omerfirmak can you merge instead of rebase-and-force-push next time? unfriendly for branch management..
@omerfirmak need another review
1. Purpose or design rationale of this PR
This PR can work well with deployed curie provers ( >= v0.11.4).
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?