1 2017-09-03 05:46:27	0|bitcoin-git|[13bitcoin] 15gnuser opened pull request #11221: Refactor: simpler read (06master...06refactor-streams) 02https://github.com/bitcoin/bitcoin/pull/11221
 2 2017-09-03 06:48:42	0|bitcoin-git|[13bitcoin] 15lemzwerg closed pull request #11101: bitcoin_qt.m4: Minor fixes, improve code orthogonality (06master...06master) 02https://github.com/bitcoin/bitcoin/pull/11101
 3 2017-09-03 06:53:25	0|bitcoin-git|[13bitcoin] 15lemzwerg opened pull request #11222: Config fixes (06master...06config-fixes) 02https://github.com/bitcoin/bitcoin/pull/11222
 4 2017-09-03 07:45:24	0|Victorsueca|luke-jr: thanks for correcting, I would swear I have read somewhere there was something obfuscated to prevent antivirus going nuts
 5 2017-09-03 07:47:57	0|Victorsueca|ahh found it.... It was the chainstate
 6 2017-09-03 08:12:40	0|sipa|indeed, the chainstate is obfuscated
 7 2017-09-03 10:23:06	0|userbb|hi, i'd like for someone to explain to me basiclly how bitcoins work
 8 2017-09-03 10:46:10	0|molz|userbb, wrong channel, you can ask in #bitcoin
 9 2017-09-03 12:03:37	0|bitcoin-git|[13bitcoin] 15jlopp opened pull request #11224: Tx chain stats (06master...06txChainStats) 02https://github.com/bitcoin/bitcoin/pull/11224
10 2017-09-03 12:04:10	0|bitcoin-git|[13bitcoin] 15jlopp closed pull request #11224: Tx chain stats (06master...06txChainStats) 02https://github.com/bitcoin/bitcoin/pull/11224
11 2017-09-03 13:00:14	0|bitcoin-git|[13bitcoin] 15sdaftuar opened pull request #11225: wallet: update stored witness in AddToWallet (06master...062017-09-update-tx-witness) 02https://github.com/bitcoin/bitcoin/pull/11225
12 2017-09-03 16:31:31	0|brucetwain|anyone here?
13 2017-09-03 16:37:37	0|sipa|no
14 2017-09-03 16:38:01	0|brucetwain|lol
15 2017-09-03 16:38:10	0|brucetwain|hi quick question
16 2017-09-03 16:38:27	0|brucetwain|how many active developers are in the bitcoin core project
17 2017-09-03 16:45:03	0|r251d|brucetwain: https://github.com/bitcoin/bitcoin/graphs/contributors
18 2017-09-03 16:52:12	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #11226: Add Clang thread safety analysis annotations: GUARDED_BY(lock) / EXCLUSIVE_LOCKS_REQUIRED(lock) (06master...06guarded-by-trivial) 02https://github.com/bitcoin/bitcoin/pull/11226
19 2017-09-03 17:53:41	0|sturles|gmaxwell: I have been running the following for a few days, after reading your tip to sdaftuar about listing segwit transactions on top of the mempool: while sleep 10; do bitcoin-cli getblocktemplate | jq '.transactions | .[] | select(.hash != .txid) | .txid' >> swtxlog; done
20 2017-09-03 17:54:02	0|sturles|swtxlog is still empty.  I haven't seen a single one.  Not even my own.
21 2017-09-03 17:54:11	0|sturles|Does it work?
22 2017-09-03 17:55:28	0|sturles|I have set blockmaxwight=4000000 and blockmaxsize is unset.  blockmintxfee=0
23 2017-09-03 17:57:09	0|sturles|The highest total size I have seen in the CreateNewBlock() lines in debug.log is 998231, and the highest block weight is 3992816.
24 2017-09-03 18:02:36	0|sipa|sturles: you need to tell GBT that you're segwit capable
25 2017-09-03 18:03:13	0|sipa|bitcoin core supports non-segwit capable mining software; it just won't include any segwit txn for them
26 2017-09-03 18:04:56	0|sturles|How?
27 2017-09-03 18:07:29	0|arubi|sturles, add  '{"rules": ["csv","segwit"]}' to the getblocktemplate call
28 2017-09-03 18:08:39	0|arubi|you should be also getting a 'default_witness_commitment' field that wasn't there before
29 2017-09-03 18:10:06	0|sturles|That's better!
30 2017-09-03 18:11:02	0|sturles|Lots of transactions and total size > 1000000.
31 2017-09-03 20:34:50	0|gmaxwell|Does this sound like another person with an offscreen problem https://www.reddit.com/r/Bitcoin/comments/6xtr3w/bitcoin_core_problems/
32 2017-09-03 20:48:28	0|seecollinshere|Any body here?
33 2017-09-03 21:13:45	0|bitcoin-git|[13bitcoin] 15theuni opened pull request #11227: RFC: switch to libevent for node socket handling (06master...06minimal-libevent3) 02https://github.com/bitcoin/bitcoin/pull/11227
34 2017-09-03 22:38:50	0|meshcollider|gmaxwell: sounds like it to me, achow101 when you tested it on windows, does the thumbnail that pop up from the taskbar look as described or does it still show the window?
35 2017-09-03 22:39:48	0|meshcollider|I would guess that windows just takes what the window currently looks like which is nothing if its not onscreen, but im not sure
36 2017-09-03 22:47:35	0|achow101|gmaxwell: yes
37 2017-09-03 22:47:37	0|achow101|meshcollider: yes
38 2017-09-03 22:54:05	0|gmaxwell|::sigh::
39 2017-09-03 22:55:03	0|meshcollider|if we're getting this many issues with it, maybe we do need to get the fix into 0.15.0
40 2017-09-03 22:59:36	0|gmaxwell|it isn't a new issue at least, as far as I can tell.
41 2017-09-03 23:00:02	0|gmaxwell|it's just obnoxious that such a low value feature (saving the window position across starts) results in such a serious bug.
42 2017-09-03 23:00:19	0|meshcollider|achow101 have you got any further with the mem access violation crash in #11171?
43 2017-09-03 23:16:18	0|achow101|meshcollider: not really.
44 2017-09-03 23:16:29	0|achow101|see the comment I made which is about as far as I got with it
45 2017-09-03 23:16:56	0|achow101|I think it has to do with a weird string for the proxy which is causing it to get all messed up
46 2017-09-03 23:40:48	0|meshcollider|So it's probably a once off incident, not going to be reproduced without deliberate tampering?
47 2017-09-03 23:42:54	0|meshcollider|Btw can someone rerun Travis on #11178, failure in unrelated test
48 2017-09-03 23:54:38	0|achow101|meshcollider: done
49 2017-09-03 23:54:47	0|meshcollider|Thanks :)
50 2017-09-03 23:55:17	0|meshcollider|sipa: sorry what does your comment on #11210 mean?
51 2017-09-03 23:56:39	0|sipa|meshcollider: you're thinking that i would suggest having a single catch around the whole block - i'm pointing out that i won't suggest that, because it would be incorrect