-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
110 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| Papyrus Network - Comparison Matrix | ||
| ============================= | ||
|
|
||
| ===================== =========================== ========================== ==================== | ||
| Blockchain **Ethereum** **EOS** **Papyrus Network** | ||
| TPS 15 3000 1200 | ||
| Block Time 12s 0.5s 3s | ||
| Block Finality Probabilistic Yes, in 180s Yes, maximum timing | ||
| depends on amount | ||
| of validators | ||
| Consensus PoW dPoS PoA | ||
| Transaction Model Gas Staking Staking | ||
| Average tx fee 0.25 USD 1 USD per 1000 bytes < 0.001 USD | ||
| very volatile of used RAM, very volatile | ||
| Smart Contracts EVM/Solidity WASM EVM/Solidity | ||
| Network availability network clogging can Not guaranteed, Ensured by token resource paralyze applications block sealers resource allocation | ||
| (CryptoKitties case) don’t have liabilities and protected from | ||
| if network fails network clogging | ||
| Trust model 51% Pow attack is 21 block producers | ||
| expensive and are incentivized to behave | ||
| economically not well to keep being elected Validators are all | ||
| reasonable for large identified credible | ||
| mining pools organizations which | ||
| put their reputation | ||
| and business at risk in | ||
| case of abuse | ||
| ===================== =========================== ========================== ==================== |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| FAQ | ||
| === | ||
| **What is Papyrus Network?** | ||
| ------------ | ||
|
|
||
| Papyrus Network is a decentralized blockchain platform for supporting smart contracts and high throughput designed for mass adoption and enterprise usage. Papyrus Network is an operating system which will allow developers to deploy their own decentralized applications and will allow companies integrate custom blockchain for their business needs. | ||
|
|
||
| **What is the prospects of Papyrus Network?** | ||
| ------------ | ||
|
|
||
| We aim to build a Papyrus Network ecosystem that everyone can participate in and benefit from. Some of the features of Papyrus Network are: | ||
| - Users are able to reduce costs, enjoy convenience, and build fortunes by using different DApp functions deployed in Papyrus Network. Instead of gas transaction fee model token staking model is implemented to allocate network processing power and storage facilities. | ||
| - Developers have a vast range of rights including deploying DApp in Papyrus Network net, expanding business and gaining traction as influencers and authority leaders. | ||
| - Authority node holders demonstrate support for Papyrus Network and its abundant returns. | ||
| Everyone will devote their energy to the construction of the Papyrus Network ecosystem, and will benefit from helping to build Papyrus Network regardless of their role as users, developers or Papyrus Network Authority node holders. | ||
|
|
||
| **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 is 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. | ||
| - *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. | ||
|
|
||
| For more information on what differs Papyrus Network from others, go check Comparison table in the next session of 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,60 +1,42 @@ | ||
| Papyrus Network Memo | ||
| =================== | ||
|
|
||
| Intro | ||
| ------------- | ||
|
|
||
|
|
||
| ================= | ||
| Papyrus network is a public blockchain for developers designed for mass adoption and enterprise usage. | ||
| This is the first Ethereum-based scalable universal blockchain network with various smart contracts capabilities which can be successfully used in all industries, especially in data centric applications. Papyrus Network utilizes Proof of Authority (PoA) as its consensus mechanism. We provide the flexibility to code in Ethereum standards with the added benefits of Papyrus Network solutions to scalability and interoperability in blockchain networks. | ||
| This is the first Ethereum-based scalable universal blockchain network with various smart contracts capabilities which can be successfully used in all industries, especially in data centric applications. Papyrus Network utilizes Proof of Authority (PoA) as its consensus mechanism. Developers have a possibility to code in Ethereum standards with the added benefits of Papyrus Network solutions to scalability and interoperability in blockchain networks. | ||
|
|
||
| Papyrus Network is based on Ethereum code base with two major changes: | ||
|
|
||
|
|
||
| * Instead of energy intensive Proof-of-Work we use lightweight Proof-of-Authority consensus, where fixed amount of network nodes called “block sealers” are operated by credible organizations Consortium with public exposure and formalized legally binding governance agreement. | ||
| * Instead of gas transaction fee model we implement token staking model, 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 energy intensive Proof-of-Work a lightweight Proof-of-Authority consensus is used, where fixed amount of network nodes called “block sealers” are operated by credible organizations with public exposure; | ||
| - 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. | ||
|
|
||
| What challenges does Papyrus Network solve? | ||
| ------------ | ||
|
|
||
|
|
||
| Nowadays there are a lot of challenges of using public blockchains as application platforms and for the wide-usage: | ||
| * Lack of trust (network is usually controlled by anonymous elite, which control largest mining pools or use coalitions of network nodes in own interest) | ||
| * Lack of reliability (network is not protected from failures and application developer may experience large losses due to mistakes of others) | ||
| * Lack of responsibility (there is no any formal responsibility by network operators for application developers) | ||
| * Lack of support (application developers need to find solution for every problem themselves) | ||
| * Poor user experience (existing solutions are too complex and push users away by requiring them to use sophisticated wallets and plugins) | ||
| * Extreme costs and volatility (application developers need to care about cryptocurrency prices because they are used to pay network fees, they cannot build stable business model because of too high dependence on cryptocurrency market) | ||
|
|
||
|
|
||
|
|
||
| Solution Papyrus Network offers | ||
| -------------- | ||
|
|
||
| - Lack of trust (network is usually controlled by anonymous elite, which control largest mining pools or use coalitions of network nodes in own interest); | ||
| - Lack of reliability (network is not protected from failures and application developer may experience large losses due to mistakes of others); | ||
| - Lack of responsibility (there is no any formal responsibility by network operators for application developers); | ||
| - Lack of support (application developers need to find solution for every problem themselves) | ||
| - Poor user experience (existing solutions are too complex and push users away by requiring them to use sophisticated wallets and plugins) | ||
| - Extreme costs and volatility (application developers need to care about cryptocurrency prices because they are used to pay network fees, they cannot build stable business model because of too high dependence on cryptocurrency market). | ||
|
|
||
| What solution does Papyrus Network see? | ||
| ------------ | ||
| The way to solve stated problems is to mix properties of permissioned and public blockchains: | ||
| Network nodes shall be permissioned, while public access is allowed. | ||
|
|
||
| * Trust – control of the network nodes should belong to decentralized consortium of credible organizations with full public disclosure of governance processes, disputes between application developers and consortium members should be settled by formal arbitration procedures established with legally binding agreements | ||
| * Reliability – formal service level agreements with application developers may be introduced, network architecture should enable control of network resources allocation between registered application developers to avoid network overload | ||
| * Responsibility – being publicly exposed and having their business and reputation at risk consortium members will be responsible for their activities | ||
| * Great user experience – moving obligation to pay network fees from user to application developer significantly improve user experience as now users don’t need to care about keeping positive crypto wallet balance, calculating transaction fees and confirming them | ||
| * Reasonable and stable costs – application developers should be able to reserve necessary network bandwidth for specified period of time with reasonable upfront payment, it allow them to provision their expenses and eliminate crypto volatility impact on their business models. | ||
|
|
||
|
|
||
|
|
||
| - Trust – control of the network nodes should belong to decentralized consortium of credible organizations with full public disclosure of governance processes, disputes between application developers and consortium members should be settled by formal arbitration procedures established with legally binding agreements | ||
| - Reliability – formal service level agreements with application developers may be introduced, network architecture should enable control of network resources allocation between registered application developers to avoid network overload | ||
| - Responsibility – being publicly exposed and having their business and reputation at risk consortium members will be responsible for their activities | ||
| - Great user experience – moving obligation to pay network fees from user to application developer significantly improve user experience as now users don’t need to care about keeping positive crypto wallet balance, calculating transaction fees and confirming them | ||
| - Reasonable and stable costs – application developers should be able to reserve necessary network bandwidth for specified period of time with reasonable upfront payment, it allow them to provision their expenses and eliminate crypto volatility impact on their business models. | ||
|
|
||
| The main features of Papyrus Network | ||
| ---------- | ||
|
|
||
| * Compatibility with existing Ethereum ecosystem, including wallets, smart contracts, and other tools; no need to study new languages and frameworks; | ||
| * A Service Level Agreement for guaranteed network availability and throughput for mission-critical enterprise applications; | ||
| * Increased Network speed and reliability. No more worries about application scalability and availability issues; | ||
| * High standard of network security provided by the governance of decentralized consortium of credible organizations with public disclosure, which cannot be achieved in the environment of anonymous mining pools; | ||
| * First Customer-Facing blockchain, which doesn’t require a whole IT department for deploying and operating. We provide prepared node containers with instructions on how to deploy and run them without console magic. | ||
| * An Unprecedented level of user experience — token staking model with no need to install complex plugins or browsers, pay fees or to make gas calculations; just use your application like any other — Facebook or Amazon; | ||
| * An easy way of making money without building complex token economies — you can simply sell subscriptions or in-app services to your application users, accepting both traditional payments and cryptocurrencies; | ||
| * Low network resource cost and low volatility; you can plan your infrastructure expenses in USD. | ||
| * Network availability ensured by token staking resource allocation and protected from network clogging; validator liabilities can be defined in SLA Contracts. | ||
| * Validators are bound with joint contractual agreement defining their responsibilities and re-election process; validators appoint a steering committee to supervise protocol development and customer relations. | ||
| * Validators are all identified credible organizations which put their reputation and business at risk in case of abuse. | ||
| * Network is governed by decentralized consortium of credible organizations with public disclosure, creating high standard of network security, which cannot be achieved in the environment of anonymous mining pools. | ||
| ------------ | ||
| - **Compatibility with existing Ethereum ecosystem** including wallets, smart contracts, and other tools; no need to study new languages and frameworks; | ||
| - **Increased Network speed and reliability**: no more worries about application scalability and availability issues; | ||
| - **High standard of network security** provided by the Authority nodes of credible organizations with public disclosure, which cannot be achieved in the environment of anonymous mining pools; | ||
| - **First Customer-Facing blockchain**, which doesn’t require a whole IT department for deploying and operating. P.N provides prepared node containers with instructions on how to deploy and run them without console magic; | ||
| - **An Unprecedented level of user experience** — token staking model with no need to install complex plugins or browsers, pay fees or to make gas calculations; just use your application like any other — Facebook or Amazon; | ||
| - **An easy way of making money** without building complex token economies — you can simply sell subscriptions or in-app services to your application users, accepting both traditional payments and cryptocurrencies; | ||
| - **Low network resource cost and low volatility**: you can plan your infrastructure expenses in USD; | ||
| - **Network availability ensured by token staking resource** allocation and protected from network clogging; | ||
| - **Validators are all identified credible organizations** which put their reputation and business at risk in case of abuse. | ||
| - **Network is governed by decentralized consortium** of credible organizations with public disclosure, creating high standard of network security, which cannot be achieved in the environment of anonymous mining pools. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| Required knowledge | ||
| ================ | ||
| Good news is that if you already had some experience with Ethereum, it can be applied in Papyrus Network. The same EVM fully compatible with Solidity is used in Papyrus network and as result, all your knowledge will be useful and existing smart contracts may be transferred to Papyrus to achieve greater performance and convenience. | ||
| One of the key differences is that in Ethereum you have to pay gas for any transaction but in the Papyrus network you can divide the contract execution fee between the contract developer and users by token staking. | ||
| Here ( ссылка на нашу статью про Papyrus PoA blockchain) you could read more about this staking system. | ||
| If you have no any experience in Ethereum, don’t you worry! Solidity itself is a pretty simple language and its syntax is very similar to JavaScript. | ||
| - You can familiarize yourself with it by taking any guide, for example this one: | ||
| https://ethereumbuilders.gitbooks.io/guide/content/en/solidity_tutorials.html | ||
| And this generic tutorial: | ||
| https://solidity.readthedocs.io/en/v0.4.24/ | ||
| - Next step - to chose IDE. Remix IDE can be a suitable choice for the beginning - it is written in Java Script and supports all e2e development steps such as building/testing/debugging and deployment. | ||
| - Geth — it is the official client software provided by the Ethereum Foundation. It contains Papyrus consensus, so you may deploy your own testnet or connect to Papyrus network or testnet. | ||
|
|
||
| What if I do not have required scope of knowledge? | ||
| ------------ | ||
| If you or your team do not have some of the skills mentioned above, it is not a big deal. | ||
| Papyrus Network core team is always here to help you to develop smart contracts tailored to one’s business needs either from scratch, or just port it from Ethereum, if the business has a smart contract written in Solidity. | ||
| If you are interested, please do not hesitate to leave an inquiry here https://papyrusglobal.typeform.com/to/opWAfy |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters