Identify tactics to simplify new endpoint creation

Owned by Ed Rotthoff
Last updated: Mar 07, 2022
1 min read

Purpose:

The purpose of this document is to capture the strategies and tactics that are applicable for the Fio Protocol in consideration of eliminating the need for changes to core code in the protocol when endpoints for signed calls are being added into FIO.

 

Issue:

presently engineers must make code changes to the chain_plugin, chain_api_plugin, and clio executable when adding new endpoints to the Fio Protocol.

 

Details of issue:

For any new endpoint engineers must consider to make the following changes to the C++ core code.

Affected FIO components

Chain plugin

Chain API plugin

clio command line executable

Required Changes

Add the parameters used in the new call. (chain plugin)

Add the results returned by the new call. (chain plugin)

Add the name of the new call. (chain api plugin)

Optional changes

Integrate the new call into the clio command line tool. (clio command line tool)

 

Objective

We want to remove the necessity to have to recompile the core code of FIO when new signed calls are added into the protocol. Put another way, we want to be able to use state tables, and other configuration information in combination with calling actions provided in FIO system contracts, to add a new endpoint without having to deliver a new version of the core code when endpoints are added.