1 2018-04-02 12:52:28	0|wumpus|merge notifications not working?
 2 2018-04-02 14:13:46	0|jcorgan|apparently not
 3 2018-04-02 14:23:34	0|wumpus|well at least we still have https://twitter.com/bitcoinmerges
 4 2018-04-02 14:35:48	0|jcorgan|and Slack :-)
 5 2018-04-02 15:03:36	0|sipa|wumpus: i set +n on the channel to prevent spam
 6 2018-04-02 15:03:50	0|wumpus|sipa: ok
 7 2018-04-02 15:04:28	0|wumpus|it might be possible to make the github commits bot authenticate
 8 2018-04-02 15:05:38	0|wumpus|yes, that's possible. So we could do that if the spammers keep it up.
 9 2018-04-02 15:20:02	0|sipa|wumpus: n prevents sending messages to the channel without joining
10 2018-04-02 15:20:20	0|sipa|the bots don't do that to avoid join/leave cruft
11 2018-04-02 15:20:58	0|wumpus|there's also an option to make it message with joining, but yes that's intentionally disabled for that reason
12 2018-04-02 18:33:39	0|bitcoin-git|[13bitcoin] 15luke-jr opened pull request #12859: Bugfix: Include <memory> for std::unique_ptr (06master...06incl_memory) 02https://github.com/bitcoin/bitcoin/pull/12859
13 2018-04-02 18:54:40	0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #12860: Add testmempoolaccept to release-notes, Add missing const (06master...06Mf1804-docReleaseNotes) 02https://github.com/bitcoin/bitcoin/pull/12860
14 2018-04-02 19:44:34	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #12861: [tests] Stop feature_block.py from blowing up memory. (06master...06feature_block_memory) 02https://github.com/bitcoin/bitcoin/pull/12861
15 2018-04-02 19:53:21	0|nmnkgl|Hi. I have some ideas on an alternative transaction relay protocol and I was wondering if this is a good place to get some feedback? If not, where should I look instead?
16 2018-04-02 19:55:00	0|jcorgan|#bitcoin-dev or #bitcoin
17 2018-04-02 19:56:04	0|luke-jr|nmnkgl: bitcoin-dev ML would probably be best
18 2018-04-02 19:56:25	0|luke-jr|but here is fine too if it's just chatter
19 2018-04-02 19:56:37	0|bitcoin-git|[13bitcoin] 15GabrielDav opened pull request #12862:  Add from_me and bip125-replaceable to listunspent and gettransaction (06master...0611613-rpc-transaction-expose-source) 02https://github.com/bitcoin/bitcoin/pull/12862
20 2018-04-02 19:58:49	0|nmnkgl|Well, I think it's kinda more, it will be around 300 words for a summary. So I'll better send an email to bitcoin-dev ML.
21 2018-04-02 20:00:54	0|sipa|nmnkgl: are you aware of existing work around e.g. dandelion?
22 2018-04-02 20:01:46	0|nmnkgl|sipa: yeah, I think I'm trying to solve a different problem. Is there anything else besides dandelion?
23 2018-04-02 20:03:50	0|sipa|nmnkgl: there has also been some work around mempool reconciliation, though less formal writeups
24 2018-04-02 20:07:06	0|nmnkgl|Good to know, thanks. I think I'll send an email to the ML anyways. Currently I have a draft of the formal paper. If anyone is interested, please let me know, I can send it over email.
25 2018-04-02 20:07:47	0|sipa|can you give a one-sentence summary of what issue you're trying to address
26 2018-04-02 20:09:09	0|sipa|(i'm interested in hearing more!)
27 2018-04-02 20:09:25	0|nmnkgl|sipa: I think we had a call in February when I was talking about my current research. It's about bandwidth requirements for running a public-IP node.
28 2018-04-02 20:09:52	0|sipa|i was wondering if it was you :)
29 2018-04-02 20:12:23	0|nmnkgl|I was also wondering whether http://luke.dashjr.org/programs/bitcoin/files/charts/software.html attempts to get all the nodes running Bitcoin Core, even those which not accept incoming connections?
30 2018-04-02 20:17:10	0|luke-jr|nmnkgl: it does
31 2018-04-02 20:18:38	0|bitcoin-git|[13bitcoin] 15practicalswift closed pull request #12767: Initialize nVersionDummy to zero in deserialization code (06master...06initialize-nVersionDummy-to-zero) 02https://github.com/bitcoin/bitcoin/pull/12767
32 2018-04-02 20:19:30	0|nmnkgl|luke-jr: Good job, thanks. I was just confused because the published and peer-reviewed paper "The Bitcoin P2P Network" claims 800k+ nodes, even though it was published in 2014.
33 2018-04-02 20:20:27	0|luke-jr|nmnkgl: lots of nonsense gets published
34 2018-04-02 20:20:52	0|luke-jr|nmnkgl: but do note that my thing doesn't try to show light clients, only full nodes
35 2018-04-02 20:21:09	0|luke-jr|light clients are much harder to estimate, sadly
36 2018-04-02 20:21:41	0|sipa|also much less relevant imho ;)
37 2018-04-02 20:24:21	0|luke-jr|sipa: well, ratio of full nodes to all wallets would be a useful number to know
38 2018-04-02 20:29:48	0|echeveria|there’s almost nobody using bip37.
39 2018-04-02 20:30:08	0|echeveria|I’ve logged the filter load instruction for years.
40 2018-04-02 20:35:33	0|luke-jr|echeveria: BIP37 nodes don't usually implement p2p address stuff properly, so they all connect to a few nodes and none of the rest
41 2018-04-02 20:45:52	0|phantomcircuit|nmnkgl, peer reviewed, but by whose peers?
42 2018-04-02 20:49:50	0|nmnkgl|phantomcircuit: well, it's fortunate that I'm aware of luke-jr work, but I think
43 2018-04-02 20:50:35	0|nmnkgl|For average researcher the paper might be more trustworthy than random piechart from stackoverflow.
44 2018-04-02 20:57:51	0|phantomcircuit|nmnkgl, i cant remember the last time i read an academic paper that had anything to do with bitcoin that wasn't mostly garbage
45 2018-04-02 20:57:58	0|phantomcircuit|sorry, published paper
46 2018-04-02 21:41:55	0|bitcoin-git|13bitcoin/06master 1489fe5fe 15John Newbery: [tests] Stop feature_block.py from blowing up memory....
47 2018-04-02 21:41:55	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/18815b4bfb20...c564424d98b1
48 2018-04-02 21:41:56	0|bitcoin-git|13bitcoin/06master 14c564424 15MarcoFalke: Merge #12861: [tests] Stop feature_block.py from blowing up memory....
49 2018-04-02 21:42:45	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12861: [tests] Stop feature_block.py from blowing up memory. (06master...06feature_block_memory) 02https://github.com/bitcoin/bitcoin/pull/12861
50 2018-04-02 21:43:51	0|aj|MarcoFalke: \o/