EOS.IO Dawn 2.0 has been released along with a public test
(…).As published in our Roadmap, “Phase 2 – Minimal Viable Test Network” was to demonstrate the following by Fall 2017:
- P2P Network Code
- Wasm Sanitation & CPU Sandboxing
- Resource Usage Tracking / Rate Limiting
- Genesis Import Testing
- Inter-Blockchain Communication
(…).all blockchain and network code necessary to launch and operate a private network can be found in our Github repository. Our internal testing shows we can sustain several thousand transfers per second and 1 second blocks using our single-threaded implementation on average hardware. (…).
Over the next 6 months, we will be continuously testing and debugging the network to improve stability and performance.
New Features in Dawn 2.0
Genesis Import Testing
We have implemented a snapshot tool that will import initial state based upon the EOS ERC-20 token distribution on the Ethereum network. (…).
Token Faucets
We have also implemented a “faucet” facility to allow testing of the network by those who do not hold tokens or have not yet registered a valid EOS public key.
Resource Usage & Rate Limiting
We have implemented basic rate limiting and resource usage tracking. (…).
Bandwidth
All transactions consume some of the maximum network bandwidth as configured by the block producers. (…).
Computational Bandwidth
All transactions consume some computation. Computation can be executed in parallel, so it can be viewed as a multi-lane highway with each lane having different congestion. (…).
Database Storage
EOS.IO contracts have access to an in-memory database where they can store application state. The contract is billed based upon the total data they store plus a constant overhead factor for each independent database entry(…).
P2P Network Code
We have a basic implementation of mesh network code that is being demonstrated by our public test network. Block.one is operating 21 independent servers each with one of the initial producers configured.
EOS Dawn 3.0
EOS Dawn 3.0 will re-introduce horizontal scaling of single chains and infinite scaling via secure inter-blockchain communication. (…).
Infinite Scaling and Infinite Decentralization
The holy grail of blockchain technology is to enable secure communication between two independent blockchains without requiring both blockchains to validate everything on the other blockchain. This requires making one blockchain a light-client of another blockchain.
(…).Under this model, the communication will be secured so long as at least ⅓ of producers are honest. Furthermore, if even one producer is corrupt they can be automatically punished if they sign any message that could potentially corrupt a light client (aka foreign blockchain).
(…).
Public / Private Communication
With interchain communication it will be possible for private blockchains to have secure two-way communication with public blockchains. (…).
Development Progress
In order to deliver our public test network, we divided our development into two parallel paths (…).
With EOS Dawn 3.0 we will be restoring the ability to do multi-machine horizontal scaling by use of up to 65,000 different regions. All regions will share the same accounts and contract code, but have independent in memory databases(…).
Working Integration with Apple’s Secure Enclave
In our last update we announced our intention to support the same elliptic curve used by Apple, Android, and many smart cards. (…).
(…).
Known Issues
There are a number of known issues with EOS Dawn 2.0 and it is expected for there to be significant instability with this early release. The purpose of this release is to demonstrate a basic capability and our team will be ironing out bugs and improving stability and performance over the the next 6 months.
In order to support stability of the test network, we have disabled producer voting.”