When we first sat down to talk about connecting Gno to the rest of the Cosmos ecosystem via IBC, the idea seemed straightforward. In practice, it took the better part of eight months — across four repositories and three GitHub organizations — to get from 'should just work' to actually working.
AtomOne v4 is built on three distinct pillars — a full upgrade to Cosmos SDK v0.50 and IBC-go v10, the introduction of Governors as a governance-specific delegation mechanism decoupled from staking, and a set of economic controls aligned with the AtomOne Constitution.
Interchain Security showed that shared security models can work technically, but also that incentives matter. VaaS simplifies assumptions and treats validation as an explicit service.
The internet used to feel different. Before timelines, algorithms, the performative haze, there was honesty. Words mattered. You didn’t need a strategy to speak your mind. That’s what we’re building towards again.
GovGen governance-only chain is distinct from the AtomOne hub chain and aims to help define and finalize the constitution of AtomOne before AtomOne itself launches.
AiB will vote NWV on prop 848, $ATOM “Halving.” We value Cosmos' core components of security, sustainability, and decentralization and cannot support a proposal that threatens these foundational pillars and places the network at risk.
To take this technology to the next level and make blockchains more accessible to a wider net of developers, AiB supports Ignite, a feature-packed CLI tool for building sovereign blockchains.
The Cosmos Hub community has found itself facing some difficult choices lately. While AIB voted and recommended NWV on prop82, we recognize that some of the ideas in the ATOM 2.0 whitepaper deserve to be explored.