Somewhere beneath the surface of over a hundred blockchain networks, from Cosmos Hub to Osmosis to Celestia, there's a consensus engine quietly doing the heavy lifting. It's called CometBFT, and unless you've spent time wandering the Cosmos ecosystem, you've probably never encountered
Today, May 25th, we're rolling out the Omni fork for Reactive Lasna. The first testnet built on Reactive Network's new CometBFT-based architecture is live and ready for developers to start building, testing, and experimenting with the changes we've been working toward over the past
Reactive Network is getting a new engine. We're calling this the Omni fork. The consensus layer, the developer experience, and the way reactive contracts work are all being rebuilt. This document covers the technical specifics: what's changing, what stays the same, and what it means if
We spent 2025 building, shipping, and watching a growing cohort of developers push the network forward, stress testing its functionality. As we close out this inaugural year, we've taken stock: what's working, what needs improvement, and where this goes from here. This roadmap is a story
In DeFi Hack Postmortem Part 1, we looked at how Reactive Contracts address the root cause of bridge exploits: the gap between what a validator claims has happened and what actually has happened on-chain. That's the prevention side: stopping the hack before it starts. But prevention only works