EOS EOSIO DApp 개발 – '에브리피디아 백서 읽기' 시리즈 9.EOS.IO Implementation

smarteasy (43)in #eos • 8 years ago (edited)

에브리피디아에 대한 것보다 EOS.IO에 대한 것이 주를 이룹니다. 그래서 그런 것인지는 모르겠지만 글 배치와 전개가 좀 불안합니다.
불필요한 내용들은 과감히 생략하고 추가적인 설명이 필요해 보이는 부분은 관련 주제를 다루는 글을 링크로 달았습니다.

EOS.IO Implementation

EOS.IO software is a Turing-complete distributed computing platform and smart contract system in which block producers allocate bandwidth & storage for large scale decentralized applications proportional to the user/developer EOS token balance.

EOS.IO는 자신을 분산앱을 실행하기 위한 운영체제라고 표방하고 있지.

This allows for feeless transactions since accounts are only rate-limited based on their EOS token balance. The more EOS tokens an account holds, the more of their transactions an account can expect to be included in the ledger. This gasless protocol (compared to Ethereum) allows for the building of rich decentralized consumer applications.

또한 예치(staking) 방식을 사용하기 때문에 이더리움의 가스와 같은 직접적인 거래 비용도 없어.

Additionally, the EOS protocol has a special process in which the community votes to allocate EOS tokens to up to 3 “community benefit applications” that directly benefit the EOS network. An implementation of the Everipedia Network on EOS.IO software will plan to provide maximal community value and innovation to be successfully considered for one of these three coveted spots.

EOS에는 WPS(Worker Proposal System)이란게 있어. EOS 커뮤니티 가치를 높이는 DApp을 투표로 선정해서 보상해주는 거야. 에브리피디아는 아마도 선정될 확률이 높을거야.
WPS에 대한 것은 다음 링크를 참조하도록. https://steemkr.com/eos/@eddieyi/4-eos-worker-proposal

EOS.IO schematic: Block producers of the network provide bandwidth, IPFS storage, query services, servers, and gateway interfaces. They are incentivized to do this through newly minted EOS tokens, similar to how Bitcoin miners are incentivized to provide SHA256 hashing services to the network through Bitcoin block rewards. Users (clients) then connect to services made available by block producers similar to using classical internet services. Since there are multiple block producers, there is a distributed entry point to all software on the EOS.io network unlike classical centralized web applications. img-source: EOS.IO retrieved from: steemit.com

EOS.IO는 개발자들이 DApp 개발에만 신경쓰게 하고 싶어 해. 즉 운영의 부담을 없애주고자 한다는 거지. 쉽게 말해서 탈중앙화된 분산형 클라우드 서비스를 제공해 주겠다는 거지.
EOS 토큰을 예치하기만 하면 되는데 아마도 그 비용은 직접적으로 서버를 운영하거나 클라우드 서비스를 사용하는 것에 비하면 매우 낮은 비용이 될 거야.
EOS.IO는 위의 그림 처럼 이를 지원하기 위한 구성요소들을 가지고 있지. 이에 대한 자세한 설명은 다음 링크를 참조하도록. https://steemkr.com/eosiokorea/@eos.io-korea/4whjiu-eos-io

Everipedia Network articles (as well as their histories) will be stored using IPFS protocol nodes incentivized through EOS block producer rewards. This means that EOS block producers would provide IPFS retrieval of articles to users free of charge but rate limited by the balance of EOS tokens held by the Everipedia Network EOS account.

에브리피디아 네트워크 글들은 IPFS 프로토콜을 사용해서 블록 생성자 노드에 저장될거야. 파일 저장소도 예치 방식을 사용해. 이게 어떤 의미인지는 알지?

Since EOS block producers are independent node operators on the EOS network, any block producer can retrieve Everipedia articles to a requesting user. In this sense, it would not be possible for states or other organizations to easily block access to Everipedia articles as they can do with Wikipedia by blocking access to a centralized server or a DNS recordset (ie: the domain name Wikipedia.org). In order to block access to Everipedia Network content, actors would have to prevent any TCP/IP interaction and packet exchange between end users and the EOS mainnet entirely as even a single EOS block producer can provide access to Everipedia content. This task, while theoretically feasible, is substantially more difficult than blocking a single domain and is more akin to attempting to shut down torrent networks by going after all individual torrent seeders - a task that has consistently proven impossible for many well-funded organizations and state actors.

탈중앙화된 분산화된 환경에서 주나 다른 기관이 글에 대한 접근을 막는 것과 같은 통제는 이론적으로는 가능하지만 실제적으로는 거의 불가능에 가깝지. 정부와 같은 권력 기관이 자신들의 입 맛대로 조작할 수 없다는 거지.

Additionally, it is possible for community members to host any set of articles from their own private IPFS daemon which listens for edits of articles by connecting to the EOS network. This means that anyone who wishes to host articles (or some subset of articles) can do so from any location or server by running their own IPFS node and light EOS client.

원하면 자신의 IPFS 노드와 경량 EOS 클라이언트를 실행해서 어떤 위치나 서버에서 일부 글을 호스팅할 수 있어. 데몬을 EOS 네트워크에 연결해서 글 편집에 대해 통지받을 수 있도록 하면 되지.

Under the EOS.IO implementation, an Everipedia “reader” is any individual with an internet connection that can access the EOS main network. Reading and requesting Everipedia content is planned to be free to all end users and does not require any IQ token balance.

EOS.IO 구현 하에서, 에브리피디아 독자는 EOS 메인 넷에 인터넷으로 연결된 개인이겠지. 이들은 무료로 에브리피디아 컨텐츠에 접근하고 읽을 수 있지.

Conversely, an Everipedia “user” is any individual who possesses a functional wallet (an EOS.IO account) with a valid balance of IQ tokens to propose edits. Users will sign all their transactions with the associated private key to demonstrate ownership of a valid balance.

에브리피디아 사용자는 EOS.IO 계정을 보유한 편집 제안을 위해 토큰 잔고가 있는 개인이겠지. 사용자는 유효한 잔고에 대한 소유권을 제시하는 개인 키를 가지고 그들 자신의 트랜잭션에 서명할거야.

Using the EOS.IO account system allows for various web standards and benefits that are not currently available on other blockchains such as account recovery and human readable usernames. This would essentially create a seamless user experience similar to using a web application with classical user and account authentication. Additionally, it is possible to leverage upcoming EOS.IO identification and reputation systems to incorporate into the validation algorithm and edit approval process such that previous edit histories and identities of editors can be measured in the consensus process.

중앙화된 시스템을 사용하는 사용자들은 대부분 계정시스템에 익숙해져있지. 이런 사용자들은 기억할 수 있는 형태의 계정 이름과 계정 복구를 당연한 것으로 여기지. EOS.IO도 계정시스템을 도입함으로 이러한 사용자들의 사용성을 만족시켜줄 수 있지. 계정 별로 편집 이력을 관리할 수 있기 때문에 추후에 검증 알고리즘 등에 평판 시스템을 도입할 수도 있지.

Current internet content businesses are based on the model on the left. A company is formed which creates a service or platform using rented or bought centralized server hardware. Users produce content and/or use the service. The business owners extract value from users, content-producers, and value creators through advertising, subscriptions, and as many means as possible to pay for server and business costs. The profits are then accrued for investors and stockholders. A distributed autonomous platform (right) uses token value stores to align the incentives of all participants (content creators, curators, bandwidth). There are no central stockholders, profit-takers, or rent-seeking behavior since all participants hold the same type of value store in the network. All participants also directly work toward making each part of the service useful to each class of participant. Img-sources (partially altered): EOS.io presentation. retrieved from: youtube.com