Note: This is not the inaugural #1 Stacks blockchain call, but rather a reboot of the previous public Stacks blockchain call series. The “#1” designation has been added to support clear tracking throughout 2026.
Date: Tuesday, February 10, 2026, at 10:00am ET
Hosted by: David - Manager of Core Team
Duration: 50 mins
Participants: 19, Google Meet
1. Agenda Overview
- Call Introduction and Purpose
- Community Questions and Transparency
- SIP-032 Improved Stacking Priority
- Upcoming Epoch 3.4 Development Work
- Chain Performance Improvements and Privacy
- How Can Community Support Core and Where
2. Key Meeting Highlights
Call Introduction and Purpose
- David: Introduced the first official Stacks blockchain community call, emphasizing its role as an open forum for questions, concerns, comments, and feedback. Highlighted the importance of community engagement alongside regular core’s internal meetings.
- PeaceLoveMusic: Introduced himself as the founder of the Deorganized Media Project and Governance CAB member, suggesting increased promotion to attract more founders and developers.
Community Questions and Transparency
- Quantum Resistance Discussion: Addressed the need for quantum-resistant cryptography for Stacks. NIST quantum signature proposals exist but require expert vetting. Lamport signatures are a potential migration option but are significantly larger than ECDSA signatures and degrade with use.
- ASCII strings vs buffers: TripnMonkey’s Inquiry. Discussed the differences between ASCII strings and buffers in Clarity functions. Strings offer human readability, while buffers allow easy serialization with consensus-buff functions.
- bridging UI/UX: Ayomi raised issues with the current bridging UI/UX, describing it as clunky and not user-friendly. Teams are working on improving the design and flow, with a request for a more programmable bridge to USDC for easier currency conversion.
- Technical Roadmap Transparency: Approximately 95% of the internal roadmap can be shared publicly, while 5% must remains private for security reasons, such as unresolved vulnerabilities.
- SIP Copyright & Licensing: Addressed concerns about SIPs being designed “behind closed doors.” and whether this was about IP protection instead of public-good design. All products and SIPs are intended as permissively licensed public goods with an open, documented process.
- StackerDB: questions around workstreams like StackerDB. It was brought up as a community tool to observe real-time signer activity and network health on Stacks, giving builders more visibility into how the protocol is operating in practice. Observe real-time signer activity https://slotwatch.dev dashboard
- BIP-110 Bitcoin Network fork impact (Bitcoin Knots proposing to restrict functions): Stacks would follow heaviest chain as done during SegWit activation. Stacks can work on multiple Bitcoin forks if needed. Even without OP_RETURN, could embed data in UTXOs (less efficient but possible)
SIP-032 Improved Stacking Priority
- Priority: SIP-032, focused on improved stacking, is the top priority for Stacks Labs. While the full SIP specification may not be visible by February, announcements and discussions are expected by the end of the month.
- Development: The new stacking version is in development, with the spec being refined internally before public review to ensure a coherent initial proposal.
Upcoming Epoch 3.4 Development Work
- Brice outlined three main Clarity-related items targeted for epoch 3.4:
- New Post-condition Mode: Allows asset movements involving other accounts/contracts while maintaining strong protection for the origin signer’s account.
- Clarity 5 Bugfix Bundle: Includes fixes for known issues, such as burn block height and double hashing in the
secp256r1_verifyfunction. - New NFT Post-condition Variant: Adds flexibility by allowing a “may transfer” condition for NFTs, analogous to a less-than-or-equal-to condition for fungible tokens.
Chain Performance Improvements and Privacy
- Performance Work: Ongoing efforts to compress blockchain size, with Jude and Federico’s work estimated 20-25% space savings with minimal performance cost.
- Privacy Discussion: Legal implications make privacy features challenging. Despite strong cryptography, metadata leakage remains a concern, as demonstrated by Zcash’s transaction deanonymization.
- Jude’s research showed, even with strong cryptography like Zcash’s zero‑knowledge proofs, 90%+ of Zcash transactions can be deanonymized due to metadata leakage
- True differential privacy extremely difficult due to IP (IPv4) layer design - David
How Can Community Support Core and Where
- Share honest feedback: Honest, specific feedback about pain points and issues is encouraged to improve the ecosystem.
- Feedback Channels: Bi-weekly calls, Stacks core repository, Stacks Discord - Builders Channels, and Slack are available for community feedback.
- Report Genuine Bugs: Report genuine bugs. Core team requests if the community to stop sending AI-generated immunefi vulnerability reports due to the high volume received.
Resources & References
- Stacks Core Repository: GitHub
- Clarity 5 and Epoch 3.4: Github
- feat: new SIP for improved post-conditions: Github
- SIP Repo: Github
- immunefi bug bounty: Website
- Stacks Discord
- Quantum Safe Lamport Signatures: Article by BitMex Research
Call to Action
- Join the Community Calls: Take part in the bi-weekly calls to stay aligned on priorities, ask questions, and collaborate directly with core contributors. → Add to Your Calendar
- Share Clear, Actionable Feedback: Flag real pain points and concrete issues early. If it’s not raised, the core team may not see it - your input directly shapes what gets fixed or improved.
- Contribute to Core repo: Engage with the Stacks core repo, open issues, review PRs, or jump into community channels to help move things forward.
- Help Grow the Call: Spread the word so more builders know this channel exists. Better attendance = stronger feedback loops = a better Stacks for everyone.
