Press
Heads up: Lasna goes offline for migration on Wednesday, October 7th, at 12:00 UTC. Why Pause? Back on May 26th, we announced the launch of a new version of Lasna testnet, running on our new CometBFT-based architecture. Now, in preparation for our mainnet migration, the original Lasna testnet, which
Fundamentals
On August 12th, Solana came within four and a half percentage points of losing the ability to finalize blocks, and almost nobody noticed. The network kept producing blocks and processing transactions the entire time, the status page recorded nothing unusual, and for roughly half an hour the margin between business
Fiet is integrating with Reactive Network to automate one of the hardest problems in DeFi for everyday traders: guaranteeing liquidity is settled promptly without sacrificing user experience. By deploying Reactive Contracts (RCs), Fiet will remove the need for traders to manually claim funds when liquidity that was temporarily unavailable, becomes
We recently took a look back at some of the utility introduced to Reactive Network so far in 2025, now it's time to look ahead. By 2026, Reactive Contracts are no longer an experiment. They are part of the baseline expectations for how on-chain systems behave. Contracts that
Reactive Network began with a simple observation: most smart contracts spend their lives waiting. They wait for users, bots, or keepers to notice something has changed and to push them into action. Reactive Contracts invert that relationship. They remain alert, notice changes on-chain as they happen, and respond automatically. In
Blockchain is reaching a tipping point. After years of experimentation, the first signs of institutional-grade infrastructure are beginning to emerge. Two markets stand out as the drivers of this shift: tokenized real-world assets (RWA) and decentralized finance (DeFi). The challenge, however, is no longer raw throughput. The bottleneck is coordination.
Reactive Staking Season 8 closes at block 6,816,896 on Sunday, September 13th, and its one-month pool expires with it. Season 9 picks up on the very next block, so stakers can roll straight into the next round with no gap in between. The new round keeps the shape
A wallet that wanted to support five bridges used to integrate five SDKs. Five fee oracles, five sets of error codes, five ideas about what "the transfer went through" means. Multiply that by every wallet and every app, and you get the state of cross-chain UX for most
For as long as Ethereum has existed, sending ETH from one address to another has cost 21,000 gas. It is one of the very few numbers that survived every fork, every roadmap rewrite, and every philosophical argument the ecosystem has had since 2015. Wallets hardcode it. Fee estimators assume
Veritas was the sixth and last of the projects in our look at the UHI9 hookathon, and it puts a reactive contract to a use none of the others needed: keeping a stored number true after the thing it measures has quietly changed. The full project lives on GitHub, though
Season 7 is wrapping up. Our 1-month staking pool expires at block 6,437,662 (Thursday, August 13th), and with it we're opening the door to Season 8. Season 8 repeats Season 7 in structure: a single 1-month pool. We're finalizing the final matters of the
Maestro was the fifth of the six projects in our look at the UHI9 hookathon, and it points a reactive contract at something none of the others touched: the real market price, sitting on a different chain. The full project is open here. Maestro is a Uniswap v4 hook whose
Coinstancy has taken on a practical challenge with Reactive Network: how to keep a portfolio aligned with its intended allocation when market prices are constantly moving. Instead of relying on someone to continuously monitor positions and execute trades, the system responds automatically when a portfolio drifts too far from its
Lambda was the fourth of the six projects in our look at the UHI9 hookathon, and it puts a reactive contract to the use Reactive Network is most literally built for: turning an event on one chain into a transaction on another, with no server in between. The full project,
TrancheShield was the third of the six projects in our look at the UHI9 hookathon, and it takes yet another angle on the same limit: a Uniswap hook only runs when someone trades, but a pool's risk does not sit still between trades. Here is how it deals
Unistrata was the second of the six projects in our look at the UHI9 hookathon, and it draws a different lesson from the same limit: a Uniswap hook only runs when someone trades, but some decisions can’t wait for the next trade. Here is how it handles that. The
EvenFlow was the first of the six projects in our look at the UHI9 hookathon, and the one we singled out as the clearest case of something a Uniswap hook simply can’t do on its own. Here is a closer look at how it gets around that. The full
Plenty of teams came through the UHI9 hookathon, and a good share of them used Reactive Network. The judges did something more useful than count claims: they checked whether each project's reactive contract actually fired a callback on-chain. Six passed that test. This is a look at those
