Why is it better than golem ?

It's hard to describe.
Technically, other Supercomputers such as Golem maybe have great use cases (or one use case should I say?) that we currently cannot cover at all ... Blender Rendering for example. If they manage to get their infrastructure stable and safe, they will be able to offer at least one use case that we can't - not now at least.

Elastic works different: We do not have one specific use case, instead the use case has to be coded by the users in Elastic's own programming language - Elastic PL. It is similar to C but with limited functionality so it can be guaranteed that Elastic code can be executed on other machines without causing any harm. Ther language has been discussed about for a very long time and many brilliant heads have helped designing it. You can write a program in Elastic PL and others can be sure that if executed, no exploits, no endless loops, no data leakage or anything else may happen.

So while our Elastic Baby is more flexible in designing tasks, is does not perform that good for one partucular use case that other systems are tailored for. It's sort of a trade off between flexibility and performance / doability. But: If you want to do 6 different tasks you need 6 different "Coins" if you pursue the other coin's approaches. Elastic can do them all ;-) Please keep in mind, that due to the nature "mining" work, some use cases are not yet possible - only tasks which explore a search space can be done now, and not "stupid" tasks which are divided into multiple packages (like rendering divides a large image into many smaller tiles).

But I am sure that Elastic PL will get better over time: Since we have a "flexible" system built and designed this way from ground up to allow "user configurable tasks" - we are as far as I now the only ones that offer this - we are basically limitless concerning our imagination.

Please correct me if I'm wrong. Please ask if something is unclear. And please write that more beautifully - I suck at writing.

If you want to help Elastic litewallet launch please post your IP/hostname node(s) here: https://talk.elasticexplorer.org/t/ip-hostname-if-you-want-to-launch-node-for-mainnet/237

Thanks!

another quick update...

When EK wrote his BTC example, he identified 2 key issues.  1) We needed a more flexible memory model, and 2) Incorporating Functions into the language was needed (it was originally not incorporated due to issues w/ recursion).  I am about done with the upgrades to the ElasticPL engine which addresses these 2 issues as well as incorporates several other fixes to prepare for SN integration.

To see an example of how much more user friendly the language is now, I rewrote EK's BTC example using the language upgrades:

     https://github.com/sprocket-fpga/xel_miner/blob/master/examples/SHA256_BTC.epl

Here's what it looked like before the changes to ElasticPL:

     https://github.com/OrdinaryDude/elastic_bitcoin_miner/blob/master/test

I am still a couple weeks away from wrapping up all the changes to ElasticPL, but they should be ready to test soon.  However, there are still other key issues that still need to be addressed before everything is ready:

     1) Will we have POW, and if so what logic is needed to ensure the miner actually performed the work
     2) How to store data between iterations and distribute to miners
     3) SN Integration

These are complex issues that will take time to solve.  It will require quite a bit of change to both the Core Server and Miner and will require quite a bit of coding from both EK and myself to complete.

Are there folks that want to start forging right from first blocks of litewallet? I would like to contact with you first so we can little test before I'll annouce to the rest of community that mannet is open. Please leave a comment or send me PM.

I also assume that you know how to setup your node and I think that's clear that I'm asking for people that are able to run node 24/7 (at least first few days).

Voting should be made only after we can understand and articulate clearly what our different options are with their respected implications (lite wallet is one of the options). Setting up voting without all the other options to choose from will be undemocratic and manipulative to say the least.

I'd like the first release to contain something innovative and not just sending/receiving tokens. But the community can vote on this.

I'd like the first release to contain something innovative and not just sending/receiving tokens. But the community can vote on this.

I keep bumping the versions because people silently upgrade and cripple the blockchain since the versions are not ready and hard-fork every 10 minutes due to protocol changes that I experiment with.
I have to push it to the git so all nodes in the cloud can sync it.

I agree that a develop branch would be better, but I have not found the time yet to port it.

Neither 0.10 nor 0.11 were ready at all ;-) But 0.12 will be ... I am currently experimenting with the python elastic-sdk and hope that I can demonstrate a real use case in python later on.

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.

Who will do work for PR? community's plan / dev's plan?

I've became a father today! Little Michael came to our (crypto driven) world. I don't know why but I felt I need to share this with you all guys! Happy XEL and new life!

I know this is big offtop but I thought it's big news for all of us that new crypto-sick child is aware of the world .

News from my own perspective:

I'm working on XEL PR website. I hope I'll deliver it soon. It will be not CMS but all source will be on github/bitbucket. So anyone who want to update content will have free will (pull requests). Full open source.

Just short update from me.

I'm 24h on foot without sleep. I'm going to bed. Good night for all XEL freaks.

I am doing as fast as I can, but sometimes there is a point where you face so many expectations that you start working faster and faster - with a higher likelihood of errors and mistakes.



I have finished the core client, it now has:

- Supernodes, these are the nodes who sign off on works, pow packages and bounties. Anyone with 250000 XEL can become a supernode and help support the network. The 250000 XEL go into a secure deposit, and are given back when the supernode status times out and is not renewed. Unless ...
- Guardnodes, these are watchdogs that occasionally (with a very low probability) run plausibility checks on what supernodes do. If a supernode comfirms work solutions, which can be proven wrong, the supernode loses both its super node status and its deposit. So ... unless a bounty is higher than 250000 XEL, the supernodes have no incentives to behave maliciously. Nobody can become a guardnode unless he is hard coded into the client.
- Supernodes earn 10% of all bounties and POW rewards. I have initially set the reward to 10%, so there is a high incentive to run one of these. The exact value can be negotiated of course.
- Also, redeem transactions have now the exact timestamp of the corresponding BTC transaction in the BTC blockchain.
- All forfeited deposits (be it from malicious supernodes or from bounty haxx0rs - remember, blounty submissions need a deposit one block earlier) go to an account called the "DEPOSIT FORFEIT ACCOUNT". Not sure who should hold it and what happens with those funds ... but for now, it's there. Giving everything to the miners could be one option, but what if a bug causes a deposit to be taken by accident. Let's keep this on the radar.

There were many other little changes, the API is fully functional and has been extended by the features described above, and everything should work fine now. I say "should", I am not saying it is ... so we should do some more testing. But before we can do so, we need to get the supernodes up and running simply because of the very simple rule: no supernodes, no work!

I cannot finish them today though. I have been working 10 hours yesterday and around 11 hours today to get the core client ready. The faster I go the more superficial the coding process will become and the more testing you guys will have to do.

I have added numerous tests which test all kinds of reward, deposit and deposit forfeit scenarios! However, those tests do not test what has not been thought of. We need at least 1-2 days of heavy testing I would say.

... ah, and: everthing is in the Git.