Workerdrop 1 was a success!

iExec is a decentralized marketplace for cloud computing resources. On July 20th, iExec ran its first workerdrop. Having recently deployed all its features on the Ethereum mainnet, the goal of this workerdrop was to educate and encourage any computer owner to open a new revenue stream by providing their computing power to execute blockchain applications.

For the first time ever, hundreds of computers were connected simultaneously to the iExec network on Mainnet. These computers received Blender 3D rendering tasks to achieve, and once they did so, got compensated in RLC tokens.

This marked a major milestone achieved by the iExec team, especially given that public worker pools are scheduled for September 2018. The whole team was extremely excited throughout the day to see people joining in and contributing, and has gathered a tremendous amount of feedback to improve its product.

Some stats and metrics

Over 200 nodes participated on the iExec Workerdrop 1

The workerdrop lasted for a total of 8 hours

51 work orders have been successfully executed

510 RLC were earned by participants

The total CPU units count reached 722

The total CPU power reached 453 THz

The total RAM reached 1,613 GB

The necessary average time needed to manage a work order was 1,900 seconds (30 minutes)

The average task execution time was 1,243 seconds (20 minutes), including an average real computation time of 395 seconds (6 minutes)

14 work orders were not finalized. We will deeply analyze each one of these cases. We know that a syncing problem of our Ethereum node could have occurred and generated this kind of issue when Ethereum transactions are propagated by the scheduler. In addition, multiple events are sometimes watched and we have to determine if the responsibility is either on the level of our Ethereum node or the level of the client library. For the next workerdrop, we will test a workaround for this event duplication problem.

The website recorded an increased activity, which attests of the community interest towards participating in the building and testing of such a cutting-edge technology. Thank you!

The iExec Workerdrop Dashboard at mid-Day

What did not work, and why?

Throughout the day, there has been some moments during which problems arose. Below is a log of these events, and how they have been fixed by our developers.

08:10 AM UTC, a maintenance restart of the scheduler took place. The scheduler was rebooted, and it took us some time to bring it back on its feet again. From there, everything rolled out smoothly, and new work orders were delivered regularly at the pace of 1 every 10 minutes, and later at the pace of 1 every 5 minutes.

From 18:30 PM UTC, the total prize pool of RLC reserved for workerdrop 1 was liquidated, and the scheduler was shut down.

Some participants contributed by executing work orders but did not receive their 10 RLC. This issue is linked to the 14 work orders not reaching their Completed status. We are currently examining what happened. On the meantime, if you’re in this case, please get in touch with us by sharing your public key. We’ll send your reward with an extra.

About Workerdrop 2

A second workerdrop is scheduled, with a prize pool of over 4,000 RLC. During this second event, the execution of tasks will be replicated on three workers to increase the level of security.

No staking will be needed and the process is totally similar to the first workerdrop. This second workerdrop will stand for 24 hours: from July 24, 12pm UTC (noon) to July 25, 12pm UTC (noon).

Turn your computer into a worker again and take the chance to win RLC tokens. This time, workers will be powering a fintech application applying Monte Carlo methods for option pricing on the Apple stock.

A new work will be sent out every 15 minutes. During this workerdrop, because we are increasing the level of security by introducing redunduncy, each work will be executed by 3 different workers. The total reward for each work is 45 RLC divided by 3 workers, therefore rewarding each participant with 15 RLC if their reputation score is the exactly the same.

Is your VM ready? If not, follow this tutorial to get started:

PS: China can now join the party as well, as we have made everything accessible from the Middle Kingdom.

Follow Us

Website • Blog • Slack • Telegram • Reddit • Twitter • Facebook • LinkedIn• Youtube • Github • Kakao • Instagram • Steemit • Katacoda • Docs