Releases: omni-network/omni
v0.11.0
We are excited to announce the release of Omni Network CLI and Halo version 0.11.0! This update is a significant milestone, focusing on security enhancements in preparation for Omni’s Mainnet launch.
Key Fixes from the Cantina Audit Competition:
- Reject octane payloads with deposits (#2528).
- Ensure correct proposal transaction count (#2529).
- Prevent adding empty attestations (#2524).
- Fix next proposer algorithm (#2526).
- Support blob transactions (#2498).
- Gracefully handle post-finalization errors (#2508).
- Verify votes before proposing blocks (#2482).
- Handle engine application errors (#2469).
- Prevent ECDSA signature malleability (#2438).
- Always verify public keys (#2439).
Key halo
Improvements:
Note: This version of
halo
is compatible with geth v1.14.12.
Full Changelog:
Check out all the changes here.
A special shoutout to @raehat for their first contribution—welcome to the Omni Network community!
v0.10.0
We are pleased to announce the release of version 0.10.0 of the Omni Network CLI and Halo. This is a non-urgent update focusing primarily on enhancing the functionality and improving performance for operators.
Key halo
enhancements:
- Add docker health
/ready
endpoint #2035, #2179, - Reduce xchain RPC queries by 25% #2160
- Use gRPC to query Cosmos state #2002, #2216
- Low severity audit fixes #2071, #2094, #2086, #2030, #2140, #2121, #2120,
Key omni
CLI enhancements:
Note this version of halo is compatible with geth v1.14.11.
Full Changelog: v0.9.0...v0.10.0
v0.9.0
We are pleased to announce the release of version 0.9.0 of the Omni Network CLI and Halo. It is a critical coordinated release containing the Uluwatu network upgrade, see here for more details.
Key halo
enhancements:
- Uluwatu network upgrade #1983
- No panics when halo detects network upgrades #1996
- Fixed low-likelihood issue in voter persistence #1998
- Improved halo command errors #205
- Cosmos gRPC and REST APIs enabled by default #2036
Note this version of halo is compatible with geth v1.14.11.
Full Changelog: v0.8.0...v0.9.0
v0.8.1
We are pleased to announce the release of version 0.8.1 of the Omni Network CLI and Halo. It is a non-urgent patch release. It contains backports from upcoming v0.9.0 release and focusses on improving the network upgrade process and will replace v0.8.0 as the genesis binaty inside halovisor:v0.9.0
. See details of upcoming Uluwato network upgrade here.
Key halo enhancements:
- No panics when halo detects network upgrades #1996
- Fixed low-likelihood issue in voter persistence #1998
- Improved halo command errors #2057
Full Changelog: v0.8.0...v0.8.1
v0.8.0
We are pleased to announce the release of version 0.8.0 of the Omni Network CLI and Halo. It is a non-urgent release, and will be the last release before the upcoming uluwatu
network upgrade (hard fork) planned for release v0.9.0. It focusses on improving the experience of operators running omni nodes on Omega testnet. See details of the upcoming Uluwatu network update here.
Key halo
enhancements:
- Improved validator performance prometheus metrics. #1872,
- Added support for Cosmos gRPC and RESP APIs. #1907
- REST: Configured in
halo.toml
viaapi.enable
andapi.address
fields. This is disabled by default and binds tolocalhost:1317
. - gRPC: Configured in
halo.toml
viagrpc.enable
andgrpc.address
fields. This is enabled by default and binds tolocalhost:9090
.
- REST: Configured in
Key omni
CLI enhancements:
- Geth discovery issue solved by enabling
30303/UDP
port in docker compose. #1943
Key halovisor
docker image enhancements :
- Switched to using a fork of cosmovisor #1977
- Only a single mount is required:
~/.omni/<network>/halo:/halo
#1977 - Selected binaries are persisted between restarts at:
/halo/halovisor-current
. #1977 - Switching binaries supported when state-syncing to post-upgrade height #1976
Note this version of halo is compatible with geth v1.14.8.
Full Changelog: v0.7.0...v0.8.0
v0.7.0
We are pleased to announce the release of version 0.7.0 of the Omni Network CLI and Halo. This is a non-urgent update focusing primarily on enhancing the functionality of the omni
CLI to enable external operators to join the Omega testnet as validators and archive nodes.
Key omni
CLI Enhancements:
omni operator init-nodes
:- Added a
--archive
flag to configure archive nodes. - Improved idempotency, ensuring existing files are preserved and not overwritten.
- Added a
omni operator create-operator-key
:- Generates an insecure, hex-encoded EOA private key file for the operator address.
omni operator create-consensus-key
:- Produces the CometBFT consensus private key and state files required for consensus operations.
Note this version of halo is compatible with geth v1.14.8.
Full Changelog: v0.6.0...v0.7.0
v0.6.0
This is the v0.6.0 release of the Omni Network cli and docker images. This is a regular maintenance release with no major changes or new features introduced. The focus of this update is to enhance the performance, stability, and security of the network through minor fixes and optimizations.
Note this version of halo is compatible with geth v1.14.8.
Full Changelog: v0.5.0...v0.6.0
v0.5.0
This is the v0.5.0 release of the Omni Network cli and docker images. This is a regular maintenance release with no major changes or new features introduced. The focus of this update is to enhance the performance, stability, and security of the network through minor fixes and optimizations.
Full Changelog: View the changes
v0.4.0
We are excited to announce the first public release of the Omni Network's Omega testnet! This milestone marks a significant step forward in the development of our cross-chain protocol, providing the community with an opportunity to test and interact with the network in a real-world environment.
Highlights:
- Public Omega Testnet Access: The Omega testnet is now open to the public, allowing anyone to permissionlessly join the network, deploy smart contracts, and participate in cross-chain transactions.
- Enhanced Networking: Improved stability and performance for node connectivity, ensuring a more robust and decentralized network.
- Security Upgrades: Implementation of key security patches and audit recommendations to strengthen the protocol.
- Protocol Improvements: Various protocol optimizations for better efficiency and scalability.
We encourage developers, validators, and the broader community to explore the Omega testnet, provide feedback, and help us identify areas for further enhancement as we progress towards the mainnet launch.
Full Changelog: View the changes