# OpCo – A DAO-adjacent Entity for Strategy Execution

**URL:** <https://forum.arbitrum.foundation/t/opco-a-dao-adjacent-entity-for-strategy-execution/27361>\
**Category:** Finalized AIPs\
**Created:** [October 30, 2024, 9:23pm UTC](https://forum.arbitrum.foundation/t/opco-a-dao-adjacent-entity-for-strategy-execution/27361 "2024-10-30T21:23:24Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![JoJo](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/jojo/32/2666_2.png) [@JoJo](https://forum.arbitrum.foundation/u/JoJo)\
**Post date:** [November 1, 2024, 1:15am UTC](https://forum.arbitrum.foundation/t/opco-a-dao-adjacent-entity-for-strategy-execution/27361/7 "2024-11-01T01:15:09Z")

</div>

Gm Entropy. That took a long time to read it all. Only started scratching the surface and likely will go over it again with new observations and questions.

> [@Entropy](#):
>
> most DAO programs operate in silos, leading to, among other things, redundant efforts and non-existing cross-initiative resources

This is one of the key reason why we need the OpCo

> [@Entropy](#):
>
> The DAO also generally depends on a single initiative leader for the continuation of a successful program, while some initiatives don’t even have clear owners

Solving ownership is definitely first step. Accountability is right after that, most of the time they match, but if and when they match I can tell that so far we haven’t build any structure (including comp) that would favor proper accountability.

> [@Entropy](#):
>
> It is of utmost importance that Arbitrum DAO maintains a decentralized and bottoms-up system for bootstrapping new […]. For the avoidance of doubt, the DAO would always have ultimate authority over OpCo.

This is definitely the biggest risk of the OpCo: becoming an entity that just sucks everything internally. To me, the biggest work will be not to make it work, but to establish the right boundaries for it to not become the decision maker/executor in place of the DAO.

> [@Entropy](#):
>
> it is expected that delegates vote against such a proposal if it can be better executed via OpCo’s involvement.

This will be quite tricky, initially, to evaluate from the DAO standpoint.

> [@Entropy](#):
>
> Chief Chaos Coordinator

Could vote on the proposal just for this tbh

* * *

Now a few questions here

> [@Entropy](#):
>
> OpCo’s main mandate is to enable the execution of DAO-defined strategies within the Financial Management and Ecosystem Support categories when requested by delegates.

While you explain the why of this narrowed choice, i honestly see opco being able to help in other sectors as well. Do you think it would be possible to insert some degree of flexibility for which, if the dao really wants it, OpCo would be able to tap and help/manage specific initiatives outside the 2 categories above?

> [@Entropy](#):
>
> However, as mentioned earlier, the DAO can roll any service provider or individual contributor into OpCo by passing an onchain vote.

Does this mean that OpCo will be responsible for the overviewing of this contracted sp/individual? If not I might have missed the main value point of this, beside coordination.

All in all i think the proposal is well thought. I am unsure about the categorization of grants outside of ecosystem growth, would dare to say it could fall into it, but maybe is just semantic.

It poses, tho, the question: if the dao feels like this type of internalization is the way forward, for grants or other operation outside the opco structure, what would be the way forward? Enlarge this structure, or create a parallel one?

As said will come back again to all of this. For now thank you for tackling a topic that is not only needed but also complex to address, in a way that seems reasonable (defining a specific scope of operations).

---

_[View the full topic](https://forum.arbitrum.foundation/t/opco-a-dao-adjacent-entity-for-strategy-execution/27361)._
