Re: [ANN] Spark | X11 | BTer/Bittrex/C-CEX | PoW/PoS | Exchanges | Roadmap |
well... how should I start...
right now, it's save to say (at least, that's what I experience here) that the SPARK network is stuck at around block 27622... on the 1.2 clients. thee chain that is at around 27620something supposedly is the one, the most clients are around thus build the whole of the potential network anyway...
...then there's that seednode client at spark.cryptonotepool... RentaMouse had set up and included as seednode for the 1.3 client update... with the new staking parameters... but that's stuck as well I think... I don't know exactly which client version runs on bittrex and bter (bittrex updated to 1.3 and after 55blocks went offline with the wallet is my last info)
so, regarding the facts:
- block generation with the 1.2 client obviously doesn't work as for a full PoS with such parameters, a strong network of staking clients is needed. that will fail if there's just a couple clients online every now and then... staking deadlock, as I guess at least a lot of the small to medium wallets experienced...
- block generation with the 1.3 client as well didn't work, as this network seems to consist of only the seednode and the chain, that forked off ~1000blks ago seem to be abandoned, at least I don't get any new blocks from that side...
I draw the conclusion, that only by turning on PoW again, there is a chance to bring back movement into the stuck chain.
Silkcoin, which is something like SPARKs clone parent, had a similar thing implemented... they turned of PoW for some time and reopened after blk 50000 or something.
atm, I'm calculating some parameters, but I'm planing to release the code any time soon in the new repository. I think I will trim down coin generation at around 1 SPARK per block. it was at: 200 < blk7200, then 100 < blk14400... I will calculate some reasonable values and post them here as soon as I got them. yet, as a rough calculation and first experimental settings I used a new upper PoW bound of 500k new blocks... that'd make 500k new coins over a period of ... many years, have to actually calculate that, not in my head right now... but many many years
...so, staking still would be beneficial and possible... and some miners as well would be able to help maintaining the network with a little amount of mining power, gaining a little amount of extra spark.
well, as I mentioned I'm far from beeing an experienced coin dev, so speaking with that amount of experience and maybe a decent amount of general development experience, I'd say it's the only way to don't let the coin eventually die out in the state we've got right now.
I'm collecting the values now and post them here, will finish the code, contact the exchanges to check upon their wallet status first to coordinate the update... if they have rolled back to 1.2, there shouldn't be the biggest problem anyway... however, I guess it would be even better for them to wait a couple days with the update until the current clients are updated, working and I can confirm to them, that the network has stabilized and generating new blocks again...
if however anyone has suggestions. ideas, objections or concernc, please discuss.
hasta la vista... I'll be back
right now, it's save to say (at least, that's what I experience here) that the SPARK network is stuck at around block 27622... on the 1.2 clients. thee chain that is at around 27620something supposedly is the one, the most clients are around thus build the whole of the potential network anyway...
...then there's that seednode client at spark.cryptonotepool... RentaMouse had set up and included as seednode for the 1.3 client update... with the new staking parameters... but that's stuck as well I think... I don't know exactly which client version runs on bittrex and bter (bittrex updated to 1.3 and after 55blocks went offline with the wallet is my last info)
so, regarding the facts:
- block generation with the 1.2 client obviously doesn't work as for a full PoS with such parameters, a strong network of staking clients is needed. that will fail if there's just a couple clients online every now and then... staking deadlock, as I guess at least a lot of the small to medium wallets experienced...
- block generation with the 1.3 client as well didn't work, as this network seems to consist of only the seednode and the chain, that forked off ~1000blks ago seem to be abandoned, at least I don't get any new blocks from that side...
I draw the conclusion, that only by turning on PoW again, there is a chance to bring back movement into the stuck chain.
Silkcoin, which is something like SPARKs clone parent, had a similar thing implemented... they turned of PoW for some time and reopened after blk 50000 or something.
atm, I'm calculating some parameters, but I'm planing to release the code any time soon in the new repository. I think I will trim down coin generation at around 1 SPARK per block. it was at: 200 < blk7200, then 100 < blk14400... I will calculate some reasonable values and post them here as soon as I got them. yet, as a rough calculation and first experimental settings I used a new upper PoW bound of 500k new blocks... that'd make 500k new coins over a period of ... many years, have to actually calculate that, not in my head right now... but many many years
...so, staking still would be beneficial and possible... and some miners as well would be able to help maintaining the network with a little amount of mining power, gaining a little amount of extra spark.well, as I mentioned I'm far from beeing an experienced coin dev, so speaking with that amount of experience and maybe a decent amount of general development experience, I'd say it's the only way to don't let the coin eventually die out in the state we've got right now.
I'm collecting the values now and post them here, will finish the code, contact the exchanges to check upon their wallet status first to coordinate the update... if they have rolled back to 1.2, there shouldn't be the biggest problem anyway... however, I guess it would be even better for them to wait a couple days with the update until the current clients are updated, working and I can confirm to them, that the network has stabilized and generating new blocks again...
if however anyone has suggestions. ideas, objections or concernc, please discuss.
hasta la vista... I'll be back