Multiplayer Governance of IP Assets

[jzhao23]

When considering the solution for how multiple addresses can govern an IP Asset, we first need to delineate a clear philosophy about what lives on the smart contract ("protocol") level, the platform ("API") level, and what lives on the application logic ("app") level.

The protocol governs all core legal and economic primitives, both of which the notion of governance (co-ownership) coincides with.

The API should simplify the protocol's core logic into common workstreams, making the protocol easily useable.

The app should add bespoke logic that is not generalizable at either the protocol or API level. As much should belong to the application as possible, in an effort to minimize the protocol and make it more elegant and flexible.

Therefore, multiplayer governance of an IP Asset should be reflected at the protocol level via multisig ownership, taking lessons from DAOs. However the UX of this should be dramatically improved by the API, which can instantiate simple voting smart contracts for common use cases. In other words, ownership is reflected on the protocol level and made useable/seamless by the API. Any very specific logic should be done by the app - if the API's standard governance templates (and these should be extremely simple) are too simple, the app should create custom governance logic.