Stacks Status

Block production has resumed and core developers are continuing to monitor the chain

Core Developers are aware of issues with block production on Stacks, following a Bitcoin re-org. They are investigating and will provide updates shortly

Core devs have been made aware of reports that @VelarBTC, an app on Stacks, may be experiencing a security issue. The Stacks network itself is unaffected. If you're a Velar user, we recommend following official Velar channels for updates.

Stacks Core releases are available from github.com/stacks-network…

The Stacks core development team has released Node Version 3.2.0.0.2, which includes an important security update. If you operate a Stacks node, please update to version 3.2.0.0.2 as soon as possible. No action from users who do not operate nodes is needed. Only the Stacks nodes package needs to be updated, not the signer package, and no state migration is required.

Learn more about how you can cancel pending transactions or increase the fee. 2/2. x.com/LeatherBTC/sta…

Core developers are aware of ongoing mempool congestion caused by a known issue, which will be addressed in an upcoming upgrade. In the meantime, you can increase the fee to speed up your transaction or wait for confirmation as network conditions improve. More info: below. 1/2

Note: Data on outlets such as Coingecko, CMC, and others may lag as they work to update their profiles for Stacks - the Stacks Foundation is actively in touch to provide support and information. SIP-031 contract: explorer.hiro.so/txid/SP0000000… Stacks Endowment Address: SM1Z6BP8PDKYKXTZXXSKXFEY6NQ7RAM7DAEAYR045

Release 3.2 has activated at Bitcoin block 907,740. This release implements SIP-031; all network operators are encouraged to upgrade as soon as possible. Release: github.com/stacks-network…

Users may notice a number of large transactions in the mempool that are leading to longer processing times. Users with time sensitive transactions should review and set higher fees as needed.

Block production has resumed but users may see intermittent gaps as the network fully stabilizes over the next two hours. Thank you to all operators who upgraded

Attention Stacks nodes operators (particularly signers): there is a stall in block production due to a Bitcoin re-org Pre 0.13 nodes have a bug that prevent them from handling this properly If you run any Stacks node or Signer: Upgrade your stacks-core to 3.1.0.0.13 when you do your restore - Check your node's v2/info: curl -s cet.stacksnodes.org:20443/v2/info | jq .burn_block_height - If the burn block height returned is at or near the current bitcoin tip (check mempool.space), your signer is running okay. - If not, you will need to restore your stacks-node from a snapshot - If you have one, restore your stacks-node from your own snapshot (as long as it is older than the stall -- 1:30PM Eastern). If not, use the Hiro archive: archive.hiro.so/mainnet/stacks… - Upgrade your stacks-core to 3.1.0.0.13 when you do your restore

There are reports from the @ALEXLABBTC team of a potential security incident with the ALEX application. Neither the Stacks chain nor sBTC are impacted by this and remain fully secure In order to help constrain the attackers' activities, we have temporarily disabled the sBTC bridge, thereby stopping withdrawals. Again, this is being done to help apps and exchanges reduce the attacker's movements, and the sBTC protocol and funds all remain secure.

Blocks have resumed but there may be further occasional degradation in block production as we wait for all miners and signers to upgrade

The .11 release is now live - please upgrade immediately if you are operating a miner, signer, or node github.com/stacks-network…

Update: Developers are preparing a release to address misbehavior stemming in the stacks-node's mempool syncing logic. All node operators (especially Miners & Signers) will need to upgrade their nodes to this release (.11), which will be released shortly.

Core devs have identified a potential cause of the issue and are investigating further

Core devs are investigating a delay in block production Standby for more updates

Normal block production has resumed

Developers have identified the issue as likely relating to a tenure extend in a now orphaned Bitcoin block which caused the chain state of nodes that went into the fork to become invalid. Signers are now restoring to a previous version of the chainstate and once 70% of signers have, the network will resume. This restoration may take another 60-120 minutes to complete.

Core devs are investigating a delay in block production related to a bitcoin fork at block 897442. Standby for more updates.