Topic: [ANN] Spark | X11 | BTer/Bittrex/C-CEX | PoW/PoS | Exchanges | Roadmap | - page 9. (Read 108569 times)

you should discuss this directly with bittrex , will be faster to find a resolution, they've dealt with this before

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.

...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:

• after finding the EXACT first block with the chain beeing split

we need to find out:

• 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...

What RPC Port are you using?

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....

Same here.. Thanxs bro fixed!!!

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

I've been having a quick scan through the Github repo and although it does appear to be mostly a SilcCoin/ZeroCoin clone the dev was adding some new stuff for a "Market API". Last update was 8 days ago though, so currently it does look like the dev has had an unfortunate accident/been kidnapped by aliens/ turned out to be Alex Green - however unless the last option turns out to be true (somewhat unlikely he had time to turn out a coin in the last couple of weeks) there doesnt seem to be any evidence of a "scam" so far. Whilst we wait I will fork the Git repo and see if it will compile a new release of the wallet, so we at least have the option of a community takeover.

I'm not a coder, just a tinkerer, so dont get your hopes up for Sparkv2 or anything, just keeping the options open.

Where the fuck is the dev?

Do we just leave the wallet to stake or do we have to add "setgenerate true"?

when UI finally pops up it crashes immediately, i also restart router disconnect cables even close electricity for a while... exe still crashing

maybe i should switch off the world!   

I wonder if this thing will make a comeback like the recent GHOST coin gongshow did?!? 

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)

Anyone got issues with wallet? After restarting my computer the wallet wont start, at start up screen the .exe file crashes. I delete the folder @ roaming keep the wallet.dat and got still the same issue. Even moving wallet.dat and let it create a new one the .exe file still crash.

For those of us that have spark on bittrex, does that mean only chance for market to reopen is if dev solves fork issue?

forgott....


just in case, my peerlist... might help:




17:16:39

[
{
"addr" : "213.136.72.235:16665",
"services" : "00000001",
"lastsend" : 1414512845,
"lastrecv" : 1414512888,
"conntime" : 1414502352,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14144,
"banscore" : 0
},
{
"addr" : "178.62.47.198:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502357,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14144,
"banscore" : 0
},
{
"addr" : "98.229.49.119:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502363,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14144,
"banscore" : 0
},
{
"addr" : "46.105.118.15:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502407,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14145,
"banscore" : 0
},
{
"addr" : "194.79.23.168:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502423,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14145,
"banscore" : 0
},
{
"addr" : "206.116.116.186:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502614,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14152,
"banscore" : 0
},
{
"addr" : "66.175.212.66:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414502709,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14156,
"banscore" : 0
},
{
"addr" : "217.129.141.209:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512888,
"conntime" : 1414507791,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 14303,
"banscore" : 0
},
{
"addr" : "114.98.197.184:16665",
"services" : "00000001",
"lastsend" : 1414512888,
"lastrecv" : 1414512889,
"conntime" : 1414512042,
"version" : 70000,
"subver" : "/Spark:1.0.0/",
"inbound" : false,
"startingheight" : 11605,
"banscore" : 0
}
]