sipa: We've actually met once (very briefly) at Bitcoin 2014. :) I said hi, and told you that I'm a moderator on Bitcoin.SE. and you said, you love our work. Heh.
Completely different topic: I'm going to have a meeting later today about a potential master thesis in the area of Bitcoin. I've proposed to do my master thesis on Coin Selection (which I've did some simulation work before, e.g. gmaxwell had commented then). I've seen that CoinSelection is scheduled to be "looked at" for 0.13. Do you think it would make sense to have a more systematic analysis of CoinSelection even though that's schedu
My intent is to point out an easy improvement that could be made in the communication with the broader Bitcoin community. Unless I'm mistaken and the table is up-to-date. Then I'll rest my case of course. ;)
btcdrak: E.g. adam3us has referred to the table 16 days ago (https://www.reddit.com/r/Bitcoin/comments/4d3pdg/clearing_the_fud_around_segwit/d1nxxq6) as showing that secondary projects are working on SegWit. I've called him out on that, because the table doesn't actually show that. (I'm Xekyo on reddit). I would like to propose that development teams listed on that table get nudged to update their status, because it is my understanding
bitcoin.sipa.be is a node, and run with -segnet
morcos: there is this bug https://github.com/sipa/bitcoin/issues/73, I'll find out what happen later, but the problem is that the transaction is rejected by mempool but still added to wallet transactions. Then after one block, the transaction is rebroadcasted but this time accepted to mempool. The caller of sendtoaddress got an error and thought the money
[bitcoin] laanwj closed pull request #7625: Bugfix: Check for bench_bitcoin being enabled where needed, and skip UniValue dependency when unused (master...bugfix_bench_checks) https://github.com/bitcoin/bitcoin/pull/7625
Thanks for subscribing to the Bitcoin Core announcements list. Please confirm your subscription by clicking the link below: <-- the irony that the email goes out of its way to make the link un-clickable.. btcdrak
maybe it would be interesting for me as well... whenever my laptop battaery dies while compiling bitcoin core (not surprisingly, that's the most common activity during which power fails), my git tree is corrupted
could work I guess, but seems overkill, every project just supports out-of-tree builds except bitcoin core :)
jonasschnelli: interesting - so a reindex is slow with LMDB, but a sync from another node is fast? Greg did a benchmark with a sync from another node and LMDB came out much faster: https://github.com/laanwj/bitcoin/tree/2016_04_mdb#x86_64 . Also wonder where the bottleneck is, but will add it to the performance results
sipa:http://bitcoin.sipa.be/ data is not up to date
hmm, the sendheaders stuff is pretty bitcoin-core-specific
we DoS a node for sending us a header that doesnt connect to our chain, because bitcoin core keeps track of what it thinks its peers have for headers (and assumes they never throw away headers)
for emails rejected on the bitcoin-core-dev mailing list, should they also be forwarded to firstname.lastname@example.org or should that feed remain for bitcoin-dev mailing list rejection only?
[bitcoin] paveljanik opened pull request #7842: RPC: do not print minping time in getpeerinfo when no ping received yet (master...20160408_getpeerinfo_no_ping_yet) https://github.com/bitcoin/bitcoin/pull/7842