Re: [ANN] Spark | X11 | BTer/Bittrex/C-CEX | PoW/PoS | Exchanges | Roadmap |
Sorry, I probably didnt make it clear in my last post, but 10041 was the "bad" block, the forks appear to deviate after 10042, glad others corroborate that.
Unfortunately I think Bittrex are on the minority chain which we probably dont want to switch back to as the PoW phase isnt complete yet, and we'd have a load of miners upset about losing 4000 blocks worth of PoW mining. How that will affect Bittrex probably depends on how soon they suspended trading after block 10041
Unless someone comes up with a good reason not to I think I will see about releasing an updated wallet later that will definitely sync with the majority chain, as the current version on Github (and I assume the Windows download, I havent tested it yet) will not.
Unfortunately I think Bittrex are on the minority chain which we probably dont want to switch back to as the PoW phase isnt complete yet, and we'd have a load of miners upset about losing 4000 blocks worth of PoW mining. How that will affect Bittrex probably depends on how soon they suspended trading after block 10041
Unless someone comes up with a good reason not to I think I will see about releasing an updated wallet later that will definitely sync with the majority chain, as the current version on Github (and I assume the Windows download, I havent tested it yet) will not.
...it indeed went past me while reading, but however, knowing it beeing Blk 10041 makes us getting somewhere,
resp. that would be the starting point for bittrex to estimate the transaction volume that has to be devaluated,
if they need to drop their chain;
which - if I understand correctly - would be anyway the only option to get a spark wallet back into
the network with the (only) working blockchain. same, that is used by factually all spark wallets
to date beyond blk 14400 (15699 as of now).
now bottom line seems, that any other option would be either way technically impossible or economically gross unacceptable.
ok, I think after bittrex has a picture how much transactions volume got involved and would need to be compensated, we will see how to get past that problem
