# Recommended Folder Structure
This document outlines the recommended structure of Cosmos SDK modules. These ideas are meant to be applied as suggestions. Application developers are encouraged to improve upon and contribute to module structure and development design.
A typical Cosmos SDK module can be structured as follows:
abci.go: The module's
EndBlockerimplementations (if any).
client/: The module's CLI and REST client functionality implementation and testing.
exported/: The module's exported types -- typically type interfaces. If a module relies on other module keepers, it is expected to receive them as interface contracts through the
expected_keepers.go(which are detailed below) design to avoid having a direct dependency on the implementing module. However, these contracts can define methods that operate on and/or return types that are specific to the contract's implementing module and this is where
exported/comes into play. Types defined here allow for
expected_keepers.goin other modules to define contracts that use single canonical types. This pattern allows for code to remain DRY and also alleviates import cycle chaos.
genesis.go: The module's genesis related business logic (e.g.
InitGenesis). Note, genesis types are defined in
handler.go: The module's message handlers.
keeper/: The module's keeper implementation along with any auxiliary implementations such as the querier and invariants.
types/: The module's type definitions such as messages,
KVStorekeys, parameter types, Protocol Buffer definitions, and
module.go: The module's implementation of the
simulation/: The module's simulation package defines all the required functions used on the blockchain simulator: randomized genesis state, parameters, weighted operations, proposal contents and types decoders.
Learn about Errors