< bitcoin-git> [bitcoin] glowang opened pull request #18391: doc: Update init and reduce-traffic docs for -blocksonly (master...update_blocksonly_docs) https://github.com/bitcoin/bitcoin/pull/18391
< dmos> Greetings from Bisq! Experiencing weird interaction between our (outdated) fork of BitcoinJ and Bitcoin Core 0.19.0.1. This log entry sums it up: `o.b.core.PeerSocketHandler: [127.0.0.1]:18444 - org.bitcoinj.core.ProtocolException: Received AlertMessage before version handshake is complete.`
< dmos> There's two things that are weird about it. The alerts system was retired in 0.13.0, but my local BTC node is 0.19.0.1. And, it's sending this while the handshake isn't completed yet, which bitcoinj considers a breach of protocol.
< dmos> To be clear, client is bitcoinj and bitcoin core is the node being connected to.
< dmos> Can someone shed some light on this
< dmos> ?
< dmos> Why is Bitcoin Core sending an alert message? Is it really a breach of BTC protocol?
< emilengler> I think this question is probably a bit misplaced here. However maybe #7692 helps you. It was the PR when Bitcoin Core removed the alert system. AFAIK the alert field is still in the protocol but I'm not sure on this.
< gribble> https://github.com/bitcoin/bitcoin/issues/7692 | Remove p2p alert system by btcdrak · Pull Request #7692 · bitcoin/bitcoin · GitHub
< emilengler> But I would suggest you asking on #bitcoin for protocol question rather than this channel
< dmos> Will do, thanks.
< nickler> ysangkok: There's one old open PR https://github.com/ElementsProject/secp256k1-zkp/pull/87, but that was before we changed the tiebreaker to even/odd Y. I expect that it can be further simplified now.
< ysangkok> nickler: all right. but it at least sounds like the structs will stay the same. i am making bindings, i don't think it will be too hard to adapt to even/odd Y. thanks for your reply
< nickler> ysangkok: yeah, the struct will stay similar to PR 87
< wumpus> dmos: note that even as of 0.20.0, we still send the "final alert message" https://github.com/bitcoin/bitcoin/blob/master/src/net_processing.cpp#L2087 to older peers
< wumpus> this is to prevent faked messages from being sent, in any case the mitigation is to igniore 'alert' messages
< wumpus> what new kind of horror is this, gpg2 --list-keys seems to hang at 100% CPU somewhere
< wumpus> oh it finishes but takes a long time
< sipa> wumpus: yeah i saw that too
< sipa> with one particular key, i even had the impression
< wumpus> sipa: yes, it seemed to happen at kanzure's key here, but after (temporarily) removing that one it just hangs somewhere else
< sipa> hmm
< wumpus> it looks like all gpg operations take a long time, even verifying signatures
< wumpus> could definitely be a local problem on this machine, but otoh everything else is working fine
< wumpus> i have so little motivation to go debug gpg now...
< kanzure> hm?
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #18392: ci: Run feature_block in valgrind (master...2003-ciMoreVal) https://github.com/bitcoin/bitcoin/pull/18392
< bitcoin-git> [bitcoin] practicalswift opened pull request #18393: tests: Don't assume presence of __builtin_mul_overflow(…) in MultiplicationOverflow(…) fuzzing harness (master...multiplication-overflow-fixup) https://github.com/bitcoin/bitcoin/pull/18393
< ysangkok> nickler: can the pre_session be reused? if i understand correctly, it can
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #18392: ci: Run feature_block in valgrind (master...2003-ciMoreVal) https://github.com/bitcoin/bitcoin/pull/18392
< bitcoin-git> [bitcoin] MarcoFalke reopened pull request #18392: ci: Run feature_block in valgrind (master...2003-ciMoreVal) https://github.com/bitcoin/bitcoin/pull/18392
< instagibbs> wallet meeting? or are people fighting off the corona
< achow101> instagibbs: off by an hour
< instagibbs> :| I was sure I set iceland time
< instagibbs> ah only did that for main meeting, rekt
< sipa_> instagibbs: i think you're off by 169 hours
< achow101> 169?
< instagibbs> he's claiming off by week error in addition
< achow101> ah. my calendar says today though
< achow101> wait no it doesn't
< sipa> we had one last week
< instagibbs> ok my calendar is completely screwed up somehow
< bitcoin-git> [bitcoin] brakmic opened pull request #18394: test: added test for JSONRPC-objects (master...expanding-rpc-test-coverage) https://github.com/bitcoin/bitcoin/pull/18394
< wumpus> kanzure: FWIW i haven't found out what was the problem, have started a new pubring from scratch importing individual keys, but your key definitely wasn't the problem
< kanzure> thank you
< wumpus> when i tried to reimport the entire set of keys it was hanging again, so have to go one by one; there's one key with 2000 signatures(?) that i suspect
< wumpus> ouch, "Tor Browser Developers (signing key) <torbrowser@torproject.org>" has 22MB of signatures, wouldn't recomment importing that one
< midnight> i thought sks-replacement servers strip sigs now
< wumpus> that's good at least