[22:07:48] <wumpus:#bitcoin-core-dev> jonasschnelli: could you elaborate in #8546 what you mean with " I think its acceptable if it breaks wallets used back in 0.3.x in conjunction with IP transaction". I don't think it'd be acceptable if the client suddenly crashes if someone happens to be using a wallet that still has a pay-to-IP transaction in it.
cfields was last seen in #bitcoin-core-dev 5 days, 0 hours, 12 minutes, and 27 seconds ago: <cfields> gmaxwell: for one in every X connections, we could proxy and route messages together for peer-pairs. Then they'd poison their own stats :p
cfields_ was last seen in #bitcoin-core-dev 4 hours, 55 minutes, and 44 seconds ago: <cfields_> yes, that one's on purpose
And in terms of all the libraries, if you mean the ones that go into Bitcoin Core (OpenSSL, Qt, boost, etc.), the whole beauty of the depends system is that you don't need to know about that
I'm trying to better understand the purpose and future use of checkpoints in Bitcoin. My understanding is that the checkpoints are in place in order to prevent attackers from spamming nodes with low PoW block headers at low chain heights. And that a side effect of checkpoints is a performance speedup in initial block download due to skipping signature verification.
michagogo: HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt and HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt-testnet
TD-Linux: you're right, bitcoin users wouldn't appreciate that much
wtf. why does sendtoaddress' help have an actual bitcoin address in the example? O_o we worked hard elsewhere to keep real addresses out of examples.
"It's not that we don't like you overclocking, but rather that your overclocking has actually given us the wrong answer to math, which is kinda important to Bitcoin working right."
I'd love to have some crash detection wrapper around bitcoin core that told people "THIS SHOULD NEVER CRASH. IF IT CRASHES WE WANT TO KNOW _NOW_" .. but unfortunately virtually all crashes I've seen from users are bad hardware, and we don't really want to know. :)
someone might plausably run a bitcoin node on port 80 or port 443 since it's a little more likely to make it through firewalls.
curious why we are even trying to connect to nodes with port zero, is anyone really going to be running a privileged port Bitcoin node?
01:17:13 <GitHub81> bitcoin/0.13 a5cef7b Wladimir J. van der Laan: Bump version to 0.13.1