Stacks Status
@stacksstatus
Followers
2K
Following
3
Media
1
Statuses
104
Network status updates for the @Stacks blockchain layer. Show us your Naka•mojo• 🟧: https://t.co/dXQBkxYKBE
Joined October 2022
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.
3
5
28
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.
0
2
11
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.
2
10
46
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.
🚨 Security Incident Update from ALEX 🚨. We are aware of the malicious activities at ALEX. Our team is working around the clock to contain the situation and mitigate further impact. We are coordinating closely with centralized exchanges (CEXs), as part of the stolen funds have.
15
12
74
Blocks have resumed but there may be further occasional degradation in block production as we wait for all miners and signers to upgrade.
0
4
13
The .11 release is now live - please upgrade immediately if you are operating a miner, signer, or node.
github.com
The Stacks blockchain implementation. Contribute to stacks-network/stacks-core development by creating an account on GitHub.
2
3
17
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.
3
9
40
Core devs have identified a potential cause of the issue and are investigating further.
0
0
7
Core devs are investigating a delay in block production. Standby for more updates.
1
4
34
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.
3
9
22
Core devs are investigating a delay in block production related to a bitcoin fork at block 897442. Standby for more updates.
6
15
55
Hey Stackers, core developers are aware of intermittent issues in block production, specifically when there are longer windows between Bitcoin blocks. A simple patch to address it is being tested and is expected soon. For node operators: No action is needed right now, and.
2
4
28
Earlier this week Stacks core developers identified and thwarted a sophisticated supply chain attack. All funds are safe, the network remains operational, and we have found no evidence that any releases were compromised. Out of an abundance of caution, core developers are.
27
29
132
Some independent app builders in the Stacks ecosystem were recently targeted via Github in an effort to insert malicious code in their app repositories. We have found no evidence of an attack or compromise of the sBTC or Stacks Core repositories, but because some of these.
5
13
62
The network is successfully producing blocks again, and while additional signers continue to restore, you may notice minor intermittent activity over the next hour. Everything is progressing as expected, and we appreciate your patience during this time.
7
5
47
The network is successfully producing blocks again, and while additional signers continue to restore, you may notice minor intermittent activity over the next hour. Everything is progressing as expected, and we appreciate your patience during this time.
1
0
4
Update: There was a temporary drop in signer participation, which affected the threshold required for optimal signing. Core developers are working with signers to restore their signers. More info will follow soon as signers are restored.
Core devs are investigating a delay in block production related to a Signer. Standby for more updates.
1
0
21
Update: There was a temporary drop in signer participation, which affected the threshold required for optimal signing. Core developers are working with signers to restore their signers. More info will follow soon as signers are restored.
3
1
8