A bug in stacks-increase call is impacting Stacking rewards this cycle

Hey all, a release that begins to address the ongoing bug affecting Stacking is now available!

Core developers have recommended, and a SIP has been approved, for disabling PoX for one or two cycles while a bug in the stacks-increase function in the pox-2 boot contract is addressed. This is an established route for addressing bugs like this and will ensure adequate time for further testing of the next release.

Conversations between developers, contributors, & community converged on an option that disables PoX as a first step in addressing the bug. SIP-022 approves this fork and introduces a rule to temporarily disable PoX and switch fully to Proof-of-burn as previously outlined. Post-upgrade, the network will ignore any non-upgraded nodes.

This option has been recommended because it is technically sound and follows an established route for addressing bugs like this. It will also ensure adequate time for further testing of solutions. Various community reviewers, CABs, and the SIP process have been followed/included.

Notably, all STX will automatically be unlocked from the network, affording users the most flexibility during this time. However, Stacking rewards will not be available for these 1-2 cycles while work is underway. Exchanges and Stacking Pools have been notified about the upgrade. Normal trading and deposits/withdrawals should not be impacted as long as exchanges upgrade.

This upgrade should be simple since the chainstate is compatible with 2.1.0.0.0. There will be another upgrade in 2-4 weeks after the bug has been resolved and Stackers will reactivate PoX by Stacking as normal.

Key Resources:

1 Like