< jl2012> https://twitter.com/sysmannet/status/728709054936186880 Less Bitcoin Orphans as results of bitcoin p2p network & src code performance improvements
< sipa> 0.12.1 should not have impact on that, i think
< jl2012> sipa: yes, but that could be a result of some miners upgrading directly from 0.11.2 to 0.12.1. Or just statistical variation
< phantomcircuit> sipa: there's a fix for block downloads between 0.12.0 and 0.12.1
< phantomcircuit> some of the sybil nodes claim to be network nodes but aren't
< sipa> oh right
< gmaxwell> someone should probably respond "more improvements coming!"
< gmaxwell> It would be really nice to get the gitian process building ppa/rpm and also arm binaries.
< luke-jr> yes.. but real RPMs, not just repackaged statics :/
< luke-jr> note PPAs *cannot* be self-compiled :x
< wallet42> i want gitian-style homebrew (osx packagemanager) bottles/builds
< wumpus> there was a pull that added arm binaries to gitian descriptors, I am not sure what happend to it
< wumpus> ah, was closed because of a different solution, but never followed up https://github.com/bitcoin/bitcoin/pull/7659
< wumpus> probably we want armhf and aarch64 :-) no need for GUI binaries but bitcoind and the utilities would be nice
< wumpus> (this hopefully reduces the additional download size)
< * wumpus> thinks SipHash should be renamed SipaHash
< NicolasDorier> wumpus: Sipash
< wumpus> heh
< instagibbs> sipa, looking at the chart I think his sample timeframe for 0.12.1 is too short to even tell
< instagibbs> which is whatever, the improvements in 0.12 are clear
< achow101> any planned date for the repository move?
< Chris_Stewart_5> What relation does SIGHASH_ANYONECANPAY have with sequence numbers?
< Chris_Stewart_5> or signature hashes in general and sequence numbers, asking because of this test case