Want to add news about this ICO? Fill in the form and add the link to the news in "Your message" field.
Minimal Viable Testing Environment
The goal of this phase is to establish the APIs that developers will require to start building and testing applications on EOS.IO. In order for developers to start testing their applications they will require the following to be implemented:
Standalone Node (Dan & Nathan)
A standalone node operates a test blockchain and produces blocks while exposing an API. This node does not need to concern itself with any P2P networking code.
Native Contracts (Nathan)
The EOS.IO software has a number of native contracts. These are contracts that manage the core operations of the blockchain and exist outside the Web Assembly interface. These contracts include:
@eos - manages EOS token transfers
@stake - manages locked EOS, voting, and Producer Election
@system - manages permissions, messages, and contact code updates
Virtual Machine API (Dan)
Contracts are compiled to WebAssembly (WASM) and WASM must interface with the blockchain via a defined API. This API is what developers depend upon to build applications and be relatively stable before developers can really start to build on EOS.
RPC Interface (Arhag, Nathan)
A simple JSON RPC over HTTP interface will be provided that enables developers to broadcast transactions and query application state. This is critical for both publishing and interacting with test applications.
Command line Tools (Arhag)
Command line tools facilitate integrating the RPC interface with developer build environments.
Basic Developer Documentation (Josh)
Documents that teach developers how to get started with building on EOS.IO blockchains. This includes documentations of the WASM API, RPC Interface, and Command Line Tools.
Minimal Viable Test Network
Everything in Phase 1 assumes a trusted environment that only runs the developer's own code. Before a test network can be deployed several additional features need to be implemented and tested.
P2P Network Code (Phil)
This is a plugin that is responsible for synchronizing the blockchain state between two standalone nodes.
WASM Sanitation & CPU Sandboxing (Brian)
The WASM code needs to be sanitized to check for non-deterministic behavior such as floating point operations and infinite loops.
Resource Usage Tracking & Rate Limiting (Arhag)
To prevent abuse the resource monitoring and usage tracking rate limits users accoding to staked EOS.
Genesis Import Testing (DappHub)
Tools need to be developed to export data from the EOS Token Distribution state and create a genesis configuration file. This will enable anyone participating in the Token Distribution to acquire some initial test EOS (TEOS).
Interblockchain Communication (Nathan)
This feature involves verifying the Merkle hashing of transactions is proper.
Testing & Security Audits
During this phase the platform will undergo heavy testing with a focus on finding security issues and bug. At the end of Phase 3 version 1.0 will be tagged.
Develop Example Applications
Example applications are critical to proving the platform provides the features required by real developers.
Bounties for Succesfully Attacking Network
Attacking the network with spam, virtual machine exploits, and bug crashes, and non-deterministic behavior will be a heavily involved process but necessary to ensure that version 1.0 is stable.
Adding support for additional langauges to be compiled to WASM: C++, Rust, etc.
Documentation & Tutorials.
After getting a stable 1.0 product released, we will move toward optimizing the code for parallel execution.
The EOS.IO software introduces a new Blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications. This is achieved by creating an operating system-like construct upon which applications can be built.
The software provides accounts, authentication, databases, asynchronous communication and the scheduling of applications across hundreds of CPU cores or clusters. The resulting technology is a Blockchain architecture that scales to millions of transactions per second, eliminates user fees, and allows for quick and easy deployment of decentralized applications.
Add ICO to Favorites
Save the ICO projects you are interested in and get quick access to their news and updates
To start getting notifications about ICO start, you need:
ICO added to Favourites
ICO removed from Favorites
This rating is provided by the ICORating.com.
It is based on the clear assessment standards for projects and is based on a transparent and standardized scale. A profound and unbiased analysis of a project allows an objective risks evaluation and the creation of a complete picture of the project and its potential. This includes the technical features of its platform, the business model, the team, strengths and weaknesses of the decentralized infrastructure, etc. The scales are for the hype and risks, with the final evaluation of the project potential.
This rating is provided by the ICOBench.com.
It is a combination of an assessment algorithm that uses more than 20 different criteria and the rating provided by the independent experts. The rating is not permanent. The ICOs are monitored on a daily basis. Also new experts join and rate the ICOs. If none of the experts rated the ICO yet, only the assessment algorithm is used.
Enter the E-mail you provided during registration, we will send you instructions
Password is successfully changed. Check your E-mail.