-
Notifications
You must be signed in to change notification settings - Fork 809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
networks: update regtest params #580
Conversation
Codecov Report
@@ Coverage Diff @@
## master #580 +/- ##
==========================================
- Coverage 53.31% 52.82% -0.49%
==========================================
Files 104 104
Lines 27668 27661 -7
Branches 4738 4736 -2
==========================================
- Hits 14750 14611 -139
- Misses 12918 13050 +132
Continue to review full report at Codecov.
|
Tested connecting a bitcoind + bcoin node in a regtest network, and there is also a difference with when segwit is activated, leading to bcoin rejecting blocks with:
I've manually activated segwit on regtest for bcoin, and blocks connected. |
segwit gets activated around block 400 and something on regtest. Although I think I saw discussion of that getting removed now that segwit has been activated for a while. |
May have already been updated, the first block had witness data from testing against Bitcoin Core v0.16 regtest. |
I think it would be good to get this in for testing between multiple implementations. I think identifying the issue with segwit activation is the only last remaining item? |
0b73b94
to
6466059
Compare
@braydonf Made minimal changes which enable segwit from genesis to match |
Just a poke on this open PR since it isn't ready to be merged yet.
|
Closing as #676 includes these changes. |
refs #579