> How do you know which of 2 blocks with the same height is "newer"?
From the particular node's perspective. I'm aware there is no
possibility of consistent global ordering.
Dave's code is about switching blocks (instead of continuing on the
existing one), and, in that context, "old" means the fi
It's pretty obvious that Dave is suggesting an alternate tie-breaker:
> It also makes an empty block far less attractive because it is easily
> replaced, all the way until the next block locks it in.
I do see a problem with the proposal. Right now, when a miner sees a
new block with the most wor
I will point out that the current situation is not an accident:
https://github.com/bitcoin/bips/pulls?utf8=%E2%9C%93&q=44 is a great
place to get some context for what happened. I believe you can also
find the other half of this discussion on the mailing list archives.
The cointypes being simple i
So I checked, and the code described *does not* run when behind a
proxy of any kind, including tor:
https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23#diff-11780fa178b655146cb414161c635219R265
At least based on my admittedly weak understanding of how the intern
