1 2018-06-15 01:34:43 0|bitcoin-git|13bitcoin/06master 14abd2678 15Ben Woosley: Drop ParseHashUV in favor of calling ParseHashStr...
2 2018-06-15 01:34:43 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/1939536eea7a...2b770080a49f
3 2018-06-15 01:34:44 0|bitcoin-git|13bitcoin/06master 142b77008 15MarcoFalke: Merge #13422: Drop ParseHashUV in favor of calling ParseHashStr...
4 2018-06-15 01:35:22 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13422: Drop ParseHashUV in favor of calling ParseHashStr (06master...06parse-hash-uv) 02 https://github.com/bitcoin/bitcoin/pull/13422
5 2018-06-15 05:30:36 0|jojeyh|in regards to moving over to libevent, is the goal to replace ALL networking functionality to use libevent?
6 2018-06-15 07:09:11 0|bitcoin-git|[13bitcoin] 15nikhilkumar94 opened pull request #13474: For Testing (06master...06master) 02 https://github.com/bitcoin/bitcoin/pull/13474
7 2018-06-15 07:10:27 0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #13474: For Testing (06master...06master) 02 https://github.com/bitcoin/bitcoin/pull/13474
8 2018-06-15 07:20:55 0|kallewoof|I am looking for ZMQ dumps or any other format of log files showing when transactions enter/exit the mempool, as well as when blocks are mined (although the
9 2018-06-15 07:21:22 0|kallewoof|latter can be deduced with some work). If anyone has dumps let me know. I have most of this year covered but missing most of January.
10 2018-06-15 08:38:07 0|bitcoin-git|[13bitcoin] 15murrayn opened pull request #13476: Fix incorrect shell quoting in FreeBSD build instructions. (06master...06freebsd-doc) 02 https://github.com/bitcoin/bitcoin/pull/13476
11 2018-06-15 09:49:00 0|provoostenator|Are there any WIP branches or proposals / discussions regarding partial functionality while IBD is in progress?
12 2018-06-15 09:50:27 0|provoostenator|And the various security trade-offs. For example showing a freshly generated receive address seems perfectly safe vs. trusting the mempool when the address receives funds very unsafe.
13 2018-06-15 09:51:27 0|provoostenator|But perhaps, after a header sync, temporarily assuming the most recent block is valid and validating all new blocks (while IBD catches up), would give at least some confidence that the funds are actually there if confirmed.
14 2018-06-15 09:52:57 0|provoostenator|Scarier, but very interesting if possible, would be if you can open a lightning channel, either where it's purely your own funds at stake and you only spend those, or the reverse where only the other side spends.
15 2018-06-15 09:54:51 0|provoostenator|I'm aware of #9483 but this would be orthogonal to any SPV or even neutrino stuff.
16 2018-06-15 09:54:55 0|gribble|https://github.com/bitcoin/bitcoin/issues/9483 | Complete hybrid full block SPV mode by jonasschnelli ÷ Pull Request #9483 ÷ bitcoin/bitcoin ÷ GitHub
17 2018-06-15 09:58:17 0|provoostenator|Use case is basically: user just bought some low power ARM device, a smart phone or Pi, which needs a week to do initial sync. During IBD such a device is useless, so everyone uses light-weight clients, even though long term it might be perfectly capable of staying in sync as a full node. So that 1 week experience causes a poor long term trade-off.
18 2018-06-15 10:06:06 0|provoostenator|It could even spend 5 minutes downloading and partially validating the most recent 300 blocks; obviously it doesn't know the UTXO set, but at least it can check against complete nonsense.
19 2018-06-15 10:10:14 0|provoostenator|Argh, this is the second time I misinterpreted the title of 9483, and agree with Luke's comment at the top. Will study it a bit more closely.
20 2018-06-15 13:21:37 0|bitcoin-git|13bitcoin/06master 14c9924a2 15murrayn: Fix incorrect shell quoting in FreeBSD build instructions.
21 2018-06-15 13:21:37 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/2b770080a49f...9501938a4453
22 2018-06-15 13:21:38 0|bitcoin-git|13bitcoin/06master 149501938 15MarcoFalke: Merge #13476: Fix incorrect shell quoting in FreeBSD build instructions....
23 2018-06-15 13:22:32 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13476: Fix incorrect shell quoting in FreeBSD build instructions. (06master...06freebsd-doc) 02 https://github.com/bitcoin/bitcoin/pull/13476
24 2018-06-15 13:36:05 0|bitcoin-git|13bitcoin/06master 14ad691f6 15practicalswift: Add linter: Enforce the source code file naming convention described in the developer notes
25 2018-06-15 13:36:05 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/9501938a4453...32bf4c619d2a
26 2018-06-15 13:36:06 0|bitcoin-git|13bitcoin/06master 1432bf4c6 15MarcoFalke: Merge #13450: Add linter: Enforce the source code file naming convention described in the developer notes...
27 2018-06-15 13:36:53 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13450: Add linter: Enforce the source code file naming convention described in the developer notes (06master...06lint-filenames) 02 https://github.com/bitcoin/bitcoin/pull/13450
28 2018-06-15 13:58:20 0|bitcoin-git|13bitcoin/06master 1425bc961 15Matt Corallo: Document validationinterace callback blocking deadlock potential.
29 2018-06-15 13:58:20 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/32bf4c619d2a...43fa3554b759
30 2018-06-15 13:58:21 0|bitcoin-git|13bitcoin/06master 1443fa355 15MarcoFalke: Merge #13402: Document validationinterace callback blocking deadlock potential....
31 2018-06-15 13:59:07 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13402: Document validationinterace callback blocking deadlock potential. (06master...062018-05-abc-scheduler-docs) 02 https://github.com/bitcoin/bitcoin/pull/13402
32 2018-06-15 14:12:20 0|fanquake|wumpus: You must have just about ripped out every trace of Qt4 now..
33 2018-06-15 14:29:32 0|wumpus|fanquake: I hope I pulled it out with all roots now, though it seems more pervasive then I thought
34 2018-06-15 14:30:18 0|fanquake|wumpus Your doing a good job so far. I've been looking at the leftover QT_VERSION related code, I think we'll be able to clean it up a lot further after that PR is merged.
35 2018-06-15 14:30:20 0|wumpus|but I'm happy people are looking for all remaning traces of it, better to to this in one go
36 2018-06-15 14:30:45 0|fanquake|Although going to depend somewhat on where we set the minimum required Qt
37 2018-06-15 14:38:58 0|fanquake|Just looking at Qt "supported versions", the lowest version of qt5 that is still supported is 5.6 (LTS), and that ends in March 2019.
38 2018-06-15 14:39:40 0|fanquake|5.9 (LTS), which we might move depends too, is supported until May 2020
39 2018-06-15 14:40:31 0|wumpus|I think we should try to support as many versions as possible, unless there's good reason not to
40 2018-06-15 14:40:38 0|fanquake|Obviously not saying we have to jump to 5.9 as a minimum.. but Qt's release frequency is getting quite aggressive
41 2018-06-15 14:40:50 0|wumpus|yes, agreed
42 2018-06-15 14:41:27 0|fanquake|Wondering if someone will volunteer to compile with increasingly older versions of Qt5, until something breaks :p
43 2018-06-15 14:47:12 0|wumpus|someone must be using debian stable or some othe rdistro with an old qt
44 2018-06-15 14:54:52 0|fanquake|Pretty sure everyone running Core is using Debian sid and the master branch on GH? Alleviating the need to support anything older than a few weeks
45 2018-06-15 15:36:14 0|fanquake|wumpus Opened #13478 for qt5 minimum discussion, will add some more thoughts a bit later
46 2018-06-15 15:36:15 0|gribble|https://github.com/bitcoin/bitcoin/issues/13478 | [RFC] gui: Minimum required Qt5 ÷ Issue #13478 ÷ bitcoin/bitcoin ÷ GitHub
47 2018-06-15 16:06:16 0|provoostenator|fanquake: "not far away" points back to the issue itself
48 2018-06-15 16:09:42 0|provoostenator|I can do some testing with older QT5 versions on macOS, though on macOS it seems unlikely users can't upgrade to Qt5-fairly-recent, except if they have old (e.g. 32 bit) machines: http://doc.qt.io/qt-5/osx.html#macos-versions
49 2018-06-15 16:11:36 0|provoostenator|Seems like those Macs are older than Bitcoin itself though: https://apple.stackexchange.com/questions/99640/how-old-are-macs-that-cannot-run-64-bit-applications
50 2018-06-15 16:12:31 0|provoostenator|(I'll look at the other requirements than 64 bit later)
51 2018-06-15 16:20:39 0|luke-jr|I'd be surprised if they can run our minimum required macOS version
52 2018-06-15 16:20:57 0|wumpus|yes, 32-bit mac is completely irrelevant to us
53 2018-06-15 16:30:31 0|wumpus|0.16.1 executables up btw https://bitcoincore.org/bin/bitcoin-core-0.16.1/
54 2018-06-15 16:30:38 0|bitcoin-git|13bitcoin/06master 14280924e 15Wladimir J. van der Laan: doc: Add historical release notes for 0.16.1...
55 2018-06-15 16:30:38 0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 06master: 02 https://github.com/bitcoin/bitcoin/commit/280924e6729b83b979a1b7384927b4fbc941b2fd
56 2018-06-15 16:32:31 0|bitcoin-git|13bitcoin/06master 149b72c98 15Ben Woosley: scripted-diff: Avoid temporary copies when looping over std::map...
57 2018-06-15 16:32:31 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/280924e6729b...be27048a1842
58 2018-06-15 16:32:32 0|bitcoin-git|13bitcoin/06master 14be27048 15MarcoFalke: Merge #13241: scripted-diff: Avoid temporary copies when looping over std::map...
59 2018-06-15 16:33:08 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13241: scripted-diff: Avoid temporary copies when looping over std::map (06master...06pair-const-key) 02 https://github.com/bitcoin/bitcoin/pull/13241
60 2018-06-15 16:43:54 0|harding|wumpus: release PR for the website updated to use correct dates and magnet URI, and it now passes Travis. It needs you, jonasschnelli, or jnewbery to Approve PR for me to be able to merge.
61 2018-06-15 16:51:30 0|wumpus|harding: ACKed
62 2018-06-15 16:52:22 0|harding|wumpus: thanks! Merging momentarily.
63 2018-06-15 17:26:26 0|cfields|Empact: neat! Nice work.
64 2018-06-15 17:26:40 0|cfields|Empact: turns out clang has a warning for those. Mind if i go ahead and clean up the rest, and add the warning?
65 2018-06-15 17:39:03 0|cfields|Empact: turned out to be trivial, I'm just going to go ahead and PR it.
66 2018-06-15 17:46:11 0|bitcoin-git|[13bitcoin] 15loganaden opened pull request #13479: Fix CVE-2018-12356 by hardening the regex. (06master...06master) 02 https://github.com/bitcoin/bitcoin/pull/13479
67 2018-06-15 17:54:31 0|bitcoin-git|[13bitcoin] 15theuni opened pull request #13480: Avoid copies in range-for loops and add a warning to detect them (06master...06no-for-copies) 02 https://github.com/bitcoin/bitcoin/pull/13480
68 2018-06-15 17:59:12 0|bitcoin-git|13bitcoin/06master 14cf01fd6 15Chun Kuan Lee: Avoid concurrency issue
69 2018-06-15 17:59:12 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/be27048a1842...81069a75bd71
70 2018-06-15 17:59:13 0|bitcoin-git|13bitcoin/06master 1481069a7 15MarcoFalke: Merge #13465: Avoid concurrency issue when make multiple target...
71 2018-06-15 17:59:40 0|provoostenator|Doesn't #11423 deserve slightly more emphasis in the release notes? E.g. "Disables OP_CODESEPARATOR in non-segwit scripts, make positive FindAndDelete result invalid, reject transaction smaller than 82 bytes (non-segwit size."
72 2018-06-15 17:59:43 0|gribble|https://github.com/bitcoin/bitcoin/issues/11423 | [Policy] Several transaction standardness rules by jl2012 ÷ Pull Request #11423 ÷ bitcoin/bitcoin ÷ GitHub
73 2018-06-15 18:00:08 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #13465: Avoid concurrency issue when make multiple target (06master...06no_parallel) 02 https://github.com/bitcoin/bitcoin/pull/13465
74 2018-06-15 19:26:27 0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #13481: doc: Rewrite some validation docs as lock annotations (06master...06Mf1806-docValLockAnnot) 02 https://github.com/bitcoin/bitcoin/pull/13481
75 2018-06-15 19:50:18 0|MarcoFalke|> feature request: in the conflict checker, if one PR is just a prefix of another one's commits, don't call it a conflict
76 2018-06-15 19:50:23 0|MarcoFalke|Done (hopefully)
77 2018-06-15 20:05:45 0|wumpus|nice