Hedera 백서

Hedera

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 6쪽 중 3쪽

timate fork would not be able to provide a valid state proof. And there is little incentive for nodes to openly create a forked copy, because there is unlikely to be much demand from users to shift to using an invalid version. So there are strong incentives to avoid forks, even aside from any legal incentives. The cryptographic proofs and unique identifiers that prevent forks are also critically important for secure sharding. They allow shards to send each other messages, with assurance that the message from a given shard was truly the consensus of that shard. 25STABILIT Y Legal Controls and Transparency The Hedera codebase will be governed by the Hedera Governing Council. Version 1.0 of the codebase, which is expected in 2020, will be “open review,” meaning that anyone will be able to read the source code, recompile it, and verify that it is correct. No license will be required to use the Hedera platform. No license will be required to write software that uses the services of the Hedera platform. No license will be required to build smart contracts on top of the Hedera platform. Applications built upon the Hedera platform can be open source or proprietary. They do not require any license or any approval from Hedera. Software developed using the platform APIs will not be encumbered in any way. Software developers will have complete ownership and discretion on the licensing they choose for their applications that use the Hedera platform. Swirlds owns the intellectual property rights in the hashgraph consensus algorithm. The Hedera Governing Council has a license from Swirlds to use the hashgraph consensus algorithm and associated technology for the Hedera distributed public ledger platform. In exchange for that license, the Hedera Governing Council will pay Swirlds 10% of network revenue (with monthly minimums) and Swirlds will own 5% of Hedera coins. Swirlds will continue to require licenses for use of the hashgraph technology in private, permissioned networks, but no license will be required for distributed applications that run on Hedera’s public platform. Hedera and Swirlds will use the patent rights associated with the hashgraph algorithm defensively to legally prohibit the forking of the codebase and the creation of a competing platform and currency. Developers are free to build distributed applications on top of the Hedera platform with associated native tokens. In summary, Hedera will simultaneously embrace open review of the software code, while bringing stability to the platform and cryptocurrency by controlling the license. In this way, Hedera will provide a transparent codebase, assuring the stability that markets demand for mainstream adoption. 26REGULATORY COMPLIANCE Regulatory Compliance We expect that governments will continue to extend policy objectives to users, enterprises, and developers utilizing public ledgers and associated cryptocurrencies and tokens. We consider it a fundamental goal that the Hedera network can provide necessary tools for all members of its ecosystem to comply with applicable laws and regulations, including existing regimes such as the European Union’s General Data Privacy Regulations (GDPR) and anti-money laundering (AML) obligations. We will continue to work with regulators to enable compliance with new and changing laws and regulations as well. The sections below outline some of the key elements of the Hedera network that allow for a path to regulatory compliance. SELF-CUSTODY Just like with most other distributed ledgers, all transactions that affect the state of a Hedera account must be signed by the account’s private key. This enables end users who retain possession of their private key to have sole control over their accounts and never relinquish custody of any funds to Hedera, developers, or enterprises. Even cryptocurrency transactions are completely peer-to-peer without intermediaries taking possession of hbars. Developers can either design and build wallets and applications on the Hedera network that utilize self-custody of private keys and funds or choose to host the private keys of their users and comply with the regulatory obligations arising from such custodial relationship. DATA SELF-SOVREIGNITY Unlike most other distributed ledgers, the Hedera network implements controlled mutability. When data is published on the Hedera network the publisher can define an authorization policy for future deletion and/or modification by specifying which keys have those authorizations. This allows developers to build applications that can comply with the “right to erasure” requirement under the GDPR or allow its users to maintain full control of which data is public and for how long. PRIVACY MANAGEMENT The Hedera network also allows users to manage their own identities and transaction requirements. By default, accounts are pseudonymous, like most other distributed ledgers. However, the Hedera technology framework can support future implementations that allow users to attach their real identity (as asserted by an accredited party acting as a Certificate Authority) to be logically bound to their ledger account so that, when using that account to move funds, appropriate KYC checks can be performed A counterparty could choose to require full proof of identity (including full legal name) or specific identity characteristics (such as age) consistent with their compliance program in order to accept a transaction on the network. User remain in control of their personal information and whether to provide proof of identity or characteristics to a counterparty; the counterparty remains in control of meeting compliance obligations before engaging in a transaction. The system is opt-in, in that a user must explicitly choose to avail themselves of the mechanism and, if they do not, their account transactions will remain pseudonymous. This choice, however, may prevent them from engaging in certain financial transactions. SECTION 27 The system is designed to provide the appropriate balance of: 1. Government visibility 2. Security 3. User privacy Comparable to showing a driver’s license when creating a new bank account, the model has a user attach a hash of a digital certificate created by a recognized identity provider to their account. This attachment will take the form of a transaction sent out to the network. This transaction: 1. May need to be signed by both the user’s private key and that of the identity provider 2. Can stipulate what parties are authorized to subsequently detach the hash (and so revoke the binding between the identity and the account). As long as the attachment between account and certificate has not been revoked, by either the user or the identity provider, it can be used to establish that the account is bound to a known user whenever funds move in or out of that account. If and when appropriate, the identity provider can revoke the binding simply by sending a signed transaction to the network. As an example of how it might work, consider a user trying to send money from their Hedera account to a US bank. The user would provide to the bank the certificate as well as their account address. The bank would look up the account and confirm that the account had the corresponding hash for the certificate, and that the certificate was issued by a trusted identity provider. Only if all these checks were confirmed would the bank authorize the transaction and accept the funds. The bank might be asked by the corresponding government to send the certificate and transaction details, either in real-time (perhaps based on the amount of the transfer) or on a schedule. ANTI-MONEY LAUNDERING Some developers and enterprises utilizing the Hedera network may have anti-money laundering reporting obligations. For such entities, on-network identity certificates and the use of network data from mirror nodes could form the basis of a compliance program. Mirror nodes, as discussed in more depth below, will eventually be able to run by anyone and serve as “read-only” observers of network activity. With such mirror nodes, all public data on the network can be viewed, stored, and analyzed to conduct investigations and flag suspicious behavior. Hedera is a founding member of the Distributed Ledger Foundation and will work with the broader DLT community and governments to ensure that regulatory requirements can be satisfied, while maintaining privacy and security. Hedera directly resolves the five fundamental obstacles to mainstream market adoption of public ledger technology: Performance, Security, Stability, Governance, and Regulatory Compliance. The hashgraph data structure and consensus algorithm provide a best-in-class, unmatched combination of performance and security. The Hedera platform and Hedera Governing Council will provide transparency, open innovation, platform stability, tools to enable opt-in KYC and AML, and global, cross-industry expertise to provide governance and decision making for a globally distributed network and cryptocurrency. 28 Part 2 Architecture ARCHITECTURE DECENTRALIZED APPLICATION HEDERA HASHGRAPH NETWORK INTE RNET WALLET CRYPTOCURRE NCY SMART CONTRAC TS CONSENSUS SERVICE FILE SERVICE 29ARCHITECTURE 30 INTERNET LAYER The Hedera network nodes are all computers on the internet, communicating by TCP/IP connections protected by TLS encryption with ephemeral keys for perfect forward secrecy. Nodes are addressed by IP address and port, rather than by symbolic names, so attacks on the DNS system will not affect the network. HASHGRAPH CONSENSUS LAYER The nodes take transactions from clients and share them throughout the network with a gossip protocol. Then all nodes run the hashgraph consensus algorithm to reach agreement on a consensus timestamp for each transaction and its consensus order in history. Each node then applies the effects of the transactions in consensus order to modify its copy of the shared state. In this way, all nodes maintain an identical consensus state (within any given shard). SERVICES LAYER CRYPTOCURRENCY The cryptocurrency is designed to be fast, which leads to low network fees, making very small microtransactions practical. When the Hedera platform is running at scale, any user will be able to run a node in the network and earn cryptocurrency payments for doing so. Any user will be able to create an account by simply creating a key pair, without any name or address attached to it. Optionally, provisions are made to allow a user to attach hashes of identity certificates. These could come from any third-party certificate authority or identity authority that the user chooses. This is intended to allow regulatory compliance, for cryptocurrency accounts that will be used in a jurisdiction with Know Your Customer (KYC) or Anti-Money Laundering (AML) laws. More detail is given in the Regulatory Compliance section. FILE STORAGE The file system allows users to store information, with consensus on exactly what is stored and what is not stored. Every node in the shard stores the same files, so they will not be lost if one of the nodes crashes. Stored information can only be deleted by those that were given permission. In this way, the file system can act as a revocation service. For example, in the future, a user might be issued a driver’s license from the Department of Motor Vehicles (DMV), and both the user and the DMV digitally sign the transaction that puts a hash of it into the ledger. Both have the right to remove the hash of the license. The user can choose to prove to someone that they have a valid license, by giving that person a copy of the license file, so the person can check whether the hash is still stored in the ledger. If the DMV revokes the license, it would also delete the hash, to show the world that the license is no longer valid. If the user tries to store the hash again, without a signature from the DMV, it will be evident that the hash was stored only by the user without DMV cooperation, and would not be considered valid evidence of the user’s right to drive. ARCHITECTURE 31ARCHITECTURE Files are actually stored as Merkle trees, but we provide Java classes to allow developers to manipulate them. We give developers Java code to manipulate a Merkle tree as if it were a file system. They see directories, subdirectories and files. And they change file contents and directory names, move things around, and copy and paste. Yet, underneath, it’s all being stored as a Merkle tree automatically. This allows us to give proofs that a file is part of the consensus state. Users also can store an entire directory in the Hedera file system. We not only store Merkle trees, we store Merkle DAGs, which means that if two files have some bytes in common, we might only store one copy of the common bytes. A file can be accessed by its hash, so people can rely on the fact that it is immutable. But it also has a File ID. Its owner can create a new file, and make the File ID to be associated with the new file instead of the old one. In this way, it is possible for users to always find the latest version of a file. They just access the File ID instead of the hash. So files are both securely immutable and securely non-immutable, at the same time. If a file is accessed by its hash, then it never changes. If it is accessed by its File ID, then the latest version is found. SMART CONTRACTS The Hedera ledger can run smart contracts written in Solidity. Currently, large libraries of Solidity smart contract code exist, and they can be run unchanged on Hedera. These allow for distributed applications to be easily built on top of Hedera. CONSENSUS The Hedera Consensus Service will offer an efficient alternative to smart contracts and the file system for building distributed applications. Clients submit messages to Hedera for time-stamping and ordering within specific topics. These ordered messages will flow out to mirror nodes or clients of mirror nodes for processing in the consensus order. The consensus service will give distributed applications direct access to the native speed, security, and fair ordering guarantees of the hashgraph consensus algorithm, with the full trust of the Hedera ledger. Full details on the Hedera platform’s consensus service, which will not be available initially but added in a subsequent phase of the platform’s development, are available in Appendix 2. 32ARCHITECTURE Mirror network The Hedera mirror network is a set of nodes that will maintain all of the same requirements and most of the functionality of the main Hedera network The primary difference in functionality is that mirror nodes do not have the ability to submit transactions to be incorporated into the network’s ledger. Mirror nodes will gossip, and will calculate consensus and verify signatures, but because they are unable to create events, mirror nodes have no effect on the hashgraph structure. Therefore they have no ability to submit transactions for consensus and no voting power. Mirror nodes can be thought of as “read-only” nodes in that transactions cannot be submitted to a mirror node via the Hedera API. Mirror nodes are free to develop additional APIs for providing new kinds of services that they create. The mirror network will provide an efficient way to get the state of the ledger out to many more users and dApps in a short period of time without having a major impact on the performance of the main network. As a result, dApps may choose to host their own mirror nodes to listen to transactions on the main network and respond accordingly. For example, a dApp that deploys a smart contract may choose to host a mirror node, listen for events from its smart contract, filter out other transactions, and respond accordingly. 33ARCHITECTURE Sharding Initially, the Hedera network will be a small number of nodes operated by Governing Council Members, all in a single shard. As the Hedera Governing Council grows and others begin to operate nodes, the network will gain a sufficient number of nodes to justify multiple shards. Sharding can offer performance advantages as every node need not process every transaction. Consensus can consequently proceed in parallel. Shards will trust each other, so one shard will honor requests to move cryptocurrency or to put a hold on various resources made by another shard - as long as those requests can be proven to reflect the consensus of the requesting shard. This will allow the multi-shard ledger as a whole to achieve asynchronous Byzantine fault tolerance, and to prevent double spends or other conflicting states of the ledger, because each individual shard will have those properties, and because all messages between them will contain proofs that they are the consensus of that shard. The plan is that nodes will be randomly grouped into different shards, within which consensus on transactions will be established as normal. Each shard will be made up of a subset of the nodes, all of which share the same state, which will be a subset of the state of the entire ledger. Transactions will be placed into consensus order within individual shards in the normal manner — all nodes within a shard will contribute only to the consensus for transactions that originate in that shard. The assignment of nodes to shards will be performed randomly by a master shard, which will assign new nodes to a shard once a day, and also will move nodes between shards as necessary to ensure that each shard has a large total amount of hbars being staked, and that no one node within a shard will have a large fraction of that total amount. Shards will communicate through the exchange of messages between nodes of the different shards. All such messages are push (rather than pull). Each shard (its nodes) will maintain a queue of outgoing messages to each of the other shards. Each shard will remember the sequence number of the last message it processed from each of the other shards. A message will be sent for transfer from shard Alpha to shard Beta by nodes in Alpha randomly contacting nodes in Beta, along with a proof that it is part of the consensus state of the Alpha shard. They will continue doing this until one of the Beta nodes replies with a proof that the Beta shard shared state includes a sequence number indicating that this message was received and processed. In this manner, transactions that impact addresses in different shards will be appropriately recorded into each shard’s state, and so into the entire state of the entire ledger. More details are given in the Sharding appendix. 34 Part 3 Cryptoeconomics CRYPTOECONOMICS 35CRYPTOECONOMICS Staking and proxy staking The Hedera ledger uses a proof-of-stake consensus mechanism, in which each node’s influence on consensus is proportional to the amount of cryptocurrency it has staked to it. A transaction is validated and placed into consensus after it is validated by nodes representing an aggregate stake of over two- thirds of the network’s total number of hbars (the number of hbars is fixed at 50 billion). It is important to ensure that most of the cryptocurrency is actually being staked, so that the network continues to run. In the initial phase of the network, the Hedera Treasury will “proxy-stake” over two-thirds of the total number of hbars to nodes hosted by Council Members. After hbars become more widely distributed (so that no single user or group of users can attain control of one-third of all hbars), the network will allow anyone to host a node (i.e., it will be a permissionless network). At that time, when a node joins the network, it must declare one or more accounts that it can control, and prove that it has the private keys for those accounts. From then on, the amount of hbars in those accounts will be used to weight its votes in the hashgr
프로젝트로 돌아가기