1 2017-11-10 01:20:22	0|bitcoin-git|[13bitcoin] 15emprisupriatna opened pull request #11650: BIP148 user activated activation of segwit (06master...06bip-segwit-flagday) 02https://github.com/bitcoin/bitcoin/pull/11650
 2 2017-11-10 01:24:15	0|bitcoin-git|[13bitcoin] 15sipa closed pull request #11650: BIP148 user activated activation of segwit (06master...06bip-segwit-flagday) 02https://github.com/bitcoin/bitcoin/pull/11650
 3 2017-11-10 01:46:29	0|cfields|gitian builders: v0.15.1 detached sigs are pushed
 4 2017-11-10 01:47:12	0|meshcollider|cfields: sweet. I'll have to wait til I get home though
 5 2017-11-10 01:47:47	0|cfields|meshcollider: no rush :)
 6 2017-11-10 01:51:32	0|bitcoin-git|[13bitcoin] 15MeshCollider opened pull request #11651: refactor: Make all #includes relative to project root (rebased) (06master...06201711_absolute_includes) 02https://github.com/bitcoin/bitcoin/pull/11651
 7 2017-11-10 02:03:08	0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #11053: refactor: Make all #includes relative to project root (06master...062017_08_includes_absolute) 02https://github.com/bitcoin/bitcoin/pull/11053
 8 2017-11-10 04:08:21	0|LumberCartel|exit70:  This is probably where you want to start looking into the source code for Bitcoin:  https://www.github.com/bitcoin/
 9 2017-11-10 04:10:15	0|LumberCartel|exit70:  There's a bot here named bitcoin-git that announces pull requests and the status updates.  So lurking here can be educational too.  (Welcome, by the way.)
10 2017-11-10 04:11:05	0|exit70|thanks!
11 2017-11-10 05:58:55	0|meshcollider|achow101: yay is this the work of your new recruit? https://bitcoincore.org/en/meetings/2017/10/26/
12 2017-11-10 05:59:06	0|meshcollider|Heh "Note the author of these notes is insulted by the above exchange."
13 2017-11-10 06:10:07	0|achow101|meshcollider: yes
14 2017-11-10 07:06:39	0|wumpus|hehe
15 2017-11-10 07:07:12	0|wumpus|good to see meeting notes again
16 2017-11-10 07:08:30	0|wumpus|Ivan should probably credit his own name too?
17 2017-11-10 07:21:08	0|bitcoin-git|13bitcoin/06master 14620bae3 15Matt Corallo: Require a steady clock for bench with at least micro precision
18 2017-11-10 07:21:08	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/6e4e98ee8ce2...fe503e118f08
19 2017-11-10 07:21:09	0|bitcoin-git|13bitcoin/06master 14fe503e1 15Wladimir J. van der Laan: Merge #11646: Require a steady clock for bench with at least micro precision...
20 2017-11-10 07:21:45	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11646: Require a steady clock for bench with at least micro precision (06master...062017-11-11562-cleanups) 02https://github.com/bitcoin/bitcoin/pull/11646
21 2017-11-10 08:21:01	0|cluelessperson|Does anyone have any logs of dropped transactions from nodes?
22 2017-11-10 08:21:25	0|cluelessperson|My understanding is that nodes have an expiry setting and I'd be interested to review dropped/failed transactions, if they exist.
23 2017-11-10 09:38:29	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #11652: Add missing locks to init.cpp (in AppInitMain + ThreadImport) and validation.cpp (06master...06init-and-validation-locks) 02https://github.com/bitcoin/bitcoin/pull/11652
24 2017-11-10 09:52:28	0|wumpus|I don't, but IIRC there are people logging all transactions, that's a huge amount of data though
25 2017-11-10 09:52:57	0|gmaxwell|cluelessperson: expirations are rare, we might have just had some this week, but most of the prior year probably none.
26 2017-11-10 09:54:35	0|wumpus|oh you mean dropped from the mempool, I interpreted it as dropped on receive
27 2017-11-10 09:55:42	0|gmaxwell|cluelessperson: the only time anything would get expired is when this graph doesn't ever make it to zero for a width of two weeks: https://jochen-hoenicke.de/queue/#all  looks like there was a period in june.
28 2017-11-10 09:55:56	0|gmaxwell|wumpus: ah, I see how you read it, yes I thought he was asking about mempool expiration.
29 2017-11-10 10:01:21	0|bitcoin-git|[13bitcoin] 15NicolasDorier opened pull request #11653: [RPC] Add utility getsignaturehash (06master...06getsignaturehash) 02https://github.com/bitcoin/bitcoin/pull/11653
30 2017-11-10 10:06:13	0|gmaxwell|sipa: ^ that is super yuckky. the generic dummysigner thing would be so much better.
31 2017-11-10 13:47:33	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #11654: Initialize recently introduced non-static class member lastCycles to zero in constructor (06master...06uninitialized-members) 02https://github.com/bitcoin/bitcoin/pull/11654
32 2017-11-10 14:37:14	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #11655: Explicitly state assumption that state.m_chain_sync.m_work_header != nullptr in ConsiderEviction(…) (06master...06m_chain_sync.m_work_header) 02https://github.com/bitcoin/bitcoin/pull/11655
33 2017-11-10 15:11:57	0|bitcoin-git|13bitcoin/06master 147481579 15John Newbery: [tests] Make comp test framework more debuggable...
34 2017-11-10 15:11:57	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/fe503e118f08...76b334915967
35 2017-11-10 15:11:58	0|bitcoin-git|13bitcoin/06master 1476b3349 15MarcoFalke: Merge #11468: [tests] Make comp test framework more debuggable...
36 2017-11-10 15:12:25	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11468: [tests] Make comp test framework more debuggable (06master...06comp_test_debuggable) 02https://github.com/bitcoin/bitcoin/pull/11468
37 2017-11-10 15:48:09	0|bitcoin-git|13bitcoin/06master 14d052e38 15CryptAxe: [qt] Add use available balance in send coins dialog
38 2017-11-10 15:48:09	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/76b334915967...22cdf93c062e
39 2017-11-10 15:48:10	0|bitcoin-git|13bitcoin/06master 1422cdf93 15MarcoFalke: Merge #11316: [qt] Add use available balance in send coins dialog (CryptAxe, promag)...
40 2017-11-10 15:48:32	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11316: [qt] Add use available balance in send coins dialog (CryptAxe, promag) (06master...062017-09-add-use-available-balance) 02https://github.com/bitcoin/bitcoin/pull/11316
41 2017-11-10 16:00:15	0|crys|help
42 2017-11-10 16:00:46	0|BlueMatt|crys: you probably want #bitcoin
43 2017-11-10 16:57:57	0|bitcoin-git|13bitcoin/06master 14109a858 15practicalswift: tests: Add missing locks to tests...
44 2017-11-10 16:57:57	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/22cdf93c062e...ee92243e66f2
45 2017-11-10 16:57:58	0|bitcoin-git|13bitcoin/06master 14ee92243 15MarcoFalke: Merge #11623: tests: Add missing locks to tests...
46 2017-11-10 16:58:32	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11623: tests: Add missing locks to tests (06master...06test-locks) 02https://github.com/bitcoin/bitcoin/pull/11623
47 2017-11-10 17:25:03	0|cluelessperson|wumpus: gmaxwell   Well I have >14TB ready to start logging data
48 2017-11-10 17:25:13	0|cluelessperson|I was thinking about recording debug logs
49 2017-11-10 17:53:51	0|wumpus|the bitcoin core debug log doesn't contain raw transaction data
50 2017-11-10 18:00:35	0|wumpus|you could add that but that'd be quite inefficient - either dumping to a binary file, or to zmq and logging externally would be more efficient
51 2017-11-10 18:30:32	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #9939: Cache vout IsMine() value on `CWallet::AvailableCoins()` (06master...06enhancement/cache-wallet-available-coins-output-ismine) 02https://github.com/bitcoin/bitcoin/pull/9939
52 2017-11-10 18:52:06	0|sipa|Murch: i don't understand your comment here: https://github.com/bitcoin/bitcoin/commit/4fcb915944b27759dafb188566bfd14dbcd95cff#commitcomment-25537794
53 2017-11-10 19:05:03	0|sdaftuar|sipa: Murch: i just finished a first draft of trying to explain our partition resistance.  i think it addresses murch's question: https://gist.github.com/sdaftuar/c2a3320c751efb078a7c1fd834036cb0
54 2017-11-10 19:05:10	0|sdaftuar|feedback would be welcome!
55 2017-11-10 19:08:01	0|Murch|sipa: The release notes make it sound that whenever there is a block interval greater than 30 minutes, one of your outbound peers gets replaced. And the peer that relayed you a block first is never affected. I am wondering whether that would allow you to replace all outbound peers of nodes.
56 2017-11-10 19:09:16	0|sdaftuar|Murch: we have limitations in place to prevent that from happening.
57 2017-11-10 19:10:05	0|sdaftuar|Murch: first, the mechanism is that we connect to a 9th peer (rather than disconnect one of our existing at the beginning)
58 2017-11-10 19:11:09	0|sdaftuar|that 9th peer shouldn't be connected for very long before we decide whether we need to evict someone because we have more than 8 outbound peers (there's a 45 second timer)
59 2017-11-10 19:11:24	0|sdaftuar|and we resolve ties by disconnecting our newest peer.  so if the 9th peer tells us nothing new, it gets evicted.
60 2017-11-10 19:11:46	0|sdaftuar|after an eviction, we don't try connecting to a new 9th peer until the stale tip check fires again (that runs every 10 minutes)
61 2017-11-10 19:12:06	0|sdaftuar|finally, we protect 4 of our existing peers from eviction under this algorithm
62 2017-11-10 19:12:30	0|sdaftuar|so at worst, half your peers could be taken over this way
63 2017-11-10 19:14:53	0|Murch|sdaftuar: Thanks for the explanation, that sounds very reasonable. It seems someone else already had the same concern. ;)
64 2017-11-10 19:15:11	0|sdaftuar|yes matt noticed that issue :)
65 2017-11-10 19:15:29	0|Murch|@sipa: I've removed my comment.
66 2017-11-10 19:26:23	0|bitcoin-git|13bitcoin/06master 145b9748f 15Dan Raviv: Small refactor of CCoinsViewCache::BatchWrite()...
67 2017-11-10 19:26:23	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/ee92243e66f2...05a761932edd
68 2017-11-10 19:26:24	0|bitcoin-git|13bitcoin/06master 1405a7619 15MarcoFalke: Merge #11353: Small refactor of CCoinsViewCache::BatchWrite()...
69 2017-11-10 19:26:46	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11353: Small refactor of CCoinsViewCache::BatchWrite() (06master...06refactor/coins-view-cache-batch-write) 02https://github.com/bitcoin/bitcoin/pull/11353
70 2017-11-10 19:42:44	0|MarcoFalke|wumpus: BlueMatt: You were talking about rpc and logging a few days ago. Might be interested in #11191 ?
71 2017-11-10 19:42:46	0|gribble|https://github.com/bitcoin/bitcoin/issues/11191 | RPC: Improve help text and behavior of RPC-logging. by AkioNak · Pull Request #11191 · bitcoin/bitcoin · GitHub
72 2017-11-10 20:37:09	0|bitcoin-git|13bitcoin/06master 14203a4aa 15donaloconnor: Fix CTxMemPoolEntry::UpdateAncestorState: modifySigOps param type int -> int64_t
73 2017-11-10 20:37:09	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/05a761932edd...61fb80660f73
74 2017-11-10 20:37:10	0|bitcoin-git|13bitcoin/06master 1461fb806 15MarcoFalke: Merge #11269: [Mempool] CTxMemPoolEntry::UpdateAncestorState: modifySiagOps param type...
75 2017-11-10 20:37:37	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11269: [Mempool] CTxMemPoolEntry::UpdateAncestorState: modifySiagOps param type (06master...06fix_params_branch) 02https://github.com/bitcoin/bitcoin/pull/11269
76 2017-11-10 21:43:32	0|cluelessperson|I'm sorry to annoy you, does anyone have a potential idea of when bitcoin core will support segwit addresses?
77 2017-11-10 21:43:53	0|achow101|cluelessperson: soon(tm)
78 2017-11-10 21:44:19	0|cluelessperson|How can I help?
79 2017-11-10 21:44:26	0|achow101|cluelessperson: whenever #11403 is merged
80 2017-11-10 21:44:26	0|BlueMatt|when sipa finds time to write up the approach doc, everyone else has time to review and debate it, then folks review the pr for full-segwit-wallet-support, then it gets merged, then there is an 0.16rc cycle, then 0.16 ships :p
81 2017-11-10 21:44:27	0|cluelessperson|My background is in DevOps.
82 2017-11-10 21:44:28	0|gribble|https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
83 2017-11-10 21:45:03	0|BlueMatt|i believe if you use master right now you can send to segwit addresses, just not receive on them? though probably dont do that, master is scary
84 2017-11-10 21:49:36	0|BertrandRussell|BlueMatt you can receive on segwit address using core, but you have to use the addwitnessaddress rpc call to generate the receiving address
85 2017-11-10 21:50:11	0|sipa|BlueMatt: you can receive on them, but you need addwitnessaddress
86 2017-11-10 21:50:14	0|BertrandRussell|master supports BIP173 addresses but 0.15.1 does not (only P2SH)
87 2017-11-10 21:50:20	0|BlueMatt|only p2sh-wrapped, though
88 2017-11-10 21:50:24	0|BlueMatt|i thought he meant bech32
89 2017-11-10 21:50:31	0|BertrandRussell|master supports bech32/BIP173
90 2017-11-10 21:50:31	0|sipa|BlueMatt: no, you can receive on bech32 in master now
91 2017-11-10 21:50:40	0|achow101|BlueMatt: addwitnessaddress has an option for p2sh or bech32
92 2017-11-10 21:50:40	0|sipa|but still only after addwitnessaddress
93 2017-11-10 22:00:32	0|BlueMatt|ah, k
94 2017-11-10 22:00:57	0|meshcollider|C.f. #11167
95 2017-11-10 22:02:04	0|gribble|https://github.com/bitcoin/bitcoin/issues/11167 | Full BIP173 (Bech32) support by sipa · Pull Request #11167 · bitcoin/bitcoin · GitHub
96 2017-11-10 23:32:51	0|aj|cluelessperson: i did tx logging via zmq a while ago (never got around to analysing it), script was http://azure.erisian.com.au/~aj/tmp/btc_zmq_tx_sub.py.txt fwiw
97 2017-11-10 23:35:45	0|cluelessperson|aj: is that just connecting to a local node?
98 2017-11-10 23:49:11	0|aj|cluelessperson: yeah, zmqSubSocket.connect("tcp://127.0.0.1:%i" % port)