1 2018-06-16 01:18:26	0|CubicEarths|Would it be reasonable to have an option where discarding blocks under pruned mode was conditional on an RPC message specifying each block to be thrown out?
 2 2018-06-16 01:19:59	0|CubicEarths|The benefit being something like a lightning node could decide when it no longer needed a block, and let Bitcoin know
 3 2018-06-16 01:24:50	0|sipa|CubicEarths: already exists
 4 2018-06-16 01:25:31	0|sipa|CubicEarths: just specify -prune rather than -prune=size, and call the pruneblockchain RPC
 5 2018-06-16 01:25:38	0|CubicEarths|sipa: amazing :)
 6 2018-06-16 02:00:27	0|luke-jr|sipa: not exactly the same thing IMO
 7 2018-06-16 02:01:02	0|luke-jr|at least as I imagine it, there would be a way for software to define "prune locks" that set a maximum height to prune to; and then those locks can be updated by the software as it scans
 8 2018-06-16 02:01:29	0|luke-jr|thus, each wallet (even not loaded) could have a persistent prune lock set until it's updated
 9 2018-06-16 02:01:38	0|luke-jr|or external programs like Lightning daemons etc
10 2018-06-16 02:03:33	0|sipa|luke-jr: yeah, a per-user way of specifying prunability rather than globally would make sense
11 2018-06-16 04:24:14	0|bitcoin-git|[13bitcoin] 15ken2812221 opened pull request #13482: Remove boost::program_options dependency (06master...06program_options) 02https://github.com/bitcoin/bitcoin/pull/13482
12 2018-06-16 05:03:53	0|CubicEarths|luke-jr: sipa: Are you taking about a way to only prune if all locks from different users up to a given height are lifted?
13 2018-06-16 05:04:23	0|luke-jr|right
14 2018-06-16 05:05:58	0|CubicEarths|I see a funny irony in that concept, since the more users / clients had locks, the less pruning would happen :)
15 2018-06-16 05:06:38	0|CubicEarths|It could be useful for a small handful of users tough
16 2018-06-16 05:06:58	0|luke-jr|useful for lots of things
17 2018-06-16 05:07:10	0|luke-jr|eg, it would enable Armory to prune
18 2018-06-16 05:07:45	0|CubicEarths|For a single user, why is pruneblockchain any different?
19 2018-06-16 05:07:59	0|luke-jr|I suppose that's workable too
20 2018-06-16 05:08:09	0|luke-jr|but it would also make it more feasible to have external indexes too
21 2018-06-16 05:09:12	0|CubicEarths|That too wouldn't be the same for a single client?
22 2018-06-16 05:09:23	0|luke-jr|you wouldn't have a single client
23 2018-06-16 05:09:31	0|luke-jr|the index would be one client, and your wallet another
24 2018-06-16 05:09:50	0|CubicEarths|I see.
25 2018-06-16 05:11:44	0|CubicEarths|Do you agree though, that if you have many clients, you are probably better off just leaving things unpruned? I mean you could allow pruning, but it would only prune as far as the most needy client allowed.
26 2018-06-16 05:12:03	0|CubicEarths|Again, it could be very effective for a small number of clients
27 2018-06-16 05:25:00	0|luke-jr|CubicEarths: the goal would be to have everything catch up reasonably
28 2018-06-16 06:12:32	0|cfields|I'll be away Mon-Fri and won't have my laptop on me, but I'll try to keep up with responses on github/mail. Not that I've been very productive lately anyway. Hoping a few days away will break me out of my slump :)
29 2018-06-16 06:13:23	0|fanquake|cfields Have a good time!
30 2018-06-16 06:13:34	0|fanquake|I'll make sure to harass you the second you are back :p
31 2018-06-16 06:14:50	0|cfields|fanquake: heh, thanks. I tried to knock out a bunch of yours this week, but I know there are several still outstanding.
32 2018-06-16 06:16:28	0|fanquake|cfields np, I've got a few more changes to PR over the weekend. Need to follow up with you about some non-Core related stuff too.
33 2018-06-16 12:10:26	0|rk3y|but lets stay in contact: mine is rk3y at protonmail.com
34 2018-06-16 12:25:31	0|fanquake|rk3y: wrong channel?
35 2018-06-16 12:50:42	0|provoostenator|luke-jr: having control over when which block gets pruned certainly seems useful, see e.g. discussion here: https://github.com/ElementsProject/lightning/issues/1502#issuecomment-390633666
36 2018-06-16 12:51:21	0|provoostenator|Even if it's just "blocks below height are now safe to prune for lock N"
37 2018-06-16 12:52:06	0|provoostenator|Somewhat related would be the ability to refetch a specific pruned block: https://github.com/ElementsProject/lightning/issues/1297#issuecomment-394228514
38 2018-06-16 12:55:02	0|provoostenator|Keeping track of these locks in a robust way seems potentially tricky though. It should probably abandon a lock if a max disk storage threshold is about to be exceeded.
39 2018-06-16 13:09:54	0|rk3y|fanquake: sorry strange shortcut + human copy paste error
40 2018-06-16 13:19:34	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/81069a75bd71...fa2ea37940ed
41 2018-06-16 13:19:35	0|bitcoin-git|13bitcoin/06master 149e2e562 15Loganaden Velvindron: Fix CVE-2018-12356 by hardening the regex.
42 2018-06-16 13:19:36	0|bitcoin-git|13bitcoin/06master 14fa2ea37 15Wladimir J. van der Laan: Merge #13479: contrib: Fix CVE-2018-12356 by hardening the regex...
43 2018-06-16 13:20:36	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13479: contrib: Fix CVE-2018-12356 by hardening the regex (06master...06master) 02https://github.com/bitcoin/bitcoin/pull/13479
44 2018-06-16 13:22:23	0|bitcoin-git|13bitcoin/06master 14634bd97 15practicalswift: Explicitly specify encoding when opening text files in Python code
45 2018-06-16 13:22:23	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/fa2ea37940ed...a90ca4087a6f
46 2018-06-16 13:22:24	0|bitcoin-git|13bitcoin/06master 14a90ca40 15Wladimir J. van der Laan: Merge #13448: Add linter: Make sure we explicitly open all text files using UTF-8 encoding in Python...
47 2018-06-16 13:22:24	0|bitcoin-git|13bitcoin/06master 14c8176b3 15practicalswift: Add linter: Make sure we explicitly open all text files using UTF-8 or ASCII encoding in Python
48 2018-06-16 13:23:18	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #13448: Add linter: Make sure we explicitly open all text files using UTF-8 encoding in Python (06master...06lint-python-utf8-encoding) 02https://github.com/bitcoin/bitcoin/pull/13448
49 2018-06-16 15:08:54	0|sipa|provoostenator: look at jonasschnelli's auxiliary blocks
50 2018-06-16 15:27:13	0|provoostenator|sipa: #9171?
51 2018-06-16 15:27:16	0|gribble|https://github.com/bitcoin/bitcoin/issues/9171 | Introduce auxiliary block requests by jonasschnelli · Pull Request #9171 · bitcoin/bitcoin · GitHub
52 2018-06-16 18:12:16	0|bitcoin-git|[13bitcoin] 15luke-jr closed pull request #10730: Move script flag to/from-string logic from tests to script/interpreter (06master...06scriptflag_strings) 02https://github.com/bitcoin/bitcoin/pull/10730
53 2018-06-16 23:21:19	0|bitcoin-git|[13bitcoin] 15ken2812221 opened pull request #13485: Ensure that event loop is empty before the loop exit (06master...06http_shutdown) 02https://github.com/bitcoin/bitcoin/pull/13485
54 2018-06-16 23:21:54	0|bitcoin-git|[13bitcoin] 15ken2812221 closed pull request #13390: Tests: Ignore RemoteDisconnected and BadStatusLine when stopping node (06master...06stop_node) 02https://github.com/bitcoin/bitcoin/pull/13390