Adding A New Application Level Rule To The Rule Processor Diamond

​

Purpose

There are several updates that need to take place in order to add a new applicaiton level rule. In this document we’ll be covering the steps required to update the protocol rule processor diamond including: updating the code for the appropriate facets and upgrading the diamond. This document will walk through the process step by step. (We will be using an existing rule, Max Value By Risk Score, as our example)

​

Creating The Rule

​

Updating Diamond Storage

The first step is to update the diamond storage to account for the new rule. We’ll need to update RuleStoragePositionLib. For our example we would first add the following constant to the top of the contract to define the storage position for our Account Max Value By Risk Score rule:

bytes32 constant ACCOUNT_MAX_VALUE_BY_RISK_SCORE_POSITION = bytes32(uint256(keccak256("account-max-value-by-risk-score")) - 1);

Next we’ll want to define the storage structure for our rule. For our example we would add the following struct to IRuleStorage:

    struct AccountMaxValueByRiskScoreS {
        mapping(uint32 => IApplicationRules.AccountMaxValueByRiskScore) accountMaxValueByRiskScoreRules;
        uint32 accountMaxValueByRiskScoreIndex;
    }

Finally we’ll want to add a function to retrieve the storage for our rule to RuleStoragePositionLib.sol. For our example we would add the following function:

    function accountMaxTxValueByRiskScoreStorage() internal pure returns (IRuleStorage.AccountMaxTxValueByRiskScoreS storage ds);

​

Facet Updates

The next step is to update the AppRuleDataFacet contract to include a function that can be used to create an instance of our new rule and register it with the diamond. For our example we would add the following function:

    function addAccountMaxValueByRiskScore(address _appManagerAddr, uint8[] calldata _riskScores, uint48[] calldata _maxValue) external ruleAdministratorOnly(_appManagerAddr) returns (uint32);

The next step is to add the functions necessary to manage the rule to ProtocolApplicationHandler. The functions consist of: setRuleName, activateRuleName, getRuleNameId, isRuleNameActive (RuleName being replaced by the name of the specific rule instace the file is handling).

The following function uses the ruleId we received when we created the instance of the rule to set the instance in the diamond and activate it:

    function setAccountMaxValueByRiskScoreId(uint32 _ruleId) external ruleAdministratorOnly(appManagerAddress);

The following function is used to activate/deactivate the instance of the rule that’s already set in the diamond:

    function activateAccountMaxValueByRiskScore(bool _on) external ruleAdministratorOnly(appManagerAddress);

The following function is used to retrieve the rule id for the Account Max Value By Risk Score Rule currently set on the diamond:

    function getAccountMaxValueByRiskScoreId() external view returns (uint32);

The following function is used to check whether the rule is currently active:

    function isAccountMaxValueByRiskScoreActive() external view returns (bool);

The next step is to update the appropriate function in ProtocolApplicationHandler to include a check for our new rule. For our example we’ll be updating the _checkRiskRules function.

    function _checkRiskRules(address _from, address _to, uint128 _balanceValuation, uint128 _transferValuation) internal;

​

Upgrading Existing Diamonds

Once the above changes have been made to add the new rule, in order to make the rule available we will need to upgrade the existing diamond instance. Step by step instructions on this upgrade are provided in RULE-PROCESSOR-DIAMOND-UPGRADE