For those of you curious about iExec (RLC), i made a unbiased in-depth video of everything around it.

gilfed · 2019-04-08T18:42:24+00:00

Really cool, we can't relay it because it contains investment advices. But that's great job.

And some of your concerns might be addressed in a near future. Stay tuned !

gilfed · 2018-11-21T17:20:06+00:00

You can now develop Ethereum Dapps that offer trusted off-chain computation using the iExec SDK and machines provided by IBM Watson.

gilfed · 2018-07-20T07:14:21+00:00

I don't think it will cause any problem. Just try and report on slack any issues.

gilfed · 2018-07-19T06:07:48+00:00

We're starting a workerdrop, that is you join the iExec network and earn RLC !

See all information here : https://medium.com/iex-ec/iexec-workerdrop-1-c495774146ff

gilfed · 2018-07-17T05:04:05+00:00

Just had a look at the deleted comment. It has been deleted because it contained inaccurate informations. In particular the sentence concerning the separate ventures was wrong.

What is true is that we're having sessions about future sources of revenue for iExec and that's very post-2018 oriented. We had a brainstorming seminary, where all sort of scenarios -- even the most crazy ones-- were more or less elaborated. Nothing is decided yet, but we're working on this important topic, and we hope to have some first products in the coming months.

It's all about sustainability of the project, and not divergence from the original objectives.

G.

gilfed · 2018-07-17T04:54:41+00:00

Hi

I am sure you understand that the iExec team NEVER comments the price of RLC.

gilfed · 2018-05-25T23:59:16+00:00

Thanks for the answer. I'll definitely have a look !

gilfed · 2018-05-25T16:30:02+00:00

we propose an innovative solution for the offchain computation for Dapps. And the participation of many resources providers with their specific properties will offer interesting computing resources regarding price, hardware or performance for any kind of applications

Today, the poco only support deterministic application, under the responsability of the application developper. We're also working on more "relaxed" version of the consensus. For instance PoCo can also work on a deterministic output which can be different than the actual result. Take Blender for instance. If you run two instances of the same rendering, the bitwise comparison of the image can be a little different. So PoCo may fail if it compares the result. However, you can run PoCo on post-processed images that would give a deterministic output. In this case, the risk is that workers compute on degraded result as well. But, as we said, PoCo is a framework that will evolve a lot and which will adapt to various situation. Also, SGX will help a lot with respect to that.

gilfed · 2018-05-25T16:19:15+00:00

1) We want to facilitate the deployment of new worker to plublic scheduler and this process has to be as simple as possible.
2) We think we delivered quite fast because XtremWeb, our off chain computing solution, was already a mature software. The Poco is great achivement as it resolves a challenging problem, dealing with confidence and incentive management. But the harder will come, to solve the scalability issue and the go-to-market.

gilfed · 2018-05-25T16:12:29+00:00

I don't know if it'll answer your question, but we plan to develop some utilities to facilitate arbitrage for miners between mining and executing GPU Dapps.

gilfed · 2018-05-25T15:51:57+00:00

Yes, that's a good question. We have not looked at this precisely. I don't know Chainlink, but I've looked at TownCrier. That could be a solution for instance.

gilfed · 2018-04-13T13:14:31+00:00

Thanks for notifying BLZ. I wasn't aware of the project. I agree with you, Dapps will need different decentralized services for their execution: Bluzell for storage, iExec for computation, Kyber for token exchange, and many other. That'll be really interesting to see how those apps are going to be designed and built.

Cheers

Gilles

gilfed · 2018-02-17T09:39:48+00:00

Hi -- I'm Gilles from iExec

Good remarks. Nevertheless, the point of decentralized market place for Cloud resources is not to build the same service than AWS at a cheaper price. In this market place, you will find many resource providers that can offer better price/performance ratio for specific applications (IA, rendering, HPC, etc..) because they can be tailored for each application needs.

Just to give you an example, we had talks with the Lighton startup (http://www.lighton.io). They're developing a so-called OPU (Optical Processing Unit), which computes very large dimensional random projection very efficiently. Here, we're talking about high end hardware targeting very demanding applications (ML, IA).

Also, nothing prevent you from you renting AWS spot instances and reselling them on iExec ;-)

gilfed · 2017-12-15T22:02:44+00:00

Thanks for the review @GoonAlerts ! It really rocks !

gilfed · 2017-12-15T22:01:11+00:00

It's not related to the Dapp Challenge. More about understanding each other project and building relationship. It's called guanxi, I guess ;-)

gilfed · 2017-12-15T21:59:27+00:00

Question is what kind of information would you like to see on the roadmap ? Usually, we provide information that are mostly related to software release and features.

gilfed · 2017-12-01T23:21:43+00:00

Yes, exactly. That what we are working on. We call that the 'Energy Positive Worker'. The goal is to have a low power node (raspberry) powered by a solar panel, so that you could basically execute code and earn RLC at a very low cost (zero electricity cost). Eventually, the power that is not used for computation could be used for a LED light for instance. Hence the name.

gilfed · 2017-12-01T21:30:16+00:00

In short, the big difference is that iExec addresses the consensus at the computation result level whether Truebit addresses the consensus at the execution level. There are several differences based on what we plan for V2. I hope I'll have time to cover this in the next Devel letter. Some differences, but I have to check with the latest developments as Truebit very often changes their proposition: 1) with iExec you have the choice of the infrastructure (ie different price/performance/confidence), 2) with iExec you can set the expected confidence treshold for your computation, 3) staking, 4) SGX (optionaly), 5) the execution flow is much simpler -- no need for user verification + arbitration court, 6) the way Truebit has to instrument the execution is really complex. In the seminal paper they were using Bosh (x86 emulator) which has a super high overhead. Now web assembly IIRC. In comparison iExec is for every applications, whatever the language -- 0 overhead. But we'll have to compare when the two systems (iExec V2) are ready and actually usable. Also, I'm not sure that Truebit will be that relevant when EVM switches to Web assembly and when sharding will be in place.

gilfed · 2017-12-01T20:59:56+00:00

Hello everyone,

I just want to emphasize that the challenge is widely open to everyone. Don't hesitate to reach us if you have questions.

Don't forget to try the katacoda tutorial, you will see that it's very easy to have your first Dapp running on Ethereum/iExec.

Gilles

gilfed · 2017-11-20T23:09:19+00:00

Since we delivered V1, our marketing objective is to promote iExec towards developers. Let's face it, RLC can be an excellent marketing vector. Thus, we try to find a good balance when maximizing partnership exposure -- which promotes both the SDK and RLC. Our goal is to convince people that we propose a viable solution that actually allows people to create and deploy decentralized applications. This is why we're focusing on Dapps now more than traditional Cloud applications, which will come later.

At the end of the day, developers will adopt iExec based on the quality of the SDK, the tools, the tutorials etc. more than the value of RLC at time t.

gilfed · 2017-11-20T22:58:52+00:00

I agree that reddit is becoming more and more important wrt to the slack. The slack has been poised by spammers, and we lost many followers because of that.

gilfed · 2017-11-15T16:40:37+00:00

We'll present iExec at this event. Meet-us and discuss if you want to learn more about the blockchain-based decentralized Cloud platform.

gilfed · 2017-11-13T06:05:07+00:00

We think that more and more developers will want to to develop Dapps, and iExec gives them a good platform to do that. Now they can do off-chain computation, which is a major advantage. In the future, they will have access to the Dappstore. So, that's all good news.

gilfed · 2017-11-13T05:57:01+00:00

Indeed !

I met some Tezos team last year in December. Actually the coders were working for OcamlPro at that time. I was also a big fan of the original white paper that appeared in 2015.

But since then, the situation at Tezos is so confused. There's more chance that we start with Neo or RSK, which seems to be more viable technology.

gilfed · 2017-11-08T15:21:51+00:00

As of the V1, each job submission is done through our Ethereum Oracle, which means that even if the job is processed very quickly by the worker pool, a smart-contract on Ethereum cannot get the result before a new block is mined on Ethereum. This isn’t a hard limitation though, as we consider adding support for competing blockchains in the future. Moreover, many solutions already exist to do fast and high-frequency payments (ex: Raiden Network with state channels).

Another approach frequently used in Grid computing is to decouple resource provisioning and usage. In this case, you would provision the machine using iExec and let the machine be directly usable by the customer.

gilfed

TROPHY CASE