I don't know how that site counts XT blocks, but if it's simply version > 3, then this recent block by Slush could've triggered it.
https://blockchain.info/block/00000000000000000174419fa2ba5003e123dbd97c6982aff1863f016b04789d
Though, it's apparently not XT, just a strange version number.
https://blockchain.info/block/00000000000000000174419fa2ba5003e123dbd97c6982aff1863f016b04789d
Though, it's apparently not XT, just a strange version number.
So it's not an XT block, it's just another bitcointalk.org 'Gavin-ista' trying his best to spread a bit of FUD on the forum?
Why do ppl here always take some post as fact without even checking it first?
This is why the FUD against BitcoinXT went out of control here.
Is 536870919 the version number for BIP101. If not, what would be the right version number?
This is Slushpool setup right now :
Quote
It's a little tricky, so here's a more in depth explanation:
There are 2 mining urls, vanilla and XT.
Both serve stratum shares, as usual.
Vanilla has block version 3, XT has block version 0x20000007. Nothing else is different.
Shares are valid and shared across the pool.
It won't work after the split. But if the split happens, slush would move everyone to the new branch.
Until then it works great. And we've got at least 4 months before the split.
There are 2 mining urls, vanilla and XT.
Both serve stratum shares, as usual.
Vanilla has block version 3, XT has block version 0x20000007. Nothing else is different.
Shares are valid and shared across the pool.
It won't work after the split. But if the split happens, slush would move everyone to the new branch.
Until then it works great. And we've got at least 4 months before the split.
Version: 536870919(10) = 0x20000007 (hex)
Hope that answers your question.
