Network status updates for the @Stacks blockchain layer.
Joined October 2022
- Tweets116
- Following1
- Followers1.7K
- Likes6
Core developers are aware of an issue with block production at BTC Block 962,150 and are investigating.
Updates to follow.
Block production has resumed with BTC Block 962,151
Based on investigation, core developers believe this was due to a number of new signers initially being offline at the cycle 141 boundary. This was a temporary condition and stable block production is expected to continue.
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.
Hello everyone, kindly avoid trading on Velar perpdex for time being. Due to an oracle price feed issue, some user has started draining our Perpdex LP pools recently, thus we are withdrawing liquidity out of the perpdex pools temporarily. This issue is limited to perpdex only, Velar Dharma dex is working fine. We are coordinating with @Stacks as the foundation have put majority liquidity and they are withdrawing it temporarily as we speak till we resolve it. We have also found a solution and are working to resolve it asap.
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.
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
Learn more about how you can cancel pending transactions or increase the fee. 2/2.
xitter.cf/LeatherBTC/status/1955…
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/st…
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/SP0000…
Stacks Endowment Address: SM1Z6BP8PDKYKXTZXXSKXFEY6NQ7RAM7DAEAYR045
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.
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… | 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/stac…
- 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.
🚨 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 been traced to those platforms.
To ensure the safety of all users, we have temporarily suspended all platform activities.
A full post-mortem will be shared as soon as possible.
Thank you for your patience and support.
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.
The .11 release is now live - please upgrade immediately if you are operating a miner, signer, or node
github.com/stacks-network/st…