Skip to content

Releases: Hydra-Chain/hydragon-node

v2.0.5

07 Mar 07:53
0dae3b4

Choose a tag to compare

Hydra v2.0.5 — Vesting Status Command

🆕 What's New

  • 📊 Added: New read-only hydragon vesting-status command that lets validators check their vesting position status on-chain
  • 🔍 Queries: 4 view functions across HydraStaking and HydraDelegation contracts — no state changes, no gas costs
  • 📋 Displays: Vesting period (in weeks), start/end timestamps, base stake, bonuses, generated rewards, unclaimed rewards, and claimable commissions

📌 Usage

# Human-readable output
hydra hydragon vesting-status --data-dir /path/to/data --jsonrpc http://localhost:8545

# JSON output
hydra hydragon vesting-status --data-dir /path/to/data --jsonrpc http://localhost:8545 --json

📌 Important Notes

  • 🧩 This is a read-only command — it only queries on-chain state, no transactions are sent.
  • ⛔ Validators with an active vesting position will see full details; validators without vesting will see a compact view with generated rewards, unclaimed rewards, and claimable commissions.

What's Changed

Full Changelog: v2.0.4...v2.0.5

v2.0.4

30 Oct 02:13
9167f0b

Choose a tag to compare

Hydra v2.0.4 — Bootnodes and Restart Bootstrap Enhancements

🌐 Mainnet Release

This release brings the bootnode discovery and restart bootstrap improvements previously tested on Testnet to the Mainnet network.

🆕 What's New

  • 🗺️ Automatic Bootnode Initialization:
    On first startup, the node automatically generates a bootnodes.json, pre-seeded with the default bootnodes from genesis.json.

  • 🔄 Persistent Peer Tracking:
    The node now maintains a last_peers.json file, continuously recording recently connected peers during runtime to speed up reconnections.

  • ⚙️ Enhanced Restart Bootstrap:
    On restart, the node first connects to the default bootnodes and then gracefully falls back to peers listed in last_peers.json if needed.

  • 🧭 Improved Network Resilience:
    Optimized peer discovery and recovery flow ensures smoother restarts and faster network convergence without manual peer configuration.

📌 Important Notes

  • 🧩 Default bootnodes remain the primary discovery source; last_peers.json serves as a fallback only.
  • 🧼 For best performance, perform graceful shutdowns to ensure last_peers.json captures a fresh, valid peer set.
  • 💾 Both bootnodes.json and last_peers.json are human-readable JSON lists of multiaddrs for easy inspection and manual edits.
  • All validators must upgrade to adopt the new bootnode and restart logic.

What's Changed

Full Changelog: v2.0.0...v2.0.4

📦 Additional Resources

Docker Image


Hydra v2.0.4-rc — Bootnodes and Restart Bootstrap Enhancements(Testnet Release)

16 Oct 10:27
7861072

Choose a tag to compare

Hydra v2.0.4-rc — Bootnodes and Restart Bootstrap Enhancements

🚀 Testnet Release Only

This is a Testnet-only release.

🆕 What's New

  • 🗺️ Added: Automatic generation of bootnodes.json on first startup, seeded with default bootnodes from genesis.json.
  • 🔄 Introduced: Continuous peer tracking via last_peers.json — the server now records recently connected peers during runtime for faster reconnection.
  • ⚙️ Enhanced: Smart restart flow with prioritized fallback — the node first attempts to connect to default bootnodes, then gracefully falls back to peers in last_peers.json if needed.
  • 🧭 Improved: Network recovery and bootstrap performance, ensuring smoother restarts without manual peer configuration.

📌 Important Notes

  • 🧩 Default bootnodes remain the primary source for discovery; last_peers.json acts only as a fallback.
  • 🧼 Prefer graceful shutdowns so that last_peers.json captures an up-to-date, high-quality peer list.
  • 💾 Both bootnodes.json and last_peers.json are simple JSON lists of multiaddrs for easy inspection and editing.
  • All validators must upgrade to adopt the new logic.

📦 Additional Resources

Docker Image

Hydra v2.0.3-rc (Testnet Release)

16 Oct 10:06
57bb459

Choose a tag to compare

🚀 Testnet Release Only

This is a Testnet-only release.

🆕 What's New

  • 🐞 Fixed: Consensus quorum calculation bug that caused "parent quorum not reached" errors.
  • 📈 Improved: Consensus stability when validator nodes go offline.
  • ⚠️ Breaking Change: All validators must upgrade to adopt the new consensus logic.

📌 Important Notes

  • 🧪 Testnet nodes should upgrade first to verify the fix.
  • 🌐 Following successful Testnet validation, this update will be deployed to Mainnet.
  • ⛔ This is a mandatory upgrade for all validators.

📦 Additional Resources

Docker Image

v2.0.2

17 May 11:45

Choose a tag to compare

Hydra v2.0.2

🔥 Who Should Upgrade?

  • Testnet Node Operators: Upgrade is mandatory due to updated boot node configurations.
  • Mainnet Node Operators: No action required. This update is not mandatory.

✨ What's New?

  1. Updated Testnet Boot Nodes
    • The genesis.json configuration has been updated to reflect migrated boot nodes for the testnet environment.

⚠️ Upgrade Instructions

  1. Download and Install the Latest Binary
    Ensure you're using the v2.0.2 binary.

  2. Restart Your Node
    After installation, restart your node to apply the new configurations.

📦 Additional Resources

Docker Image

v2.0.1

14 Mar 09:30

Choose a tag to compare

Hydra v2.0.1

🔥 Who Should Upgrade?

  • Testnet Node Operators: Upgrade is mandatory due to updated boot node configurations.
  • Mainnet Node Operators: No action required. This update is not mandatory.

✨ What's New?

  1. Updated Testnet Boot Nodes
    • The genesis.json configuration has been updated to reflect migrated boot nodes for the testnet environment.

⚠️ Upgrade Instructions

  1. Download and Install the Latest Binary
    Ensure you're using the v2.0.1 binary.

  2. Restart Your Node
    After installation, restart your node to apply the new configurations.

📦 Additional Resources

Docker Image

v2.0.0

17 Feb 11:06

Choose a tag to compare

Hydra v2.0.0

Breaking Changes – Action Required

This release introduces the Price Oracle Fix, which will be activated at block 12419989 (approximately 20 days after this release). Node operators must upgrade to ensure accurate price fetching and maintain consensus.

Additionally, the --chain flag for the server command has been simplified to accept predefined network values instead of requiring a genesis file path.

⚠️ Upgrade Instructions

  • Validators & Node Operators: Upgrade before block 12419989 to ensure proper price oracle functionality.
  • --chain flag of the server command doesn't need a genesis path anymore but instead uses mainnet or testnet as values. More information can be found in the README.md file.

What's Changed

Full Changelog: v1.0.0...v2.0.0

Additional assets

Docker Image

v2.0.0-rc.1

04 Feb 12:34

Choose a tag to compare

v2.0.0-rc.1 Pre-release
Pre-release

Hydra v2.0.0

Breaking Change for Testnet Users

This release introduces an activation for the Price Oracle Fix on the testnet. Testnet nodes must upgrade to this release to ensure accurate price fetching and compatibility with the latest protocol changes.

What's Changed

Full Changelog: v1.0.0...v2.0.0-rc.1

Additional assets

Docker Image

v1.0.0

20 Dec 13:09

Choose a tag to compare

Hydra v1.0.0: Foundations for the Future

Today, we release Hydra v1.0.0 — the first chapter of an ambitious story. Built for speed, scalability, and resilience, Hydra introduces sub-1-second block times, instant finality, and the promise of seamless cross-shard communication through Project Prometheus. Early stress tests have shown its capabilities, but we know this is only the foundation for what’s to come.

This is not just a release; it’s an invitation to developers, innovators, and dreamers to explore what’s possible. Together, we’ll shape the next evolution of decentralized technology, one block at a time.

Additional assets

Docker Image

v1.0.0-rc.5

03 Dec 14:43
fc102b4

Choose a tag to compare

v1.0.0-rc.5 Pre-release
Pre-release

What's Changed

Full Changelog: v1.0.0-rc.4...v1.0.0-rc.5

Additional assets

Docker Image