Injective governance is considering Meridian, a chain upgrade designed to support regulated assets and improve the connection between its EVM environment and native exchange infrastructure. Proposal 701 set a target halt at block 184,394,000, estimated for September 24 at 15:00 UTC, if the vote passed.
Governance comes first
The proposal was submitted on September 18 and was receiving about 99% support among non-abstaining votes when BlockchainReporter covered it. Voting was scheduled to close on September 22 at 17:02 UTC. The official governance record is the appropriate place to check the final result and proposal status.
A target block is more precise than a calendar estimate because block production can move faster or slower than expected. Validators and infrastructure operators would need to install version 1.20.4 before the chain reaches the designated height. Users should rely on final network notices rather than treating the estimated date as unconditional.
Regulated tokens and MultiVM controls
Meridian would add regulated-token implementations to Injective’s EVM. Issuers could build transfer and compliance requirements into tokenized products, including real-world assets and tokenized equities. MultiVM features are intended to keep those controls consistent between Injective’s native environment and EVM applications.
An exchange precompile would also give EVM applications more direct access to Injective’s liquidity and settlement functions. That could reduce the amount of custom integration work required for developers building trading products, while leaving the network’s underlying execution and risk rules in place.
Privacy testing and market data
The proposal includes early testing for private request-for-quote flows. RFQ systems allow counterparties to request and negotiate prices away from a public order book. Injective’s planned tests are meant to explore institutional access to on-chain liquidity without exposing all order information before execution. They are preparatory work, not a promise that a complete privacy system is already available.
Meridian also changes oracle prioritization, relay validation, transaction signing and risk controls. These components matter for derivatives and tokenized assets because settlement depends on dependable prices and clearly defined execution rules.
What users should verify
The vote result, actual halt time and software release are the immediate checkpoints. Tokenization features also need issuer adoption before they produce real markets. The upgrade creates technical capacity; it does not by itself establish regulatory approval for any asset or guarantee liquidity after issuance.
Operational preparation matters
Validators must coordinate software installation around the target height, while exchanges, wallets and application operators need to monitor the halt and recovery. A governance approval does not remove upgrade risk: an incorrect binary, delayed validator participation or an incompatible integration can interrupt service. The practical evidence of completion will be a finalized vote, the published release, resumed block production and applications operating correctly after the network restarts.
Sources & further reading
- Adapted from BlockchainReporter: Injective Meridian Upgrade Vote Targets September 24 Mainnet Activation
- Primary governance record: Injective proposal 701