issues : 10
Great issue: Segregate Master Admin into Functional Roles
Description
High-frequency operational tasks and high-risk structural changes share the same Admin role check. This increases the "blast radius" for a single compromised key and forces the master admin into frequent on-chain activity, increasing exposure risk.
Requirements and context
- Properly utilize
MarketAdmin and FeeAdmin roles for operational tasks.
- Reserve the master
Admin role for structural changes like upgrades.
Suggested execution
- Fork the repo and create a branch:
git checkout -b fix/issue-10-role-segregation
- Update authorization checks in admin modules.
Implementation changes
- Modify
lib.rs and submodule admin.rs to split authorization logic.
Test and commit
- Verify that a
FeeAdmin cannot perform a contract upgrade but can update fee tiers.
Example commit message
fix: implement granular role-based access control for administrative tasks
Guidelines
- Principle of Least Privilege.
- Timeframe: 72 hours.
issues : 10
Great issue: Segregate Master Admin into Functional Roles
Description
High-frequency operational tasks and high-risk structural changes share the same
Adminrole check. This increases the "blast radius" for a single compromised key and forces the master admin into frequent on-chain activity, increasing exposure risk.Requirements and context
MarketAdminandFeeAdminroles for operational tasks.Adminrole for structural changes like upgrades.Suggested execution
git checkout -b fix/issue-10-role-segregationImplementation changes
lib.rsand submoduleadmin.rsto split authorization logic.Test and commit
FeeAdmincannot perform a contract upgrade but can update fee tiers.Example commit message
fix: implement granular role-based access control for administrative tasks
Guidelines