14. Algoritmo di consenso
● DPOS-BFT
● 1 blocco ogni 0.5 sec
● Round di 126 blocchi (21 x 6)
● Irreversibility dopo 15 BP hanno firmato un blocco
“DPOS Consensus Algorithm - The Missing White Paper” – Dan Larimer
15. EOS Token Sale
● 1 B tokens @ ICO
● 100 M riservati per
block.one (10%)
● Release su 10 anni
● ICO 26 Giugno 2017
– 26 Giugno 2018
● First 5 days, 200 M
● 350 periodi da 23h, 2
M token
● 4 B$ raccolti https://steemit.com/eos/@trogdor/the-eos-ico-for-dummies
16. EOS Incentives
Worker Proposal System
- Progetti per comunità
- Riduzione Spam
5% - 50 M
Annual inflation
1 % - 10 M
BP reward
.75% - 7.5 M (per
vote)
.25 - 2.5 M (per
block)
4% - 40 M
Treasury
17. Mainnet - Layers
• EOSIO Core
o 21 Block Producers
• EOSIO Access Network
o Seeds nodes (sync,
candidates, validating
nodes)
o API nodes (cleos
requests)
• EOSIO Consumers
o Validating nodes
o The rest of us!
Web application
Millions of users->scalabile su tutte le industry, critical mass needed
Free for app users->senza costi di transazione
Responsive->no latency, lag few sec
Upgradable->permettere agli sviluppatori di aggiornare gli smart contract
Account names->real names
No purchase necessary
Account recovery->lost keys
Thousand of actions per sec->sequential and parallel performance
Bug recovery->bug exists
Ogni app ha bisogno services (account, recovery, permission)
Ogni app cerca di implementare OS in modo diverso (come Vista on x86)
---
If you look at the blockchain industry, everyone wants to build smart businesses, decentralized organizations, etc..., and in the process developers built decentralized computers from the ground up which can run their smart apps. In this process, all app developers have to solve many of the same problems:
account systems
recovery processes
multi-sig
manage challenges
What they're missing is the operating system, which could provide all the common features that every application depends upon, allowing applications to focus on what makes them different. For example, there is a huge commonality between Bitshares and Steem in terms of functions, and relatively a very small difference in terms of application business logic.
EOS aims to provide this operating system to provide all the core functions to app developers and allow them to focus on just the business logic that makes their apps unique.
***
If you look at the blockchain industry, everyone wants to build smart businesses, decentralized organizations, etc..., and in the process developers built decentralized computers from the ground up which can run their smart apps. In this process, all app developers have to solve many of the same problems: account systems, recovery processes, multi-sig, manage challenges, and what they're missing is the operating system, which could provide all the common features that every application depends upon, allowing applications to focus on what makes them different. For example, there is a huge commonality between Bitshares and Steem in terms of functions, and relatively a very small difference in terms of application business logic. EOS aims to provide this operating system to provide all the core functions to app developers and allow them to focus on just the business logic that makes their apps unique.
Account permission-auth & permission mngmt
Indexed db
multi user control
Interapp (sync e async)
***
EOS provides parallel processing of smart contracts through horizontal scalability, asynchronous communication, and interoperability. It will provide databases, account permissions, scheduling, authentication, and internet-application communication. For example, both Bitshares and Steem can be run on EOS in parallel, and because of the asynchronous communication, additional nodes and entire clusters can be thrown behind the processing of transactions to scale up to any transaction volume you want.
EOS is the first blockchain operating system. It provides your application with databases, a schema, multiple indices so you can have sorted data that's easy to manage. it gives you account permissions and a whole set of users, account recovery, handles all the complexities of scheduling multiple tasks across CPU cores or even clusters, handles all the authentication and key management so you can focus on business logic and not cryptography, and it handles all the internet-application communication. EOS is the operating system that we've been waiting for that allows us to focus on building the apps that our users need without getting in the way, without forcing gas, without requiring users to purchase anything before using, and it dramatically accelerates the rate at which developers can build apps.
Scalable
Goal 1000s DAPPs removing cpu bottlenexk
Parallel
Read only in parallel, write spep in sequence
Flexible
Freeze->se DAO happen no hard fork, collectively update single application
Eliminate gas
https bug dopo molti anni
Multiple vm->messages
Web assembly industry standard
Add other languages
Governance
Election
P2p agreement->costitution e autorithy
Dispute happen/bug happen->process con jurisdiction
Self funded
Usable for developper
Trasparenza->database by schema
Tutto è leggibile
Permission system declarative
----
Scalable: EOS can support 1000s of commercial-scale DAPPs through parallel execution and asynchronous communication. It separates the authentication from the action. For example, a transfer is a simple action of reducing one account's balance and increasing another, but all the authentication steps are validating signatures, checking to make sure that are sufficient funds, etc... but authentication steps only need to happen once when the block is produced. After a block is irreversibly added to the blockchain you never have to authenticate again. EOS puts the source code on the blockchain so that it is human readable what the contract says, and everyone can see it and developers can optimize it and compile on different machines, all without breaking consensus. It also eliminates gas to eliminate the extra operations that are required to count the important operations.
Flexible: Because EOS will use delegated proof-of-stake, if an app is broken or fails, elected block producers can freeze the application until a bug can be fixed and then update the code. So if the DAO had been implemented on EOS, for example, it could have been frozen, fixed, and updated, all without ever having to hard fork or disrupt any other application on the chain. EOS is also flexible in the sense that you only have to run the applications that you need. If you are running an exchange, you don't have to run the social media apps, and you can configure your local node to process only the data you care about. Not every node needs to run and maintain the full state of the blockchain. EOS also publishes source code, not assembly, and provides generalized role-based permissions.
Usable: EOS will include a web toolkit for interface development, self-describing interfaces (data that goes on the blockchain can be read by humans but is also compressed), self-describing database schemas, and a declarative permission scheme. This allows a fine-grained level of permissions in which you can easily delegate specific account permission to other accounts.
Governance: Delegated proof-of-stake has elected block producers. A legally binding constitution (think decentralized peer-to-peer terms of service) establishes a common jurisdiction for disputes and dispute resolution. EOS will also include self-funded community benefit apps that are selected through stake-weighted voting. Ever account will have to sign the constitution. One idea is that every transaction may include the hash of the current state of the constitution. The constitution itself is something that can be modified and evolve, and captures the intent of what the blockchain is trying to express and guides the way when trying to resolve disputes. Signing the constitution expires if you do not use the platform just like other apps updating their terms of service.
EOS never consumed – è un token fungible - no fees
Allocazione di banda EOS in “staking contract” usare available resource
1% storage – 1% EOS (rilasciare)
1% computational
1% bandwidth
Elezione
Allocazione