< moneyball>
Oh maybe not haha. Yes meshcollider I am
< moneyball>
Expect to hear more this coming week
< moneyball>
Feel free to ask me questions if you have any
< meshcollider>
moneyball: awesome, theres some very cheap flights at the moment so it'd be good to hear asap :)
< moneyball>
the dates are set - same as communicated a few months ago. it will precede the breaking bitcoin conference, june 5-7, with the conference being that weekend june 8-9, in amsterdam. so you should feel comfortable booking flights with those dates in mind.
< bitcoin-git>
bitcoin/master fa4ce70 MarcoFalke: rpc: Actually throw help when passed invalid number of params
< bitcoin-git>
bitcoin/master 1a8a5ed Wladimir J. van der Laan: Merge #15401: rpc: Actually throw help when passed invalid number of param...
< bitcoin-git>
[bitcoin] laanwj merged pull request #15401: rpc: Actually throw help when passed invalid number of params (master...Mf1902-rpcNumArgs) https://github.com/bitcoin/bitcoin/pull/15401
< nanai>
hi
< nanai>
can i withdraw b2x to bitcoincore v0.17.1 ? or is it only for btc
< bitcoin-git>
[bitcoin] laanwj opened pull request #15471: rpc/gui: Remove 'Unknown block versions being mined' warning (master...2019_02_false_positives) https://github.com/bitcoin/bitcoin/pull/15471
< wumpus>
uhmmm test_bitcoin is printing loads of these
< wumpus>
Error: Specified -walletdir "/tmp/test_bitcoin/1551089075_943311758/tempdir/path_does_not_exist" does not exist
< provoostenator>
Is there a SegWit v1 proposal on the bitcoin-dev list or elsewhere that I just managed to overlook? I though gmaxwell referred to that a few days ago in the context of SIGHASH_NO_INPUT_FULL_DISCLAIMER
< luke-jr>
provoostenator: I sent one like a year ago, but I think there's been more recent work since (possibly unrelated?)
< luke-jr>
provoostenator: it seems to completely fly in the face of supposed principles of merging; the protocol change has near zero community support
< provoostenator>
luke-jr: that PR simply drops the warning entirely (option 2 in my list), I think you're confusing it with #13972 (option 3 in my list)
< luke-jr>
provoostenator: no, dropping the warning is what I meant
< provoostenator>
luke-jr: good news, for now: I ran the numbers back to before SegWit and if you look *per bit* we can stil use the 50 out of 100 blocks threshold for warnings.
< provoostenator>
Afaik the protocol doesn't support signalling by rotating bits, so that shouldn't be a violation.
< luke-jr>
provoostenator: what do you mean?
< provoostenator>
Alerts are currently triggered when 50 out of 100 recent blocks have any unexpected bit set, even if it's a different bit in each of those blocks.
< luke-jr>
hmm, that's weird. fixing that does make sense
< provoostenator>
If we change that to tracking each bit individually, then there wouuld have been no alerts expect for SegWit and BIP91.
< luke-jr>
gotta run, bbiab
< sipa>
we already track each bit individually
< provoostenator>
sipa: the activation logic does, the alert logic doesn't
< sipa>
yes we do
< sipa>
(separate from the warning logic under discussio nnow)
< provoostenator>
We check if each block has an unexpected value. Any unexpected value.
< sipa>
yes, i know
< sipa>
i'm saying there is also another warning mechanism which does work per bit
< provoostenator>
Ah yes, the one that warns some new rule is active.
< provoostenator>
But that's not the one causing all the false positive alerts afaik.
< sipa>
correct
< provoostenator>
The nUpgraded warning says "It's possible unknown rules are in effect", but that's only possible if a lower threshold or some other upgrade mechanism than BIP9 is introduced.
< provoostenator>
Or if a future soft fork makes another bit permanent.
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #15481: Restrict timestamp when mining a diff-adjustment block to prev-600 (master...2019-02-600s-gbt) https://github.com/bitcoin/bitcoin/pull/15481
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #15482: Implement BIPXXX's new softfork rules (The Great Consensus Cleanup) (master...2019-02-great-consensus-cleanup) https://github.com/bitcoin/bitcoin/pull/15482