These are new known issues and code updates added during the competition. The new known issues will now be considered out of scope and invalid for a reward.
If a bug fix can be bypassed, the associated bug which bypasses the previous fix is considered new, valid and in scope.
If a code change unrelated to a bug introduces a bug, the introduced bug is considered new, valid and in scope.
Changelog
- Bug: Cannot fetch token total supply before the token exists https://github.com/stacks-network/sbtc/issues/1026
- Bug: A "rogue" signer could block someone who submitted a deposit from receiving sBTC, even after the signers have swept in the deposited funds https://github.com/stacks-network/sbtc/issues/1057
- Bug: Only accept deposits if all inputs are fine, instead of just any input being fine https://github.com/stacks-network/sbtc/issues/1046 : corresponding fix https://github.com/stacks-network/sbtc/pull/1077
- Bug: Locktimes of 16 are handled incorrectly, leading to such deposits incorrectly failing validation https://github.com/stacks-network/sbtc/issues/1078
- Bug: Remove sweep transaction messages https://github.com/stacks-network/sbtc/issues/1057
- Bug: When someone submits deposit request data to Emily, we do not have a way of ensuring that the sender is the same entity that created the deposit UTXO https://github.com/stacks-network/sbtc/issues/1116
- Bug: The coordinator can trigger DKG whenever they want https://github.com/stacks-network/sbtc/issues/1114
- Bug: Avoid skipping the rest of the block if we err when processing an event in new block handler https://github.com/stacks-network/sbtc/issues/1182
- Bug: Signers can censoring pending deposits https://github.com/stacks-network/sbtc/issues/1183
- Bug: Set the request body payload size limit https://github.com/stacks-network/sbtc/issues/1186
- Bug: Enforce decoding order for Signed messages https://github.com/stacks-network/sbtc/issues/1187
- Bug: Ensure we check for nonempty pre-sign requests https://github.com/stacks-network/sbtc/issues/1189
All fixes will be added to the scope of this competition.
Comments
0 comments
Article is closed for comments.