< bitcoin-git>
[bitcoin] murrayn opened pull request #12630: Provide useful error message if datadir is not writable. (master...datadir_writable) https://github.com/bitcoin/bitcoin/pull/12630
< stevenroose>
Quick question, I'm sure you thought about this. I explained CT to a friend and we wondered if the birthday paradox applies to finding a correct s and a that match a commitment
< stevenroose>
In the case where you want to create more money than you are supposed to, so find any high a (within bounds of 21 million ofc) and any s value (not sure you call them s, the one in sG+aH) that makes the sum go round
< stevenroose>
It's basically brute force reversing a private key, but with two values that you can change. Potentially even more since you can create multiple txs
< stevenroose>
outputs*
< stevenroose>
I'm sure it's still impossible, but if the birthday paradox applies, it would slightly reduce the security as compared to current bitcoin
< bitcoin-git>
bitcoin/master fa3528a MarcoFalke: qa: Fix some tests to work on native windows
< bitcoin-git>
bitcoin/master 791c3ea MarcoFalke: Merge #12627: qa: Fix some tests to work on native windows...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12627: qa: Fix some tests to work on native windows (master...Mf1803-qaWindowsTests) https://github.com/bitcoin/bitcoin/pull/12627
< bitcoin-git>
[bitcoin] kallewoof opened pull request #12634: [refactor] Make TransactionWithinChainLimit more flexible (master...txmempool-chain-limit-value) https://github.com/bitcoin/bitcoin/pull/12634
< gribble>
https://github.com/bitcoin/bitcoin/issues/9598 | Improve readability by removing redundant casts to same type (on all platforms) by practicalswift · Pull Request #9598 · bitcoin/bitcoin · GitHub
< meshcollider>
should be RTM now
< bitcoin-git>
[bitcoin] fanquake opened pull request #12637: backport: #12556 fix version typo in getpeerinfo RPC call help (0.16...backport-fix-version-typo) https://github.com/bitcoin/bitcoin/pull/12637
< bitcoin-git>
bitcoin/master 46e7f80 e0: Limit the number of IPs we use from each DNS seeder...
< bitcoin-git>
bitcoin/master efa18a2 Wladimir J. van der Laan: Merge #12626: Limit the number of IPs addrman learns from each DNS seeder...
< bitcoin-git>
[bitcoin] laanwj closed pull request #12626: Limit the number of IPs addrman learns from each DNS seeder (master...master) https://github.com/bitcoin/bitcoin/pull/12626
< bitcoin-git>
bitcoin/master 06edc23 practicalswift: Improve readability by removing redundant casts to same type (on all platforms)
< bitcoin-git>
bitcoin/master a34ac6a Wladimir J. van der Laan: Merge #9598: Improve readability by removing redundant casts to same type (on all platforms)...
< michagogo>
What’s that new noversion tag?
< kanzure>
anyone have the fingerprint of the release key handy?
< wumpus>
michagogo: do 'git show noversion' for explanation
< michagogo>
I did see the message
< michagogo>
But I’m not sure I understand what that meant
< michagogo>
Unless I just saw the first line and the rest isn’t in the rss?
< michagogo>
I don’t know if I understand why a “Dummy tag for commits on master” is useful
< wumpus>
please read the lines after that too
< michagogo>
Okay, I’ll take a look when I get a chance
< michagogo>
Weird
< michagogo>
I’m not seeing it on GitHub
< michagogo>
I mean, the mobile version doesn’t show tags at all for some reason, but when I switch to the full site and look at the list it doesn’t show up there
< michagogo>
Interesting
< michagogo>
I didn’t know about `git describe`
< wumpus>
right, it prints the number of commits since the last signed tag, which is useful on branches, not so much on master, but at least "noversion" is clearer than seeing v0.9.0rc2+X
< bitcoin-git>
[bitcoin] laanwj closed pull request #12184: [TRIVIAL] Drop C headers in favour of C++-compatibility headers. (master...cpp11_includes) https://github.com/bitcoin/bitcoin/pull/12184
< arubi>
at least it's not IBM's LSF ;)
< bitcoin-git>
[bitcoin] laanwj closed pull request #11892: [Qt] Warn if fallback fee has been used (master...2017/12/qt_warn_fallbackfee) https://github.com/bitcoin/bitcoin/pull/11892
< wumpus>
promag: travis is snowed under in a lot of changing pull requests and merges
< promag>
wumpus: it's been 2 hours since the push
< wumpus>
I just cancelled a whole bunch of master travis jobs (except the last merge)
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #12638: qa: Remove mempool.dat from cached regtest datadir (master...Mf1803-qaMempoolCache) https://github.com/bitcoin/bitcoin/pull/12638
< bitcoin-git>
[bitcoin] laanwj closed pull request #10353: Refactor script interpreter flags to use new CScriptFlags class for stricter checking (master...scriptflags) https://github.com/bitcoin/bitcoin/pull/10353
< wumpus>
but it's very hard to get right, if not impossible using the current http functionality
< stevenroose>
I'm looking to implement an RPC (using gRPC) to get it in btcd
< stevenroose>
But yeah it's tricky
< stevenroose>
You could make a streaming RPC that streams them in chunks, but the db would be locked the entire time, preventing block validation the entire time while an RPC client is downloading the set
< stevenroose>
Even though it might be possible to break your db lock every once and a while (like once a second), but then you could have a change to the set while you're streaming it
< promag>
wumpus: do you think we should switch to evhttp_send_reply_start evhttp_send_reply_chunk evhttp_send_reply_end?
< wumpus>
stevenroose: leveldb supports snapshotting, so the state changes while running aren't a problem for us