Note: Communities achieve full sovereignty of their DAOs right out of the gate, whether this infrastructure is under the control of the SNS DAO or not. As I’ve stated, each Personal DAO is fully autonomous and does not rely on this infrastructure for sustainability.
This infrastructure is part of a service that is offered by a private company. Personal DAOs deployed to the internet computer have the full freedom to contract any private company they wish when seeking to maintenance and/or update their DAOs. I’ve created the Personal DAOs to make it easy for DAO communities to reach consensus on who they wish to contract, how they assign canister access to said contractor, how they revoke canister access to said contractor and how they compensate said contractor. All of the tooling needed for Personal DAO communities to explore alternative options for development services are provided right out of the box for each and every DAO community.
In theory, if you (@rem.codes ) disapprove of the updates being offered by our dev team, you have all of the tools needed to offer a competing service to any of the Personal DAOs deployed to the internet computer:
- you pull the open sourced codebase and make the changes requested by the community.
- the community submits a proposal to grant you canister control so that you may push updates.
- the community submits a proposal to revoke your access to canister control after you’ve pushed the updates.
- the community submits a proposal to compensate you from their multisig wallet in accordance to whatever agreement you reached with them.
Although it’s not necessary for affording sovereignty to each Personal DAO community, I have considered placing this infrastructure under the control of the SNS DAO (and I’m still considering it), but at this time, i will not be doing so. The reason is that it introduces the possibility of some legal liabilities that could jeopardize the viability of the project.
Our compliance team consists of two legal experts, one is actively pursuing regulatory compliance in the EU. The other is actively defending against regulatory persecution in the US.
Placing the aforementioned infrastructure under the control of the SNS DAO removes our team’s ability to ensure that recommended measures are taken to avoid the proliferation of this technology into jurisdictions sanctioned by the US and EU.
In such a case, this would curtail our efforts towards regulatory compliance before being able to achieve them.
For this reason, it is imperative that we be able to practice discretion in how these DAOs are introduced to the marketplace.
Note: Accessibility to this technology is a priority. We want people of all nations to be able to access this technology, which is again why the codebase is open sourced and the DAOs are very easy to deploy via the CLI with very little technical knowledge required. Any developer or community can permissionlessly pull the code, deploy their DAO and plug right into the ecosystem.
As a doxxed team, building a product that challenges the viability of big tech, and big finance, and regularly interacts with institutions, we do need to maintain a reasonable level of plausible deniability in the event that bad actors leverage these DAOs for nefarious purposes. And we’ll do that by ensuring that the people who are able to purchase the DAOs via our no-code solution are from countries that aren’t subject to sanctions by the US or EU.
We intend to use positive working examples of these DAOs to bolster our efforts for greater regulatory approval.
Our current approach is to onboard universities throughout the US who are looking to leverage these DAOs as a way to monetize the research produced by their faculty. The possibility for sovereign AI agents that can be queried for a fee has been attractive to several universities throughout three distinct regions of the US.
These efforts stand to be undermined by a single organization on the terrorist list gaining access to these DAOs via a no-code solution built by our team.
in the short term (< 6 months) I plan to introduce the no-code DAO deployment solution for people from countries that are not subject sanctions by the US or EU.
But as for where we are with the current phase of development, it would be premature (and unnecessary for achieving sovereignty) to have this infrastructure be controlled by the SNS DAO. There’s still testing and debugging to do before it’s ready to go live.
As a courtesy, I’ve been deploying DAOs for members of the ICP community upon request and a video call meeting.
Before the investors’ final neurons are unlocked (within 6 months of the launch) the process will be automated and the no-code DAO deployment solution will be offered but it may or may not be decentralized depending on a few factors.
In either case, holders of the token will be able to exercise the token’s utility to purchase their own DAOs and computational resources, which is the purpose of introducing the token.