- User Since
- Nov 23 2018, 01:26 (47 w, 4 d)
Aug 18 2019
Aug 17 2019
oh goody, I was looking forward to this one :)
Would have been good to have a release note for this, I just chatted with one person who was confused their regtest setup mysteriously stopped working upon upgrade.
Aug 15 2019
ok, still feels weird to me to have chainwork not match the assumevalid block though
add nonnegative check per Fabien's suggestion
Aug 14 2019
rebase; increase test coverage and add comments.
updated to use CheckMinimalPush
Aug 13 2019
arc update to make it follow standard procedure
Aug 12 2019
oops! that was me :)
Aug 9 2019
just noticed this bug on testnet in my -debug=net logfile
Just to follow up, this did indeed break my testnet node's ability to sync to the fork testnet. I had to put minimumchainwork=0 in the bitcoin.conf so it would stop disconnecting imaginary_username's node with reason "Disconnecting outbound peer 51 -- headers chain has insufficient work"
rebase for conflict (standard.cpp in D3807)
Aug 6 2019
rebase for landed parent
move comments up a line
Aug 5 2019
Aug 4 2019
Note -- it only supports up to 20 pubkeys like regular multisig, rather this static assert is only here since the implementation's usage of a 32-bit number (and >> operator) is implicitly assuming < 32 keys.
Aug 1 2019
Jul 30 2019
Jul 29 2019
Hmm, I don't get why there is the 'should' / 'must' distinction here, but yeah 👍 I wondered why it had been written that way.
rebase onto the updated parent
Jul 28 2019
Jul 27 2019
Jul 26 2019
update feature_nulldummy test to only run pre-activation
Jul 25 2019
Hmm, I tried also running ./test/functional/test_runner.py --with-gravitonactivation which actually causes a failure in feature_nulldummy.py, which is not surprising because the reject reason will have changed.
@deadalnix ok to commandeer now
add more test cases
Jul 23 2019
Jul 20 2019
Jul 19 2019
rebased & change to the new bitfield decoding scheme
Jul 18 2019
Jul 15 2019
for include order (and rebuild)
Jul 14 2019
Note that rejected and reconnect_p2p don't actually get used in this test; could probably be taken out. Initially I was thinking they might come in useful later, now I can't imagine that anything like that would be added.
reworked into parents
Jul 13 2019
update comments & remove unneeded empty line
guessing at what types are expected
minor conflict -- one braces fix now done in ancestor
minor conflict from parent
rebased parent & new abc ver
update per jason's comments
Jul 12 2019
[Errno 28] No space left on device
Jul 11 2019
Confirm mainnet 000000000000000004425aeeb553758650da20031643fbfff0f53ac5dd1b39c3 and its chainwork; has currently 45 confirmations.
Jul 10 2019
developer notes were done in D2941