# Cosmos DAO Module I want ot propose that Cosmos could be particularly suited for DAO implementations using the [Object Capability](https://en.wikipedia.org/wiki/Object-capability_model) (Ocap) Model. Ocap is a security and concurrency model that operates at the level of the OS Kernel. The Inter-blockchain Communications (IBC) Protocol under development will be based on OCap. The key concept of OCap is that scopes of cababilities can be limited at an extremely granular level, which produces highly secure computation. Capabilities are transferable and can be securely communicated across systems, as invariants that achieve concurrency - even if communications are asynchronous. Using OCap within smart contracts enables highly secure and concurrent transfers of electronic rights. Essentially all transactions are defined as transfers of rights. This is a powerful paradigm - especially in the context of governance operations. I have recently written about the idea in my Medium Article [Cosmic Rights](https://medium.com/ixo-blog/cosmic-rights-7810fc0f4241). From what I understand, DAOs are all about defining electronic rights, in order to achieve system governance, control and operational autonomy. Building the Argon DAO framework into a Cosmos SDK module is both necessary for Cosmos Networks and an opportunity for Aragon to take DAO mechanisms to the next evolution. For an excellent overview of the Cosmos architecture, [check out this presentation](https://www.slideshare.net/tendermint/many-chains-many-tokens-one-ecosystem-132725139) from Sunny. Developing a Cosmos SDK module in Go is really straightforward and the Cosmos team has recently improved the developer experience. [Check out this tutorial](https://github.com/cosmos/sdk-application-tutorial). One of the hackathon participants developed this [module boilerplate generator](https://github.com/shanev/cosmos-gen), which could be useful.