1 2017-09-09 00:56:07	0|meshcollider|there we go, travis is happy once again
 2 2017-09-09 00:57:35	0|sipa|\o/
 3 2017-09-09 04:47:36	0|Machine_Ex98|Hi all
 4 2017-09-09 09:10:54	0|meshcollider|There's no support for BIP 39 in core currently is there
 5 2017-09-09 09:11:50	0|sipa|no
 6 2017-09-09 09:12:28	0|meshcollider|#11085 is adding ability to set a new HD seed using a WIF private key, would there be any reason not to take that further and allow setting a 512 bit seed or even mnemonic itself?
 7 2017-09-09 09:50:06	0|gmaxwell|meshcollider: bip39 is a bad spec, disavowed by some of its authors even. Among other issues it has no facilities for versioning, which is a critical flaw.
 8 2017-09-09 09:55:34	0|meshcollider|mhm true, but its pretty widely supported in hardware wallets and online wallets for backups so even if we didn't add mnemonic support itself, wouldn't it be useful to be able to set any seed for an HD wallet if you wanted to? Not just using a WIF private key?
 9 2017-09-09 09:56:10	0|gmaxwell|doesn't make any sense.
10 2017-09-09 09:56:15	0|gmaxwell|you can import indivigual keys
11 2017-09-09 09:56:27	0|gmaxwell|but just having the same seed wouldn't result in the same derrived keys
12 2017-09-09 09:56:37	0|gmaxwell|unless the feature set and style were exactly the same.
13 2017-09-09 09:57:19	0|gmaxwell|The whole idea of compatibly imported keys is wrongheaded-- at least in a world where all wallets don't have exactly the same functionality-- and can result in funds loss.
14 2017-09-09 09:57:45	0|meshcollider|I mean, most support bip 32, 39 and 44, so if you imported the 512 bit seed generated from a mnemonic from bip 39, using bip 32 to generate master key, you'd have all the same keys?
15 2017-09-09 09:58:18	0|meshcollider|as long as they support the same seed -> master key in bip32 and tree structure in bip44
16 2017-09-09 09:58:38	0|gmaxwell|Which we will not, because it's insecure if key export is possible.
17 2017-09-09 10:00:03	0|meshcollider|not sure what you mean sorry?
18 2017-09-09 10:00:05	0|gmaxwell|and again, not actually compatible because.. unversioned.. how do you know if the key is using segwit or not.. p2sh or not.
19 2017-09-09 10:00:13	0|meshcollider|key export is possible currently with dumpwallet?
20 2017-09-09 10:00:41	0|gmaxwell|meshcollider: bip 44 forces public derrivation, if you give someone one private key and they find out your extended public key they can derrive all your private keys.
21 2017-09-09 10:01:27	0|gmaxwell|BIP44 basically violates bip32 by applying public derrivation to all cases, it should only be used in cases where export is not permitted;  which is plausable for hardware wallets.
22 2017-09-09 10:02:46	0|meshcollider|ohhh you mean no to adding bip 44 support, not importing arbitrary seeds
23 2017-09-09 10:03:03	0|meshcollider|Yeah good point, fair enough then it would be pretty useless 👍
24 2017-09-09 10:03:36	0|meshcollider|I was only thinking about the security of importing the seed, not about bip44 itself hence my confusion
25 2017-09-09 10:03:44	0|gmaxwell|at some point we might support wallets which have export disabled, e.g. wallets with a public derrivation of whatever path, but it should be seperate.
26 2017-09-09 10:03:54	0|gmaxwell|with multiwallet thats more reasonable.
27 2017-09-09 17:00:28	0|bitcoin-git|[13bitcoin] 15jamesob opened pull request #11293: Deduplicate CMerkleBlock construction code, add test coverage (06master...06dedup-cmerkleblock) 02https://github.com/bitcoin/bitcoin/pull/11293
28 2017-09-09 17:14:48	0|aleph_null|what is the latency in the FIBRE network?
29 2017-09-09 17:15:00	0|aleph_null|in practical, every day scenarios
30 2017-09-09 18:20:58	0|gmaxwell|aleph_null: a couple milliseconds over the best path distances 95% of the time.
31 2017-09-09 18:21:14	0|bane5000|Hey guys, was thinking about running a bitcoin core p2p only headless server on debian. Just had a couple of questions regarding the online documentation... first of all, do you recommend running this as root? Would it be wiser to run the daemon as a separate user/group?
32 2017-09-09 18:22:15	0|bane5000|Also, I know how to operate a firewall, with that being said, does the p2p function require upnp? Would i be safe to turn it off and just forward incoming connections on port 8333 (or whichever port it is) to the server?
33 2017-09-09 18:22:17	0|bane5000|Thanks guys :)
34 2017-09-09 18:25:31	0|sipa|bane5000: no need to run as root, forwarding 8333 is perfectly fine but you'll need to configure your external ip address (-externalip=IP on cmdline, or externalip=IP in bitcoin.conf)
35 2017-09-09 18:27:34	0|bane5000|sipa: Fantastic! I appreciate the information. Also, upon compilation, i just issue ./configure --disable-wallet (if i remember correctly?)
36 2017-09-09 19:15:04	0|MarcoFalke|where is gribble? pls revive
37 2017-09-09 19:20:22	0|sipa|nanotube: ^
38 2017-09-09 19:34:32	0|nanotube|sipa: it looks like gribble is banned from here
39 2017-09-09 19:34:46	0|nanotube|* #bitcoin-core-dev Banlist: Thu Aug 17 15:16:57 2017 *!*gribble@unaffiliated/nanotube/bot/gribble sipa!~pw@unaffiliated/sipa1024
40 2017-09-09 19:36:31	0|sipa|oh, yes!
41 2017-09-09 19:36:40	0|nanotube|was it thrashing?
42 2017-09-09 19:37:13	0|sipa|it was responding with extremely large lag (minutes or more), making it more distracting than helpful
43 2017-09-09 19:37:39	0|nanotube|ah
44 2017-09-09 19:37:55	0|nanotube|it seems it's working speedily presently
45 2017-09-09 19:38:01	0|sipa|good
46 2017-09-09 19:38:44	0|nanotube|i'll tell him to join back in once the ban's off. :)