Stacks Blockchain Call #2 – Meeting Recap | Tue, 24 Feb 2026

Working Groups
1

Date: Tuesday, February 24, 2026, at 10:00am ET

Hosted by: David - Manager of Core Team

Duration: ~15 mins

1. Agenda Overview

  • “at-block” Functionality Changes
  • Usage Analysis & Impact
  • Current Use Cases
  • Developer Outreach
  • Next Steps

2. Key Meeting Highlights

at-block Functionality Changes

  • Proposed Changes:
    • Major changes to at-block feature under consideration.
    • Aim to reduce chain state size and improve performance.
  • Two main Approaches under consideration:
    • Limit “lookback” period to ~60 days.
    • Remove At-Block entirely, preferred by some core devs.

Usage Analysis & Impact

  • Findings:
    • 99% of At-Block usage within last 60 days.
    • Remaining 1% primarily test-related scenarios.
  • Core Dev Perspective:
    • Removing At-Block simplifies implementation code. Cleanest path from Brice’s perspective.
    • No other blockchains have similar functionality.
  • The Risk
    • Could potentially break existing contracts or trap assets used by apps.

Current Use Cases

  • Primary Applications:
    • Potentially DeFi protocols and DAO governance.
    • Potential gaming applications.
  • Alternative Approaches:
    • Record snapshots at block time rather than replay later.
    • Different logic patterns can achieve similar behavior.

Developer Outreach

  • Engagement Efforts:
    • Reaching out to Stacks builders with past At-Block usage.
    • Ensuring no existing contracts become unusable.
  • Developer Adaptation:
    • Developers on other chains manage without this functionality.
    • Key contacts like Zest/Bitflow consulted directly.

Next Steps

  • Actions:
    • Continue collecting developers feedback.
    • Verify no critical contracts affected.
    • Consider 60-day lookback as compromise if full removal not feasible.

:link: Resources & References

:megaphone: Call to Action

  • Provide Feedback: Builders are encouraged to offer feedback on their use cases for at-block to help core developers decide on the best path forward. Log your feedback under this thread.
  • 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
  • Contribute to Core repo: Engage with the Stacks core repo, open issues, review PRs, or jump into community channels to help move things forward.