Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 187. (Read 450523 times)

Evil-Knievel, dude, We want to see Mainnet cmon my friend

I was thinking to mention to Ben Dickson's twitter about XEL , but i couldn't send him a link with extensive information about the project . I think that we should hire a professional for promoting .
A new ANN thread would be a nice first step , where we could gather all the information spread in this thread and informing about the roadmap of the project . For something like that we need graphics , logo and a nice website .
Maybe we should make a mini donation as community or donate a portion of our coins for that purpose .
EK and guys ( ttook , coralfreerer etc ) have done so many things for XEL , i think it's time for the rest of us to do our part of the job .

EK paid others from his own pocket from what I know.

Who said, that developers don't get paid ? Evil-Knievel paying, as long as I remember

nothing scammy here, but since developers don't get paid ( which is terrible), they have to work along with their paying jobs and family and etc.

There's always a room for "one more test" or "one more feature", you know. But this is one of a few projects where the words "long term" don't sound scammy to me.

Almost done might be mean today, next week, next month, who knows 

only EK knows 

2017? I thought we are almost done !

Are you planning to launch before the end of 2017?

Totally agree.So less announces about XEL.

We will do more marketing.

Yeah, if you didnt pay the journo you aint gunna get "hyped". No matter. Keep on chuggin fellas. You are an inspiration to the real folks here not trolling. 

There is no need to rush to be recognized. Bitcoin never did. There is going to be a functional and useful system very soon. From that point it will grow steadily for sure.

Such articles work very often on a basis of initiation. That means we contact an author and introduce him to XEL and next time he eventually mentions us.

For us its best to wait with such contacts until we are live and can not only declare something that we want to accomplish in the future, but something that already WORKS. Thats a BIG advantage in contrast to all those nice plans of Golem and others.

To me, it seems that the journalist could have done his job better. There is no other way I could explain why the almost finished and already working XEL is ignored while for example "iex.ce" is thoroughly elaborated on.

https://techcrunch.com/2016/12/27/how-blockchain-can-create-the-worlds-biggest-supercomputer/

  they should put XEL in this obvious PR article.

Thanks ;-) Well the holiday was two-fold. First, the mustang broke down, then I got a rental which also broke down and I was standing 5 hours on the highway waiting for a replacement   What a weekend.

Regarding the work scheme, I (and we all) was just sticking to the original idea and together we came up with something that is actually working and which allows for an almost-reliable proof-of-execution. Surely, it is perfectly suited for one specific class of computation problems.

What you describe is usable for different kinds of tasks, ones that do not explore a search space for the right solution to a complex computation problem but which "map-reduces" a large but simple computation problem into multiple smaller tasks which are computed by multiple nodes and then puzzled together afterward.

Golem does exactly what you have described and I think that it is not sufficient to verify the computation result by letting multiple nodes (or should I say my own Sybils) execute the same package and checking for the equality of the results. I would go even further ;-) I am quite sure that I will be able to show a way to bypass Golems verification mechanism (as it is described currently) and I think I would be willing to put a public 1000 dollar bid on it! Surely, I could lose but at the moment I am really confident. And if I can't make it, I think HMC would be very likely able to claim my stake ;-)

(Reference: https://golem.network/doc/Golemwhitepaper.pdf, Nov 2016, Resilence Chapter)

Enjoy holidays! Well deserved!

The way I picture distributed computing is that work request doesn't contain the work data, or even the code - but just the hash for it. E.g. using IPFS to distribute the data/code. Then computation should arrive at same result done by multiple workers and workers only publish the hash of the result. Once there is agreement work is correctly computed - payment is made. At least that's how I would do it. But nothing wrong with making what you have go live, and later expand it to include more computation methods as they mature.

Is there anything I should know before giving it a shot. Any pitfalls? Do u have a record of offences for which u have been convicted and sentenced to two years in australian correctional facility? Do u eat bugs? Damnit I wouldnt touch it until I have a detailed report on an introvert behind XEL btctalk account.

Just came back an hour ago. I will post some updates tomorrow.

hi ek, any update?


* elastic pl
* website
* core testing
* mainnet

?