|
|
||
|---|---|---|
| .. | ||
| address | ||
| appmodule | ||
| branch | ||
| comet | ||
| context | ||
| event | ||
| gas | ||
| genesis | ||
| header | ||
| legacy | ||
| log | ||
| registry | ||
| router | ||
| server | ||
| store | ||
| testing | ||
| transaction | ||
| CHANGELOG.md | ||
| go.mod | ||
| go.sum | ||
| Makefile | ||
| README.md | ||
| sonar-project.properties | ||
Cosmos SDK Core
The cosmossdk.io/core Go module defines essential APIs and interfaces for the Cosmos SDK ecosystem. It serves as a foundation for building modular blockchain applications.
Key features and principles:
- Provides stable, long-term maintained APIs for module development and app composition.
- Focuses on interface definitions without implementation details.
- Implementations are housed in the runtime(/v2) or individual modules.
- Modules depend solely on core APIs for maximum compatibility.
- New API additions undergo thorough consideration to maintain stability.
- Adheres to a no-breaking-changes policy for reliable dependency management.
- Aimed to have zero dependencies, ensuring a lightweight and self-contained foundation.
The core module offers the appmodule and appmodule/v2 packages that include APIs to describe how modules can be written.
Additionally, it contains all core services APIs that can be used in modules to interact with the SDK, majoritarily via the appmodule.Environment struct.
Last but not least, it provides codecs and packages for the Cosmos SDK's core types (think of, for instance, logger, store interface or an address codec).
Developers and contributors approach core API design with careful deliberation, ensuring that additions provide significant value while maintaining the module's stability and simplicity.