Orbs 백서

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

ple of atomic swap mechanism: ​https://en.bitcoin.it/wiki/Atomic_cross-chain_trading 19 The Orbs Platform Overview The Orbs platform is a decentralized, open and transparent network providing public blockchain Infrastructure as a Service (IaaS) for large-scale consumer apps. As the trend for decentralized businesses continues to rise, we expect more and more established consumer brands to take advantage of the new opportunities decentralization presents and start making the transition to blockchain. Orbs provides the cloud infrastructure to run these decentralized applications and facilitate this transition. The three primary infrastructure offerings of the Orbs platform include consensus-based decentralized compute services, consensus-based decentralized storage services and Consensus as a Service (CaaS). Decentralized-Consensus Compute Compute services enable developers of decentralized applications to run their apps over the network and execute their code on the various nodes. Applications are executed in a fully decentralized and secure way over multiple independent nodes. The results of execution undergo consensus to make sure a single coherent outcome emerges. Compute services are similar in spirit to centralized IaaS services like AWS EC2 or even AWS Lambda , but use 23 24 blockchain technologies. In the blockchain world, compute services are similar in principle to the execution of ​smart contracts​ over Ethereum. Decentralized-Consensus Storage Storage services enable developers of decentralized applications to store data over the network. Data is replicated and sharded between multiple independent nodes and stored 25 securely in a fully decentralized manner. Storage forces data to be in consensus, making sure 23 ​https://aws.amazon.com/ec2/ 24 ​https://aws.amazon.com/lambda/ 25 ​https://en.wikipedia.org/wiki/Shard_(database_architecture) 20 THE O RBS PLATFOR M there are no inconsistencies between nodes. Storage services are similar in spirit to centralized IaaS services like AWS S3 or even AWS DynamoDB . From a blockchain 26 27 perspective, storage services are similar in principle to storing data on the blockchain itself in Ethereum, or on IPFS . 28 Consensus as a Service Since the Orbs platform is completely decentralized and comprised of independent nodes owned or operated by different organizations, the ability to reach consensus between these nodes is a core underlying capability of the network. The consensus layer of Orbs is architected to be modular and allow additional infrastructure layers, such as compute and storage to be built on top of it. It also allows its users to reach consensus independently of the other services. For example, one might use CaaS to notarize documents, or inputs from decentralized oracles. Using Orbs’ inherent cross-chain connectors, CaaS can even be used to notarize states in other blockchain platforms, or execute atomic swaps between platforms. Design Principles Orbs is designed in a requirements-driven approach. By working with design partners that are currently operating mass-market applications serving hundreds of millions of users, we’ve been able to distill the following four areas as our focal points: Service Level Agreement (SLA) SLA is a commitment between the service provider and a service user. Particular aspects of the service - like minimum quality, availability, responsiveness - are agreed upon in advance with detailed mechanisms to guarantee the SLA in practice or compensate the user if the SLA is not met. SLAs are an industry standard in the traditional consumer infrastructure space and are widely used by centralized IaaS platforms like AWS . In Orbs, SLAs are much more than 29 these traditional written agreements between parties, since they are implemented as a direct part of the protocol and are ​ integral to the network design​ . SLAs are important for consumer apps in order to increase the predictability of the service level. Consumer expectations are high and even small disruptions in the availability of an app causes users to leave. A blockchain platform will bring little value to its applications if it fails to perform when congested, even if it provides magnificent performance and ultra-low fees. 26 ​ https://aws.amazon.com/s3/ 27 ​ https://aws.amazon.com/dynamodb/ 28 ​ https://github.com/ipfs/ipfs/blob/master/papers/ipfs-cap2pfs/ipfs-p2p-file-system.pdf 29 ​ https://cloudiqtech.com/aws-sla-summary/ 21 Consumer Scale Consumer apps serving millions of end users normally have aggressive scaling demands, particularly for message throughput, message latency, and the number of supported users. As a reference, Lyft handles over a million rides per day . If handled over blockchain technology, 30 each of these rides should consist of several transactions: ordering the ride, driver taking the ride, payment, review, etc. Each of these transactions needs to be processed almost immediately to accommodate an efficient transaction between the rider and the driver. Using blockchain terminology, message throughput and latency translate to transaction throughput and confirmation time. Business-grade scale does not only apply to raw network properties like throughput and latency. Scale influences almost every aspect of platform design. Consider the scalability of the fee model for example. Infrastructure fees with a fixed cost-per-transaction that only scale linearly (with the number of transactions) provide a poor framework for apps to grow, especially for mass usage patterns like microtransactions. Consumer Protection and Regulation There is a common misconception, that decentralized networks are unregulatable. In practice, regulation may lag behind fast-paced technological innovation, but its users are ultimately subject to the ruling of regulators and seek its protection when in need. Consumer apps are normally developed by well-defined organizations or companies with clear legal identities, even if they are decentralized. They are subject to regulation, both by governments and by industry bodies (e.g. app stores), and must operate within legal and contractual limits. For established consumer brands, that have much to lose if found noncompliant, regulatory uncertainty is a risk rather than an opportunity. Our experience with design partners shows that compliance often becomes the critical path of the roadmap. Technical and infrastructure choices may impact the requirement for government licenses and compliance to app store rules. Modern Deployment Paradigms Painful lessons in history, such as Bitcoin SegWit2X , have shown how governance plays a 31 critical role in the practical success of a decentralized system and its ability to keep improving over time. We consider governance and the orderly process for the continuous evolution of the protocol a first-class citizen in the design of Orbs. Incentives for evergreen nodes are constructed into the very base of the ORBS token economy. 30 ​https://blog.lyft.com/posts/one-million-rides-a-day 31 ​https://www.coindesk.com/2x-called-off-bitcoin-hard-fork-suspended-lack-consensus/ 22 The challenge of smart contract immutability has also become important with ordeals such as the aftermath of the Parity multisig bug on Ethereum . Smart contracts could use some local 32 governance, to be able to adapt to extreme situations without requiring intervention of the governing bodies (or the governing DAOs). Furthermore, our experience with real-world production at scale also shows that it is impractical for a production system to deploy major changes to the network as forks, going from 0% to 100% at the flick of a switch. Modern deployment strategies require the ability to deploy changes gradually (5% to 20%, then to 50%, etc.) with constant monitoring and the ability to rollback. The system must also be allowed to deploy multiple orthogonal changes side by side as independent experiments or else development will have to be serial and slow down significantly. 32 ​https://blog.comae.io/the-280m-ethereums-bug-f28e5de43513 23 Network Entities Orbs is a blockchain infrastructure for large-scale consumer apps. As such, we can categorize several distinct types of entities participating in the network: Consumers These are the end users in the network who use the apps that are running on top of it. They would make up the vast majority of wallet holders for currency-based products. In general, we can assume they number in the hundreds of millions. Consumers will likely gain access to the network by using a mobile app or a website. Consumers do not have direct access to the Orbs network and do not operate nodes like in alternative blockchain implementations such as Bitcoin. Consumers’ access to the Orbs network is always provided through an ​ app​ . Usage profiles on mobile apps and websites are characterized by extremely low availability of resources - low computational ability, low memory and low persistent disk storage. Network connectivity is extremely intermittent without any guarantee of how often consumers are online and for how long. Consumer apps in general are also suffering from high churn - meaning users are prone to abandon the app. The number of active users is usually significantly lower than the number of registered users (this number is often as low as 5%). From a regulatory perspective, most of the effort made by regulators is aimed at the protection of consumer interests. 24 Apps These are the products running on top of the blockchain infrastructure, performing transactions for the benefit of consumers. We can assume a low number of popular apps in the network, in the area of several hundreds. This is mostly because apps are extremely competitive and consumer attention is very difficult to attain. The average mobile consumer does not use more than a dozen mobile apps, although millions of apps exist in app stores. The Orbs platform is naturally optimizing for the most high-volume, popular apps. Consumer-brand apps are normally developed by well-defined organizations or companies with clear legal identities. They are prone to regulation and must operate within legal limits. The majority of consumer brands targeted by the Orbs project are well established and have existed as centralized entities prior to the blockchain era. They currently rely on centralized channels to reach consumers: Mobile apps in the app stores, as well as websites with branded domains are fully centralized. Resources should be plentiful for such apps. Outside of the blockchain world, consumers are known to have high expectations of network scale and responsiveness. We can assume nodes operated by apps will have higher computational ability, more abundant memory and persistent disk space. Network connectivity can also be assumed to be steady and performant. Consensus Nodes These are the servers that participate in the consensus process and provide the actual compute and storage resources to execute the decentralized apps on top of the blockchain infrastructure. Nodes are owned and operated by various companies and organizations. Each of the organizations may operate multiple nodes. Nodes participate in the network by following the protocol, for example by running the Orbs software stack - a freely distributed open source reference implementation introduced by the 33 Orbs project and maintained by the open source community. The collection of nodes in the network does not have any centralized point of governance and is not owned or controlled by the Orbs project. The number of nodes in the network could be in the same order of magnitude as the number of apps. In fact, app developers are encouraged to operate nodes in the network and a large similarity between the two groups can be expected. If we account for node redundancy (a single organization spawning several nodes for robustness) and ecosystem apps like Kin (where an ecosystem of organizations operate an app together), we can expect the number of nodes to be one or two orders of magnitude larger. 33 ​ https://github.com/orbs-network 25 Audit Nodes These are also servers in the network whose primary purpose is adding another layer of security by public audit of the blockchain. Audit nodes do not take an active part in the consensus process itself and do not have the capability to write data to storage or close blocks. As such, unreliable behavior by audit nodes, such as intermittent network connection or downtime, does not have a direct negative effect on the overall performance of the network. Audit nodes also participate in the network by running the same software stack as consensus nodes. In fact, consensus nodes perform a similar audit process among themselves in parallel to their additional responsibilities. Like consensus nodes, they do not have any centralized point of governance and the collection of audit nodes is not owned or controlled by the Orbs project. The Orbs platform is designed to be public and open for inspection. Any entity and individual is encouraged to operate audit nodes to help contribute to the network general security. Node operation is also incentivized by the token economic model. We can accommodate a large number of audit nodes in the network which doesn’t necessarily correlate to the number of consensus nodes. 26 The Orbs Ecosystem Core Infrastructure The nodes of the network running the Orbs protocol software stack provide the core competence of the Orbs platform as an infrastructure layer for the developers of consumer-oriented decentralized apps. The core offering includes consensus-based compute, consensus-based storage services and CaaS. The reliance upon Turing-complete languages 34 as the basis for applications to build upon has been proven as vital by projects like Ethereum. We consider it unwise for an infrastructure layer to limit the abilities of the applications it carries, as they are the main driver of innovation in the field and their exact requirements cannot be fully anticipated in advance. Specialized Infrastructure The core competence of the platform only holds the most basic of the building blocks for decentralized apps. These blocks are the most flexible, but experience shows that complex applications require specialized infrastructure as well, that is often built by third parties. Decentralized analytics is a concrete example of specialized infrastructure in the Kin use case. Most of the partners in the Kin ecosystem would need a data and business intelligence layer (BI) but don’t have the resources to develop or maintain their own solution. Reliance on a centralized BI solution offered by an established software vendor, such as Sisense or 35 Tableau , would be problematic: partners should base their most strategic decision-making 36 on this data, but they cannot trust that the data was not manipulated by whoever controls the centralized account. A decentralized solution is a better alternative, but currently Kin would have to develop it from scratch. The best option in this case is for an established BI software vendor to develop a decentralized version of its analytics platform, given that it already 34 ​https://en.wikipedia.org/wiki/Turing_completeness 35 ​https://www.sisense.com/ 36 ​https://www.tableau.com/ 27 THE O RBS ECOS YSTEM possesses the domain expertise. The vendor can interface with the Orbs platform to provide the infrastructure to Kin developers via APIs directly accessible from Orbs smart contracts. Of course, use-cases for specialized infrastructure are not limited to BI and can also include tools and integration points such as back-office software, oracles, integration ERP/CRM platforms, other types of storage and databases that go beyond a naive key-value store, and much more. Infrastructure Marketplace Orbs will encourage the formation of an open infrastructure ecosystem of specialized third party solutions, whose participants will provide a ​ one stop shop for decentralized application developers. Such a platform will promote decentralized technologies in general and empower specialized complementary infrastructure providers. This ecosystem will establish an economy for services based on the ORBS token where third parties can receive payment using the token for infrastructure solutions they have created. The benefit for decentralized application developers is clear - a single integration channel and a common language for all of their decentralized technology needs. This model has been proven to be successful on centralized infrastructure platforms such as AWS Marketplace , 37 where third parties are upselling specialized services to AWS customers. Complementary Infrastructure Orbs can also serve as a complementary, augmenting infrastructure layer on top of other blockchain protocols like Ethereum. While Ethereum settles into a position as the industry standard for token protocols and ICOs, the network struggles with scale. Orbs utilizes blockchain virtualization to optimize traffic for decentralized apps, a form of intelligent sharding that is more efficient (as a first level of sharding) than other sharding methods. By migrating to Orbs, users of existing projects can elect to anchor their ERC-20 tokens in reserve on Ethereum while using 1:1 atomic swaps to launch avatar tokens on Orbs. Their original tokens remain in ERC-20 format, backing the tokens running over the more scale-friendly network created by Orbs. 37 ​ https://aws.amazon.com/mp/ 28 The ORBS Token Overview As the native token for the network, the Orbs platform relies on the ORBS token to fuel network operation and provide the means to pay the fees involved with operation of the consensus layer, execution of smart contracts and consensus-based storage - as these are the three primary services provided by the platform. The fee model serves as incentive for nodes to allocate the necessary resources for operating nodes and ensures an SLA consistent with consumer expectations in term of predictable and stable service, availability, performance and degree of security. In other words, nodes are paid for their services to consumer applications that utilize them. The ORBS token is not only the driver for the Orbs core infrastructure, but for the entire ecosystem built around the Orbs platform. It fuels an ​infrastructure marketplace and serves as the means of payment for third party infrastructure providers which choose to upsell specialized decentralized infrastructure solutions on top of the platform. The billing models for third party decentralized infrastructure solutions must evolve side by side with the infrastructure itself. They also must adapt to the new token economy and rely upon the new dimensions of billing flexibility and the programmability it provides. Billing Subsystem The Orbs platform makes a clear distinction between ​billing and ​accounting​. Drawing inspiration from centralized infrastructure counterparts such as AWS, where billing uses local fiat currencies in monthly intervals and accounting is tabulated separately per use and on demand with domain-specific metrics (CPU minute for compute or GB for storage and bandwidth). Current-generation blockchain platforms, like Ethereum, do not make this distinction and pair between transactions and their fee payments by requiring that the fee itself be explicitly attached to every transaction. The Orbs billing subsystem is based on the ORBS token and provides the flexibility to be performed in monthly intervals as well. Accounting on the Orbs platform is performed separately per transaction and on demand with domain-specific metrics (transaction throughput or storage used on chain). This separation adds a degree of flexibility compared to
프로젝트로 돌아가기