< bitcoin-git> [bitcoin] vivganes opened pull request #11624: Docs: Change formatting for sequence of steps (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11624
< ossifrage> ProcessMessages(headers, 161031 bytes): Exception 'ReadCompactSize(): size too large: iostream error' caught
< ossifrage> I've been getting a fairly large number of this error with 0e707919f596c80056bca295abd71543ccae4956
< ossifrage> Ugg, that was from the wrong debug.log, not a recent version
< sipa> ossifrage: that means a peer is not following the protocol
< sipa> jnewbery: https://github.com/bitcoin/bitcoin/pull/10150 -> any reason why the logging RPC is hidden?
< achow101> there's a logging RPC?
< sipa> achow101: QED.
< wumpus> I think it started as experimental
< wumpus> could be un-hidden now
< wumpus> I think it's useful enough for general use now
< wumpus> #11626
< gribble> https://github.com/bitcoin/bitcoin/issues/11626 | rpc: Make `logging` RPC public by laanwj · Pull Request #11626 · bitcoin/bitcoin · GitHub
< wumpus> sipa: ossifrage: we should probably hide such protocol errors unless net debugging is enabled
< wumpus> any peer can connect and violate the protocol grossly and spam your debug.log, it can be scary to esp. new users
< gmaxwell> I've updated my banlists, in addition to the spies and mass-connectors, they now also include about 30 hosts which are running B2X but using fake service flags: https://people.xiph.org/~greg/banlist.cli.txt https://people.xiph.org/~greg/banlist.gui.txt
< jnewbery> sipa: I implemented it that way because logging is a debug/troubleshooting feature which shouldn't be of interest to the general user
< jnewbery> I have no strong opionion about whether it should hidden or unhidden
< jnewbery> sipa: #11389 failed travis here: https://travis-ci.org/bitcoin/bitcoin/jobs/298345172 . Looks unrelated, I'm going to restart it
< gribble> https://github.com/bitcoin/bitcoin/issues/11389 | Support having SegWit always active in regtest by sipa · Pull Request #11389 · bitcoin/bitcoin · GitHub
< wumpus> jnewbery: well the number of surprised people all around that are glad to see that call seems to indicate otherwise :)
< MarcoFalke> The gh irc bot seems dead
< wumpus> maybe it's lagging again
< bsm117532> I really liked Anthony Towns' talk at Scaling Bitcoin regarding adding some kind of replay protection to Bitcoin.
< bsm117532> Because you can't expect hostile forkers to Do The Right Thing or do it correctly.
< bsm117532> And his points about using market information (e.g. futures) to decide on forks.
< bsm117532> Are there any plans to implement something like this?
< bsm117532> I have the green light from my new employer to do some work on Bitcoin, and I might be interested in pursuing this.
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11629: Fixed some typoes in norwegian translation. (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11629
< ghost43> https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki -- "Created: 2016-03-20" I think there is a typo and it should be 2017, as the date of the first commit here is 2017-03-20 https://github.com/sipa/bech32/commit/52b5a0fa6d3174c4150393fb7d6b58d34b4f5e0b -- I can't open an issue in the BIP repo, so I figured I would just note it here. sipa luke-jr
< MarcoFalke> ghost43: Pull request welcome :)
< ghost43> ok, done
< wumpus> bsm117532: no, I don't think anyone is working on replay protection on our side of the chain, the risk is also that they might also try to thwart it, like w/ the service bits
< bsm117532> wumpus: A proposal is far from complete, clearly.
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/998c3046fab2...f9b74ef3fc74
< bitcoin-git> bitcoin/master d0b1fc8 Vivek Ganesan: Docs: Change formatting for sequence of steps...
< bitcoin-git> bitcoin/master f9b74ef MarcoFalke: Merge #11624: Docs: Change formatting for sequence of steps...
< bsm117532> I think some mechanisms could not be thwarted, e.g. OP_CHECKBLOCKHASHATHEIGHT or committing to a chain's block hash with the signing algorithm.
< yurit> Hello everyone. I am interested in learning about bitcoin one of the doubts that I have is technically. What makes the difficulty of mining increase?
< bsm117532> yurit: try asking your question in #bitcoin
< bsm117532> I'll answer there
< yurit> bsm117532: ok
< cfields> \o/ #10866
< gribble> https://github.com/bitcoin/bitcoin/issues/10866 | Fix -Wthread-safety-analysis warnings. Compile with -Wthread-safety-analysis if available. by practicalswift · Pull Request #10866 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ef8a63435884...6f01dcf63873
< bitcoin-git> bitcoin/master a02c5e4 Karl-Johan Alm: [trivial] Fix error messages in CFeeBumper
< bitcoin-git> bitcoin/master 6f01dcf MarcoFalke: Merge #11597: [trivial] Fix error messages in CFeeBumper...
< BlueMatt> cfields: #11363 needs rebase
< gribble> https://github.com/bitcoin/bitcoin/issues/11363 | net: Split socket create/connect by theuni · Pull Request #11363 · bitcoin/bitcoin · GitHub
< cfields> BlueMatt: thanks, done
< BlueMatt> cfields: "Cannot post comment, commit is no longer a part of PR".......
< cfields> eh?
< BlueMatt> cfields: oh, ignore my comment
< cfields> heh, comment at exactly the same time i force-pushed ?
< BlueMatt> cfields: is SOCKET ever going to be a not-int?
< BlueMatt> can we just pass-by-copy instead of pass-by-const-ref for an int?
< cfields> BlueMatt: i think passing by const ref reinforces the idea that it's a handle. Otherwise I'm afraid someone may stash it somewhere and destroy it elsewhere
< BlueMatt> hmm, alright fair
< cfields> could wrap it up in a struct or something to force the semantics if you'd like?
< BlueMatt> nah, all good
< BlueMatt> can I get some comments on #11517? Specifically, it adds the ability for bench_bitcoin to generate html which has a <script ref="cdn.server"> - should we check in this plotly.js library (its apparently already mit) or would we prefer to keep the link in the generated output (its optional, you can still get the csv-style output on cli if you want)
< gribble> https://github.com/bitcoin/bitcoin/issues/11517 | Tests: Improve benchmark precision by martinus · Pull Request #11517 · bitcoin/bitcoin · GitHub
< BlueMatt> probably a wumpus decision, I suppose
< gmaxwell> BlueMatt: is the plotting thing that you use with fibre that kills firefox?
< BlueMatt> gmaxwell: heh, no, thats some google charts library thing
< BlueMatt> gmaxwell: and, fwiw, I can now *only* plot it on firefox
< BlueMatt> it blows chromium up by exceeding some per-tab memory limit they have
< BlueMatt> but firefox does fine
< cfields> BlueMatt: how much of plotly would we need?
< BlueMatt> cfields: no idea, haven't looked, but the usage is rather trivial
< BlueMatt> its just like making box plots of runtimes of benchmark runs
< cfields> I'm confused as to why that wouldn't just be a server-side thing, though? Why not just parse a csv in realtime?
< BlueMatt> server-side?
< BlueMatt> there is no server?
< MarcoFalke> The plotly printout is optional, right?
< cfields> BlueMatt: I meant that outputting a reasonable csv seems like enough. If a nice plot/markup is desired, that seems beyond the scope of the bench tool
< BlueMatt> MarcoFalke: yes, default is to print the csv-style output
< MarcoFalke> I don't mind adding an option for common formats
< BlueMatt> cfields: its nice to have a tool to do it....anyway, I was asking for comments, would like to get comments ont he pr
< BlueMatt> on the
< cfields> ok, will do
< MarcoFalke> They would just sit around free for people to use and fix in case they break. Why not? Would at least encourage some to run the bench more often
< MarcoFalke> Or we could host a nightly bench on github pages
< cfields> if it can be setup so that you just supply your own plotly, that seems fine to me. But if it requires that we commit it, or fetch it, i'd be uneasy
< sipa> cfields: yes, it's just a url
< phantomcircuit> BlueMatt, 2.8 GB btw
< BlueMatt> phantomcircuit: E_NO_CONTEXT
< phantomcircuit> memory requirement under chromium for fibre stats page
< BlueMatt> yea, well also that stats page hasnt been updated in months cause I changed the network topology and haven't updated the stats-parsing script to actually understand the new topology
< bitcoin-git> [bitcoin] sipa opened pull request #11630: Simplify Base32 and Base64 conversions (master...201711_simpleconvert) https://github.com/bitcoin/bitcoin/pull/11630