Introduction to on-chain roles

Roles give the appropriate level of access to different contributors and entities. Roles are administrative rights granted to Safes, externally owned accounts (EOA), or other smart contracts inside the Palmera Module.

To understand roles better, we need to establish 2 types of basic relationships present within the hierarchical structure: Super Safes (parent) and subsafes (child). Let's look at the following diagram to better illustrate these ideas.

Root Safe

Root Safe

This is the Safe positioned at the top of the hierarchy structure. It can be viewed as the control tower in charge of supervising and controlling the rest of the structure.

It has admin rights over any safe located in all levels below it, additionally it can add or remove EOAs, or smart contracts from its hierarchy structure.

Super Safes and subSafes

Super Safes (parent)

A super Safes (parent Safes) refers to any Safe that has a subsafes (child safes). It can also be defined as any Safe that has rights over another Safe located one level down in the hierarchy structure. This role is useful to limit the amount of control and the kind of operations subsafes can perform.

SubSafes (child)

A subsafe is any Safe that has a Super Safe (parent Safe), in other words, a subsafe refers to any Safe which has another Safe located one level up in the hierarchy structure. This role is ideal for granting Safe certain rights while limiting the amount of control they have over the rest of the hierarchical structure.