iExec is an open-source, decentralized cloud computing platform, running on Ethereum blockchain. iExec allows decentralized applications (dApps) an on-demand access to computing resources and technologies on iExec cloud. iExec has built a blockchain network where dApps can take advantage of cost effective and high-performance resources such as servers, databases, SaaS applications, web hosting and computer farms. iExec’s native cryptocurrency — The RLC token is the primary asset used to access services in iExec infrastructure. RLC is short for “Run on Lots of Computers.” iExec is headquartered at Lyon, France. It was founded by Gilles Fedak and Haiwu He, both are serving as Chief Executive Officer and Head of Asian-Pacific Region of iExec, respectively. Oleg Lodygensky is the Chief Technical Officer. Gilles Fedak received his PhD from the University of Paris Sud in 2003, and has been working as INRIA (Inventeurs du Monde Numerique) research scientist at ENS in Lyon, France. Similarly, Haiwu completed his M.Sc. and PhD from the University of Sciences and Technologies of Lille, France. On April 19, 2017, iExec launched its token sale and raised more than $12 million in exchange for 86,999,784 RLC. In order to support dApps, smart contracts, and their platforms, iExec takes processing-intensive computations off-chain so as to keep a blockchain’s on-chain functions running smoothly. To do this, iExec makes use of XtremWeb-HEP, an open-sourced Desktop Grid Software. Desktop Grid computing (also known as Volunteer Computing) pools unused computing resources to be used by applications and platforms, and according to iExec’s whitepaper, XtremWeb-HEP “implements all the needed features” to make this possible on a global scale, including “fault-tolerance, multi-applications, multi-users, hybrid public/private infrastructure, deployment of virtual images, data management, security and accountability, and many more.” Essentially, with this software, dApps can utilize any computing resource in the iExec framework to run their programs. In their whitepaper, the iExec team lays out the project’s competitive landscape and explains these competitors in relation to iExec. They’re quick to note that decentralized cloud storage providers like Filecoin, Storj, and Siacoin are not direct competitors, and it’s easy to see why. While iExec could theoretically take a step in this direction as it matures, it’s not a storage platform; it’s a computing platform. This does put it in competition with other decentralized computing protocols like Golem and SONM. Both of these, however, are taking aim at a different animal. Essentially, they’re both building a decentralized supercomputer on blockchain technology, while iExec is targeting dApp development and sustainability. Both look towards a future of a blockchain-powered, decentralized internet, but their functions, while sometimes similar, are more complementary than conflicting.
Beam Mimblewimble is a scalable, fungible, and confidential cryptocurrency based on the Mimblewimble implementation. WHY BEAM? Core features include complete control over your privacy, All transactions are private by default, No addresses or other private information are stored on the blockchain, Superior scalability due to compact blockchain size, Opt-in Auditability, Support online and offline transactions, atomic swap, hardware wallets integration. Governance model No premine, No ICO. Backed by Treasury Establishing a non-profit foundation to govern the protocol after Mainnet launch How does it work? Wallets’ owners create new transaction using secure channel either online or offline Both wallets participate in signing the transaction using Schnorr protocol Wallet sends transaction to node Each transaction contains a list of Inputs and Outputs represented by Pedersen Commitments, as well as explicit fees and kernels. Each transaction also contains non-interactive zero knowledge range proof to verify that the output transaction value is positive Transaction is verified by the node Each transaction is verified with respect to the recent blockchain state which is stored as a Merkle Tree. The root hash of the tree is recorded in block header along with a proof of work. In addition, each node periodically creates compacted history to allow ‘fast sync’ of new and existing nodes. Transaction is added to the mining pool A block is mined every minute and is sent back to the node for verification and distribution. Mined blocks containing the new transactions are sent to the known peers A valid block that is extending the longest chain is accepted as a new Tip and propagated further until full consensus is reached. Fast sync When a new node connects to the network for the first time it can request compacted history containing only system state and blockchain headers. There is no need to retrieve the entire transaction history.