With aims and domains ratified, we now have better clarity on how to proceed with the organizational structure for Orcanauts. Currently, the org-naut pod is an inactive pod with no commissioned domains. A decision needs to be made on how to handle org-naut’s on-chain presence.
- No change: We leave the org-naut pod as is, and evaluate at a later point.
- Move to a “drydock” pod: We remove it as a member from orcanauts.pod.xyz and create a new pod for stalling inactive pods.
- Add orcanauts.pod.xyz as its only member: We remove it as a member from orcanauts.pod.xyz, remove all current pod members and add orcanauts.pod.xyz as its only member.
- Expel it entirely from the organization: We remove it as a member from orcanauts.pod.xyz, remove all current pod members and transfer admin key to the Ethereum burn address.
- Number of transactions: Any on-chain transaction will cost some gas.
- Consequences: Possible effects of this approach.
|1. No change||None||Podarchy would not reflect current agreements|
|2. Move to “drydock” pod||>=4||Keeps org-naut visible but out of the way. Could become a bloated pod over time|
|3. Swap members with orcanauts.pod||>=6||Keeps the pod close and reusable, without it taking space in the podarchy|
|4. Expel entirely||5||Most complete on-chain cleanup, but we lose the option to reuse this pod|
The process would look as follows:
- remove org-naut.pod.xyz as a member from orcanauts.pod.xyz
- remove all current members from org-naut.pod.xyz
- add orcanauts.pod.xyz as a member to org-naut.pod.xyz
- transfer the admin key from zkchun.eth to orcanauts.pod.xyz
This has the most transactions, but keeps also the org-naut pod reusable for the future. Additionally, it moves the pod out of the Orcanaut podarchy, which makes it less confusing for outsiders to interpret at first glance.
The time limit for this proposal (2022-05-07T21:59:00Z) is set to be on the shorter side as it has been a discussion topic in several pod lead meetings and on Discord, where we seem to have reached general agreement.