1 2017-05-10 04:21:04	0|jl2012|does --prematurewitness work on mainnet?
 2 2017-05-10 04:22:34	0|jl2012|i think it works.
 3 2017-05-10 05:43:02	0|wumpus|MarcoFalke: thanks for letting me know, I'll have a look what went wrong
 4 2017-05-10 06:13:01	0|wumpus|doxygen shoould be up to date again
 5 2017-05-10 09:24:51	0|kallewoof|Is there a neat and tidy way to store metadata on a per address (or key) basis? CKeyMetadata does not seem to ever be updated, and CAddressBookData seems to be about accounts not addresses (at least "name" is the account name).
 6 2017-05-10 09:25:06	0|kallewoof|Since accounts are about to be thrown out I don't really wanna touch the latter.
 7 2017-05-10 09:26:33	0|kallewoof|And besides, I can't tell how persistent either of them are. I don't want the data to vanish suddenly.
 8 2017-05-10 09:33:37	0|wumpus|kallewoof: DestData
 9 2017-05-10 09:33:59	0|wumpus|it stores data on per-address/destination basis
10 2017-05-10 09:34:14	0|wumpus|this is used to store metadata such as payment requests
11 2017-05-10 09:35:44	0|kallewoof|wumpus: Ahh, thanks!
12 2017-05-10 09:38:06	0|bitcoin-git|[13bitcoin] 15madeo opened pull request #10380: [doc] Removing comments about dirty entries on txmempool (06master...06master) 02https://github.com/bitcoin/bitcoin/pull/10380
13 2017-05-10 10:39:22	0|jl2012|Want to double check, according to BIP9, height of the first block with new rules is divisible by 2016?
14 2017-05-10 10:39:53	0|jl2012|(Not 1 before or after?)
15 2017-05-10 15:14:34	0|wumpus|jl2012: AFAIK that is correct
16 2017-05-10 15:17:06	0|bitcoin-git|[13bitcoin] 15laanwj pushed 6 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/4b766fcdd4ca...a26280bc1415
17 2017-05-10 15:17:07	0|bitcoin-git|13bitcoin/06master 147d92c6f 15fanquake: [depends] Latest config.guess and config.sub
18 2017-05-10 15:17:07	0|bitcoin-git|13bitcoin/06master 14d78269a 15fanquake: [depends] Boost 1.64.0
19 2017-05-10 15:17:08	0|bitcoin-git|13bitcoin/06master 14daeb767 15fanquake: [depends] libevent 2.1.8-stable
20 2017-05-10 15:17:35	0|jl2012|wumpus: thanks. Say it activates at 201600, if I want to make sure my tx won't get in an earlier block, the nLockTIme should be 201599, right?
21 2017-05-10 15:17:44	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10325: 0.15.0 Depends Updates (06master...06depends-0-15-0) 02https://github.com/bitcoin/bitcoin/pull/10325
22 2017-05-10 15:22:23	0|wumpus|yes
23 2017-05-10 15:22:53	0|wumpus|eh I'm not entirely sure actually if nLockTime would need to be 201600 or 201599
24 2017-05-10 15:24:36	0|wumpus|I think 201599 but not 100% sure
25 2017-05-10 15:29:23	0|SopaXorzTaker|wait
26 2017-05-10 15:29:35	0|SopaXorzTaker|AntPool mine nearly empty blocks for their advantage
27 2017-05-10 15:29:45	0|SopaXorzTaker|why can't we implement proof-of-UTXO
28 2017-05-10 15:30:22	0|SopaXorzTaker|e.g. a block must include at least len(UTXO)/n transactions or 1 MB of them, either is smaller
29 2017-05-10 16:05:46	0|instagibbs|SopaXorzTaker, this is more for #bitcoin, as it's not short-term development
30 2017-05-10 16:16:08	0|SopaXorzTaker|instagibbs, this is about the core, though
31 2017-05-10 16:16:30	0|SopaXorzTaker|how do I write a BIP? *excited*
32 2017-05-10 16:18:02	0|sipa|SopaXorzTaker: this idea gets proposed about once per month for the past few years. it's utterly broken, as miners can just stuff their blocks with their own transactions
33 2017-05-10 16:18:20	0|sipa|SopaXorzTaker: and bitcoin development is not just bitcoin core development
34 2017-05-10 16:18:55	0|SopaXorzTaker|hmm
35 2017-05-10 16:19:40	0|SopaXorzTaker|maybe a subreward based on the coin age (since the input TX)?
36 2017-05-10 16:19:57	0|sipa|take it elsewhere, sorry
37 2017-05-10 16:20:16	0|SopaXorzTaker|no problem, I understand this is not the right place
38 2017-05-10 16:20:17	0|sipa|we're developing software here, not wonder idly about tweaks to the consensus protocol
39 2017-05-10 16:21:20	0|sipa|discussions like this belong on the mailing list, where they're open for everyone
40 2017-05-10 16:24:07	0|sipa|but again, such ideas really don't work
41 2017-05-10 17:49:36	0|bitcoin-git|[13bitcoin] 15paveljanik opened pull request #10381: Shadowing is not enabled by default, update doc accordingly (06master...0620170510_Wshadow_not_enabled_by_default) 02https://github.com/bitcoin/bitcoin/pull/10381
42 2017-05-10 18:45:59	0|bitcoin-git|[13bitcoin] 15Casimir1904 opened pull request #10382: test (06master...06release) 02https://github.com/bitcoin/bitcoin/pull/10382
43 2017-05-10 18:46:15	0|bitcoin-git|[13bitcoin] 15Casimir1904 closed pull request #10382: test (06master...06release) 02https://github.com/bitcoin/bitcoin/pull/10382
44 2017-05-10 19:54:19	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10383: [logging] log system time and mock time (06master...06log_mocktime) 02https://github.com/bitcoin/bitcoin/pull/10383
45 2017-05-10 20:12:15	0|bitcoin-git|[13bitcoin] 15jonasschnelli opened pull request #10384: Make sure we disable NODE_BLOOM when pruning is enabled (06master...062017/05/prune_bloom) 02https://github.com/bitcoin/bitcoin/pull/10384
46 2017-05-10 20:15:49	0|jonasschnelli|BlueMatt: but in prune, we disable NODE_NETWORK but *NOT* NODE_BLOOM
47 2017-05-10 20:15:59	0|jonasschnelli|So.. in prune mode, we can't offer bloom filtering..
48 2017-05-10 20:16:03	0|BlueMatt|that is correct
49 2017-05-10 20:16:14	0|BlueMatt|we can bloom in prune mode, though
50 2017-05-10 20:16:22	0|jonasschnelli|Not reliable...
51 2017-05-10 20:16:27	0|BlueMatt|we will still filter mempool requests and can provide filtered access to recent blocks
52 2017-05-10 20:16:35	0|BlueMatt|what do you mean not reliably? we still provide the last few blocks
53 2017-05-10 20:16:38	0|BlueMatt|and mempool
54 2017-05-10 20:17:07	0|jonasschnelli|You argument would also say that we can serve "blocks"...
55 2017-05-10 20:17:16	0|BlueMatt|hmm?
56 2017-05-10 20:17:28	0|sipa|NODE_NETWORK indicates we can serve blocks
57 2017-05-10 20:17:32	0|Eliel_|you might not be able to provide all transaction history, but you'll be able to provide all the data the light node needs to make transactions.
58 2017-05-10 20:17:36	0|sipa|NODE_BLOOM indicates we can filter whatever is served
59 2017-05-10 20:17:39	0|BlueMatt|sipa: in this case !NODE_NETWORK
60 2017-05-10 20:17:42	0|jonasschnelli|If we can't server blocks we can't filter them
61 2017-05-10 20:17:48	0|sipa|jonasschnelli: yes, so?
62 2017-05-10 20:18:03	0|BlueMatt|i mean maybe the correct response is to add the new recent blocks serve bits
63 2017-05-10 20:18:04	0|sipa|NODE_BLOOM does not mean "i provide access to all historical blocks"
64 2017-05-10 20:18:07	0|BlueMatt|and then we can do those | NODE_BLOOM
65 2017-05-10 20:18:33	0|jonasschnelli|sipa: hmm.. okay. I see your point.
66 2017-05-10 20:19:13	0|jonasschnelli|I was misinterpreting NODE_BLOOM
67 2017-05-10 20:19:23	0|BlueMatt|jonasschnelli: proposed BIP text updates? :p
68 2017-05-10 20:19:50	0|sipa|jonasschnelli: well it can be clarified in the BIP i guess
69 2017-05-10 20:19:56	0|jonasschnelli|Na... I think it's good.
70 2017-05-10 20:19:56	0|sipa|jonasschnelli: but it's the most useful interpretation
71 2017-05-10 20:20:08	0|sipa|independent bits for independent features
72 2017-05-10 20:20:16	0|BlueMatt|jonasschnelli: misunderstandings are usually an indication that the BIP text needs to be clarified
73 2017-05-10 20:20:26	0|BlueMatt|just because you can go back and read it a different way isnt a useful outcome :p
74 2017-05-10 20:20:28	0|jonasschnelli|I was a bit confused about the use case NODE_BLOOM & ~NODE_NETWORK...
75 2017-05-10 20:20:36	0|BlueMatt|great, should be clarified! :p
76 2017-05-10 20:20:38	0|sipa|jonasschnelli: there is likely none
77 2017-05-10 20:20:45	0|jonasschnelli|mempool filtering maybe
78 2017-05-10 20:20:57	0|sipa|jonasschnelli: but there likely will be a use case for NODE_BLOOM & NODE_LAST_WEEK_BLOCKS
79 2017-05-10 20:21:03	0|sipa|s/&/|/
80 2017-05-10 20:21:13	0|BlueMatt|or (NODE_BLOOM & ~NODE_NETWORK) | SERVES_RECENT_BLOCKS
81 2017-05-10 20:21:20	0|jonasschnelli|Yes... i was stumbled over this during my NODE_NETWORK_LIMITED work
82 2017-05-10 20:22:43	0|bitcoin-git|[13bitcoin] 15jonasschnelli closed pull request #10384: Make sure we disable NODE_BLOOM when pruning is enabled (06master...062017/05/prune_bloom) 02https://github.com/bitcoin/bitcoin/pull/10384
83 2017-05-10 21:40:21	0|BlueMatt|sipa: have you seen http://www.agner.org/optimize/optimizing_cpp.pdf ?
84 2017-05-10 21:41:23	0|BlueMatt|figured you might be curious given your occasional overoptimization tendancies :p
85 2017-05-10 21:42:15	0|sipa|how do you mean 'occasional'? ;)
86 2017-05-10 21:42:40	0|BlueMatt|guy also has a everything-you-didnt-want-to-know-about-x86-internals pdf on the same site
87 2017-05-10 21:48:54	0|gmaxwell|yea, his figures are pretty good.
88 2017-05-10 21:49:45	0|TD-Linux|yes, his microarchitecture guides and instruction cycle PDFs are the only such resource out there if you're doing assembly
89 2017-05-10 23:22:31	0|bitcoin-git|[13bitcoin] 15pinheadmz opened pull request #10385: RPC: getblock returns coinbase scriptsig (06master...06cbtext) 02https://github.com/bitcoin/bitcoin/pull/10385