Departments
Last updated
Last updated
Departments are subsets of Verified Contributors, where each department has its own "tag" (e.g. DISPUTE for the dispute department and EXPERT for the expert department). These tags can be applied to and removed from any Verified Contributor NFT by the department itself, allowing the department to pick its own members, with the restriction that they hold a Verified Contributor NFT.
The department owner, the DAO formed by all Verified Contributors, holds the permission to manage these tags, allowing or revoking a certain address from being able to grant a certain tag. Hence creating and removing a department is done by a proposal in the department owner DAO. The smart contracts required to be deployed for the new department can be found .
Departments provide the opportunity to complete tasks as a group and pay all members a fixed salary. For this to be sustainable, the department members should earn more together than the combined salary. Having a consistent income is preferred by most people and will allow members to work on bigger tasks without having to worry about their monthly expenses.
Most of the departments will mainly be taking tasks related to Openmesh products, for example, the technical departments would be requested to implement new features. These requests are expected to mostly come from the Openmesh community DAO (governed by OPEN token holders), but other entities that have an interest in having these features developed can also create such tasks.
Similar to the optimistic actions of the , a department member can perform a certain action if no department member rejects it within 7 days. For departments, these actions are limited to interactions with the OpenR&D smart contract (based on address).
Department members are recommended to have an OpenR&D task with their department to handle their payments. This task should hold enough funding for at least 1 payout, in case they did their work but the department refuses to pay them. For this to be possible, the task should clearly describe what they are expected to do. They can then make use of dispute resolution to still get their payment. As payments, top-ups, and deadline extensions related to managing these members are regular occurrences, they can be done optimistically.
Any other actions will need at least 20% of all department members to vote on it and the majority (>50%) to approve it. In case the NFT of a department member has been burned, the tagging contract needs to be made aware to update the total department members for this threshold to be 20%.
The only action that is expected is the granting and revoking of their tag, to add or remove department members.
The department members are in complete control of this DAO, so they can decide on any other actions they want to perform. They are also able to change the governance thresholds or add more optimistic actions if they prefer.
The departments all have a smart account for a deterministic address across chains (controlled by the DAO on Polygon and controlled by the crosschain account on Ethereum). This smart account holds all funds and permissions to be able to easily change the way it is controlled (for example, if we wish to change DAO platform in the future, allows us to keep the same address, permissions, and assets). This smart account also supports "modules" to extend it.
Using we have a smart contract on Ethereum for the department (which are deployed on Polygon). This allows them to actually take tasks of the Openmesh community DAO (which is deployed on Ethereum) and hold assets which do not exist on Polygon. They can also use any Ethereum dApps this way, paying Polygon gas fees for governance and only the Ethereum gas fee once for actually executing the action.