final chain serialization bits #199
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
magik6k
approved these changes
Sep 17, 2019
chain/sync.go
Outdated
| @@ -16,15 +16,15 @@ import ( | |||
| "github.com/filecoin-project/go-lotus/chain/types" | |||
| "github.com/filecoin-project/go-lotus/chain/vm" | |||
| "github.com/filecoin-project/go-lotus/lib/vdf" | |||
| cbg "github.com/whyrusleeping/cbor-gen" | |||
Merged
Co-Authored-By: Łukasz Magiera <magik6k@users.noreply.github.com>
nonsense
pushed a commit
that referenced
this pull request
Nov 6, 2020
…dd missing mocked verification calls (#199) * warn when extracting a message from a tipset that contains more leading messages from the same sender, as this leads to nonce misalignment. * fix mocked randomness being too short (must be 32 bytes). * mock some further verification syscalls.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should be the last of the bits required to have 'correct' chain seialization, Actors and Message receipts got the codegen treatment, and we switched to using the AMT instead of the sharray everywhere.