Quote from: r3morph3d on October 29, 2014, 03:27:48 AM

Quote from: jawitech on October 29, 2014, 02:54:56 AM

Quote from: edschroedinger on October 28, 2014, 04:14:00 PM

if any of you end up with your windows-qt client crashing every time shortly after start, just to remember:
pull the network cable -> start client -> wait on UI finally popping up ->now connect back -> don't touch the 'market' buttons (or start with point 1)

Thanks Ed, your advice made me able to withdraw my few coins.

Same here.. Thanxs bro fixed!!!

no wrorries, good it worked...! that's some rather odd bug, to say the least... yet, credits go one step further @Framauro, he came up with that solution... and to be honest, I wouldn't have tried that myself in a hundred years Cheesy

---

Quote from: RentaMouse on October 29, 2014, 03:56:56 AM

Bit more info for you, I've managed to get the latest build of the Linux wallet to compile after some effort (issues with my system rather than with the code) and have been looking at the peer info - there are definitely two forks in existence currently, one is around block 12750 and the other is at block 15000. Looks like the major part of the PoW hash went on one fork but somehow the other one continued and got well behind in blocks whilst the difficulty was adjusting down to the reduced hashpower.

I've been digging a bit more though and its a bit peculiar, with my new daemon it will only sync on the 12750 chain and rejects PoS blocks from the other chain. If I set the conf file so it only connects to nodes on the 15000 blockchain and try resyncing it gets to block 10041 and then just rejects PoS blocks.

As I mentioned before, I'm a tinkerer not a coder, and I don't know the PoS stuff that well but from what I've seen so far I have a suspicion that the dev accidentally released two different versions of the daemon, if you look at this commit from around when the coin was launched there are a couple of key PoS changes made: https://github.com/RentaMouse/Spark/commit/71d360fdbb18aacf9c49179e0be882f0b9fac289 - the PoW endpoint in the PoS code is changed from 10000 to 14000, and the PoS key is changed. Pre-change daemons could have mined a PoS block after 10000, post change versions wouldnt accept it.

On GitHub there are actually two release versions, 1.0.0 and 1.1.0, looking at the peer info from my daemon there are a few nodes on 1.1.0 but none of those are on the 15k blockchain, which backs up my theory. I suspect Bittrex are running 1.1.0 because they would have compiled from Github and they added the coin later than most....

At the moment its too late for me to decide whether its actually a really bad thing, although I suspect it explains the disappearance of the dev, he may just be running from his backers cos he realised his error a week ago

Quite possibly its not the end of the world as I suspect all the pools will be on the old code, so no miners should lose out on a load of coin, and Bittrex stopped their trading pretty quickly.

What I'm pretty sure of is that I can release an updated version of the wallet which will work properly with the 15000 chain so everyone can get in sync with that.

Discuss away, I'll be back in a few hours....

yay @R.a.Mouse, that sounds like a scenario that actually might have happened quite the way you suspect...

yesterday I wrote back to ryan from bittrex to shed some info on how he evaluates the situation on their side and possible ways to fix... yet, no response. but they're following this thread anyway, so I guess they at least know that - even when dev doesn't show up anymore (and undeniably signs point on that with glow colours) - there's action gonna be taken to fix the issue and bring train back on rails...
...which will be of course some work to do, yet my senses told me it shouldn't be too much of a challenge, to get that thing going again... distribution so far seemed to run rather smooth during PoW period, even considering that fork.

so, the currency is there, and if handled with the necessary caution, this coin even has a good chance to get a save way back with the necessary amount of confidence from the community, so it won't become dumped to death the first day it hits markets back again Wink

.

unfortunately I have rather little time today but I will check back with bittrex to get some info on how next steps could evolve...

so, however... everyone just keep staking Wink

...if wallet crashes on start - pull network cable. start and wait on wallet ui. plug network back in.

I'll check back in between randomly and keep u updated as soon as new intel is available.

---

Quote from: CryptoStoner on October 29, 2014, 08:29:54 AM

Releasing an updated version would be perfect, if Dev does not appear we should seriously consider finding a dev that is willing to take over this project.

it's all a wee bit kept in between the last 3-4 pages... I guess we should consider the dev already MIA at this point, as there's no time to spend on pure waiting due to the nature of the stuck market problems to fix.
if he pops up again out of thin air (or even anonymously wants to free some resources or simply turn over info that would make a takeover easier), welcome...! that would make the whole thing moving further immediately, I guess. yet, at this point I evalutate the probability of this happening practically zero.
but things are already rolling... I believe, it won't take long till first results will follow