Stacks Core Engineers: Weekly Tech Reports
Stay updated on the latest developments from Stacks core engineers with regular updates on their progress. Every week or bi-weekly, depending on the release cycle, they will share insights into what’s been shipped, what’s currently being refined, and what exciting features are planned for future releases. Dive in to see how a decentralized group of core engineers are building and improving the leading Bitcoin L2, step by step.
Weekly Tech Timeline
November 7, 2024
Following the Nakamoto hard fork, several partners and node operators have run into issues with nodes either stalling or struggling to keep up with the network. These issues are being investigated, along with reports of some regressions on one of the API endpoints.
This week, the core devs have focused their efforts on the timely release of version 3.0.0.0.1 point release, that focuses on ironing out the issues encountered by node operators.
Read Full Tech Report 👈 This week, the core devs have focused their efforts on the timely release of version 3.0.0.0.1 point release, that focuses on ironing out the issues encountered by node operators.
October 28, 2024
The Nakamoto Upgrade is activated, bringing Bitcoin finality and fast blocks to Stacks. We’ve just entered a new era for Bitcoin. The stage is set for sBTC, and we know wherever Satoshi is right now, they're proud of the builders bringing innovation back to Bitcoin.
👉 Read Full Announcement Nov 7, 2024
Weekly Tech Report
Following the Nakamoto hard fork, several partners and node operators have run into issues with nodes either stalling or struggling to keep up with the network. These issues are being investigated, along with reports of some regressions on one of the API endpoints.
This week, the core devs have focused their efforts on the timely release of version 3.0.0.0.1 point release, that focuses on ironing out the issues encountered by node operators.
Highlights + notes
Another point release will fast follow with this change which fixes a few bugs and adds some optimizations to the P2P stack, including handling “unhealthy” peers. This is the fix to the temporary resolution re deny_nodes.
This week, the core devs have focused their efforts on the timely release of version 3.0.0.0.1 point release, that focuses on ironing out the issues encountered by node operators.
Highlights + notes
- This change adds a new index to speed up some database lookups. We profiled a node before this change and it was spending ~20% time in this code path. With this change we’re seeing significantly better performance — it should help the nodes that were struggling to keep up, and help miners with more consistent block production.
- This change removes an unnecessary panic when the code detects a database deadlock. Deadlocks will still be logged but the node will continue to run instead of crashing.
- There’s a public node still running Stacks 2.5 that’s interacting with 3.0 nodes in a suboptimal way. While devs test a proper fix, a workaround is to add the following under the [node] section of your Stacks config: deny_nodes = "84.32.186.15:20444"
Another point release will fast follow with this change which fixes a few bugs and adds some optimizations to the P2P stack, including handling “unhealthy” peers. This is the fix to the temporary resolution re deny_nodes.
- Following work on current issues, devs will be focused on tenure extend and cost functions. Updates on this work will be communicated in these updates.