Doesn't really make sense to enable public before the sidechain imho

Should be the focus though. Having public workers but 0 tasks (because too expensive) won't reflect well on the price

At least speaking from observing the market and the available dApps, there is close to 0 usage right now. The main reason is, in my opinion, that smart contract fees are higher than almost any possible computation in the current categories. Meaning that the marketplace would never be used by anyone with economic requirements as long as the cost of transaction > cost of computation. I know that there is the possibility of calling iexec functions from smart contracts which needs to run on-chain anyway, but I haven't seen any example of these and can't think of any near term applications for this. I'd be happy, if you have examples which disprove my point, but realistically I think the main point of iExec is enabling cheaper computations for massively parallel tasks, OpenMOLE would be a good example.

As Loom have shown, building fast and cheap sidechains for ethereum is possible and most dApps which are built today and not designed for massive computations (such as games, simpler applications, etc.) build on Loom. So a focus on sidechains for iexec would have a very high priority imho

I'm not (thats why I sold and waiting to rebuy lol). It's just my opinion that enabling those cheap computations is one of the most important things to show that iExec actually has value for the business world. Waiting for Plasma to be completed (which could be Q4 2019 or later, no one knows) could prove to be a big mistake.

Although considering OpenMole, it'll be interesting to see their 'bag of tasks' and whether or not that tips the scales of economy in iExec favour regardless of ETH fees.

Yes the dApp challenge has been very fruitful and the feedback is probably extremely valuable for the team. I'm interested in the "bag of tasks" approach as well, although I'm not sure if this needs on-chain consensus per-task (=expensive) or not.

@BlairMac No, unfortunately not. Am away for vacation atm.

Lack of liquidity and userbase will probably prevent listing for now, but can't hurt to try. In the longer term if RLC continues on their current trajectory, I'm fairly sure they will get listed, but it will take some time

@BlairMac Jup, still around, just busy with life:) Bear markets like this leave a lot of room for being productive 😄

So when approximately will the first sidechain version be ready ?

Night Man
Good read, but I was more hoping for a estimation how many RLC will be needed should staking or the equivalent be used.

Right now something around 30% of the computation cost for a task will be needed to "stake". I wouldn't call it staking though, as no new coins are created, but rather a security deposit.

Jordy Hut
The only thing I do not understand is iExec's reserved attitude with the public workers. The reason may be Sidechain improvements with Parity are not yet on point / SGX support for privacy-preserving off-chain computing for public workers and kata containers are not yet on the point / Standards specifications proposed by the Enterprise Ethereum Alliance does not yet provide any authority for public workers.

Probably because there is no demand for work on the mainnet yet with the current private workers, so making public workers available isn't a high priority. Rather its making the marketplace more attractive/economical for developers and computation requestors. Making workers public is a great opportunity for PR, so the timing needs to be right. No demand for computation = bad PR, because computations providers (miners) would get frustrated.

From what I understand, the parity WASM interpreter can run smart contracts written in web assembly and now also runs on SGX, yes

chrome works too

Microsoft talking now, pretty good talker

Jup, Lei speaking now