Skip to content
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.

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

FIP-0076: make aggregate proof type parameter an option, absent if not aggregating #934

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

anorth
Copy link
Member

@anorth anorth commented Feb 1, 2024

@@ -186,8 +186,8 @@ struct ProveCommitSectors3Params {
// Aggregate proof for all sectors.
// Exactly one of sector_proofs or aggregate_proof must be non-empty.
AggregateProof: []byte,
// The proof type for the aggregate proof (ignored if no aggregate proof).
AggregateProofType: RegisteredAggregateProof,
// The proof type for the aggregate proof (must be absent if no aggregate proof).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm. Actually, this should probably say "must be null".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left this as a future-proof comment. It's true that today there must be no aggregate proof, but that's the true cause of the constraint.

@anorth anorth merged commit 16391e9 into master Feb 5, 2024
1 check passed
@anorth anorth deleted the anorth/76-optprooftype branch February 5, 2024 21:47
rvagg added a commit to filecoin-project/go-state-types that referenced this pull request Feb 6, 2024
rvagg added a commit to filecoin-project/go-state-types that referenced this pull request Feb 7, 2024
magik6k pushed a commit to filecoin-project/go-state-types that referenced this pull request Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ☑️ Done (Archive)
Development

Successfully merging this pull request may close these issues.

4 participants