The Hibiscus V7 Celestia upgrade, scheduled for mid-March, aims to improve interoperability and sovereignty for networks built on a modular data availability layer.
Key features of Hibiscus V7 release
of Hibiscus (V7) release of Celestia is scheduled for mid-March and targets the long-standing trade-off between sovereignty and interoperability. By enhancing network interaction, rollups and app chains built on Celestia feel more integrated, while still maintaining their independence.
Additionally, this upgrade introduces two key features to improve cross-chain operations. First, the new transfer module We focus on user-friendly token routing. hyperlane. Second, ZK Interchain Security Module (ZK ISM) provides cryptographic verification of interchain messages designed for high-value, minimal trust activities.
CIP-45: Transfer module for streamlined token routing
CIP-45 We provide a transfer module that allows Transferring a single signature token Cross the chain via hyperlane. Previously, when sending assets from one chain to the final destination chain through Celestia, users were often required to sign multiple transactions, increasing friction and operational risk.
Currently, users send tokens to a deterministically derived transfer address that is cryptographically bound to a specific destination and recipient. However, the actual transfer is performed as follows: Unauthorized relayer executiontransfer funds to a pre-committed address. This gives hyperlane routes the same convenience as multihop. IBCpacket forwarding middleware already provides IBC-based forwarding.
However, this design maintains non-custodial guarantees while hiding the routing complexity from end users. This is particularly relevant for applications where frequent cross-chain movements are expected but want to keep the signature flow simple and predictable.
CIP-46: ZK Interchain Security Module
CIP-46 Introducing a zero-knowledge proof base Hyperlane Interchain Security Module (x/zkism), adds cryptographic security to cross-chain messaging. What I’m currently using is gross 16 Validation to support message validation with minimal trust, rather than relying solely on trusted multisig validators.
This module allows networks to configure their own certificate-based security using: SP1 Prover program. Support for other ZK virtual machines is planned in the future, including: 0 risk. Additionally, this flexibility allows verification of consensus proofs, TEE-based proofs, or full ZK execution proofs of relayed interchain transfers. Celestia.
With the new ZK ISM, applications can choose between multisig-based and cryptographic proof-based verification depending on their risk profile. Although proof generation is more costly and may introduce additional latency compared to multisig ISMs, it provides strong guarantees suitable for high-value transfers, intra-organizational flows, or ecosystems that prioritize trustlessness over speed.
In this context, the Celestia upgrade strengthens Hyperlane as the foundation for secure, programmable cross-chain messaging and helps orchestrate security assumptions across interconnected rollups.
CIP-44: Validator fee cap adjustment
CIP-44 Focuses on validator economics. We will increase the maximum commission rate for validators from the following: twenty five% to 60%while also increasing the minimum fees enforced by the protocol. 10% to 20%. This adjustment follows the reduction in protocol growth associated with previous network upgrades.
The new limits are therefore intended to allow validators to perform more sustainable operations as rewards are compressed over time. Validators with current commissions below 20% will automatically 20% Adjust rates on upgrades to ensure consistent baseline economics across the active set.
Consensus pruning improvements for node operators
The following block retention rules have also been revised in the Hibiscus (V7) release: consensus node. Now the operator Consensus node pruning window as low as possible 3,000 blocksThis corresponds to approximately the last 5 hours of chain history in a typical situation.
Previously, the minimum retention requirement was approximately 14 days of blocks, which imposed more storage requirements and maintenance costs. However, the lower window gives node operators more flexibility in managing disk usage, especially for high-throughput chains that generate large amounts of block data.
Deployed across testnet and mainnet
The V7 release is being rolled out in stages in various areas. Celestiabase network. of Arabica The network is already up and running with the upgrade and serves as an initial environment to test real-world behavior.
on the other hand, mocha The testnet will be upgraded soon, providing another step before mainnet deployment. Mainnet activation is scheduled for mid-March and is subject to regular checks and operational readiness across validators, infrastructure providers, and application builders.
Who should look out for Hibiscus V7?
Teams building high-throughput, low-latency exchanges or chains focused on payments will benefit the most from Hibiscus. Additionally, protocols that rely heavily on cross-chain flows require multihop-style hyperlane routing; zk interchain security Especially attractive.
Developers seeking a more scalable infrastructure are encouraged to contact Celestia’s ecosystem team. Head of Partnershipis known as @0xNorocexplore how these new features can support production-ready deployments.
Overall, Hibiscus (V7) represents a meaningful evolution in Celestia’s modular stack, combining more flexible economics, leaner node operations, and strong interoperability guarantees for the next wave of on-chain applications.
