1 2017-09-13 01:58:36 <molz> Chris_Stewart_5, kanzure does  <Chris_Stewart_5> Who moderates the bitcoin dev mailing list?
 2 2017-09-13 02:39:49 <ossifrage> Any idea why bitcoin-msghand generates quite so much disk read traffic (vs outbound network traffic)?
 3 2017-09-13 02:42:09 <ossifrage> What option to I need to set to include more of the UTXO in ram vs pulling it off disk?
 4 2017-09-13 02:42:57 <gmaxwell> ossifrage: the disk traffic is fetching blocks to feed to other peers. All newly recieved blocks are written out and read in again (though this doesn't take that much time due to OS disk caching)
 5 2017-09-13 02:44:14 <ossifrage> gmaxwell, I'm currently not serving old blocks (the 24 hour limit is reached). The amount of disk read greatly exceeds the amount of network traffic
 6 2017-09-13 02:44:38 <ossifrage> >128MB in ~60s from bitcoin-msghand
 7 2017-09-13 02:46:11 <gmaxwell> ossifrage: why are you asking in here instead of #bitcoin-core-dev ?
 8 2017-09-13 02:46:20 <gmaxwell> (I just noticed the channel)
 9 2017-09-13 02:47:49 <ossifrage> gmaxwell, ok, will move... Need to collect better data first, it just seems like there is a read amplification someplace...
10 2017-09-13 02:51:28 <gmaxwell> ossifrage: sure, there is, in validating blocks it can read a lot more data than the block itself.
11 2017-09-13 02:51:56 <gmaxwell> and with compact blocks in use, the blocks themselves are quite small. :)
12 2017-09-13 02:52:46 <gmaxwell> though 128MB in 60s is more than I expect for sure.
13 2017-09-13 02:53:08 <ossifrage> No new blocks in the sampling window, just inbound txn and minimal network traffic but 100s of MB of read traffic (I assumed due to the incoming txns)
14 2017-09-13 02:54:07 <ossifrage> I need to get a clean network usage plus iotop output
15 2017-09-13 02:55:33 <gmaxwell> ossifrage: here on a long uptime node with a big dbcache I see 180.15kB/s read (60s average)
16 2017-09-13 02:56:05 <gmaxwell> oh wait sorry that was over all uptime. actual number is 114kB/s.
17 2017-09-13 02:56:44 <gmaxwell> and that is just an ordinary node plus a testnet node... so sounds like a lot less traffic than you're seeing!
18 2017-09-13 02:57:49 <ossifrage> I have the default dbcache, ~16 day uptime and 86 connections...
19 2017-09-13 02:59:53 <ossifrage> Since Sept 1, bitcoin-msghand has read 217G and written 2.3G (network is only 8GB rx, 65GB tx)
20 2017-09-13 03:00:59 <ossifrage> QThread has read 5.33G and written 90.9G (I'm running bitcoin-qt)
21 2017-09-13 12:44:14 <Chris_Stewart_5> molz: Did you figure out who moderates the list?
22 2017-09-13 12:44:37 <molz> Chris_Stewart_5, i asked btcdrak
23 2017-09-13 12:45:33 <Chris_Stewart_5> molz: Cool, thanks! Someone I am working with had their email bounced from the mailing list for some reason.
24 2017-09-13 12:45:40 <Chris_Stewart_5> and it is a high quality email -- not spam
25 2017-09-13 14:27:06 <btcdrak> Chris_Steward_5: ask kanzure
26 2017-09-13 15:54:28 <kanzure> bouncing is not under my control
27 2017-09-13 15:54:35 <kanzure> bouncing is an email protocol problem
28 2017-09-13 19:14:07 <brianhoffman__> anyone know what the estimated release for 0.15.1 is?
29 2017-09-13 19:14:20 <brianhoffman__> it will include full bech32 support correct?
30 2017-09-13 19:31:00 <achow101> brianhoffman__: the release date is still tbd. the stuff for it is still being worked on
31 2017-09-13 19:31:09 <brianhoffman__> ok thank you
32 2017-09-13 19:31:13 <achow101> what will actually go in is also tbd
33 2017-09-13 19:31:21 <achow101> just "segwit wallet stuff"
34 2017-09-13 19:35:56 <gmaxwell> This isn't a good channel to ask about bitcoin core features. #bitcoin-core-dev in the future.
35 2017-09-13 19:50:08 <brianhoffman__> oh i have to go one turtle down further from #bitcoin to #bitcoin-dev to #bitcoin-core-dev
36 2017-09-13 21:25:06 <jrick> how does fundrawtransaction determine the tx fee/kB to use? (on testnet) i'm seeing it use a fee rate of 0.00020000 when the mempool relay fee is 0.00001000 and there is no user-set fee in the wallet
37 2017-09-13 21:26:22 <jrick> a bit disconcerting when you see fees 20x what you expect them to be :)
38 2017-09-13 22:58:01 <iwkse> hi, there's a way to log wallet.dat? For example knowing when it receives new keys
39 2017-09-13 22:58:39 <iwkse> basically I'm trying to figure out when I should backup that file
40 2017-09-13 23:24:36 <StopAndDecrypt> your back up is a snapshot of the wallet at the time you backed it up
41 2017-09-13 23:24:47 <StopAndDecrypt> the actual file updates everytime a change is made
42 2017-09-13 23:25:28 <StopAndDecrypt> how often you back up is your choice, but as long as you're using HD keys it wont matter
43 2017-09-13 23:26:50 <StopAndDecrypt> which you should be if your client relatively up to date (dont know when it was added)
44 2017-09-13 23:29:16 <StopAndDecrypt> https://en.bitcoin.it/wiki/Deterministic_wallet#Type_2_hierarchical_deterministic_wallet
45 2017-09-13 23:30:45 <StopAndDecrypt> basically as long as you have the seed or the wallet.dat, the client will "look into the future" 1000 keys to see if any of those addresses were used
46 2017-09-13 23:34:22 <iwkse> StopAndDecrypt: thanks I will read on the wiki. With seed I guess you mean a paper wallet right?
47 2017-09-13 23:36:13 <StopAndDecrypt> i just realized i explained it twice to the same person lol
48 2017-09-13 23:37:07 <iwkse> lol
49 2017-09-13 23:37:25 <iwkse> I though you wanted to move the discussion on there as it's probably OT here