karelb: yes, unrelated to libbitcoin; those are just the names for our internal modules
booyah: I don't think I've seen any evidence of mainnet miners mining that way, but it's an easy mistake to make. letting it mine without segwit was a compatiblity move that has mostly served its purpose.
wumpus 14383 and #14403 should be mergeable, unless you wanted another ACK on 14403. In which case, could someone read through the discussion and ACK/NACK/comment etc
I don't know if this is a bug or expected behaviour but my regtest node doesn't seem to adjust difficulty every 2016 blocks. Two questions - a. Is this expected and b. Is there a way to force an adjustment
Varunram: I think it's expected: test/functional/test_framework/blocktools.py: block.nBits = 0x207fffff # difficulty retargeting is disabled in REGTEST chainparams
Varunram: looks like you could probably change it here (and recompile): src/chainparams.cpp: consensus.fPowNoRetargeting = true;
ah, I need to test some reorg code on testnet, hence my question, this would help a lot, thanks!
[bitcoin] practicalswift opened pull request #14475: serialize: Document integer width assumptions we are making when calculating compact sizes (master...integer-width-assumptions) https://github.com/bitcoin/bitcoin/pull/14475
Varunram, it doesn't retarget cause that would be annoying in regtest
phantomcircuit: it used to retarget
I saw a couple old SO posts that told me it did
sipa, yeah and it was annoying
phantomcircuit: I guess I found it different simply because _I_ was expecting regtest to behave like mainnet and not anything else
< * Varunram>
annoying as in? difficulty rocketing up after a couple retargets?
Varunram: right, for some tests you needed multiple retarget windows worth of blocks
which was expensive
ah, I see, thanks!
Varunram: if you want to test some reorg stuff, you can use invalidblock and reconsiderblock
achow101: yeah, that's what I'm doing now :)
MarcoFalke: It seems that Drahtbot is offline for days. Is it crash?