We were on a roll, the impatience of some has pissed of the devs. Yes the alts are on the rise, but it could be a bubble. This isn't a pump and dump project. Look at Decent, all the fud they get and they won't launch until "THEY" say they're ready. So if EK states that the project is not ready for launch, we should listen. He's trying to do something unprecedented in the crypto space.

Exactly!
We should first deliberate and discuss what are our options and how they are outlined, and then, and only then, cast our votes on the option we wish to choose.
(Seems some people here sat on some extra spicy chilly...   hold your horses and let us do this the smart way for the common benefit of everyone involved)

Unvoid, could you please set up the voting for the Lite wallet ?

+1

This is my fear and why I am for getting getting something deployed.  I believe the more we test, the more we realize better ways to provide more flexibility / value to xel job authors and it becomes a never ending cycle.  Ideally, I think it would be best if a solid version that includes basic ElasticPL functionality is deployed...but even with that we now have a couple question...do we stick with the POW model we have?, EK identified some issues with the underlying memory model so we need to determine if changes are needed there, etc...and this was just in the last 24 hours.

Hopefully, people won't make their decision based on the bubble crypto is currently in...not sure how much longer it will be but I've got to believe this bubbles going to crash and we'll be right in the middle of that...so you won't see the huge influx of buyers.  I base what I recommended to do solely on what I feel may help us get more devs to pick up some of the more mundane code fixes while EK continues to explore new use-cases.  But I could be completely wrong  

Either a HF, or we could use the new soft fork voting mechanism where the other features become "locked in" if enough block generators set the proper flag in their configuration. Either way ... a software update will be mandatory! This also means, that some "less freqeuently online people" will end up with a non-functioning wallet. But if we use the new soft fork voting, they will at least not end up on a fork, their client just stops working when the "feature" gets locked in.

Tomorrow I will show how to mine a Bitcoin block using Elastic  People were asking for a real use case, so I thought this might be real enough.
A task for a long night, but I hope when I turn on the coffee machine tomorrow morning (or afternoon) I will be done with an example that everyone can run locally.

Testnet 1.0.3 ist live.

Steps:

1. Delete the entire elastic_test_db/ folder. The old DB will fail!
2. Update to the current state: git stash; git pull
3. Compile: mvn clean compile package
4. Run: mvn exec:java


Now go ahead and destroy it! 

In the past we voted anonymously (by signing with our ico address) to make a joint decision, can we use this system to enable each ico participant to make a private anonymous contribution pledge to the future foundation wallet at mainnet launch?
This can be done parallel to creating a btc donation wallet for immediate collection.
I have no doubt that we will be collecting sufficient amounts of donations (xel and btc) while still keeping and respecting privacy, and the decision of each participant regarding the amounts he wishes to donate.

@coralreefer we need you. More than before.

You're going to have to wait until XEL gets listed on the exchanges.

Once I am finished with everything and have brought everything to a point that it all works, I am outta here.

I am dedicating a large portion of my life for this, many hours per day where others go swimming or watch some movies, and I really try to get everything right. And if something comes up that was not planned, I hit the reset button and do it over - just because I want to make it perfect for you guys.

But the more I do, the more people demand from me without even honoring what I have done so far. And if I need a few days longer I naturally become the asshole.

What once began like a fun and thrilling project becomes a true burden. I don't even like to come here anymore, because all I read is "mainnet?" "why is no documentation there?" "why is not this and that there?" "where are you? You have not reported to me for 2 days".

Regarding the status: almost done! The thing is ... do we want it "working somehow" or "working well". The working "somehow" is ready right now, the "well" needs some more testing over the weekend. We have supernodes for a day ... I don't feel comfortable to NOT test it well.

A good serious project like xel should be traded on serious exchanges that have the volume, exposure, respectability, it deserves. All small volume outlets should be disregarded. Take into account that it is much easier to create pump/dump scenarios (what we want to avoid) if the coin is traded on a marginal low volume exchange (of course it can be pumped on the big ones, but at least it takes much more finance to do so which makes it at least harder).

cross posting!

i agree hype can cause some ppl react purely emotional and cause some economical damage, however imo hype (pump) is the best PR in cryptoworld. without it projects like xmr, dash, even ltc and btc would never get exposed to such wide userbase and get some kind of mass adoption.  working product without exposure will stay under radar for long time, so long until something comes along and replace it!! so from my experience hype (pump) is necessary evil for project to get exposed and adopted.

Problem that XEL solves? how about cheap computation power we all crave to have access to! although XEL devs don't like to promote it, elastic best selling point imo would be CPU/GPU mining/solving other cryptocurrencies.

Yeah, I personally do not think so ;-) At least not if they do not fix the virtual-machine-mess. But this is just my personal opinion which might be wrong. I have told them all bugs that I see at the moment, so let's see what they do with it. The first reaction was, that I was laughed at in their slack channel ... but this might have correlated with my nickname "Long Dong Silver" somehow.  Maybe they do it, and become a very great project.

Whole package arrives as promised on weekend, including a full documentation and in fully operable state.
The roadmap was reorganized a bit, but (from my side) everything went (and goes) as planned.