This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of blockchain-spv.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hello lovely humans,
blockchain-spv just published its new version 3.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of blockchain-spv. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 15 commits .
745400c3.1.09fe89fdBlockchain: added 'estimatedChainHeight' helper function for syncing092c024HeaderStream: added 'sync' option, for ensuring blocks aren't pushed until committed into dbdfd5ee83.0.1dc4d51cBlockchain: make sure origin and and checkpoint blocks get added to height index4f15aa7Fixed tests for ES5 JS enginesc4baeb73.0.09bdd498Added HeaderStream test for reorging while initializing9d9c493Blockchain: don't unlink headers from losing forksf63b196Fixed reorg test to do reorg after stream initializesa2c7c75Fixed standard style check in test script7863f4aBlockchain: fix reorg handling (unlink previous best fork and link/index blocks in new best fork)60b0621BlockStore: always index height 0683d609Blockchain: use height index for getBlockAtHeight()b9febe5BlockStore: index blocks by height on an intervalSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade