The primary keyword for this update is Oasys v1.9.0 upgrade. The Oasys validator release notes describe v1.9.0 as adding a hacking-protection mechanism, including suspicious-transaction monitoring and a TransactionBlocker contract.
For Radar, this is not an exchange-route story. It is a protocol-ops watch about how validators coordinate security controls during a live chain upgrade.
What Happened
The Oasys release notes say suspicious transactions can be monitored and prevented from being included in blocks, with detection logic implemented as a Go plugin that can be updated without a validator upgrade.
The notes also describe an onchain TransactionBlocker contract and an emergency mode where validators can halt normal transaction processing while allowing Layer 2 rollup transactions.
Bybit separately posted support for the Oasys v1.9.0 upgrade, with the upgrade expected around May 21 at block 12,970,330, giving the event a current operational window.
Why It Matters
This matters because transaction-blocker designs change the trust surface of a chain. They may protect users during exploits, but researchers need to know who controls updates, how narrow the scope is and how emergency mode ends.
The owner-fit angle is clearly Radar: chain security modules, validator coordination, upgrade activation and protocol operations rather than trading a token ticker.
Because the release mentions both off-chain plugin logic and an onchain blocker, the follow-up question is whether observability and governance are strong enough for users and dapps to understand the control plane.
The detail that Layer 2 rollup transactions can continue during emergency handling also gives dapp teams a specific routing assumption to test instead of treating the upgrade as a generic hard fork.
What To Watch Next
Watch post-activation block production, validator release adoption and whether Oasys publishes follow-up incident or activation notes.
Also watch whether dapps, bridges or rollup operators issue user-facing guidance. Emergency controls can be technically successful while still changing app-level risk.
A useful researcher screen is blocker authority, plugin update path, activation height and rollback plan. If those remain clear, the upgrade is easier to evaluate.
Continue this cluster
Continue this cluster with May 21 chain-upgrade and tokenomics updates that separate protocol operations from exchange-only route changes.
