feat: update to latest stacks-node, store and forward boot receipts #18
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
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.
Update to stacks-node from PR stacks-network/stacks-core#3409
The above PR introduced a "block 0" event payload, which the stacks-node now emits immediately on startup, before syncing any burnchain blocks or mining a Stacks block. The boot contracts and genesis accounts are now contained in this "block 0" payload instead of the first mined Stacks block.
The docker image produced by this repo performs an initial chain bootstrap during the docker build phase: the first 100 bitcoin blocks are mined and synced with the stacks-node, then that chainstate is saved in the docker image. To preserve this capability, special handling is required for the new "block 0" event. This is implemented with a "store and forward" mechanism: during the initial bootstrap, events are recorded and persisted in the docker image, and later when the image is ran, they are POST'd to an event-observer.