关注公众号
随时掌握最新区块链知识

区块链入门、投资、套利增值的百科全书,从这里起飞!

站长QQ:61506546

EOS.IO Technical White Paper v2

ID:382 / 打印

Abstract: 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 many of CPU cores or clusters. The resulting technology is a blockchain architecture that may ultimately scale to millions of transactions per second, eliminates user fees, and allows for quick and easy deployment and maintenance of decentralized applications, in the context of a governed blockchain.

PLEASE NOTE: CRYPTOGRAPHIC TOKENS REFERRED TO IN THIS WHITE PAPER REFER TO CRYPTOGRAPHIC TOKENS ON A LAUNCHED BLOCKCHAIN THAT ADOPTS THE EOS.IO SOFTWARE. THEY DO NOT REFER TO THE ERC-20 COMPATIBLE TOKENS BEING DISTRIBUTED ON THE ETHEREUM BLOCKCHAIN IN CONNECTION WITH THE EOS TOKEN DISTRIBUTION.

Copyright © 2018 block.one

Without permission, anyone may use, reproduce or distribute any material in this white paper for non-commercial and educational use (i.e., other than for a fee or for commercial purposes) provided that the original source and the applicable copyright notice are cited.

DISCLAIMER: This EOS.IO Technical White Paper v2 is for information purposes only. block.one does not guarantee the accuracy of or the conclusions reached in this white paper, and this white paper is provided “as is”. block.one does not make and expressly disclaims all representations and warranties, express, implied, statutory or otherwise, whatsoever, including, but not limited to: (i) warranties of merchantability, fitness for a particular purpose, suitability, usage, title or noninfringement; (ii) that the contents of this white paper are free from error; and (iii) that such contents will not infringe third-party rights. block.one and its affiliates shall have no liability for damages of any kind arising out of the use, reference to, or reliance on this white paper or any of the content contained herein, even if advised of the possibility of such damages. In no event will block.one or its affiliates be liable to any person or entity for any damages, losses, liabilities, costs or expenses of any kind, whether direct or indirect, consequential, compensatory, incidental, actual, exemplary, punitive or special for the use of, reference to, or reliance on this white paper or any of the content contained herein, including, without limitation, any loss of business, revenues, profits, data, use, goodwill or other intangible losses.

  • Background

  • Requirements for Blockchain Applications

    • Support Millions of Users

    • Free Usage

    • Easy Upgrades and Bug Recovery

    • Low Latency

    • Sequential Performance

    • Parallel Performance

  • Consensus Algorithm (BFT-DPOS)

    • Transaction Confirmation

    • Transaction as Proof of Stake (TaPoS)

  • Accounts

    • Named Permission Levels

    • Permission Mapping

    • Evaluating Permissions

    • Default Permission Groups

    • Parallel Evaluation of Permissions

    • Actions & Handlers

    • Role Based Permission Management

    • Actions with Mandatory Delay

    • Recovery from Stolen Keys

  • Deterministic Parallel Execution of Applications

    • Minimizing Communication Latency

    • Read-Only Action Handlers

    • Atomic Transactions with Multiple Accounts

    • Partial Evaluation of Blockchain State

    • Subjective Best Effort Scheduling

    • Deferred Transactions

    • Context Free Actions

  • Token Model and Resource Usage

    • Objective and Subjective Measurements

    • Receiver Pays

    • Delegating Capacity

    • Separating Transaction costs from Token Value

    • State Storage Costs

    • Block Rewards

    • Worker Proposal System

  • Governance

    • Emergency Changes

    • Freezing Accounts

    • Changing Account Code

    • Constitution

    • Upgrading the Protocol & Constitution

  • Scripts & Virtual Machines

    • Schema Defined Actions

    • Schema Defined Database

    • Generic Multi Index Database API

    • Separating Authentication from Application

  • Inter Blockchain Communication

    • Merkle Proofs for Light Client Validation (LCV)

    • Latency of Interchain Communication

    • Proof of Completeness

    • Segregated Witness

  • Conclusion

EOS Technical White Paper v2.docx

EOS Technical White Paper v2.pdf


cache
Processed in 0.003978 Second.