Request 백서

Request

원문

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

Whitepaper Request Network The future of commerce A decentralized network for payment requests March 16, 2018 Contents 1 Executive summary 1 2 The platform 1 3 The ecosystem 6 3.1 The Core layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2 The Extensions layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.3 The Applications layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4 Use cases 8 4.1 B2B invoicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2 Online payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3 Automation of jobs: Accounting, Audit, Expenses . . . . . . . . . . . . . . . . . . . . . . . . 10 4.3.1 Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.3.2 Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.3.3 Expenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.4 Business Logic and Trade Laws: Government and Tax . . . . . . . . . . . . . . . . . . . . . . 13 4.5 Simplification of commercial tools: Factoring, Escrow . . . . . . . . . . . . . . . . . . . . . . . 13 4.6 Transparency of institutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.7 IoT and smart contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5 T oken 14 5.1 Incentive for a secure ecosystem of applications . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.2 Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.3 Independence of other currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4 Technical independence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.5 Make cross currency exchanges easier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6 Roadmap draft 15 7 T eam 16 7.1 Core team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8 Architecture 18 8.1 Technical considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.2 Smart contract architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1 9 Thanks 21 10 Bibliography 22 1 Executive summary Request is a decentralized1 network that allows anyone to request a payment (a Request Invoice)for which the recipient can pay in a secure way. All of the information is stored in a decentralized authentic ledger. This results in cheaper, easier, and more secure payments, and it allows for a wide range of automation possibilities. To become the backbone of world trade, Request integrates a general ledger (in the accounting sense of the term), which is: - Universal because it is designed to support 100% of global transactions, regardless of currency, legislation or language. Request is built to last. - Smart because unlike an existing standard accounting book, Request is at the origin of the exchanges and integrates a computerized trade code, as well as the management of a multitude of payment terms. Today, their absence makes the whole system inefficient and absolutely unready for the digital and IoT (Internet Of Things) revolution that is taking place. Request can be seen as a layer on top of Ethereum 2, which allows requests for payments that satisfy a legal framework.It is also possible to see currencies as tools to complete Request transactions. In this sense, Request is more global than any currency. 2 The platform Anyone can write on the Request Ledger and create a Request for Payment. The Request can be detected by the recipient monitoring the network (via a wallet or via a financial application). If the request is approved by the user, it can be paid with a single click. Then the request is completed and the network is updated. When a Request is created, the trade laws that are applicable to its specific case are taken into account, and taxes are applied. When necessary, advanced payment terms may be selected. 1http://gavwood.com/paper.pdf, 2014, Gavin Wood. Ethereum: a secure decentralised generalised transaction ledger 2https://github.com/ethereum/wiki/wiki/White-Paper 2 Bob is requesting a payment from Alice Lets look at 2 examples: Bob asks Alice for a payment, then he creates an (invoice) request and relays it to the blockchain; Alice’s wallet detects the Request and processes the payment. In the case where Bob was on Amazon and Alice was making a purchase, Amazon creates a Request on the blockchain, Alices phone analyzes the blockchain and detects the request, sends a notification, and she agrees to pay. Request offers: • Security, since it is not necessary to share banking information • Simplicity, since it requires only to click a button • Savings, since purchases dont require a third party (eg. Paypal) 3 A representation of what the General Ledger looks like Consider a second scenario, in which an autonomous car connects to a smart garage contract to buy a new wheel. They negotiate by algorithm, and agree upon a payment with deposit and escrow (money blocked until delivery). To interact financially, the machines and IoT require a payment framework. These examples are not feasible today, as there is no standard format and no interconnection between the services; it is necessary either to share banking information, or to use a third party that is common to both entities (Paypal, Venmo, Lydia , Stripe ...). Besides being limited and unsafe, it results in scattered invoices that could contain errors. The blockchain is the perfect support to create an open source, durable, smart and immutable system. 4 These new foundations simplify electronic flows. Today, this is incredibly important because everything comes down to payment. More than $5 trillion is exchanged every day3 on the SWIFT network alone, however, the flows are poorly optimized. This solution has even greater advantages. A ledger containing all standardized accounting entries can automate real-time accounting, improve auditing, automate factoring, simplify expense reporting, make es- crow simple and reliable, and detect and automatically pay taxes. 3https://www.fincen.gov/sites/default/files/shared/Appendix_D.pdf 5 Moreover, it opens up opportunities for more comprehensive trade improvement. Being able to manage data privacy makes it possible to push trade towards more transparency (public expenditure, associations), more fairness (transparency makes it possible to follow the distribution of gains and the origin of products; it also enhances fair-trade) and more justice (trade rules will be more easily aligned and enforced). It is difficult to imagine that the financial world can make any advancements without this layer. 6 3 The ecosystem Many developments will be possible on top of Request once the Core protocol is finished by the team. Our T ech mind map4 gives a full picture of the Request Network and the upcoming roadmap. We believe the Request ecosystem is the key to success, and we very much would like to nurture it. In order to drive this decentralization forward and help Request to scale, here is an introduction to theRequest Hub5. What we call Request Hub is the community outside the Request foundation that is willing to work on top of Request, create teams and projects around Request, and help with its decentralization. 3.1 The Core layer The bottom layer is the Core, which manages the consensus over the ledger and the states transitions. It consists of the most fundamental smart contracts, allowing the creation of different entities and requests for payments. It also detects when payments have been completed. It is based on immutability (ie. no one can change the information), the openness of its system (everyone can access information that concerns them) and an intelligence that allows it to know when an invoice is paid according to the rules in the invoice. This layer takes place on the Ethereum blockchain, which brings endogenous benefits for Ethereum and ERC20-labeled invoices, such as automatic detection. Other currencies are also covered via automatic pay- ment detection through the use of Oracles. This layer is free to encourage the greatest number to use it and to discourage the development of other systems. The only costs transmitted are the use of Ethereum gas and the storage of information. 4https://www.mindmeister.com/991002501?t=R1iofDilV0 5https://www.mindmeister.com/995302918?t=Y78CuCvpRn 7 3.2 The Extensions layer The second layer is the Extensions layer. Most payment requests created today are not as basic as the one proposed by the Core layer. If the request comes from an enterprise, then it includes rules for calculating taxes, payment terms, escrows or advances. All of these conditions take the form of available extensions that can be added to requests. This layer is the gateway to incredible features that do not yet exist, such as ” continuous bills ”. For example, someone could choose this module to break down their rent into 30x24 payments to the landlord, leaving this person with a fluid bank account without large end-of-month expenses. Taxes would be rerouted in real time to government agencies. With each payment, 20% of VAT would go to taxes and 80% to the recipient company. The same example would allow everyone to give 1% of all payments to NGOs (Non Governmental Organizations), or to deposit them into ones own retirement account. This layer is chargeable, in that each extension will take a fee that will be partially burned and partially transferred to the extension developers, with the extensions accrued on the same invoice. Costs decrease over time to remain competitive and discourage alternative systems. The costs of these extensions is estimated to be between 0.1% and 0.5% initially, though as the system grows, the costs will be reduced. More than 5,000 billion dollars in payments are made each day, and in the end it will be enough to finance the network by less than 0.1%. Nonetheless, the costs will continue to support the security of applications and their development. This layer is completely open, whereupon anyone can create their own extensions, with the fees also being distributed in a way that will interest and encourage the developer and the community. 3.3 The Applications layer The topmost layer is the Applications layer, which takes place outside the blockchain. Systems from different companies can connect to Request to create requests or access information. Accounting, audit, tax, debt re- 8 covery and collection, factoring or payment systems can all be connected. When a payment system connects to Request (Mycellium, Coinbase, Bank of America, Bankin ...), it will be able to access the invoices of the user and propose to pay them instantly. The Request team will develop applications, including an interface and an API for creating and accessing requests. Reputation Application A reputation system is included in this layer to guard against phishing or bad payers. For instance, a user will be able to detect whether a company is attempting phishing, in the case that other users have previously rejected its payments. Conversely, a company that does not pay its invoices on time, after having accepted them, will also be penalized by means of its reputation. The reputation system may also have other uses; for example, members of the network with the best reputation will be able to receive cost reductions or access to custom extensions. The reputation could be directly entered in the blockchain, but to keep the system light, we have chosen to keep them in the application layer thus far, since this information can be re-obtained by browsing the blockchain. 4 Use cases The use cases of this technology are extremely wide. This system automates real-time global accounting, replaces an entire branch of the audit, eliminates manual tax collection, simplifies international payments, allows machines to communicate on the same financial field, replaces payment systems such as Paypal , and makes the most advanced payment terms available to everyone. 4.1 B2B invoicing Billions of invoices are shared each year between companies, with most of them still being sent in paper and email format, which have to be copied. This results in a large number of errors, particularly when advanced payment or tax rules are applied. With Request, companies can share these bills directly via the ledger; there will be no more duplication, as accounting systems will be immediately plugged in and updated. The company awaiting payment will be able to detect a delay immediately, which will happen less often due to the development of invoice payment systems. The company has the ability to pay on the optimal date at the time of receiving the request. Each year, thousands of small and medium-sized enterprises (SMEs) bankrupt while waiting for their invoices to be paid. The ECB (European Central Bank), in particular, is setting up solutions that Request complete by adding a payment reputation system and key indicators. Today, a provider still has to trust its client and might not be paid. Tomorrow, the provider will be able to verify the payers clients reputation and other indicators, such as DPO (Days Payable Outstanding) before agreeing on a contract. 9 4.2 Online payments For example, shopping on Amazon requires payment by credit/debit card, thereby exposing sensitive infor- mation. Alternatively, selecting the option to pay via Request, the users data remain protected. Amazon will post a Request on the network, the user’s account will detect it and request a confirmation of payment from the user. This will trigger a transfer at the lowest cost, without exposing the payment information. It becomes possible to avoid unforeseen credit/debit card payments that services charge in a hidden way, because it provides a way to validate payments before they happen. Request empowers people. The advantages of Request, compared to current systems, are: • Security: Payment information is never shared, there is no risk that someone intercepts and reuses banking information. • Simplicity: One click to pay, and no manual input error possible. 10 • Cost: No third-party like Paypal 6, Bitpay7 or Stripe 8, all of whom are providers that charge between 1% and 7% of the amounts sent. Request reduces the cost. 4.3 Automation of jobs: Accounting, Audit, Expenses 4.3.1 Accounting With Request, the accounting is done automatically and in real time. Beyond cost reduction, this allows for better, faster financial management, and with more information. Use cases for accounting purposes: Request brings simultaneity to the accounting process . Payments, accounting, and VAT refunds / payments are done automatically. 6https://www.paypal.com/en/webapps/mpp/paypal-fees 7https://bitpay.com/pricing 8https://stripe.com/nl/pricing 11 In addition, it represents a switch from double-entry accounting 9 to triple-entry accounting 10. This is a revolution, expected by experts, that raises some questions about the future value of external audits. Indeed, a third validation point is added to double-entry accounting systems 11, and this is where auditors are currently acting for the validation of the authenticity of accounts. Moreover, Request allows the digitization of accounting systems , where one currently spends time to duplicate efforts through repetitive documentation and frequent checks. These manual tasks can now be automated. Request will transform the role of a CPA into consulting and support activities. This system leaves more time for value-added tasks, such as analysis, estimation and strategy. Technically, credit notes, purchase orders, reimbursement, and every accounting concepts will be possible on Request. The system will be compatible with the UN/EDIFACT standard and able to be updated to the latest standards. 4.3.2 Audit With Request, audits become a simple algorithmic check, thanks to the immutability of the system. In comparison, in 2014, Microsoft paid $46.2 million in audit fees to Deloitte12. Similarly, Bank of America paid nearly $100 million. In total, the 100 biggest companies in the United States paid $2.5 billion in audit fees. Henceforth, audits will be carried out in real time 13. Let’s call them Smart Audits 14. Blockchain auditing solutions (”smart audits”) will likely become a reliable and inexpensive alternative to today’s manual audits. Request brings significant benefits for improving the efficiency of such audits. In terms of digitization, accounting software, states and companies are still far from optimal. Many companies send invoices by mail every day, and most of them have missing invoices at the end of each year. Yet the rules are clear. The methods and technological support could change everything and substitute the intercompany and inter-subsidiary costly controls, which are carried out to ensure the reliability of the 9https://en.wikipedia.org/wiki/Double-entry_bookkeeping_system 10http://iang.org/papers/triple_entry.htmlhttps://en.wikipedia.org/wiki/Momentum_accounting_and_triple-entry_ bookkeeping 11https://bitcoinmagazine.com/articles/triple-entry-bookkeeping-bitcoin-1392069656/ 12http://fortune.com/2015/08/27/microsoft-pays-more-than-apple-for-its-audit-and-why-investors-should-care/ 13http://economia.icaew.com/features/july-2016/how-blockchain-will-impact-accountants-and-auditors 14https://request.network/assets/pdf/request_yellowpaper_smart_audits.pdf 12 accounting statements. In the computer consulting industry, the cost of the accounting officer’s time to process an invoice is be- tween $5 and $1515. To this amount can be added the time necessary for monthly checkings and corrections. The automation of the entire system is slow. The use of blockchain for accounting is an opportunity to simplify compliance, and improves double-entry accounting. Double-entry accounting dates back to the Renaissance, where it allowed managers to have confidence in their own reports. Nowadays, to justify trust, independent auditors verify the information of the major groups in a process that is costly in both time and money. The audit firm then becomes a trusted third party guaranteeing the veracity of the information established by the financial statements. However, the auditors maintain responsibility over the companies, which generates mistrust. Do the auditors work for the managers of the companies that mandate them, or for the service of the third parties who consult the information for free? Thus, instead of holding internal accounts and publishing them after the annual audit, companies can keep accounts in a decentralized, confidential and shared database with blockchain technology. All account- ing entries are then entered into the register, without the possibility of backdating, which means there is no opportunity for falsification. Therefore, it would become more difficult to make questionable year-end adjustments, and most importantly, the company benefits from this system in real time. Shareholders and external parties have access to real-time information. The cost of auditing becomes insignificant, and ac- counting entries no longer require duplicate manual checks. Finally, the integrity of the financial statements can no longer be called into question when customers and suppliers are interconnected with this system, at least by their cryptographic addresses. Request is a distributed registry that acts as a source of confidence, ultimately allowing these ”smart audits” in real-time. It includes all purchases and sales of the company. Instead of having double-entry accounts, where the information regarding a purchase appears in the purchase account and in the ban
프로젝트로 돌아가기