Configuration and Management

spherex Protect can be configured either by using the dashboard or or directly interacting with the spherex smart contract administrative functions.

Admin permissions are asinged to on-chain entities (EOA/contract), spherex Protect is therefore designed to comply with any governance structure. The role based access control includes two roles:

Administrator - The highest permissions entity in both spherexProtected and spherexEngine. The admin assigns and revokes the operator role. spherex recommends the Admin to be solely under you control.

Operator - Is in charge of the routine maintenance of the spherexEngine.

spherexProtected Permissions

Administrator

• transferSphereXAdminRole - Transfer admin role to address

• changeSphereXOperator - Change the operator role's address

Operator

• changeSphereXEngine - Set engine's address

spherexEngine Permissions

Administrator

• grantRole - Assign Operator role to an address (assign zero address to revoke operator role without assigning new operator)

Operator

The spherexEngine operator can perform the following actions:

• configureRules - Configure which advanced attack mitigations are active

• deactivateAllRules - Disable the engine

• addAllowedSender - Add protected contract address

• removeAllowedSender - Remove protected contract address

• addAllowedPatterns - Add safe execurtion fingerprints

• removeAllowedPatterns - Remove safe execurtion fingerprints

• grantSenderAdderRole - Set factory contract address

• setprotectedsigs - set the list of protected function (only in proxy mode)