refactor: move ProofType
into raiko_lib
#421
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ProofType
is a primitive component within Raiko. However, currently, there is some redundancy and confusion with similar items. I intend to refactorProofType
for clarity and independence as follows:Move
ProofType
toraiko_lib
, to ensure thatProofType
be indenpendent with other itemsMerge
Proof System ID
intoProofType
, to eliminate redundant definitions and simplify the management of proof types for taskdbRISC0_PROVER_CODE = 3
SP1_PROVER_CODE = 1
Merge
VerifierType
intoProofType
.VerifierType
This pull request focuses on the first step: moving
ProofType
intoraiko_lib
and making it independent of other constructs. In fact, this pull request is more easy than it looks like, and it doesn't introduce any new changes:ProofType
definition into raiko-lib