Author: Markus Hinrichs

Editor: Randall Roland

Note: This is the fourth article of the series "Ready for the New EOS" of the EOS Support Media Collection, where we condence the ENF blue papers for our readers.

The teams of EOS Nation, EOS Rio and Greymass worked together for this task based on their experience in developing, operating and using EOSIO (now AntelopeIO) APIs.

The development of this so-called Blue Paper, as well as the other three Blue Papers (Core+, Wallet+ and Audit+), was funded by the ENF with $250,000 each. The requirements for this paper, which was to be a mixture of white paper, yellow paper, request for proposals and roadmap, were therefore extremely high. The working group, including the Greymass team (developers of the Anchor Wallet), EOS Rio and EOS Nation, was given a window of time until early 2022.

The ENF relied on this working group constellation because all of the three independent teams had significant experience in software development, infrastructure operations, and experience delivering history solutions within EOSIO and the larger blockchain ecosystem. The original paper was to be called History+, but this name was changed to API+ after intensive initial discussions within the working group, as this broadened the necessary focus of the group to essentials and thus better described it.

Many different approaches to "data collection" were used, including:

Smaller working groups worked on the multitude of topics that emerged from the information gathering, resulting in a variety of specific documents. Then, in the large group, it was important to find the overlaps, take them out, and create a consistent document with all the relevant points that were used as proposed solutions in the last part of the paper and those that were not to be submitted as proposals.

These are the most impacted by changes to APIs, the major groups for whom APIs should be developed:

- Application developers

- Data analysts

- Exchanges/custodial services

- Executives/leadership roles

- Operators and service providers

- Protocol/tooling developers

- Smart contract developers

After discussing which APIs already exist in EOSIO, a distinction was made between native EOSIO APIs, Communty-developed APIs and non-EOSIO-specific APIs. The last and most comprehensive part of the API+ Blue Paper deals with the proposals for the ENF.

During the process of writing this Blue Paper, dozens of blockchain experts were interviewed to understand their needs and desires. Some problems were based on sheer unknowing, which could be addressed with educational initiatives (e.g. Learning Center). Others require very complex solutions. A total of 8 proposals were made, the first of which is one of the most important, namely to establish a permanent working group (APR) to coordinate the implementation of the proposals made.

The APR team performs an important research and coordination role to support the extremely complex development of EOSIO APIs.

At the core API level, an enhancement for transaction flow is to be introduced. This enhancement needs to be done by a team of experts and should be overseen by the API+ working group, as no APR team has been formed yet.




Specialized APIs are needed to meet specific requirements. For example, the native API history plugin is not sufficient for the transaction volume of the EOS Blockchain. 

To ensure a long lifetime of the specialized EOSIO infrastructure, funding for its maintenance and further development must be ensured. In addition, external teams familiar with EOSIO should be brought on board to maximize resilience for developers. 


Fund a dedicated team to provide API services and act as a public resource to bring new developers and companies into the ecosystem. These services are: 


The API+ working group proposes that 5 specialized teams dedicate themselves to creating a white paper that addresses how to develop a DAO that promotes the operation of a wide variety of APIs on EOS and other EOSIO blockchains.


This is about making blockchain data from infrastructure providers available for download to the public at standardized time intervals on a homepage such as ENF website or EOSIO to make it easier for newcomers to build their own blockchain infrastructure.




Creating a Rosetta integration for EOSIO would make it much easier to list EOSIO project tokens on Exchanges by eliminating the need to program middleware. This would lead to maximization of liquidity.



Some of the largest DeFi applications on ETH and other EVM-compatible chains use The Graph to provide their user dashboards with rich data and visual representations for detailed data charts (e.g.: token price, 24h trading volume, TVL).

 The goal is to develop the software required to integrate The Graph protocols into EOSIO to enable the creation of new data sets.




Want to dive deep into the API+ Bluepaper? View the full bluepaper here.

​

In order to immerse yourself even deeper into the Blue Papers please read the other articles of this series "Are you ready for the New EOS" in the EOS Support Media Collection.

If you liked this article, please consider following the EOS Support Twitter in your language 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
​