Re: [ANN] Spark | X11 | BTer/Bittrex/C-CEX | PoW/PoS | Exchanges | Roadmap |
...we're moving forward 
got response from bittrex (yet I won't get into much research myself today due to a great lack of time):
well, now there's TWO questions to focus upon:
1st: when exactly did the chains start deviating... suchpool states 10042 and looking at the remarkable drop in network strength at that very time it must be exactly that block or just a few blocks earlier or later.
which opens up
2nd: who (apart from bittrex aparently) stayed on the other fork after around block 10042.
that might be folks that e.g. mined on hashhot and were able to withdraw from there, as hashot seems to as well become stuck on that other fork.
and - following my impression - the stronger chainfork after the split looks to me like it's the on suprnova, suchpool, ipominer locked as well (even the official blockchain explorer cannot access it's own wallet, yet it shows the current blockcount and time of even that fork) and it also seems to be the fork, the wallet syncs if going online ... but as I stayed in sync whith that fork only the whole time over, I'm completely unaware about any other forks possible stats.
so:
to eventually vote a chain and see, how much and how to compensate losses.
so, ok... I'm looking back in later, already way overdue
will get to c-cex, bter and vaultex later to get some info about their status with SPARK so we keep the thing coordinated...
got response from bittrex (yet I won't get into much research myself today due to a great lack of time):
Quote
The best way for this to happen would be for the coin to come up on our same fork. We won't know how many coins we are short until the new wallet is up and we can see/process deposits/withdraws.
Have you found out at which block the fork happened? If we could find the first block where the blockhashes don't match we may be able to better determine how many deposits we have that would need invalidated.
Have you found out at which block the fork happened? If we could find the first block where the blockhashes don't match we may be able to better determine how many deposits we have that would need invalidated.
well, now there's TWO questions to focus upon:
1st: when exactly did the chains start deviating... suchpool states 10042 and looking at the remarkable drop in network strength at that very time it must be exactly that block or just a few blocks earlier or later.
which opens up
2nd: who (apart from bittrex aparently) stayed on the other fork after around block 10042.
that might be folks that e.g. mined on hashhot and were able to withdraw from there, as hashot seems to as well become stuck on that other fork.
and - following my impression - the stronger chainfork after the split looks to me like it's the on suprnova, suchpool, ipominer locked as well (even the official blockchain explorer cannot access it's own wallet, yet it shows the current blockcount and time of even that fork) and it also seems to be the fork, the wallet syncs if going online ... but as I stayed in sync whith that fork only the whole time over, I'm completely unaware about any other forks possible stats.
so:
- after finding the EXACT first block with the chain beeing split
- who went on on the 'dominant' chain (eg. suchpool, ipominer, suprnova in order of beeing open for mining. network still working fine to date)
- who is stuck on another chain (probably not reached 14400 and so should be unavailable by now)
to eventually vote a chain and see, how much and how to compensate losses.
so, ok... I'm looking back in later, already way overdue
will get to c-cex, bter and vaultex later to get some info about their status with SPARK so we keep the thing coordinated...
i would say it was indeed around 10042. i was monitoring the entire network and basically witnessed the fork. getting on the bittrex fork is not possible due to the invalid block on that fork which was most likely a result of 51% attack or POS staking beginning early on some wallet. both reasons mean that the invalid fork with the invalid block at 10042 cannot be used or repaired due to blockchain encryption. attempting to repair it is like trying to hack the blockchain which will not be possible. there will be only 2 options.
repair the github and rollback the blockchain to block 1000 (will not sit well with anyone)
discard the illegal fork and move forward with our current pos network.
the working fork has no corrupt blocks and you cant patch a corrupt block to move forward. it means that the working fork as i said from the start is the only legitimate fork. and that is the suchpool/supernova fork.