Specification for the Modular Financial Contract Protocol is divided into the following areas -
The MFCP is compliant on all Ethereum based chains and the Network enabled Page, specifies the list of networks the MFCP is deployed upon.
In order to function with the MFCP, a specific set of Contracts needs to be pre-deployed and the Deployed Contracts page, specifies the list of Contract deployed, accross various networks.
Amongst the deployed contracts, there are certain contracts which would enable creation of further contracts by virtue of factory contracts. Hence the total types of contracts supported by the Modular Financial Contract protocol, is higher, than the total number of contracts deployed. The total types of contracts are registered in governance contract and are depicted in the Registered Contracts page.
Governance Contract of the MFCP, has MAC based permissioning system in place, which is depicted in Permissioning section. There are two forms of permissioning , Object based labels and Subject based labels. Subject based labels are associated to addresses of the users (who mostly are governing entities to the protocol), while object based labels are associated to function within contracts and are a preconditional checks for execution of that specific governance function.
Governance Contract of the MFCP, also has a rule engine which specifies the rules for communication between various contracts of the MFCP. These rules, provide edit rights to the contract. Rule Engine sections specifies all such rules pertaining to the MFCP.
The MFCP, provides various modules, across various lifecycle stages of an Asset, made using The MFCP. The Modules section depicts all modules supported by the MFCP and their associated parameters.