Add PodAdmin gateway - expose admin fns and veto#587
Add PodAdmin gateway - expose admin fns and veto#587thomas-waite merged 39 commits intofeat-governance-upgradefrom
Conversation
thomas-waite
changed the title
thomas-waite
force-pushed
the
feat-multiple-pod-admins
branch
from
ef1ca5d to
7f9f80c
Compare
|
I think a much more scalable architecture would be to hash the podId with some salt like "ORCA_POD" and have that role be the "specific pod admin". We'd only need at most one of these roles per pod. Instead of giving ROLE_ADMIN the control over this, perhaps a better role would be "POD_ADMIN" which specifically can do all of these things. The POD_ADMIN should also be able to grant these role specific admins. So then we have the following admin priviledges for all pods: AddMember(): GOVERNOR and POD_ADMIN and "specific pod admin" |
thomas-waite
changed the title
This makes sense and I like it, it's more scaleable as you say. Implementing |
thomas-waite
changed the title
3 participants
Summary
Introduces a
PodAdminGatewaycontract, which is set as thePodAdminaddress for all deployed Orca pods.It is introduced for three reasons:
The goal is for the pods to have the following TribeRoles with the following admin priviledges :
addMember():GOVERNOR,POD_ADMINand specific pod admins granted this granular roleremoveMember():GOVERNOR,POD_ADMIN,GUARDIANand specific pod admins granted this granular roleveto():GOVERNOR,POD_VETO_ADMIN,GUARDIANand specific pod admins granted this role