-
Notifications
You must be signed in to change notification settings - Fork 696
Initial stab at a "main loop" for downloading and parsing bitcoin blocks #910
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Merged
Conversation
This file contains hidden or 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
… serializers for Secp256k1PublicKey. Also, update new location of BitcoinNetworkType
…)serializer methods for Secp256k1PublicKey
… trait to instantiate history rows from individual burn chain operations; implement helpers to insert and select rows of burn chain operations and convert them to and from database rows; implement basic DB tests
…tom) data type from a Sqlite3 Row
…o describe the order in which their column fields should be SELECT'ed
… an address and public key type in order to make it possible for the rust compiler to correctly assign impls when processing transactions
…o the rust compiler can figure out how to match impls when classifying and checking transactions in the burndb code
…know whether or not it arrived on time (per SIP 001); also, make it so this op has a type parameter for both the address and public key so the rust compiler can assign impls when classifying transactions
… bitcoin header hash
…nloader and block parser so we can chain them together
…s, fetch headers, fetch blocks, parse blocks, and (soon) feed them to the burn db
…handlers *consume* messages, and make it so we use Arc<...> for messages (so we can pass them between threads without having to copy them)
…ion to this module
Thanks! I'm in favor of your compromise approach -- we merge every week to develop (e.g. Wednesdays), and then create issues for each unaddressed item in the comments. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
There's still some stuff to do here -- in particular, checking the validity of transactions. But, we can download, parse, and commit burnchain transactions and generate consensus hashes.