Customization Options

​

Rule Modification

To modify an applied rule, simply create the new rule with the desired settings and apply it.

1. Application Rules:
   1. Create Application Rules
2. Token Specific Rules:
   1. Create Token Specific Rules

​

Rule Deactivation

To deactivate an applied rule, invoke the activation function and send it a parameter of false. This deactivates the rule, but it can be reactivated at any time.

1. Application Rules
   1. Consult the Application Rule Directory for the activation function name and invoke it on the AppManager created during deployment.
      1. This examples uses Account Max Transaction Value By Risk Score:

      cast send 0xb7278A61aa25c888815aFC32Ad3cC52fF24fE575 "activateAccountMaxTxValueByRiskScore(uint8[],bool)" [0,1,2,3,4] false --private-key 0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba --from 0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc  --rpc-url  $ETH_RPC_URL
      

2. Token Specific Rules
   1. Consult the Token Specific Rule Directory for the activation function name and invoke it on the Token Application Handler created during deployment.
      1. This example uses Account Min Max Token Balance:

      cast send 0x82e01223d51Eb87e16A03E24687EDF0F294da6f1 "activateAccountMinMaxTokenBalance(uint8[],bool)" [0,1,2,3,4] false --private-key 0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba --from 0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc  --rpc-url  $ETH_RPC_URL
      

​

Activating a Deactivated Rule

To activate a deactivated rule, invoke the activation function and send it a parameter of true. This activates the rule.

1. Application Rules
   1. Consult the Application Rule Directory for the activation function name and invoke it on the AppManager created during deployment.
      1. This examples uses Account Max Transaction Value By Risk Score:

      cast send 0xb7278A61aa25c888815aFC32Ad3cC52fF24fE575 "activateAccountMaxTxValueByRiskScore(uint8[],bool)" [0,1,2,3,4] true --private-key 0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba --from 0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc  --rpc-url  $ETH_RPC_URL
      

2. Token Specific Rules
   1. Consult the Token Specific Rule Directory for the activation function name and invoke it on the TokenApplicationHandler created during deployment.
      1. This example uses Account Min Max Token Balance:

      cast send 0x82e01223d51Eb87e16A03E24687EDF0F294da6f1 "activateAccountMinMaxTokenBalance(uint8[],bool)" [0,1,2,3,4] true --private-key 0x8b3a350cf5c34c9194ca85829a2df0ec3153be0318b5e2d3348e872092edffba --from 0x9965507d1a55bcc2695c58ba16fb37d819b0a4dc  --rpc-url  $ETH_RPC_URL
      

​

NFT Functionality

Protocol supported NFT’s implement OpenZeppelin AccessControl, ERC721, ReetrancyGuard, and ERC721Enumerable. These interfaces may be utilized in application NFT’s.

Additional logic may be added to the constructor, but it MUST still invoke the ApplicationERC721 constructor

​

Deploying Custom Application and Token Rules

Sometimes no matter what, there are just modifications that you would like to make that fall outside of the scope of what is supported by the protocol. For an example of updating the application level rules and deploying them, it is recommended to read about applying app rules to the protocol diamond. If you are interested in adding token level rules, first you must add the rule to the handler and then be sure to add the rule to the rule processor.