Blockchain infrastructure
End date:
03/06/2018, 01:59 AM
4 000 000 000 USD
Brief information
Get money
20 000 000 USD
1 ETH = 4 EOS
1 000 000 000 EOS
Start date
26 Jun 2017
  • information
  • news
  • Video
  • roadmap
  • team
  • partners

Reviews: 31

Suggest video
MasonAUS — Nov 25, 2017
CryptoWyatt — Nov 12, 2017
BritVR — May 12, 2017
Suppoman Udemy — Nov 27, 2017
The Awakenment — Nov 12, 2017
Coin Interview — Feb 06, 2017
MasonAUS — May 12, 2017
Young And Investing — Mar 07, 2017
EOS.IO — Dec 12, 2017
EOS.IO — May 12, 2017
EOS.IO — Nov 28, 2017
EOS.IO — Nov 24, 2017
EOS.IO — Jan 11, 2017
EOS.IO — Oct 29, 2017
EOS.IO — Jul 28, 2017
EOS.IO — Jul 06, 2017

Team: 4

  • Brendan Blumer
  • Daniel Larimer
  • Brock Pierce
  • Ian Grigg


Suggest news
  • 1
    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.
  • 2
    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.
  • 3
    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. Language Support Adding support for additional langauges to be compiled to WASM: C++, Rust, etc. Documentation & Tutorials.
  • 4
    Parallel Optimization
    After getting a stable 1.0 product released, we will move toward optimizing the code for parallel execution.
  • 5
    Cluster Implementation


ICO Rating   
Invest. potential
ICO Bench   
ICO profile

Full description

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.



External analytics

Found a mistake in the ICO description?

Report a mistake

Suspect a SCAM?

Report a SCAM
© 2020 ICO Market. All rights reserved