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

Looking to buy spark any interested sellers DM me

my wallet not sync? please give me some nodes!

I still cannot get the wallet working.
1.2 or 1.3

minGW Runtime Assertion Failed

Any news or update....??

Looking ahead for the revival of this coin. Keep it up edschroedinger 

I'm still watching spark, great job, edschroedinger. Let's mine some sparks again!

so now...

some numbers first:

my wallet shows me, at the moment there should be
- 2.164.130 SPARK already distributed
- which would be close to 9% of  
- a total supply of 25.000.000 SPARK.

and fact is, currently there's almost no new block beeing generated by pure staking.

that would change, if we'd turn on POW again... I'd go and distribute them like so:

 

*the ~days calculations are at most something like a very rough estimation,
as the total amount of blocks generated at the specific height, will consist
of both, POW and POS blocks.


so, about 5.500.000 SPARK - that'd be ~20% of the total supply - could be created
via POW within that next 4 years. so much for the theory... the practical side will
show that this amount in fact will be somewhat lower, as some blocks are
well beeing created via POS... whereas this should be max. 17.5% of the already yielded
coin supply every year.
however, POW will work indefinitely and could be used to generate new blocks,
yet every block just yields another 0.2 SPARK until the maximum coin supply of
25mio SPARK has been finaly worn out.

conclusion:
- final amount stays the same
- distribution allows for auxiliary mining to engage every time
- staking still is more profitable in the long run
- POW distribution of only 20% over a 4 year period doesn't exhaust coin supply
- after 4 years, POW can only generate max. 100.000 SPARK / year. that's 0.25% of the total supply

that is the only solution I could find, that actually could work and wouldn't even touch coin scarcity after all.

this is the one and only last chance I see.


other option would be to drop that thing completely, as I don't see a chance to get SPARK online with POS only.
not any time soon, not even in a hundred years  


well... that been said...

In theory, I'm ready to release the code, as well as to provide a windows .exe (w/o needing some additional .dll's anymore)

but I want to get in touch with bittrex and bter beforehand...
(I think I remember that c-cex already did close their spark market...*)
 
and I want to make sure, someone still is in this thread here and interrested in an update...
...I still get connections to the presumeably dominant network, consisting of 1.2 as well as 1.0 clients...
however, to enable POW, obviously those clients need to be updated as well or any POW block will become
rejected eventually.

so, please leave some feedback, at least to show you're still here and somehow ready to make an update within a few days.
the code changes will be supported with proper comments and so should be easy to verify...



----
*) cannot confirm, as with my smashed cellphone, as well my 2fa to enter the site is not available atm. but maybe I can fix that in the same turn...

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 










 
 

well well...


some news in all shortness:

on the good side, I might have found a solution to get the SPARK network up and running again... might...
...atm I do not get any connections anymore and I hope that will change back, as up to this morning I had like 4-5 connections more or less constantly.

the downside is, I havent heard from RentaMouse for like 2 weeks now, so no clue which conclusion to draw on that... and I'm only like starting to get a remote clue on how things work in the core of the coin.
...would be a great thing to learn, if not dealing with a patient in the emergency room... and me - to continue with the metaphor - beeing the doctor... yet, of theoretical physics xD

however, it might as well be, that I already found a solution... need to test the code and will release an update, which will be mandatory, within the next 24h... if however I can confirm the code working of course...





------ 4h later...

some bad news, but only regarding my local real world stuff... a couple minutes ago I finaly smashed my cellphone display and touchscreen went byebye, so I'm a little bit into getting into my device as - I know, I know.. - important functionality is stuck with that event... some 2fa, fone, sms, etc. ... so i have to reroute this however and see what I can do to fix that mess xD...  


...but I'm also into debugging that network issues as soon as my head is free to concentrate upon that... hope to tell you asap anyway however if and when there will be a next release that will help getting the stuck chain issue running...
I'd love to give you a well-founded assessment, but that'd be almost solely based upon educated guesswork and gut feeling... (see. the doctor thing above) :/

ok, I sorted some github things and think, we're one step further to going 'official'.
the code moved to the
NEW OFFICIAL SPARK REPOSITORY, DEVELOPEMENT ORGANIZATION, PROJECT PAGE

• at first, the new wallet repository that I just forked off the last release (1.3.0.0) from RentaMouse is now to
  be found right here: https://github.com/SparkCommunity/Spark. you know how to use that, IF you use that.
  
• this repository is not coupled to a single user rather than held by an organization with current team members: EdSchroedinger, RentaMouse (this needs to be confirmed before visible to public).
  this step should make it a matter of minutes to coordinate code and patches with new or temporary coders (if however suddenly certain volunteers appear out of thin air ), plus it renders the developement history even more transparent, relatable and comprehensible when scrutinized.
  the organization page will also contain some info on the team and whatever needs to be covered there. yet, don't expect much right now, it's low prio so still the default yadda yadda. but this will change in the near future
  http://sparkcommunity.github.io
  
• the Main Project Page is, where all the info, mostly related to the technical side, will run together from now on.
  we'll use this page to provide digested info, hopefully in a somewhat user friendlier way than the certainly more functional repository pages: http://sparkcommunity.github.io/Spark/
  
• as well no content atm. but the Project WIKI will be used as a public knowledgebase. I've got a lot of notes that will be assembled to various tutorials and walkthroughs related to compiling the wallet for various target os. as said, empty still, yet for the journal: https://github.com/SparkCommunity/Spark/wiki

I will see if I can catch RentaMouse today to coordinate the next moves and how we get behind the latest client 1.3 vs < 1.3 problem.

however, you'll find the latest Spark-Qt.exe (1.3.0.0)still over here:
https://github.com/RentaMouse/Spark/releases (you might need to get the 'post fork' release as well, if dll's are missing. there's info on the page)
there will be as well precompiled windows binaries available under the new repository structure when the next release is ready.


HOWEVER, one thing will come as save as the bank of england (will be vanished from mother earths surface on day), and that is:

another MANDATORY WALLET UPDATE, as there's no other way getting that messy network on par with the latest client version without continuously hanging around in limbo between either
a) low staking rate thus endless tx and even longer confirm times... or
b) proper tuned stake properties but too much old clients in network and having rejected the last aprox. 1000+ blocks from the 1.2 clients...

so expect an UPDATE soon... after finding a way to avoid or at least minimize further deadlocks, there will be an announcement on all relevant channels with the details.

stay in touch, more info soon...

 

any time soon... sorry it's beeing quite but consider us working every spare minute... talking of spare minutes, our daytime jobs take their tribute too and just talking about me I had forced some time off recently and a lot stuff waited to be kept track with...

nevertheless, we're at it... and when we're at a stable state, all the infrastructural stuff will be launched... had recenent contact with some of the well known internet formats (names will follow ) and the rejuvenation of SPARK seemed to be a pretty interesting topic ...so when it's ready to be officially relaunched, there will be as well some news coverage

this week was quite less time than I expected to make spare, yet the next days I think I can get a a lot deeper into it as possible over the last days...

so: YES, WE SPARK!!  ...uhm... SPARK, SPARK, HOORAY!... YAPPA DAPPA SPARK!!... well... ok, that slogan needs some work, too

any update

I'm afraid we have a fairly major problem with the blockchain atm, and in a way its a lovely example of the problem with PoS coins:

PoS staking was working fine until around the 9th Nov, with blocks being created around the target rate of 1 per minute, but then it got slower and slower until it was approaching 1 per day. This was caused by a combination of not enough SPARK actively staking on the network, and a relatively high minimum PoS difficulty. After waiting to see if the problem would sort itself out it appeared necessary to update the wallet code to address the problem - hence ver1.3 was released early on the 22nd.

Approx. 21:00 on the 22nd a large SPARK wallet (possibly as much as 300k) reconnected to the network - unfortunately before it resynced with the current blockchain it had already started generating its own PoS blocks and because its so much bigger than the rest of the wallets staking for the last two weeks that chain took precedence. Bittrex monitor things like this, I expect some alert went off and that's why we have the post from Richiela at 21:30 about the 55 block rollback.

Two problems now exist:

1) That big wallet wasnt updated to v1.3, so wallets which are updated to v1.3 are rejecting its blocks because they use the wrong difficulty calculation. Not really a major problem because the network weight (amount of staking SPARK) in 1.3 wallets is tiny compared to the 1.2 version, so we could downgrade again without much trouble.

2) The 55 block rollback means that transactions included in the lost blocks no longer exist, so exchange ledgers will no longer balance - deposits and withdrawals will have been cancelled. People have a habit of not resending coins to the exchange when that sort of thing happens, so they end up out of pocket.


The only solution I can think of currently is to enforce a rollback - if I can find a copy of the correct blockchain as close to block 24623 (where it was before that large wallet appeared) I can produce a v1.3.1 which includes checkpoints to enforce that blockchain as the correct one. Edschroedinger has sent me a copy which he thinks is pretty close to that, I havent had a chance to check it yet. Its definitely a hard fork update (again) though, so I can't guarantee that Bittrex or Bter will want to go through all the hassle of sorting it out.

still disabled on bittrex  how can i withdrawal my coins to my wallet ??

the blockchain is moving again!!!

Just bought some on bittrex. Hopefully it is a good choice. 

u got pm

have a very recent just-before-24600 copy of the chain... dropped it on mega ^^

the new block explorer works fine... can see that tx went ok @ height 24616

Little bit of good news, my main node has staked block 24631 on the ver1.3 wallet, so the new diff calc is working.

yup, and so do I ... well, actually bought some extra spark when it was at the bottom but my wallet as well contains ~2.5k spark... but the experience gain on the other hand is priceless. so, If someone want's to seriously donate some spark (when transactions and block generation go without a hitch) I encourage you to go for that address atm.:

Sg2dujC3jMa9j1ff41sjAZRV4mZkjwgN6G

all this and more will be accumulated on the new announce thread comming soon (it's already around the corner ^^)

prepare for    *#~~~[ reIgnition ]  




yup, made some notes on what to fix and I guess we almost saw the same things... but I absolutely agreed to see that as low prio... when gone through compiling the windows wallet here, I refine that note and get it to you... time to get us sort of groupware ...I'm getting back to u via mail later anyway