If anyone is attempting to write a use case in ElasticPL, feel free to contact me for tips on how to use the language.
Also, be aware that ElasticPL is undergoing a major revision...the main github does not have the majority of these changes. They are only in my github.
I just love the fact that elastic has its own working programming language and not just whitepaper gibberish. This too me it is one of the most exciting things in Elastic. I really hope some one will soon help coralreefer, and create examples/tutorials for the Elastic PL language. |
|
|
|
Is there any news accordingly from markets? If bittrex will add xel it will be great. Even on forum there is buy orders around 10k which is great
make a request to add XEL to polo here; https://www.poloniex.com/coinRequest I suggest to supply all needed info/links for this to make it easier for people to fill it correctly in the polo request form. For those who want to submit request add coin to polo; What is the name of the coin?ElasticWhat is the coin's symbol?XELPlease link to the announcement pagehttps://bitcointalk.org/index.php?topic=1957064.0If the coin has a website, please link it here.http://elastic.pw/If the coin has a block explorer, please link it here.http://elasticexplorer.org/Please explain why you would like to see this coin added to the exchange.Elastic is an open-source project that aims to build the first decentralized supercomputer. Elastic has been developed over the last year or so and provides the infrastructure for a decentralized and distributed super computer, designed to carry out arbitrary tasks over the internet. In this context, Elastic is powered by a crypto currency (XEL) and provides a market-based mechanism to buy and sell computational resources. Those who need computational resources, model their problem using Elastic’s programming language (Elastic PL) and broadcast it on the network, along with a certain amount of XEL coins. The Elastic miners are then motivated to offer their computational resources in exchange for a portion of those XEL coins.If this coin has any significant innovations over other coins, please elaborate on them here.working system unlike other similar coins such as golemfor the last two questions you can use your own answers  I would put more here if possible: "If this coin has any significant innovations over other coins, please elaborate on them here." I mean, you put that we have a working system unlike Golem, but I think there is much, much more to differentiate us and competition, and it would be really great, is someone could compile bullet like list. It really is a question,why Elastic is awesome? You could then, at the end of that list add that Elastic, unlike other projects have working system, although still in development. Thanks |
|
|
|
It was a scam guys, the most BIG SCAM of the year
I do not think SNOM is a scam, we should be patient to wait for the team to fix the website problem. so you think that a team that is not able to fix a website in a couple of days can deliver a decentralized supercomputer platform in less than a year? you're a special kind of retard what exactly does not work? At the moment the website does not show how many tokens have been sold SNM TOKEN SOLD: |
|
|
|
|
Can someone please tell me what's the purpose of a child chain in Ardor, and what's the role of IGNIS ?
Thanks
|
|
|
|
Looks like nxt will hit .30 cents soon before big news
What big news? |
|
|
|
Launch is planned at 17 June 2017 14:00 UTC. Note that this date can change if something urgent will happen to fix. Especially if there will be need for hard fork (we don't need and don't want any HF before launch). Above date is currently safe date to launch litewallet. Most probably it will happen on that date. http://countdown.elasticexplorer.org/Congratulations to all people involved! This is a great moment, and one of many that are going to come soon. Elastic has the best team and the biggest potential. |
|
|
|
Thanks for the awesome update Unvoid. I will set up a node once the main net begins. |
|
|
|
It is not suitable to discussing the ico cost. As we know, the NXT was built on 21 BTC, XEM also built on very little donated BTC, they all realize almost 10000 times profit if calculated with fiat.
Not every project is NXT, not every project is XEM, not every project is XEL.
I dont see any usage for XEL, 2000k is a good price, how someone else mentioned its 8x regarding to your Fiat Donation. XEL has no Cooperations, no product, no usecase area, nothing and you think 2000k is low? Dont know what you re dreaming of, but ive seen lot of projects like this one in the past. Dreaming all around and than realizing that you cant do anything with your coin. Iam honest, i would invest, but everything over 3000k would be ridiculous at this stage of development. Actually, 2000k is a very good price. I would sell at that. But maybe it is a bit too much don't you think? After all, 2000k sat is 0.02 btc  , I didn't notice. People will do anything for cheap coins. We should all be careful & alert ! That's right, stay vigilant folks!  |
|
|
|
Yet another supercomputer project? Come on.
HAHAHA Trying to buy cheap? |
|
|
|
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.eplHere's what it looked like before the changes to ElasticPL: https://github.com/OrdinaryDude/elastic_bitcoin_miner/blob/master/testI 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. Well done Coralreefer. sha256 proof-of-work example implemented in ElasticPL language - awesome! Did you guys think about having some kind of shared state between workers/nodes per job? I wonder how would you divide a task of some sort between workers in the network, in such a way that they do it in parallel? (I'm not sure if my question is perhaps to generic) Thanks. |
|
|
|
I think warm orange instead of the green will look better. is the choice definite, or can adjustments be made?
I haven't voted, but I would've voted for the green. The vote is over. This is what was chosen by the community and I'm happy with the outcome. At the end of the day it's about building the brand around the logo, not the logo around the brand. @twistelaar - What's the point with voting, when you want to change the logo just because you don't like the outcome of the voting, which is what majority selected! Logo looks great, was selected by fair voting, and as asenski said it's also about building a brand. |
|
|
|
Thanks unvoid. BTW, I love the way the voting is organized with elasticracy. Brilliant. Yeah, would be cool to have elasticracy built in the wallet (some day) Elasticracy will be outdated as soon as mainnet launch. Original stake holders will be irrelevant. If we want to some kind voting mechanism we should take a look at NXT or other coins that tried to implement voting mechanism. That is a valid observation indeed... Does NXT have voting built-in? |
|
|
|
Thanks unvoid. BTW, I love the way the voting is organized with elasticracy. Brilliant. |
|
|
|
Excellent choice guys! I like it very much. Don't know who made it, but thanks!  |
|
|
|
Why i can't find XEL on poloniex or bittrex?
can some body tell me where is this coin trade on? i want to keep my eyes on it
It's not listed. Still in development... Hopefully majority will vote after a lite-wallet to enable liquidity, and we could be tradable soon. |
|
|
|
I can't believe that we can't find a motivated C dev with networking experience to work on this project. How is that possible with so much talent in these forums? Did anyone put any formal ad for this somewhere?
There are motivated, experienced C developers around. The issue is how do you convince them to give some of their valuable time to Elastic? Allow them to have a stake in XEL and they will have a big incentive. For that we need to be tradable, thus we need the lite wallet soon. |
|
|
|
Although the conversation has again shifted back to a vote about a lite wallet, I'm still not sure what I perceive as the main issue is being addressed....how do we get more devs to help with the coding?
I just don't want people to go vote for a lite wallet, and we still end up with the same issue. Having BTC/XEL in a fund won't speed up my progress...I only work on this in my free time when I have nothing else going on...funding won't change that.
So whatever you vote for, the question still remains...how do you get a C programmer (experienced w/ high volume networking...which I'm not) to work on the ElasticPL engine. Of course they can code in a different language, but that would require porting over everything I've done.
Totally get your point. The key advantage we have is, that the SN part is entirely disconnected from the core client. This would allow us to start with a "PoC" SN node (which is slower due to task switching) and improve it gradually. This would not require any changes to the core client. To make it even easier, we could think about defining a Bounty-only version as the MVP (to mitigate the fast task switching thing) and move to PoW later on. What do you think? Regarding the task switching, I already got an idea. Switching libraries sucks, but what if we compile one big library with different functions (run_28727427, run_27627424, run_129929292). This library could be generated every time new work is detected and would only be needed to be loaded once. I could assist with it (or do most of it) Would it be SN that has to recompile the library every time a new work is added? If so, do you guys have any concerns about an adversary submitting cheap work repeatedly to make SN go slower due to CPU being used for compiling? Also, what if an adversary submits the jobs very quickly and the SN can't keep up with producing the needed library. Would it create a queue that would build up and make the SN unable to validate jobs? |
|
|
|
|
EK, I fully understand what you are saying. I also really, really appreciate what you are giving to this project.
This is perhaps one of the difficult moments in the projects life we need to get through together.
I don't want to upset you or anybody. If anything, I would rather help a little bit, if I can.
I really do think having a tradable token would relief pressure here and allow people to get involved.
Like you said, you need to focus on coding, designing and basically get the thing done.
To allow you to have more time for this, we need people to do other outstanding and necessary things; website, PR etc.. Like you said, I believe above, we need more people joining the project.
|
|
|
|
|
Show Posts
