[bitcoin] luke-jr closed pull request #15600: lockedpool: When possible, use madvise to avoid including sensitive information in core dumps or forked process memory spaces (master...lockedpool_dontdump) https://github.com/bitcoin/bitcoin/pull/15600
[bitcoin] MarcoFalke merged pull request #15897: QA/mininode: Send all headers upfront in send_blocks_and_test to avoid sending an unconnected one (master...qa_mininode_headers) https://github.com/bitcoin/bitcoin/pull/15897
[bitcoin] luke-jr opened pull request #15913: Bugfix: dummywallet: Add -ignorepartialspends to list of ignored wallet options (master...bugfix_nowallet_avoidpspends) https://github.com/bitcoin/bitcoin/pull/15913
We're removing BIP70 from bitcoin core completely, since essentially nothing uses it (except bitpay) --- we were close to removing it when they made it mandatory, then we held off, but since their implementation is hardly compatible there really isn't much reason to not remove it just for them.
Is it a bug with Bitpay or Bitcoin Core?
I just made a Bitcoin payment and the merchant uses Bitpay. First of all, the webpage displayed a "We see you are using Bitcoin Core" message which freaked me out. How can they know that? Secondly, I got this weird Bitcoin Core error popup when actually performing the payment (which had a green coloring around it): "Error communicating with https://bitpay.com/i/<REDACTED>: Error transferring https://bitpay.com/i/<REDACTED> - server