< jtimon> There doesn't seem to be any case where consensusParams.vDeployments[anything].nTimeout == 0 at this point
< jtimon> not just for segwit, for anything in any supported chain
< bitcoin-git> [bitcoin] earonesty reopened pull request #10442: add a -bip148 option (master...master) https://github.com/bitcoin/bitcoin/pull/10442
< bitcoin-git> [bitcoin] jonasschnelli reopened pull request #8745: [PoC] Add wallet inspection and modification tool "bitcoin-wallet-tool" (master...2016/09/wallet-tool) https://github.com/bitcoin/bitcoin/pull/8745
< jonasschnelli> cfields: maybe you can help solve the compile-issues here: https://github.com/bitcoin/bitcoin/pull/8745?
< bitcoin-git> [bitcoin] jonasschnelli opened pull request #10457: Don't use fixed "wallet.bak"-filename during salvagewallet (master...2017/05/rename_bdb) https://github.com/bitcoin/bitcoin/pull/10457
< bitcoin-git> [bitcoin] dbolser opened pull request #10458: libevent2 -> libevent on FreeBSD install docs (0.14...patch-1) https://github.com/bitcoin/bitcoin/pull/10458
< bitcoin-git> [bitcoin] dbolser opened pull request #10459: I found I needed to use gmake on FreeBSD 10.3 (0.14...patch-2) https://github.com/bitcoin/bitcoin/pull/10459
< bitc-multi> hi
< bitc-multi> intressed for a Bot in Telegramm for multiply your btc? PN
< mlong> @sipa is there an objective C library for secp256k1
< sipa> how would i know?
< mlong> You built it no?
< sipa> i'm the primary author of libsecp256k1, a C library
< sipa> i don't know anything about objective C
< mlong> nice, alot of help there pete jesus
< sipa> i'm not sure what you want me to do... i honestly do not know anything about objective C
< mlong> obviously its out there, mobile wallets hello?
< sipa> yes, use goohle
< sipa> your guess is as good as mine
< sipa> *google
< cfields> jonasschnelli: i can take a look again, sure
< jonasschnelli> for the records: libsecp256k1 is used via BreadWallet which is iOS / Obj-C
< jonasschnelli> Obj-C is, like C++ a superset of C.
< jonasschnelli> So libsecp256k1 can be directly used within Obj-C code (.mm files)
< TD-Linux> gmaxwell, they got a license from intel?
< instagibbs> TD-Linux, I believe so, they applied a while back
< bitcoin-git> [bitcoin] sipa opened pull request #10460: Broadcast address every day, not 9 hours (master...hour_is_not_24_minutes) https://github.com/bitcoin/bitcoin/pull/10460
< jonasschnelli> gmaxwell: what do you think about the ledger SGX approach? Curios...
< bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4314544d46e8...b40ceed98a11
< bitcoin-git> bitcoin/master efc2e33 practicalswift: [trivial] Fix three recently introduced typos...
< bitcoin-git> bitcoin/master b40ceed Pieter Wuille: Merge #10419: [trivial] Fix three recently introduced typos...
< bitcoin-git> [bitcoin] sipa closed pull request #10419: [trivial] Fix three recently introduced typos (master...typos-201705) https://github.com/bitcoin/bitcoin/pull/10419
< TD-Linux> their implementation is pretty much all you could ask for given the constraints imposed by intel
< jonasschnelli> TD-Linux: I guess the ledger guy do well,.. but that Intel attestation... I don't know but that feels wrong.
< TD-Linux> jonasschnelli, I mean, it is a feature primarily designed for blu ray DRM.
< jonasschnelli> I didn't know that... I though it was design as a general purpose CPU enclave
< TD-Linux> okay, well intel sells it as that. but the first licensed application was powerdvd's bluray player
< jonasschnelli> Good to know.
< jonasschnelli> I'm not sure if I would trist SGX to store my keys. Things like that (https://www.bleepingcomputer.com/news/hardware/-super-malware-steals-encryption-keys-from-intel-sgx-enclaves/) frightens me.
< jonasschnelli> IMO SGX lays a floor for "next generation backdoors"
< TD-Linux> the scare of that is possibly one reason intel licenses the feature
< jonasschnelli> But only intel knows... I guess they can hand out licenses to who they want including all sorts of "agencies"...
< TD-Linux> jonasschnelli, that ship has already sailed with the ME, which has much more power than SGX.
< jonasschnelli> Yeah,... ME is worse. But if users starts to trust SGX (with the ledger or similar), intel as "indirect access" to keys.
< jonasschnelli> It may gives a very wong sense of security to users...
< jonasschnelli> (I guess we are OT here, but since nobody complains and gmaxwell posted the URL we continue)
< TD-Linux> jonasschnelli, SGX can only talk with its parent process
< jonasschnelli> TD-Linux: but AFAIK some researchers showed cache attacks via other enclaves
< TD-Linux> yes, those are identical to normal cross process or cross VM cache attacks
< TD-Linux> I think it's reasonable to say that SGX is no worse than no SGX, but not as good as a hardware wallet.
< jonasschnelli> TD-Linux: Indeed.
< jonasschnelli> But
< jonasschnelli> The part that can make it worse is the eventually false sense of security. Corporations may consider storing keys via SGX rather then a completely decoupled environment / HSM
< bitcoin-git> [bitcoin] sipa pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/b40ceed98a11...b4b057a3e071
< bitcoin-git> bitcoin/master 822755a Pieter Wuille: Fix: make CCoinsViewDbCursor::Seek work for missing keys...
< bitcoin-git> bitcoin/master 513da90 Gregory Maxwell: Add test for empty chain and reorg consistency for gettxoutsetinfo.
< bitcoin-git> bitcoin/master b4b057a Pieter Wuille: Merge #10445: Add test for empty chain and reorg consistency for gettxoutsetinfo....
< bitcoin-git> [bitcoin] sipa closed pull request #10445: Add test for empty chain and reorg consistency for gettxoutsetinfo. (master...test_more_gettxoutset) https://github.com/bitcoin/bitcoin/pull/10445
< sipa> cfields: present?
< cfields> sipa: sure! what is it?
< * cfields> loves presents
< cfields> sipa: maybe i misunderstood your question, then
< sipa> i think you can just delete the else branch
< sipa> and leave addrConnect.nServices untouched
< sipa> and if you think you can't, then my understanding of the code is probably wrong
< cfields> sipa: look at line 1799. in the event that we _don't_ have our quota of preferred outgoing nodes yet, but we've selected a last resort after 40 tries, we're only expecting NODE_NETWORK from it
< sipa> ah, yes!
< sipa> of course
< sipa> utACK
< cfields> phew, you had me scrutinizing that really hard :)
< bitcoin-git> [bitcoin] sipa opened pull request #10461: Update style guide (master...stylish) https://github.com/bitcoin/bitcoin/pull/10461
< bitcoin-git> [bitcoin] jtimon opened pull request #10462: BIP8 implementation (master...b15-bip8-min) https://github.com/bitcoin/bitcoin/pull/10462