< bitcoin-git> [bitcoin] AkioNak opened pull request #15233: Prevent mutex lock fail even if --enable-debug (master...fix_mutex_lock_fail) https://github.com/bitcoin/bitcoin/pull/15233
< jonasschnelli> <achow101>jonasschnelli: should a wallet with disabled private keys be able to import a private key?
< jonasschnelli> no
< jonasschnelli> The idea is that you have a sane option where you can be 100% sure its watch only
< jonasschnelli> Ideal for combination with cold storage
< jonasschnelli> You can use fundrawtransaction and can not shoot in your own foot with – as example – create a new change address because you wrote "changeaddress" instead of "changeAddress".
< gmaxwell> I think they shouldn't be able to import a key.
< gmaxwell> and if thats a problem we should make more RPCs accept key arguments.
< gmaxwell> importing a private key in a key disabled wallet should convert the private key to pubkeys and import that, perhaps.
< bitcoin-git> [bitcoin] jonasschnelli pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/94167e2b5b7b...82cf6813a4ef
< bitcoin-git> bitcoin/master eb9ef04 Jonas Schnelli: REST: add "blockhashbyheight" call, fetch blockhash by height
< bitcoin-git> bitcoin/master 579d418 Jonas Schnelli: [QA] add rest tests for /rest/blockhashbyheight/<HEIGHT>.<FORMAT>
< bitcoin-git> bitcoin/master 42ff30e Jonas Schnelli: [Docs] add short documentation for /rest/blockhashbyheight
< bitcoin-git> [bitcoin] jonasschnelli closed pull request #14353: REST: add blockhash call, fetch blockhash by height (master...2018/09/rest_blockhash) https://github.com/bitcoin/bitcoin/pull/14353
< achow101> well it's currently possible to import a privkey to a private keys disabled wallet. it wasn't clear from the pr discussion whether this was intended
< sipa> i don't think it should convert to pubkey
< sipa> that could be very unexpected behaviour if someone thought they'd have access to that key
< sipa> failing sounds reasonable
< bitcoin-git> [bitcoin] achow101 opened pull request #15235: Do not import private keys to wallets with private keys disabled (master...fix-noprivs-import) https://github.com/bitcoin/bitcoin/pull/15235
< kallewoof> late, but agree that failing is better than converting to pubkey
< bitcoin-git> [bitcoin] ken2812221 reopened pull request #14922: [WIP] windows: Set _WIN32_WINNT to 0x0601 (Windows 7) (master...patch-1) https://github.com/bitcoin/bitcoin/pull/14922
< bitcoin-git> [bitcoin] hebasto opened pull request #15236: scripts and tools: Make --setup command independent (master...20190123-gitian-build-setup) https://github.com/bitcoin/bitcoin/pull/15236
< provoostenator> MarcoFalke: Drahtbot seems to be a bit out of control on #14053
< gribble> https://github.com/bitcoin/bitcoin/issues/14053 | Add address-based index (attempt 4?) by marcinja · Pull Request #14053 · bitcoin/bitcoin · GitHub
< provoostenator> (it's not consolidating)
< aj> provoostenator: fyi, in #14671 you reference deriveaddress as 14476 when it's actually #14667 (just a cut&paste typo)
< gribble> https://github.com/bitcoin/bitcoin/issues/14671 | Utility to replace RPC calls that dont need wallet or chain context · Issue #14671 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14667 | Add deriveaddresses RPC util method by Sjors · Pull Request #14667 · bitcoin/bitcoin · GitHub
< provoostenator> aj: fixed, thanks
< provoostenator> ^ might as well shameless plug my deriveaddress PR, which has a bunch of (out-dated) utACKs and concept ACKs an no actionable objections for to deal with...
< provoostenator> * for me
< bitcoin-git> [bitcoin] instagibbs opened pull request #15238: remove some magic mining constants in functional tests (master...magic_miner) https://github.com/bitcoin/bitcoin/pull/15238
< sipa> sdaftuar, gmaxwell, BlueMatt: those power9 systems you have are little endian, right?
< sdaftuar> yeah, mine is at least. i think matt said that it could run in either mode?
< gmaxwell> sipa: They can be run in either, I have one thats LE and one thats BE (though the BE one isn't plugged in ATM)
< gmaxwell> (also apparently the LE can run BE efficiently in QEMU)
< cjd> I noticed some recent amd64 processors have a movbe instruction, I wonder if a university student could be persuaded to write an amd64be arch for qemu, just for testing purposes
< cjd> It seems like it would make an interesting paper
< sipa> gmaxwell: so it seems that the feerate data doesn't just write a few easily-enumerable constants
< sipa> so we can't easily drop the float serialization code
< sipa> ideally the file format is changed to use some fixed precision encoding, but that's a bigger change
< sipa> so i'm still unclear how BE systems actually serialize floating point values in memory... apart from knowing there aren't really any guarantees
< gmaxwell> make a test program and I'll run it or get it run?
< sipa> will do
< midnightmagic> Or if gmax isn't around I can run such programs as well.
< sipa> cool, good to know
< dongcarl> Can someone add https://github.com/bitcoin/bitcoin/pull/14856 to the P2P board?
< dongcarl> And also remove #11387 from the P2P board?
< gribble> https://github.com/bitcoin/bitcoin/issues/11387 | net: remove more CConnman globals by theuni · Pull Request #11387 · bitcoin/bitcoin · GitHub
< sipa> p2p board?
< dongcarl> P2P refactor haha
< bitcoin-git> [bitcoin] hebasto opened pull request #15239: scripts and tools: Move non-linux build source tarballs to "bitcoin-binaries/version" directory (master...20190123-gitian-source-tarballs) https://github.com/bitcoin/bitcoin/pull/15239
< IzooooOOO> Hello !
< instagibbs> what's the min assumed version of python3 on functional tests
< instagibbs> d'oh! ok thanks
< instagibbs> 3.5 has .hex(), sad!
< dongcarl> instagibbs: I know... RIP
< dongcarl> Question for people more knowledgeable about depends: in depends/README.md, it says that the way to use the results of calling `make` in depends for bitcoin is to do ./configure --prefix=`pwd`/depends/x86_64-w64-mingw32, but in our gitian descriptor we seem to use it like so: CONFIG_SITE=`pwd`/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/. Is there a difference between the two?
< dongcarl> Also why `--prefix=/`? Seems very odd to me
< sipa> paging cfields_ ^
< ryanofsky> i know specifying --prefix lets bitcoin autoconf find the "config.site" file generated by depends
< ryanofsky> i didn't know about the CONFIG_SITE variable. it's probably not 100% identical but it seems more direct to use that if it works