There is a difference between a company that uses the Cosmos SDK and a company that wrote parts of it. The first reads the documentation. The second wrote the modules the documentation describes, found the bugs before they hit your mainnet, and stayed through the protobuf migration that touched nearly every line of the codebase. Vitwit is the second kind.
When you build on a chain, you are inheriting every design decision and every latent bug in its core modules. The team that wrote those modules knows the keeper internals, the migration paths, the parameter footguns, and the consensus-critical edges — because they argued about them in the original PRs. That knowledge does not come from reading a README. It comes from having shipped the code and lived with the consequences.
When a chain upgrade breaks something, or a module behaves in a way the docs don't explain, the team that authored that module isn't filing a support ticket with someone else. They are reading code they wrote. This is the practical case for working with upstream contributors rather than integrators.
Our development work centered on modules that ship with the SDK and run on every chain that builds on it.
Authorization and fee-granting primitives that let accounts delegate the right to execute messages and pay fees on behalf of others. These underpin gasless transactions, managed accounts, and a huge range of UX patterns.
On-chain multisig and policy-based group accounts — the building block for DAO-style decision-making at the protocol level. Standard on nearly every Cosmos chain today.
The module that coordinates chain upgrades. If you've ever watched a Cosmos chain hard-fork cleanly at a planned height, this is the machinery underneath. Getting it wrong halts the network.
Newer architecture work on fee distribution, the next-generation server framework, and the accounts abstraction — the parts shaping where the SDK is heading.
Chain-agnostic Go library for building payment facilitators across EVM, Solana, and Cosmos SDK networks. First-class Cosmos-native token support, on-chain payment verification, settlement, and pluggable logging.
View on GitHub →Anonymous governance voting using zero-knowledge proofs — protects voter identity while preserving vote integrity. Built natively on Cosmos.
View on GitHub →ZK-SNARK-based bridge for cross-chain communication between Cosmos EVM chains and Ethereum, verifying state transitions without trusted intermediaries.
View on GitHub →Wallet-agnostic gateway to the Cosmos ecosystem — lets users interact with any Cosmos SDK chain through the wallet of their choice.
View on GitHub →Monitoring and performance dashboard for validators who can't afford to build their own. Frees operators from manual status-checking and surfaces the parameters that affect performance and security.
View on GitHub →Contribution isn't only code — it is also proposing where the protocol should go. We've put forward research and improvements that shape the next version of the ecosystem.
The same instinct shows up in our bug findings: network halt from a PowerReduction parameter change, non-determinism when starting a new chain, state-load failures during upgrades, and a token-invalidation bug in the Game of Zones Hub. Finding these bugs before they hit your mainnet is exactly the work that keeps the ecosystem running.
A lot of infrastructure providers can run a node. Far fewer wrote the module the node depends on, found the bug that would have halted it, and proposed the standard that the next version will adopt. When you work with Vitwit, the team operating your validators, relayers, and chains is the same team that has spent nine years inside the codebase that all of it runs on.