NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #822 by repository stars
Latest stable
v0.56.1
Last release 1 months ago
07 Oct 2026
Ships fairly regularly
a new release about every 3 weeks
Some releases are documented
notes for 20 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
312 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Tag: v0.56.1 Commit: 5917bf5e2ced1d3f1cafdde6bc6fa3345fb71c3e Link: https://github.com/dominant-strategies/go-quai/
Tag: v0.56.1 Commit: 5917bf5e2ced1d3f1cafdde6bc6fa3345fb71c3e Link: https://github.com/dominant-strategies/go-quai/
Release Information
Action required
Tag: v0.56.0 Commit: f3f345c877300c044e3e0081a48bf3cf786fb9cc Link: https://github.com/dominant-strategies/go-quai/ Activation: Tueday, Sep 15, 2026 a
Tag: v0.56.0 Commit: f3f345c877300c044e3e0081a48bf3cf786fb9cc Link: https://github.com/dominant-strategies/go-quai/ Activation: Tueday, Sep 15, 2026 at 10 AM CST
Release Information
Action required
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Guarding the epoch and light cache dag size
Guarding the epoch and light cache dag size
Nothing published for this version
Tag: v0.55.0 Commit: 93372b5f9f455cd02b38463a8e1473a724f71d6d Link: https://github.com/dominant-strategies/go-quai/ Activation: Wednesday, Jun 25, 202
Tag: v0.55.0 Commit: 93372b5f9f455cd02b38463a8e1473a724f71d6d Link: https://github.com/dominant-strategies/go-quai/ Activation: Wednesday, Jun 25, 2026 at 10 PM CST
Release Information
This release makes lot of improvements to the node
Action required
Nothing published for this version
Tag: v0.54.0 Commit: 5b25e03b7a217bfb2cfd6ee8367d02bdfc303b83 Link: https://github.com/dominant-strategies/go-quai/ Activation: Friday, Jun 12, 2026 a
Tag: v0.54.0 Commit: 5b25e03b7a217bfb2cfd6ee8367d02bdfc303b83 Link: https://github.com/dominant-strategies/go-quai/ Activation: Friday, Jun 12, 2026 at 10:00 AM CST / 15:00 UTC
Release Information
This release improves miner reward stability by increasing the EMA window, making rewards, difficulty, and conversion rates smoother and more resilient to short-term hash rate swings from sources like NiceHash. It also adds a new net peers fix and API updates, improving overall network reliability and delivering a more stable, predictable experience for miners, node operators, and ecosystem participants.
Action required
BIP-302 is Quai's proposal for child-chain capture of a parent chain's block subsidy via consensus-enforced AuxPoW. The parent chain doesn't change. T
BIP-302 is Quai's proposal for child-chain capture of a parent chain's block subsidy via consensus-enforced AuxPoW. The parent chain doesn't change. The child chain does.
Drivechain has spent nine years asking Bitcoin to soft-fork. BIP-302 asks Bitcoin for nothing. The protocol stays exactly as Satoshi shipped it; Quai's consensus does all the work. Bitcoin stays small, sound, and pristine.
What Quai becomes, in the long arc: the chain that scales Bitcoin without changing Bitcoin, secures Bitcoin without asking permission, and **gives Bitcoin's miners a reason to keep their ASICs running long after the block subsidy halves to zero. **Programmable. EVM-compatible. Settled by SHA-256 proof-of-work. Deflationary with every Bitcoin block mined.
SOAP has been live against BCH, LTC, DOGE, and RVN since December 17, 2025. Five months in production. Four parent chains. Billions of value secured across each of the algorithms.
**Replacing the Bitcoin protocol is the endgame. BIP-302 is how Quai gets there. **
Eventually, Quai and Bitcoin fuse further: Quai for programmability, scalability, and shared SHA-256 security; Bitcoin for the monetary base and existing adoption.
Tag: v0.53.0 Commit: 3f915a7a45b867d39181dcc4b045c931e3831526 Link: https://github.com/dominant-strategies/go-quai/ Activation: Friday, May 15, 2026 at 10:00 AM CST / 15:00 UTC
Release Information v0.53.0 is the BIP-302 fork: the consensus upgrade that takes Quai into Bitcoin mining through SOAP.
SHA-256 has become the dominant reward driver on Quai network.
This fork renormalizes Quai's reward calculation against SHA-equivalent difficulty rather than KawPoW's native difficulty, so the hardware that will carry SOAP into Bitcoin scales appropriately.
What's in v0.53.0 Reward / consensus changes (fork-activated)
Operational / stability fixes
Action required
Api fix by @gameofpointers in https://github.com/dominant-strategies/go-quai/pull/2710
Full Changelog: https://github.com/dominant-strategies/go-quai/compare/v0.51.1...v0.52.0
Update the Qi wrapping logic to continue after the change block
Update the Qi wrapping logic to continue after the change block
Nothing published for this version
The Singularity economics are coming to Quai Network. All node operators must update to the singularity branch before block 1,530,500 (prime terminus)
The Singularity economics are coming to Quai Network. All node operators must update to the singularity branch before block 1,530,500 (prime terminus).
Release: v0.51.0
Estimated activation: Thursday, March 19, 2026 ~4:00 PM UTC (11:00 AM CDT / 12:00 PM EDT / 9:00 AM PDT)
~1.67B QUAI from the Genesis block is burned. After the fork block, monthly unlocks will simply skip these addresses — no further tokens will be released to them.
Workshare inclusion limits are doubled across the board: Total workshares per block: 16 -> 32 SHA shares per block: 8 -> 16 Scrypt shares per block: 8 -> 16
This means miners can include more workshares per block, improving mining rewards and network throughput.
We've identified and resolved issues affecting SHA and Scrypt ASIC firmware compatibility. This update includes important optimizations for ASIC minin
We've identified and resolved issues affecting SHA and Scrypt ASIC firmware compatibility. This update includes important optimizations for ASIC mining:
What's changing:
Updated the version file to v0.49.2
Updated the version file to v0.49.2
Updated the version file to v0.49.1
Updated the version file to v0.49.1
> This release contains breaking changes. All nodes must upgrade to v0.49.0 prior to the activation block to maintain consensus. Failure to upgrade wi…
This release finalizes the code changes required for the SOAP activation on Mainnet.
This release contains breaking changes. All nodes must upgrade to v0.49.0 prior to the activation block to maintain consensus. Failure to upgrade will result in network partitioning.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added support for PUSH0, MCOPY, TSTORE, and TLOAD → Enables more optimized storage lookups for contracts and keeps the EVM up to date.
3,490,000.⚠️ Note: These changes are not backwards compatible.
All nodes must upgrade to v0.48.0 to maintain consensus post-activation. Failure to do so may result in network partitioning.
Nothing published for this version
Nothing published for this version
The initial epoch turnover for the ProgPoW algorithm is scheduled at prime block height 388,800, with an estimated activation on May 20, 2025 (CST). T
The initial epoch turnover for the ProgPoW algorithm is scheduled at prime block height 388,800, with an estimated activation on May 20, 2025 (CST). This release addresses a critical bug in the ProgPoW lookup cache, ensuring robust synchronization across epochs. The fix prevents Proof-of-Work (PoW) verification failures when nodes sync from a divergent epoch, enhancing chain stability and consensus integrity.
The maximum number of tries for the CREATE opcode has been increased from 1,000 to 10,000, effective at zone block height 1,865,000, with activation slated for May 23, 2025 (CST). This adjustment mitigates contract deployment failures by ensuring sufficient attempts to generate a valid, in-scope contract address. Note: This change is non-backward compatible, requiring all nodes to upgrade to v0.47.0 to maintain consensus post-activation.
Operators are advised to update to this release promptly to ensure compatibility and avoid network partitioning.
Fix https://github.com/dominant-strategies/go-quai/pull/2629 : Removes the lookup cache that cause fails in PoW verifications between progpow epochs.
Fix https://github.com/dominant-strategies/go-quai/pull/2631: Increases the max tries for grinding a contract when Create opcode is called
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
The fix is backwards compatible but node upgrade to this release is highly recommended to keep it synced to the network. If the node is out of sync (c
Desync issues
The fix is backwards compatible but node upgrade to this release is highly recommended to keep it synced to the network. If the node is out of sync (check top right of the stats page to know the latest chain tip), just update the code to this release and start the node. If there is issue even after that use the latest snapshot https://docs.qu.ai/guides/client/node#download-and-sync-from-snapshot to sync to the chain.
Fix https://github.com/dominant-strategies/go-quai/pull/2635 : Removes the new data dependency that was introduced with the launch of Qi, that has been causing these desyncs over past few weeks.
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
Root cause of the desync issue has been found and fixed now
Sync issues
Root cause of the desync issue has been found and fixed now
The fix is backwards compatible but node upgrade to this release is highly recommended to keep it synced to the network. If the node is out of sync (check top right of the stats page to know the latest chain tip), just update the code to this release and start the node. If there is issue even after that use the latest snapshot https://docs.qu.ai/guides/client/node#download-and-sync-from-snapshot to sync to the chain.
Fix https://github.com/dominant-strategies/go-quai/pull/2628 : Fixes the desync issue by triggering the hierarchical cooridinator
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
There was a fork in the network because of nodes going out of sync. This release has the fix for getting back to the network tip
Sync issues
There was a fork in the network because of nodes going out of sync. This release has the fix for getting back to the network tip
The fix is backwards compatible but node upgrade to this release is highly recommended to keep it synced to the network. If the node is out of sync (check top right of the stats page to know the latest chain tip), use the latest snapshot https://docs.qu.ai/guides/client/node#download-and-sync-from-snapshot to sync to the chain.
Fix https://github.com/dominant-strategies/go-quai/pull/2625 : Fixing issue with node going out of sync because of state not being available
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
Fixes issues with syncing and also prevents nodes from going out of sync
Sync issues
Fixes issues with syncing and also prevents nodes from going out of sync
The fix is backwards compatible but node upgrade to this release is highly recommended to keep it synced to the network
Fix https://github.com/dominant-strategies/go-quai/pull/2625 : Fixing issue with the nodes going out of sync because of out of order execution of processing state
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
Fixes issues with the slip calculation during conversion from Quai to Qi.
Fixes issues with the slip calculation during conversion from Quai to Qi.
The fix is not backwards compatible and nodes must be upgraded before the following deadline
Improvement/Fix #2621 : Fixing the conversion flow slip calculation
GitHub: https://github.com/dominant-strategies/go-quai
Documentation: Go-Quai Docs
Community Support: Discord Link
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.