Skip to content

Commit

Permalink
Update faq.rst
Browse files Browse the repository at this point in the history
  • Loading branch information
igoraxz committed Nov 12, 2019
1 parent 97b18b5 commit f17725b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions doc/faq.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,14 +23,14 @@ What differs Papyrus Network from Ethereum, EOS and TRON?
Papyrus Network combines the best features of Ethereum and EOS avoiding their weaknesses and having something different inside:

* *Consensus Module*
Instead of energy intensive Proof-of-Work lightweight **Proof-of-Authority consensus and Separation of Powers** are realised, where fixed amount of network nodes called “block sealers” are operated by credible organizations with public exposure. As a result resource wastage can be eliminated inherent to Proof-of-Work and ensure reasonable transaction costs.
Instead of energy intensive Proof-of-Work lightweight **Proof-of-Authority consensus and Separation of Powers** are realised, where fixed amount of network nodes called Authority Nodes are operated by credible organizations with public exposure. As a result resource wastage can be eliminated inherent to Proof-of-Work and ensure reasonable transaction costs.

* *Token Staking*
Instead of gas transaction fee model **token staking model** is implemented, where token supply represents total available network throughput and each token represents fraction of it. Application developers need to stake tokens (locking them for specific period of time) to receive access to required network bandwidth and may adjust staked amount from time to time accordingly to their needs. Developers don’t need to worry about token price volatility between revisions of their bandwidth requirements.
Instead of gas transaction fee model **token staking model** is implemented, where token supply represents total available network throughput and each token represents fraction of it. Application developers need to stake tokens (locking them for specific period of time) for their dApp contracts to receive access to required network bandwidth and may adjust staked amount from time to time accordingly to their needs. Developers don’t need to worry about token price volatility between revisions of their bandwidth requirements.

For more information on what differs Papyrus Network from others, go check Comparison table in the next session of the Docs.
For more information on what differs Papyrus Network from others, go check Comparison page in the Docs.

What are Authority nodes?
-------------------------

They are active network nodes, which participate in Proof-of-Authority consensus. Initial set of Authority nodes is appointed by Papyrus team (using genesis block). After network launch Authority nodes self-elect themselves from current set of eligible node candidates, determined by Verification Committee. Inclusion or exclusion of Authority node requires majority vote from other Authority nodes. Maximum amount of Authority nodes is fixed as 25, as in our view it is good tradeoff between network speed and resistance to attacks.
They are active network nodes, which participate in Proof-of-Authority consensus. Initial set of Authority nodes was appointed by Papyrus team. After network is launched Authority nodes self-elect themselves from current set of eligible node candidates. Inclusion or exclusion of Authority nodes is based on votes from other Authority nodes. Maximum amount of Authority nodes is fixed as 47, as in our view it is good tradeoff between network speed, scalability and resistance to attacks.

0 comments on commit f17725b

Please sign in to comment.