Skip to content
Discussion options

You must be logged in to vote

@shotcollin @seccentral

I will work on getting the documentation corrected. I confirmed the workaround in the post above does correct the issue for now.

1- Create the json file and run a sealing benchmark.

./lotus-bench sealing --save-commit2-input commit2-input.json

2- Use the file to run the proving benchmark.

./lotus-bench prove commit2-input.json

Please let me know if you have any questions.

Replies: 6 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@citizen-stig
Comment options

Comment options

You must be logged in to vote
1 reply
@seccentral
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by SgtCoin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6 participants
Converted from issue

This discussion was converted from issue #5598 on February 22, 2021 08:21.