THE DAWN ON EOS.IO

••
The Dawn of EOS.IO
2 days ago by eosio 62 in eos

In the EOS.IO Technical White Paper , we proposed the EOS.IO software as the dawn of a new era of blockchain…
$630.03
489 186
block.one - Statement Regarding Proposed Changes to PRC Law
4 hours ago by eosio 62 in eos

September 4, 2017 Prior to the commencement of the distribution of the EOS ERC-20 compatible tokens on the Ethereum…
$252.05
117 28
EOS.IO의 여명 (The Dawn of EOS.IO 한글번역)
yesterday by dev1by0 49 in eos

본 글은 block.one이 2017.9.3 (한국시간 기준)에 발표한 The Dawn of EOS.IO 를 한국어로 번역한 글입니다. 원문의 의미와 느낌을 최대한 살리기 위해서 약간 번역투에 가깝게…
$103.81
66 28
EOS stats.
19 hours ago by zeartul 63 in eos

The EOS tokens are ERC-20 compatible tokens distributed on the amazing Ethereum blockchain pursuant to a related…
$72.32
99 7
BitShares price $10.00 USD through the roof by New Year 2018! - United Nations backs BitShares to help with previously inaccessible currencies!
2 days ago by nandibear 51 in bitshares

BitShares price $10.00 USD through the roof by New Year 2018! United Nations backs BitShares to help with previously…
$89.54
294 39
[뮤직홀릭]EOS의 획기적인 EOS.IO Storage(스토리지 서비스)
6 hours ago by musicholic 59 in kr

원문 : "The Dawn of EOS.IO" 번역글 : @dev1by0 님이 번역해주신 글 입니다.(제목 : EOS.IO의 여명) 먼저 전체적인 내용은 이번에 EOS.IO 소프트웨어가 모든…
$30.22
70 11
STEEM 和 EOS 价格预测 - Steemit 商业智能
2 days ago by justyy 66 in cn

此文经原作者 @paulag 同意，翻译成中文。图片版权归原作者 @paulag 原文 地址 : 翻译难免有错误或者不够准确的地方，请见谅。 记得两周前，我就对…
$55.61
81 6
block.one - 중국법에 따른 변화에 대한 성명 (번역)
4 hours ago by dev1by0 49 in eos

2017년 9월 4일 ERC-20 스마트 컨트랙트 (이하 "EOS Smart Contract")에 따른 이더리움 블록체인 상의 EOS ERC-20 호환 토큰 (이하 "EOS Tokens")의 분배 개시에…
$16.14
14 8
Translation of EOS Statement on Chinese ICO Situation
2 hours ago by demotruk 65 in cn
在根据相关的ERC-20智能合同（“EOS智能合同”）分发EOS ERC-20兼容令牌之前，依据“EOS令牌”的规定，来自中华人民共和国（“中华人民共和国”）的主要法律事务所，合理确定：…
$15.27
67 4
스팀, EOS 개발동향 (EOS 테스트넷 스냅샷 포함)
5 days ago by clayop 71 in coinkorea

제멋대로 써보는 개발동향입니다. 소스는 주로 깃허브 눈팅입니다 ^^ STEEM 스팀은 뭔가 안정화를 시도하면서도 새로운걸 조금씩 보여주는 느낌입니다. 아마 조만간 큰 그림이 나오겠죠? SMT 라는…
$108.24
156 24
STEEM and EOS Price Predictions - Steemit Business Intelligence
2 days ago by paulag 58 in cryptocurrency

Do you remember two weeks ago I made a prediction on the price of both STEEM and EOS will be at the 31st Aug? Well…
$22.79
87 20
EOS/US Dollar (EOS/USD) Price Charts for Sep 4th 2017
5 hours ago by majes 67 in eos

The value of EOS for today is $0.94688569 . It has a current circulating supply of 325 Million coins and a total…
$6.78
62 5
🌐 Block.one расскажет о следующих шагах EOS на 3-ем саммите Global Blockchain, где Брендан Блюмер будет судьей Демо Дня
21 hours ago by blockchained 63 in eos

Генеральный директор block.one Брендан Блюмер и технический директор Даниэль Лаример намерены выступить на 3-ем…
$8.25
42 1
block.one to Introduce “EOS: Next Steps” at the 3rd Global Blockchain Summit with Brendan Blumer Being the Demo Day Judge
3 days ago by eosio 62 in eos

The following announcement was made today via 记者：铅笔盒 9月1日消息，block.one的CEO Brendan Blumer与CTO Daniel…
$21.56
80 12
The Answer: an animation
7 days ago by meesterboom 72 in life

I was thinking about a particular project today and hadn't heard much about it. I thought I would do a bit of digging…
$87.28
211 89
Dan Larimer Video Interview on EpiCenter recently!! This is a MUST WATCH /listen. An In-Depth look chat about his past, Crypto life, goals, etc. 73 mins.
4 days ago by barrydutton 72 in cryptocurrency

Dan Larimer by many accounts is a genius. He has helped create Steemit/STEEM, Bitshares and now the EOS project ---…
$21.27
114 10
Is it time to re-learn C++?
2 days ago by brandonh 49 in blog

So I've been in the tech industry since 2001, and for most of the time I spent interacting and developing for the…
$10.16
27 6
[뮤직홀릭]이제는 퀀텀(QTUM)을 유심히 봐야 할 때
3 days ago by musicholic 59 in kr

제가 투자한 플랫폼 토큰 중에 퀀텀(QTUM)이 있습니다. 지난주 코인원에 상장이 있었지만 대 실망의 모습으로 상장이 되었죠. 이 부분은 코인원이 일부러 그러지 않았을 까 하는 상상을 해보게 됩니다. 이제…
$16.02
73 32
What Is the Best Crypto Investment Right Now For The Long Term Play? (Offtopic)
5 days ago by carlosd15 58 in crytpo

Once on my previous posts I did mention that talking about cryptos is not my niche, I agree with it... but now I'm…
$23.20
73 19
Did you know you can trade on Bitshares built-in decentralized exchange with ~2x leverage?
6 days ago by eosfan 45 in bitshares

Hope you guys are familiar with Bitshares On the Bitshares DEX you have trustless assets like bitUSD, bitCNY…
$36.96
24 8
Back
••
The Dawn of EOS.IO
2 days ago
eosio62 in eos

In the EOS.IO Technical White Paper, we proposed the EOS.IO software as the dawn of a new era of blockchain computing. The EOS.IO development team has spent the summer working very hard. Summer is over and the development of the EOS.IO software is ahead of schedule. It can now be used with distributed network configurations. We have a lot of exciting EOS.IO software developments to report so be sure to read to the end!

Proof of Performance
Now that the EOS.IO software can be used in distributed network configurations we can benchmark its performance. Our internal testing shows that the software is currently able to sustain over 10,000 single threaded transactions per second on a multi-node network. This puts it on track to support over 1 million transactions per second on machines with over 100 CPU cores.

Advancements in Design
Developers will be excited to learn that our latest architectural software improvements make it easier than ever to build parallel applications that communicate with each other.

Shared Database Access
We have now enabled one application to read the database state of another application without requiring complex asynchronous communication. We achieve this while preserving the ability to execute in parallel by allowing each transaction to declare the scope (data range) that it needs to read or write access to. Block producers will schedule transactions so that there are no data conflicts.

User Local Storage of Application Data
In addition to supporting read access across accounts, applications can now store data on other accounts. This means a currency contract can store the balance on individual user accounts rather than within its own scope. A transfer from Alice to Bob only requires read/write access to the scope of Alice and Bob and won’t affect the currency contract’s scope. This makes many classes of applications trivially parallel and enables processing of currency transfers in excess of the single threaded throughput limit. As far as we are aware, no other blockchain design supports such a scalable and easy approach to developing parallel software architecture.

Inline Message Passing
It is now easier than ever to send a message to another application and know with certainty that it will be accepted and validated. An application can generate any number of additional messages to append to the end of the current transaction. So long as these generated messages share the same read/write scope and can execute within the allotted time, they are guaranteed to be delivered or the entire transaction will unwind.

This approach is different than the synchronous approach used by other platforms. Synchronous message delivery, which blocks execution of the current thread until it returns, creates the potential for unanticipated reentrancy. Reentrancy has been a source of numerous bugs and exploits because it is difficult for developers to ensure their contract is in a consistent state prior to making a synchronous call. With inline message passing, which delays execution until the end of the current transaction handler, developers can dispatch a message and proceed as if it succeeded. If it fails then the entire transaction will be unwound without any harmful side effects. This means your message handlers are never called in an inconsistent state.

Deferred Message Passing
Sometimes you don’t know if a message is valid or whether there is enough time left on the clock to execute inline with the current transaction. Other times you need to send a message that accesses data outside the scope of the current transaction. In this situation applications can request the block producers schedule a message to be delivered in the next cycle or a future block. If it is valid then your application may be notified; if it is not, then it will never be scheduled and your application can clean up after a timeout.

Unlimited Horizontal Scaling
The latest design advancements in the EOS.IO software gives developers high single-machine performance; businesses can scale to a million transactions per second before requiring a more complex asynchronous architecture.

That said, the EOS.IO software will still support asynchronous message passing among groups of applications that do not need to share state. There are many benefits to async message passing (such as trivial cluster support), but those benefits come with the cost of greater development complexity; the EOS.IO software supports this for businesses that require several millions of transactions per second, but offers a streamlined approach for those that don’t.

Next Generation Network Topology
The EOS.IO software is designed to empower block producers to provide a high performance decentralized infrastructure as a service. Application developers need more than a set of block producers aggregating transactions, they need API nodes, seed nodes, database indexes, storage, and hosting.

High performance blockchains demand high performance network architectures with very different requirements from existing blockchains. At a million transactions per second each node is required to achieve 100’s of megabytes per second per connection. This is trivial for large data centers, but inconceivable for home users.

Additionally high performance blockchains consist of heterogeneous nodes running different subsets of the blockchain and will likely prune the transaction history. This is a significant departure from prior blockchain systems where all nodes are identical and have a full history.

A traditional blockchain consists of a dynamic set of randomly connected nodes in a mesh network. They target home users with limited bandwidth and are designed to traverse home routers (NAT) and dynamically add nodes to the network. Our observation is that this architecture is not well suited for high performance blockchain infrastructure.

The EOS.IO software starts with the assumption that all nodes are intentionally connected to each other. Node operators work together to ensure the network topology is secure, well planned, and efficient. This allows block producers to establish direct (and secure) connections to each other and prevents attackers from scanning the entire network topology looking for nodes to shut down.

The block producers will host public endpoints which anyone may connect to and subscribe to any subset of transaction data they desire. This will minimize the bandwidth requirements for full nodes operated by non-block producers. Nodes that do not want to trust a single block producer may either subscribe to multiple sources or wait for confirmation by ⅔ of the block producers (about 45 seconds).

The benefit of this architecture is that new nodes can connect and synchronize at very high speeds from high bandwidth infrastructure provided by the block producers. Furthermore, this architecture is designed to facilitate efficient unidirectional streaming rather than less efficient bidirectional protocols.

At scale, block producers will be operating a new internet backbone powered by EOS.IO software. Block producers will be like Tier-1 Internet providers with dedicated fiber optic connections across continents. These producers will operate data centers that Tier-2 subscribers can connect to. Tier-2 includes anyone looking to run a full or partial node or a large application. For example, services like block explorers, web wallets, and crypto-currency exchanges would be Tier-2 subscribers to the block producers.

We feel this architecture of intentional cooperative network building will enable block producers to offer a quality of service unique in the cryptocurrency industry.

The Road Ahead
In September of this year, block.one will be releasing EOS.IO Dawn 1.0 which should be stable enough and well documented enough for anyone to launch their own test network upon which they can build and deploy their applications. EOS.IO Dawn 1.0 will be the first pre-release of our EOS.IO SDK (Software Development Kit).

Those who have followed our EOS.IO Roadmap will be happy to know that we are ahead of schedule. Phase 1, The Minimal Viable Testing Environment, which includes a standalone node, native contracts, virtual machine API, RPC interface, command line tools (eosc), and basic developer documentation is complete. We will be making a tagged release as “EOS.IO Dawn 1.0”. This phase was scheduled to be complete in Summer 2017 which ends on September 22.

We have already completed half of Phase 2, the Minimal Viable Test Network. This phase is scheduled for completion in Fall 2017 and includes working networking code, virtual machine sandboxing, resource usage and rate limiting, genesis importing, and inter blockchain communication. At this time we already have functional distributed networks and virtual machine sandboxing. We are confident that we will complete Phase 2 on schedule.

EOS.IO Dawn 2.0, the next major pre-release, will come by the end of the year. EOS.IO Dawn 2.0 will include several critical features that are not present in EOS.IO Dawn 1.0 including:

Resource Rate Limiting (preventing spam / abuse)
Merkle Tree Generation (for cross chain communication)
Upgrade Management and Governance
More robust SDK
General Infrastructure improvements
Example Snapshot from ERC20 tokens
The goal of EOS.IO Dawn 2.0 is to be functional enough that one could launch a live blockchain.

One More Thing….
EOS.IO Storage!
For the first time, developers will be able to create and deploy a decentralized application and web interfaces without having to worry about bandwidth and storage costs, or even hosting any servers themselves; this enables a host of new innovative decentralized business models, such as a decentralized YouTube, Soundcloud, or other storage-intensive projects.

In addition to computational bandwidth, native EOS.IO software-based blockchain token holders will now have access to free cloud storage, hosting, and download bandwidth via IPFS / HTTPS; this access can be used without consuming or transferring tokens.

To achieve this, block producers will host files via IPFS/HTTPS for users and allow other users to download those files. Storage resources are paid for through blockchain emissions and are rate limited to token holders pro-rata to their holdings; like the EOS.IO bandwidth model, storage does not expend EOS.IO software-based blockchain tokens and per-token storage capacity will increase over time with block producer hardware upgrades.

The EOS.IO software storage solution can also support public hosting for those who don’t have any tokens; more details will be released at upcoming blockchain industry events occurring in Shanghai and London.

Disclaimer
block.one is a software company and is producing the EOS.IO software as free, open source software. This software may enable those who deploy it to launch a blockchain or decentralized applications with the features described above. block.one will not be launching a public blockchain based on the EOS.IO software. It will be the sole responsibility of third parties and the community and those who wish to become block producers to implement the features and/or provide the services described above as they see fit. block.one does not guarantee that anyone will implement such features or provide such services or that the EOS.IO software will be adopted and deployed in any way.

All statements in this document, other than statements of historical facts, including any statements regarding block.one’s business strategy, plans, prospects, developments and objectives are forward looking statements. These statements are only predictions and reflect block.one’s current beliefs and expectations with respect to future events and are based on assumptions and are subject to risk, uncertainties and change at any time. We operate in a rapidly changing environment. New risks emerge from time to time. Given these risks and uncertainties, you are cautioned not to rely on these forward-looking statements. Actual results, performance or events may differ materially from those contained in the forward-looking statements. Some of the factors that could cause actual results, performance or events to differ materially from the forward-looking statements contained herein include, without limitation: market volatility; continued availability of capital, financing and personnel; product acceptance; the commercial success of any new products or technologies; competition; government regulation and laws; and general economic, market or business conditions. Any forward-looking statement made by block.one speaks only as of the date on which it is made and block.one is under no obligation to, and expressly disclaims any obligation to, update or alter its forward-looking statements, whether as a result of new information, subsequent events or otherwise.