// the find
cosmos/cosmos-sdk
Framework for building performant, customizable blockchains with native interoperability
Cosmos SDK is the standard Go framework for building sovereign, application-specific Layer 1 blockchains. It gives you a modular system of pre-built modules (staking, governance, bank, etc.) wired together via a protobuf-based message router, with CometBFT BFT consensus underneath and IBC interoperability baked in. In production use across 200+ chains since 2019, so this is not experimental infrastructure.
Battle-tested at scale — Cosmos Hub, Osmosis, dYdX, and hundreds of others run on it in production, so the edge cases around validator slashing, governance attacks, and upgrade mechanics have actually been hit and fixed. The module system is genuinely composable: you wire modules in via depinject/app wiring and each module owns its own state namespace, which makes it tractable to reason about state isolation. The protobuf-first API design means clients, light nodes, and cross-chain protocols all work from the same schema, and the generated pulsar code handles serialization without reflection overhead. The `baseapp/txnrunner/blockstm.go` suggests they've added Block-STM parallel transaction execution, which is a meaningful throughput improvement over the old sequential model.
Breaking changes are an ongoing tax — the README's own warning about 'still making some breaking changes' understates how painful SDK upgrades have been historically; UPGRADING.md exists for a reason and it's long. The dual protobuf code generation (legacy `.pb.go` plus the newer `.pulsar.go` files) is confusing and there's no clean story yet for when to use which. Enterprise modules in `enterprise/` have different licensing terms that are easy to miss when evaluating for open-source projects. The learning curve is steep: you need to understand ABCI, CometBFT, protobuf, depinject, and the module manager before you can write a non-trivial module, and the docs, while extensive, assume you already know why you're here.