Stacks Status
@stacksstatus
Followers
2K
Following
3
Media
1
Statuses
110
Network status updates for the @Stacks blockchain layer.
Joined October 2022
Stacks Core releases are available from
github.com
The Stacks blockchain implementation. Contribute to stacks-network/stacks-core development by creating an account on GitHub.
0
1
8
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
4
18
66
Learn more about how you can cancel pending transactions or increase the fee. 2/2. https://t.co/tRr08hTH7D
Do you have a pending Stacks transaction? You can cancel it or increase your fee directly in Leather. → Go to your activity feed → Tap options → Cancel OR increase fee → Done ✅
0
0
2
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
2
0
13
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: https://t.co/FZnhbAaalD Stacks Endowment Address:
explorer.hiro.so
Explore blocks, transactions, accounts, and smart contracts on the Stacks blockchain with real-time data.
1
2
8
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
This release implements the 3.2 Stacks consensus rules which activates at Bitcoin block 907,740. For more details see SIP-031. This is a required upgrade Activation is estimated for July 29th, 202...
2
6
50
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
4
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
47
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
73
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 https://t.co/efGcxaivqZ
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
8
22
Core devs are investigating a delay in block production related to a bitcoin fork at block 897442. Standby for more updates.
6
14
52
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
27
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
25
28
128