Topic: [ANN] [XEL] :: XEL - The Decentralized Supercomputer :: - page 177. (Read 253624 times)
That's why you should do one so you can make a big splash like the other DSC's. Don't you want to have a foundation? Don't you want to compete with Golem and others?
How long is the development going on, tired of waiting to buy...light wallet - does not mean start mainnet ?
You Guys Should Do Another ICO So I Can Get 5X Need Crack Money.
What are you talking about, there is NO ICO here, so sad you miss the donation phase a year ago and you don't get your 5X
You Guys Should Do Another ICO So I Can Get 5X Need Crack Money.
Wow. I have just seen the new project relative to supercomputer . Is it the same as golem, RLC...?
I will consider to join this project if it has many special functions .
I will consider to join this project if it has many special functions .
Well, this is the first decentralized supercomputer project actually. And it has its own programming language already. Other
competitors can only dream about it...
For comparisons check this post.
again a cointelegraph news about supercomputer without mentioning Elastic... but interviewing SOMN Project.
guess if this is a paid news
https://cointelegraph.com/news/decentralized-supercomputers-marketing-ploy-or-future-global-os
guess if this is a paid news
https://cointelegraph.com/news/decentralized-supercomputers-marketing-ploy-or-future-global-os
The special function is that it has a very working prototype now which gets merged into the mainnet later (this summer?)
Wow. I have just seen the new project relative to supercomputer . Is it the same as golem, RLC...?
I will consider to join this project if it has many special functions .
I will consider to join this project if it has many special functions .
Is there any information about when the XEL will be added to exchanges and what are the exchange platform?
https://talk.elasticexplorer.org/t/preparation-to-litewallet-mainnet/227
should i use proxy server?
The very short version: A job requester would annotate an SSA form program (in a specific machine model resulting in a particularly structured (binary) flow graph) with a simple liveness/reachability model so that miners could (quickly, and without running any example case inputs) verify the necessary complexity bound of the job's individual work task before selecting. PoW solutions would operate a little differently (still using "per user" generated inputs incl nonce data, but basically hashing/checking "instruction by instruction" instead of at the end of each input run) so that PoW solution rates become uniform across jobs, being able to be found at any point mid-execution. (PoW prize pool would probably also need to work a little differently, with any amount of proof-of-work certificates able to be submitted before a bounty is found, and the PoW pool being divided proportionally after.) Bounty solutions would include an annotation of the original model with information about the eventual I/O relation, such that verifying the output submission can be reduced to an instance of a satisfiability problem. Nodes (all of them) would validate solutions against this model. (They would still need to "re-run the program" by a symbolic interpretation, but could know that they are doing so in an optimally efficient way - effectively skipping any "unrelated loops" encountered.) Jobs would always end after one bounty is found.
I'm summarizing a lot, but that is the basic idea.
Thank you for the contribute HunterMinerCrafter. I wonder has anyone of the contribuitor explorer further this concept?
I haven't really had time to look into this yet....but here are my initial thoughts...
@HunterMinerCrafter, I think the latest version of the ElasticPL language sets us up well for something like this because it requires the job author to create a "verify" function with logic for a similar purpose (right now it's just to verify the final Bounty solution...but could easily be expanded)...so I don't see this as being difficult to implement technically. What I don't have a good feel for is this...a job author may be quite successful in expressing their primary algorithm to be solved in ElasticPL, but if they don't know how to (or just get lazy) express the verification logic in SSA form they may leave lots of room for miners to exploit their POW rewards without actually working on the Bounty solution. My concern is that they may not know where these intermediate checkpoints need to be within the flow in order to keep the processing time to a minimum while ensuring the value checked truly demonstrates that the miner performed the work they say they did. Of course, I may be completely mis-understanding what you were suggesting...any additional thoughts would be appreciated.
Is there any information about when the XEL will be added to exchanges and what are the exchange platform?
https://talk.elasticexplorer.org/t/preparation-to-litewallet-mainnet/227
i want to get some xel ,how can i do ... 
You made the right decision regarding buying xel.
Your options are as follows:
A) Build a time machine and participate in the donation phase
Or
B) Wait for the mainnet launch and buy from someone OTC
Or
C) Wait for xel to be added to exchanges after launch and buy there
Good luck!
Is there any information about when the XEL will be added to exchanges and what are the exchange platform?
Any Canadian English translation bounty dev ? 
PS: I'm not Canadian but I've been to Niagara Falls ( hope I get more bounty for saying this too)
PS: I'm not Canadian but I've been to Niagara Falls ( hope I get more bounty for saying this too)
Honestly, where did all these new people suddenly come from? I mean, it's not that the old thread had a different name or so.
The new thread was posted in announcements. Many people get email notification for every new thread on this subforum so they can be early looking for airdrops, campaigns or mine new coins at low difficulty on their first blocks.
They ask these questions on every thread, they don't even read the OP.
For someone like you who actually comes here trying to talk about real tech and development, I can see why all this sounds a bit strange
Quite a good idea to promote new idea/coin over and over. Just create new thread every half a year and new investors will show up.
Honestly, where did all these new people suddenly come from? I mean, it's not that the old thread had a different name or so.
The new thread was posted in announcements. Many people get email notification for every new thread on this subforum so they can be early looking for airdrops, campaigns or mine new coins at low difficulty on their first blocks.
They ask these questions on every thread, they don't even read the OP.
For someone like you who actually comes here trying to talk about real tech and development, I can see why all this sounds a bit strange
The very short version: A job requester would annotate an SSA form program (in a specific machine model resulting in a particularly structured (binary) flow graph) with a simple liveness/reachability model so that miners could (quickly, and without running any example case inputs) verify the necessary complexity bound of the job's individual work task before selecting. PoW solutions would operate a little differently (still using "per user" generated inputs incl nonce data, but basically hashing/checking "instruction by instruction" instead of at the end of each input run) so that PoW solution rates become uniform across jobs, being able to be found at any point mid-execution. (PoW prize pool would probably also need to work a little differently, with any amount of proof-of-work certificates able to be submitted before a bounty is found, and the PoW pool being divided proportionally after.) Bounty solutions would include an annotation of the original model with information about the eventual I/O relation, such that verifying the output submission can be reduced to an instance of a satisfiability problem. Nodes (all of them) would validate solutions against this model. (They would still need to "re-run the program" by a symbolic interpretation, but could know that they are doing so in an optimally efficient way - effectively skipping any "unrelated loops" encountered.) Jobs would always end after one bounty is found.
I'm summarizing a lot, but that is the basic idea.
I'm summarizing a lot, but that is the basic idea.
Even shorter version: Instead of giving a machine and getting an input/output pair, you give a model of a machine's behavior, and get back an input/output pair's relationship to that machine. Instead of having a chance to find a PoW certificate at the end of each work attempt (effort of which varies run to run) there is chance to find a PoW certificate for each individual value propagation in the program, which would be uniform both run-to-run and job-to-job. A job requiring on average twice as many assignments per attempt would generate twice as many work proofs on average for the same number of attempts run.
I posted my last comment before I saw this. These are great ideas and definitely worth exploring further...
Thank you for the contribute HunterMinerCrafter. I wonder has anyone of the contribuitor explorer further this concept?
i want to get some xel ,how can i do ...
You made the right decision regarding buying xel.
Your options are as follows:
A) Build a time machine and participate in the donation phase
Or
B) Wait for the mainnet launch and buy from someone OTC
Or
C) Wait for xel to be to exchanges after launch and buy there
Good luck!
Time machine seems more feasible.
haha hope the mainnet release soon!
exciting time.
exciting time.
And after that happens everybody can not wait to be part of it.
Quote
Those who need computational resources, model their problem using Elastic’s programming language (Elastic PL)
how can I learn this Elastic's programming language? any tutorials or guidelines?
thank you.
ElasticPL is modeled after C...if you know C/C++, you already know ElasticPL.
Here's a summary of the language based on the most recent updates I have made to it:
https://github.com/sprocket-fpga/xel_miner/blob/master/ElasticPL/ElasticPL%20Language%20Notes.txt
Quote
Those who need computational resources, model their problem using Elastic’s programming language (Elastic PL)
how can I learn this Elastic's programming language? any tutorials or guidelines?
thank you.
Jump to: