Brice
Bad timing between the Stacks node's processing and the Bitcoin network including a block commit can cause a miner to submit a block commit which breaks the UTXO chain, severly...
The integration tests that run in epoch 3.0 take a significant amount of time just to boot to the initial state for the test. Anecdotal measurements show a test with...
When sending a block commit, a miner needs to be cautious about which Bitcoin block it gets included in. If the miner intends to RBF a block commit targeting block...
When mining a transaction replay set, we cannot skip a transaction because it hits the `max_execution_time`, since this is configurable per miner and not part of consensus. All miners should...
This issue will track the development of a chaos monkey style class of testing, where we run a Stacks network with sufficient complexity (number of miners, number of signers, etc.),...
Epoch 3 introduced a bug which causes `burn-block-height` to always return the current burn block height, even if inside of an `at-block` expression. This should be fixed to behave as...
In a recent change, we did some refactoring of the event generation code, and during this refactor, the `contract_abi` field name changed to `contract_interface`, causing a problem in Hiro's API....
The node does not currently expose much information about the miner sortition. It would be helpful to add the burn distribution to the logs and to the burn block event.
[Example failure](https://github.com/stacks-network/stacks-core/actions/runs/14714871756/job/41296697419?pr=6044)
[Sample failure](https://github.com/stacks-network/stacks-core/actions/runs/14785964910/job/41514849567?pr=6065) The flakiness comes from the simple `sleep` that is used in this test. In the above logs, you can see that the follower fails to mock-mine block 5...