Migration is complete. Lasna is now running on the Omni fork.

What's Different

The biggest change is that the RVM is gone. Reactive contracts now deploy once, to a single environment, as standard Solidity targeting version 0.8.29, and dual deployment is a thing of the past. Standard tooling works out of the box too: Hardhat, Foundry, and Remix all work without workarounds, and most of the custom RPC methods have been dropped. 

Subscriptions keep the same signature, and a new system contract now handles them. Old-style callbacks still work, and new contracts can call a system contract method instead of emitting a raw event. Existing deployments keep working as before, since we support legacy functionality. Callback delivery, destination revert handling, and the gas model are unchanged too. 

Time to Break Things

This is the best moment to put Lasna through its paces. Deploy contracts, set up subscriptions, fire callbacks, and push the faster blocks. Testnet is where surprises are cheap, and what you find now might shape what reaches the mainnet.

What’s Next?

As always, no promises can be made, however our current plans are to launch the full mainnet Omni-Fork by the end of the month, pending stress-testing of Lasna testnet. If plans change we’ll keep you updated.

About Reactive Network

Reactive Network is an EVM automation layer built around reactive contracts — event-driven smart contracts for cross-chain execution. It runs on CometBFT consensus, providing deterministic finality with roughly one-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, issuing cross-chain callback transactions when their conditions are met.

Website | Blog | X | Telegram | Discord | Docs

Build once — react everywhere!