< meshcollider> https://github.com/bitcoin/bitcoin/issues/11134#issuecomment-325175820 are there any PRs for implementing stuff like this yet
< meshcollider> (change to segwit addresses)
< meshcollider> does it still need to be implemented or just reviewed
< bitcoin-git> [bitcoin] achow101 opened pull request #11169: [GUI] Make tabs toolbar no longer have a context menu (master...rm-hide-tabs) https://github.com/bitcoin/bitcoin/pull/11169
< bitcoin-git> [bitcoin] rawodb opened pull request #11170: Add label support to "addwitnessaddress" (master...pr/rpc_addwitnessaddress) https://github.com/bitcoin/bitcoin/pull/11170
< RK_> Z
< Guest68832> I just sent a tx with 0.15rc2 and used a custom fee of 0.00021234 BTC per kB (= 21.234 sat/Byte), but blockexplorers show me a fee of 14.321 sat/Byte now... what's wrong here?
< Guest68832> tx 728b5edbc55c52dab4e693d6edf8d81cd8557abfd358ab8e2208ae828f958598
< gagvd> Hi guys
< modi> hello everybody
< gagvd> Heloo
< morcos> Guest68832: It's a segwit transaction, so you paid 21.234 sat/byte of _virtual size_ which is really the only thing that matters. the fact that it is 14.321 sat/B of actual on-wire size is irrelevant
< morcos> the consensus limit is virtual size (just weight / 4) and the mining algorithm prioritizes by fee per virtual size
< modi> JOIN
< Guest68832> Thanks morcos. Is there a block explorer that shows sat/byte of virtual size for segwit tx?
< morcos> Guest60956: I've noticed that blockchain.info has something called "fee / weight unit" which you can see is 1/4 of your 21.234
< morcos> weight unit probably makes more sense than virtual size, but virtual size exists to keep things backwards compatible. a non segwit tx has virtual size = actual size
< morcos> 4 * virtual_size = weight = actual_size + 3 * base_size (base_size is everything non-witness)
< wallet42> will other data structures also get an bech32hrp? like private keys, or xpub/xpriv stuff?
< sipa> wallet42: working on it
< sipa> wallet42: bech32's checksum isn't very good for longer lengths
< jonasschnelli> gmaxwell: most possible problem of a not-appearing GUI is probably persisted windows coordinates outside of the screen boundaries.
< jonasschnelli> could be fixed by checking the screen bounds against the QSettings coords
< jonasschnelli> -resetguisettings will just evict all user based Qt overrides (and things like window coordinates)
< gmaxwell> jonasschnelli: it might be good to check...
< jonasschnelli> Yes. we should do this (it's a priority thing)
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7fd49d01dc2e...a084767b40c0
< bitcoin-git> bitcoin/master 37c4362 danra: Trivial: Documentation fixes for CVectorWriter ctors
< bitcoin-git> bitcoin/master a084767 MarcoFalke: Merge #11155: Trivial: Documentation fixes for CVectorWriter ctors...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11155: Trivial: Documentation fixes for CVectorWriter ctors (master...patch-8) https://github.com/bitcoin/bitcoin/pull/11155
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/a084767b40c0...ede386c2193f
< bitcoin-git> bitcoin/master 946638d danra: Improve versionbits_computeblockversion test code consistency...
< bitcoin-git> bitcoin/master ede386c MarcoFalke: Merge #11160: Improve versionbits_computeblockversion test code consistency...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11160: Improve versionbits_computeblockversion test code consistency (master...patch-9) https://github.com/bitcoin/bitcoin/pull/11160