< bitcoin-git> [bitcoin] Empact opened pull request #17907: Fix improper Doxygen inline comments (master...settings-documentation) https://github.com/bitcoin/bitcoin/pull/17907
< bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/f8c69677a1a8...e258ce792a48
< bitcoin-git> bitcoin/master 498cdbb Ben Woosley: Fix improper Doxygen inline comments
< bitcoin-git> bitcoin/master e258ce7 fanquake: Merge #17907: doc: Fix improper Doxygen inline comments
< bitcoin-git> [bitcoin] fanquake merged pull request #17907: doc: Fix improper Doxygen inline comments (master...settings-documentation) https://github.com/bitcoin/bitcoin/pull/17907
< bitcoin-git> [bitcoin] hebasto opened pull request #17908: qa, qt: Remove QFont warnings with QT_QPA_PLATFORM=minimal (master...20200111-qttest-minimal-warn) https://github.com/bitcoin/bitcoin/pull/17908
< hebasto> hmm, the option to restart travis job is missing for me now...
< luke-jr> hebasto: does Travis know you're logged in?
< hebasto> sure, I'm logged in. It is possible to "Sign Out"
< hebasto> luke-jr: signed out -> signed in. It works now, Thanks!
< Kiminuo> https://github.com/bitcoin/bitcoin/blob/master/src/net_processing.cpp#L2448 - Could anyone explain this further to me? Is that byte 0x00 required for some specific reason or is it how Satoshi did that?
< sipa> Kiminuo: the p2p protocol used to have no distinction between cblock and cblockheader
< sipa> headers were just submitted as blocks with no transactiond
< Kiminuo> thanks, that makes sene
< Kiminuo> *sense
< emilengler> Is there an efficient way to get the output type from a "WalletAddress"?
< emilengler> Or from a CTxDestination
< sipa> a CTxDestination is a boost::variant
< sipa> it has a bunch of built in methods to query the type
< emilengler> sipa: I see but what's the "best way" to get the output type from it
< emilengler> Looks like there is no function which returns OutputType where CTxDestination is a parameter of
< sipa> no, that's impossible
< sipa> you can't distinguish p2sh multisig from p2sh-p2wsh multisig for example
< sipa> just based on the address
< emilengler> Ok thanks
< sipa> what are you trying to do?
< emilengler> In bitcoin-qt I wanna sort out all non legacy addresses in the sign message dialog as they are useless in this case anyway
< emilengler> The addressbook*
< luke-jr> can't signmessage with p2sh either, so that's doable
< luke-jr> should be able to just use .get
< emilengler> luke-jr: get? Of which object?
< luke-jr> the CTxDestination
< luke-jr> boost::get<PKHash>(&dest)
< emilengler> So I need to check every possible type?
< luke-jr> only PKHash because that's the only type that's valid for signing
< luke-jr> dest.type() is another way, possibly more efficient and more flexible
< emilengler> Oh sure
< emilengler> thanks
< emilengler> what is with .which()
< emilengler> luke-jr: Thx, works