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 several months. 

If you've been following our technical roadmap, this is where the technical plans become something you can actually deploy contracts to.

Major Updates

CometBFT consensus with full EVM compatibility. The consensus layer has been replaced, but the execution environment remains standard EVM. Your Solidity contracts, your tooling, your workflows – all unchanged. CometBFT gives us instant block finality (no more reorgs) and block times of approximately 1 second, down from the previous ~7 seconds.

No more RVM. Reactive contracts no longer require dual deployments across RVM and Reactive Network. Everything deploys to a single environment, the way standard smart contracts do. If you've found writing reactive contracts cumbersome in the past, this is a significant simplification. The developer experience is now much closer to what you're used to on any other EVM chain.

Standard tooling works out of the box. With the RVM gone, there's no need for custom RPC methods or manual trace inspection. Hardhat, Foundry, Remix, Blockscout, Foundry's `cast` – everything works as expected.

Existing subscription and callback formats supported. Subscription call signatures remain the same. Callbacks in the old format will continue to work. New contracts can use the new system contract interface for a cleaner experience, but nothing is being broken.

Where to Dig in 

We're particularly interested in feedback on:

• Deploying existing contracts and verifying they behave as expected on the new architecture
• The new reactive contract development flow without RVM
• Interaction with the new system contracts for subscriptions and callbacks
• General tooling compatibility across your development setup

How to Connect

Head over to Reactive Docs to connect instantly, or plug in the network details manually:

• Network Name: Reactive Lasna
• RPC URL: https://lasna-omni-rpc.rnk.dev
• Chain ID: 5318007
• Currency Symbol: lREACT
• Block Explorer: https://lasna-omni.reactscan.net

Lasna testnet runs the exact architecture mainnet will use. Every piece of feedback you give directly shapes what ships to production. 

Key Personnel Update: Thank you to our departing CEO Rong Kai Wong

Today we announce that, by mutual agreement, Rong Kai Wong is stepping down from his role as CEO of Reactive Network.

Rong Kai has been with this team since the PARSIQ days, first as COO and then as CEO across three product iterations. Under his leadership, Reactive Network grew from two use cases at launch to more than sixty within a year, and the protocol helped establish reactive contracts as a category in their own right. Rong Kai pushed consistently for accountability, dedication and transparency in everything Reactive Network did, and the protocol is stronger for it.

This transition comes as Reactive Network moves into its next chapter of growth and leadership. Reactive Network has historically operated with a distributed leadership structure between executive leadership, the Board, and core contributors, and the network is fully prepared for its next operational phase.

As set out in our recent roadmap, the protocol is decentralising: open-sourcing the codebase, migrating to CometBFT, and shifting decision-making toward the Foundation, contributors, and community governance. Within this framework, the Foundation takes on day-to-day operational matters, while strategic governance previously held at the Board transitions to the DAO and community.

Going forward, Daniil Romazanov (CTO) will lead the delivery and operations of Reactive Network’s Omni fork through the Foundation. 

Rong Kai remains deeply supportive of the vision and technology being built at Reactive Network. The transformational technology, created by a team of brilliant engineers, will change the way blockchain operates at a fundamental level. He looks forward to seeing the next generation of capabilities reach mainnet, and wishes the colleagues he has worked alongside for the past five years every success in the chapters ahead.

The work continues.

Reactive Network & Rong Kai Wong

About Reactive Network

Reactive Network is an EVM automation layer built around reactive contracts, event-driven smart contracts for cross-chain, on-chain automation. It runs on CometBFT consensus, providing instant finality and roughly 1-second block times while maintaining full EVM compatibility.

Reactive contracts subscribe to event logs across EVM chains and execute Solidity logic automatically when matching events occur, deciding autonomously when to send cross-chain callback transactions. This model supports conditional cross-chain state changes and continuous cross-chain workflows.

Website | Blog | X | Telegram | Discord | Docs

Build once — react everywhere!