Author: Markus Hinrichs
Editor: Randall Roland
The EOS Network Foundation spent money on some of the smartest minds and blockchain experts to write the four initial Blue Papers. The aim is clear: Enhance EOS and make it the best-in-class smart contract development platform for supporting Web3 applications. So...
What are these Blue Papers and how do they affect EOS?
To make EOS a leading blockchain platform that could attract developers and industrial leaders of the emerging Web3, it was fundamental to analyze the gaps and fill them. The elaboration of the proposed solutions took quite some time and involved top-class international experts. The proposals and solutions were condensed and published in distinct Blue Papers so that the EOS community could provide feedback and suggestions.
The proposals received in the four initial Blue Papers: Core+, Wallet+, Api+ and Audit+ make EOS more than ready for the future in Web3. In the following section we introduce to you the first two Bluepapers Core+ and Wallet+.
1. Core+
Core+ describes how to provide EOSIO (now AntelopeIO) users and developers with the resources they need to configure their own AntelopeIO implementation.
It serves to identify the following challenges and provides solutions in three phases:
1. Launchpad
Filling the technological gap
Reviewing and updating the documentation and training for AntelopeIO
AntelopeIO-Community owned documentation and training
2. Lift-Off
Make EOS Multi-Chain compatible
Enhancing onboarding (Events, partnerships and more)
Attract new developers, users, education and business partners
From Proof of Concept to Live: Legal framework to help projects evolve
3. Propel
Improving speed & scale of AntelopeIO
Attracting & supporting millions of new users
Bring AntelopeIO to major business centers in Europe, America & Asia
Research & Development Team
Maintain Codebase AntelopeIO
Keeping AntelopeIO a global player
In the conclusion of their Core+ blue paper, the Zaisan.io team states that AntelopeIO builts critical infrastructure this will open new markets. There lies a huge potential in the B2B (Business to Business), B2G (Business to government) and B2R (Businesss to Regulators) sectors where entities benefit from the shared infrastructure, transparent infrastructure, transparent security and interoperability between parties.
"The public EOS blockchain should derive substantial benefit from increased exposure."
Zaisan.io
Want to know more about the Core+ Bluepaper? Please click here.
2. Wallet+
Wallet+ gives an overview of the current situation in terms of Wallets, Software Development Kits, Standards, and complementary products to benefit application developers and the end-user experience for EOSIO (now AntelopeIO).
"By improving these key areas we can provide a more secure, understandable, and palatable eco-system for developers and users alike."
The teams from Greymass and Ultra collaborated to understand the broad scope of requirements for Wallets, SDKs, Standards, and Complementary Products that would benefit application developers and users.
The following list presents the different segments in a very simplified way so that the reader can have a general idea (blue paper page no. indicated in brackets):
Segments:
SDKs (Software Development Kits) (p. 12)
First steps towards creating a product suite (capable & modern EOSIO family of SDKs and tools) for all major platforms and programming languages.
Application Registry (p. 22)
A hub that helps discover new applications in a safe and fair way, with clear rules and transparent governance.
Request for Permission (p. 26)
Developing a set of guidelines and standards that use the EOSIO account permission system to enable apps to request permission to do actions on the user’s behalf, i.e. “automatic signing”.
Ricardian Contracts (p. 30)
RC is a method of recording a document as a contract at law, and linking it securely to other systems to gain:
Transaction clarity & safety
Dispute Resolution
"The ultimate goal is RC being the standard way to review transaction data on EOSIO chains"
Wallet Group (p. 33)
Recommendation to form a wallet developmet group out of the community with access to funding and responsible for various user-facing applications, such as account recovery portals pursuing the following tasks:
Wallet Standards
Onboarding & User Growth
User-Facing Services
Standardizing Language (p. 35)
Standardized language promotes ease of use, which translates into user and developer loyalty to a technology.
Recommendation the creation of a Terminology Best Practices Group who standardizes terminology
Hardware Wallets (p. 40)
Proposal to form a Hardware Wallet Integration Team. The team’s mandate will be to coordinate EOSIO support into all major hardware wallets and companion apps.
Web Authenticator (p. 44)
Providing the convenience of custodial web-based wallets without giving full custody to a third party. Keyword: Shamir's Secret Sharing technique.
Profile & Avatar System (p. 48)
A consistent, verifiable profile and avatar system that wallets and apps across all EOSIO networks can leverage to increase trust, build network loyalty, and reduce developer friction.
Multisig Improvements (p. 51)
A set of tools, standards, and documentation that will make advanced multisig capabilities accessible even to non-technical users.
Account Recovery (p. 55)
Proposal to build a flexible and decentralized account recovery system that leverages the powerful EOSIO account permissions system.
Asset Proxy Service (p. 62)
A common need for apps and Wallets is to reference assets like images and other large files that would be too expensive to store on the blockchain.
Proposal to build an open-source service that can be easily customized and deployed.
Asset Hosting Service (p. 64)
Common need for apps and Wallets is to host user generated content that would be too expensive to store directly on the blockchain.
Proposal to develop an open-source asset hosting service that is easy to deploy and customize to the needs of the operator. This service can operate in conjunction with the Asset proxy service.
The suggested approaches for future working groups have the aim to reduce friction, promote broader acceptance, and provide users and developers with a streamlined experience that both reduces work and enhances practicality.
"Future working groups will be able to use this initiative as a foundation for further research. The intent is to take the first steps, and not to walk the entire path. This will allow us to begin defining what we still do not know so that the next generation of stewards may use that as a stepping stone towards greatness.
For now, we must try to outline the projects that we believe are achievable today, define reasonable expectations for them, all while having in mind a view of the wider vision of what the EOSIO ecosystem could become."
Wallet+ Work Group
Want to dive deep into the Wallet+ Bluepaper? View the full bluepaper here.
The follow up articles will be released soon on EOS Support Media and condense the Audit+ and Api+ Blue Papers.
Have we sparked your curiosity?
Join the EOS movement now and get started by creating your first free EOS Account!
Want to start developing on EOS?
Visit the Antelope website and the EOS Support Learning Center Developer section to learn more
If you liked this article, please consider following the EOS Support Twitter for more up-to-date information, our EOS Support LIVE Giveaway Show, and our Scam Prevention Alert, where we expose the newest fraud schemes in the EOS scene. All our content is provided in 9 different languages, thanks to our international team of highly motivated agents. Want to get involved as well? We are always scouting for talent! Read here
Sources & References: