seems to follow a strong trend to set off mutant-coins these days... just waiting for DarkCoinDark to pop up

...and don't mind me asking if it wouldn't have been

• more appropriate
• creative
• even funny

to, at least, come up with something like:  UROyellow?

you never lose... sometimes it's just payday for the teachers



I'm as well still some 5-10% below break even again... yet, it was way worse... and right now, I'd just buy my ass off, If only I had enough free funds... people smell that spicy air of risk and sell with cold sweat dripping from their forehead ...time to buy, no sweat ever kept stuck on crypto

just a short note for the sake of your peace of mind, and your coins of course

DO:

  before bluring the thread with questions like: is it dead? or: what's with bittrex?
  please spend a few seconds to get yourself a picture and check the last few pages.
  most questions answered... wouldn't be 3-4 pages back, maybe just about 1, if
  each on would actually spend that time before posting...

  after making sure, your wallet works as it should now, you might want to WITHDRAW from
  the pools. I don't necessarily have the most recent info on their status, but last time i checked,
  withdrawal doesn't seem to be a problem anymore with the pools.
 
  those with stuck tx'es: gather details (address, timestamp, txid, amount, etc. the full monty)
  of those transactions and keep em ready.
  I'm not able to say ad-hoc if there might be a chance to 'rollback' those tx. might as well turn
  out to be possible, if they're not confirmed. if confirmed already, I see chances getting smaller.
  If possible, we're getting into that as well as a way to create a superblock that covers all
  valid and recorded refundable losses. we try to make losses as little as even possible afterwards
  but, no promises made... there might be still some (small) wounds to lick...

DON'T:

  really, don't become bewildered, uneasy, nervose... there's loads of reasons to do
  the exact oposit: relax, stay calm, be happy!
  this coin is in the process of fully recovering, it will get a second start,
  and THEN markets will be opening when save trading is not just possible, but save and stable.
  ...won't take all too long anymore.

  UNTIL that moment, the MARKETS are BACK ONLINE again, DON'T try to DEPOSIT (shouldn't work,
  will become stuck, will probably burn as old depo addresses will presumably rendered invalid)

1st things 1st... we're at it, sir!

if you consider spending some time in between until ready to be dished, you might want to clue yourself into the recent developement by getting some 3 to 4 pages back and make yourself a picture. deal?

...plans are coming

and step by step ...  there will be an explorer (maybe even more, 3rd party preferably: independent, distributed),
there will be a new one stop website and certainly social media representation,
and there will be a new thread on bct to manifest the takover reignition of SPARK and provide all the necessary information, any other proper announce would...

that's when all primary goals are achieved and stable to a certain amount.

let it heal organically... signs are all on good, worked out amazingly swift as of now...
just think about the state the coin was after 10041.
without immediate action it would have rendered all coins 0.
so... I'd say, we got somewhere since.

share the confidence

yet another crucial milestone settled... cool you got a first windows binary to compile... I'm still into building it via QT5/msys+mingw as well... such mess, very dependencies, many not compile, whow...
Thinking about a clean and fresh build environment (working on a doomed maschine right now) I do feel a strong urge to move away from windows and cross compile from linux... that setup might be worth the effort, as it could be a perky foundation for a one-for-all build solution plus making it available as facility image wouldn't bring up license problems. meh... good we have a 1st working version right now, RentaMouse u da man!

you found that old random-shizz-fud-post-generator somewhere... or did u rly just made that up all by yourself, smartiebootz??


NOPE? YUP!

ah cool man... I'm at it, too... yet, lot of time went by to just get those darn deps together... neither qt, nor vs are my domain in the first place... everything c/c++ under windows... yikes.
yet, out of bare nothing, I'm still confident to get it to a first clean run within the next 24h...


talked to a friend of mine today if I could get some space and cycles on his server to get an insight block explorer + wallet to run... and he was pretty curious and open after I mouthwatered him with what heck of a beast node would be (he's an oldschool perl/php guy... node was certain witchcraft to him til now ) ... think we should get that going somewhere next week... try to quench as much time out of my schedule as possible



..



creating an 'official repo', making propper announcement, etc. marketing blurb., are indeed close to be necessary...
yet, first we need to get the infrastructure going SAVE... we're getting closer, yet I would consider current state more or less as hotfixed only.

At this time, I'd say that the SPARK that is distributed will be save, as long as the market refunding works as expected.
RentaMouse is at the windows wallet, I'm too... and getting the refunds via an instamine block would be the solution to implement if possible.
however, at the moment I myself do have no solution in mind, how I would actually implement that, as I'm just getting into the guts of the techniques underneath...
...haha, well... I should be wee bit more secretive about making too much assertions before getting the wallet to compile propperly in one go under windows

however I guess we'll know within the next week if we can do reproduce the lost SPARK via superblock or the likes... or if we need to achieve it via donations.
within the next week I'll also try to get the block explorer going... a richlist will for sure help finding some folks to motivate for donations, I'd say



lol, not just that ... I looked at the silkcoin code and that doku seems to be as well behind... doku? DOKU?? we don't need no stinkin' DOKU!!! ...

ordinary trading action happening? dunno what you mean...? it's one rather stable currency compared to many others... and beeing down to ~1.3-1.5 from that hill at ~2.5 (with some amazing spikes indeed) over a say 5 month period is pretty normal... trading is not just buying just wait and go get some while its cheap. it'll go up again if, of course, there's no reason to loose interrest... btw. I'm still mining...

...look at CANN. that went down from 18k to 2.5-3k over a two spot dump , taking a mere few hours each... happened over a weekend straight. that's when you go: 'WTF was that on bittrex?'  ...got some loss first but some massive wins surfing the wave down... all about watching close... and psychology of course

hehe, the fun thing about stumbling over some coins per accident, as they pop up from time to time in certain multipools, is that as well some time might went by you getting into the corresponding thread for the first time... so you get over the first page and ponder and make your guesses about how that might develope...  
...and then you go to the last page to see what outcome actually took place...
hahaha, ok... sometimes it's easy... in this case it's so obviously beeing a busted flush...  better luck next time anyway


...starting with 10% premine, no features, no exchange, indecisive dev, no nothing... why would anymone mine this? nothing to offer... foremost neither a future nor a real short time trading value (multipool autotrades when profit spikes at times of nodiff, maybe... but those trades are ponziesque, yall know). price follows demand, trust and scarcity...

well...
dear folks, hope you don't mind to as well post your architecture, if you've got a problem with your wallets performing as expectes
...it might have different reasons, thus different solutions.

just some linux or win would do

--

I encourage you as well - especially if not watching this thread over the last week or so - to take the time and get a few pages back.

a lot of the common quirks and most problems have already been recognized, discussed, given info about, and most probably even solved (if a solution exists to date).
you most probably will find something helpful plus you get a good picture on how things developed the last several days.

too much asking and answering the same questions over and over helps rendering the thread diffuse and incomprehensible...

thanx for consideration





--

hehe, at last I got the time to w/d the last SPARKS from suchpool and ipominer... so, I can confirm both, to have obviously updated to 1.2.0, thus working as expected.

atm, it's 3 positions to settle...

bittrex: 14499.19442
b'ter:    20994

and most probably c-cex as well with a yet to be disclosed amt. of coins that'd be lost after rollback.
...still need to get to them (they strongly suggest using skype, meh... ain't my cup of tea tbh...)

so it sums up to:  35493.19442 SPARK of known losses to be refunded so far.

assuming a similar amount on c-cex, we should end up somewheere around 50k SPARK.
if that amount is fully known, that'd the exact amount a single insta-refund block should
drop, to set things straight with all three markets at once.

...VaultEX hasn't been included in the considerations so far, as I strongly suspect that no TX on after fork took place on that exchange....
but I'll make sure... just to be sure ...even if, this should be in an all good assessable range.

whow, you've really got your eyes peeled... that at least is intended to look like some very
promissing offer... thanx for the pretty observant heads up...
...I'm especially curious what that intel turns out to be...
intentionally sloppy hidden allusion style  

however, did get in touch immediately, as ANY HELP
actually bringin' forth the mission will be HIGHLY APPRECIATED


---




as for the linux kinda folks, that wallet is already fixed, up on a separate repo, and up to be compiled on your system (which is the utmost futile thing to mention )

the WIN32/64 wallet is the next thing to get catching up with v1.2.0.
guess, RentaMouse (who already provided us with the recent v1.2.0 updated and fixed linux wallet), is still dealing with getting that working eventually - if not achieved in the mean time...
I, as well, cloned the sources and got all the dependencies (yet, 'all' turns out to be such a relative word most times) now, to do my best as well... no competittion, yet double power... wee bit like mining. finding a block will be, to get that damn thing compiling w/o errors and abort... yet, it's just the next block, no matter who but that it's found

and we'll eventually find a solution to get an up to date OSX wallet as well...
however - just a random guess - delaying that to the last position won't be recognized as diminshing by any mac user any more today... it's just not so many folks with mac skills in the wild... and on the other hand, the demand is still very assessable...

-- as of now, for windows users, the current client HAS ITS QUIRKS*), yet still should be able to FULLY SYNC (w00t, we're at exactly 20000blks right NOW and counting) and enter staking as expected...  

[ *) if win wallet crashes on start: 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) ]



---



by far I won't stop anyone from donating (esp. if you look at your wallet and find yourself one of the lucky ones with shitloads of that coin, go ahead! )

yet, it's still to be considered that we as well might be able to get the full amount of SPARK that else would need to be risen via donations, by implementing a single instamine refund block dropping exactly the amount to compensate, when we've intel on the sum of coins needed to level that at once for all parties affected.

evaluating this will be one top priority so it won't be clear if that's doable this way or donations is the way to go...

if there's confidencen if and how to implement that... dearest community, you'll know first

Hehe, yaaay! coooool to see we're realy getting somewhere!

damn thing my old ISP went down yesterday night... that was at least 1 day early, sonofabitch

however I found (and brought to work) ye olde UMTS-stick...

...will check, what actually happened here the last hours, yet a short glimpse gave me the impression of just about 15k spark to compensate.
if this is the bottomline with bittrex I'd be extremely delighted as that'd be manageable hands down me thinks

I check for response (as far as I was able to send before network went down) / get contact to the other exchanges...

apart from that I'll grab the latest sources and try to get a windows qt wallet compiled... would have started already... but: no net, no git. no net, no mingw... etc, etc...

...I'm getting back as soon as there's news. at least, that umts thingie seems to do a great job

and big time kudos to RentaMouse... not necessary to say that a properly working wallet for the exchanges/pools would be a full showstopper if not available.
one big problem solved so far!

agree... more like a strong hint than evidence. yet... having just peers with those 1.1.0 clients should give a clear enough signal something is wrong

anyway, the first community release you provide is an important step that has been achieved


as of now, there's nothing really new from my side about situation @ bittrex,
but they've got the info they requested and are at at it and will getting back
that moment, they have something to get back with.

and as long as they stayed quite relaxed the whole time, I guess there's no
need to become nervous either



-- IMPORTANT --


now for something completely different....

IT MIGHT BE.... that starting with NOV 1ST. up to around NOV. 10TH
 ...I'M MORE OR LESS OFFLINE due to change of ISP :/

I so forgot about that switch as it's been my roommate caring for that this time...
...yet, I'm absolutely sure that I'm not completely blanked out for that time but
most likely there will be a difference within that 2 weeks.

for a situation like that I've got some umts modem I'm going to find now, that
should help bridge the gap...

as I'm sort of involved into fixing the already brittle situation, I thought you
should be informed about that situation, so you know
I've not as well contracted morbus vanishitis developitis or the likes


-- IMPORTANT --

I'd say, at least after ~blk 12600something, no transaction would be possible to get through with even 1 confirmation since no new block to contain one becomes generated. no PoW, cos no miner (I hope! what lunatic would that be), PoS not reached on that fork...
such tx'es will rot in tx cache til they are swept...



no one is on fork, we're all on spoon here



...now, seriously and in brief

the GOOD fork - that isn't one actually, but apparently the only valid blockchain.
it's the one currently at blk16000+somewhat, end of PoW reached as intended,
PoS currently active and working (like a ticking clock to be precise )

if your wallet got network clients at all (and there should be a lot around... got 12 active connections... had way less on bigger coins!)
then you're most probably in the right net anyway

the BAD fork that forked off after blk10041 is the one
with an erroneous blk10041 (and hard luck put bittrex on that fork as well as at least 2 of the miningpools).
this fork should end around 12600+somewhat when the last miner realized
that this leads to a dead end and went off.
the bad fork might as well already beeing abandoned (apart from the known ones) so sould only contain very
little nodes, if any.

if you go to the debug console and:
> getpeerinfo

you'll get a list of your next network neighbours. some of the info
is strong evidence about what network you joined. e.g.:

[
{
"addr" : "123.123.123.123:16665",
"services" : "00000001",
"lastsend" : 1414512845,   <-- should both be a very recent utime like this or higher
"lastrecv" : 1414512888,    <--- " --
"conntime" : 1414502352,
"version" : 70000,
"subver" : "/Spark:1.0.0/",  <-- should be an 1.0.0 client for now, the 1.1.0 is presumably a buggy linux client prone to take the bad fork...
"inbound" : false,
"startingheight" : 14144,
"banscore" : 0
}
]


---



I don't want to go as far as saying: no, but if:
a) they were deposited before block 10041
b) traded inside bittrex
then I'd say, there's good chance they won't even be touched by the problem and should
be available as soon as the wallet issue has been resolved.

if however deposits happend AFTER said 10041, then they might be in a contingent
where we need to find a solution to settle ledgers with bittrex... this is under investigation right now
after the guys at the rex got through it, we can work out a solution and foremost get a picture on
the volume of the difference to clean.
my impression when visually scraping the charts was that trading vol. should range at most at
around a few btc... 2-3 top maybe... likely some less... but that's just my eyes and 5 sec. look
and I'm pretty sure that tx volume won't top trading vol. in that relative short time window...

to me, that still sounds all well possible to fix






I promissed a brief version -----------------v            

cool yup, I think binary demand runs close to zero for linux, yet a clean repository was necessary in the first place as a starter.
if you could get a wallet to make under mingw, that'd be awesome... last time I tried similar, I was blessed with too little time and to much quirks to get that going, so I stopped trying after some short time...

I think, it won't take all too long 'til there's info on the tx'es that would require to be compensated, if (and that will be a necessary step to get them in sync again) bittrex drops the bad fork and switches tracks.

in a few hours I'll have some time in row to care for getting someone at the other three exchanges sharing info on the situation and their according status...

I'll drop any further info on that as soon as I become aware of them

If anyone else already IS or HAS BEEN in contact (and as such has some contact person in mind) with one of B'TER, C-CEX or VaultEX, this would be your moment to speak up  
...else i'd go for them as well as announced somewhat later this day...


---


quick recheck of all the listed pools showed, only spark.hashhot.com
and spark.binpool.com seem to have jumped the wrong trail,

so I guess while we're moving on and situation becomes stable, all other
pools will soon as well be able to reopen for withdrawal, the moment
they see transactions are save to be performed further on.

this of course is not yet the status quo.

the situation on binpool and hashhot would have to be evaluated separately
and I hope in that sense, not too much of mhash went there after 10041
as I deeply suspect those shares will be gone for good...

I don't know If there are any funds still locked from before 10041 but
if so, that should be as well manageable after getting them in the right
network.

---

btw. if we do have a VOLUNTEER who would be able to set up
and provide a (temporary) BLOCK EXPLORER some time soon...

any abe based would certainly do, yet... the insight.js - as the original one - would be a
goodie, but it needs node.js on the server platform.
hehe, or someone wants to play generous sponsor for getting one at blockexperts.com.
they provide the most sophisticated one so far i'd say... but it costs 100milli/ann...
ok, the latter one might become an option, after all went good and the spark has become
reignited

well, I remember earlz actually pointing at the very same two possible pitfalls in his review...
as we're after pow, part of is not needed anymore anyway. good you fixed that first
https://github.com/Earlz/coinreviews/blob/master/sparkcoin.txt

when you say, you could would be able to compile the wallet and release a binary, what architecture do you have in mind...?
if you go for windows, that'd be the one with the most demand i guess, we are at most there

however, later I should have some time to clone this and try getting it compiled with VS on another maschine...
'at most very superficial' would be the most adequate description of my experience on bitcoin-n-clones-code, so to speak...
...yet, seems to be a good time to change that.




info is already there ...yep, thought the rex (without diminishing the other exchanges) was the first to investigate as they had the highest frequence and the tightest gap in orders, so presumably the highest demand... thus first thing to become set straigt

yup, would be a real pitty to let that whole thing drown just because the old dev went lost (and I can vividly imagine him simply going: whow... such fork... very work to fix... many hates... such loose coins... I go... many not profit... whow!)
but apart from that dematerialized dev, guts told me that it won't require rocket science to get that thing going again...
and as of now, at least we're moving forward and chances are not bad to make a clean restart some time not too far in the future

I actually am in contact with ryan from bittrex on that case and get to bter c-c and vaultex asap, to get info on their status...
...I guess, as things are moving further quite good, we're getting a good picture pretty soon

...it indeed went past me while reading, but however, knowing it beeing Blk 10041 makes us getting somewhere,
resp. that would be the starting point for bittrex to estimate the transaction volume that has to be devaluated,
if they need to drop their chain;
which - if I understand correctly - would be anyway the only option to get a spark wallet back into
the network with the (only) working blockchain. same, that is used by factually all spark wallets
to date beyond blk 14400 (15699 as of now).
now bottom line seems, that any other option would be either way technically impossible or economically gross unacceptable.

ok, I think after bittrex has a picture how much transactions volume got involved and would need to be compensated, we will see how to get past that problem

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