Weekly SIP Call #165 – Call Recap | Fri, 6 Mar 2026

SIP Weekly SIP call
1

Date: Fri, March 6, 2026, at 10:30 AM Eastern Time

Hosted by: HeroGamer; PeaceLoveMusic; Haddy

Duration: ~1 hr 15 mins

Recording: https://x.com/i/broadcasts/1kJzDMwDrqXKv?s=20 starting 1:34:32 ~ 2:50:20 or watch on Youtube

1. Agenda Overview

  • SIP-042 At-Block Removal Discussion

  • SIP-038 Status Update (Zenitron’s Encrypted NFT Proposal)

  • Consensus-Breaking SIP Approval Process

  • SIP-039 Clarity 5 Concerns

  • Bitcoin Governance Reference

2. Key Meeting Highlights

SIP-042 at-block Removal Discussion

  • Pruned Nodes Introduction:

    • Enables pruned nodes for the first time on the Stacks network

    • Chain state reached 1TB, posing a major barrier for node operators

    • Lowers hardware requirements for new participants

  • Archival Nodes Incentivization:

    • No official rewards for running archival nodes? - looking to verify

    • Risk of centralization if only Stacks Labs maintains archives

    • Sovereignty benefit: self-verify without third-party APIs

  • Runtime Error Risk:

    • Existing contracts using at-block function may break after Epoch 3.4 activation

    • Need workarounds or contract updates

  • Further clarification from core devs:

    • @Haddy to post questions on forum about archival node requirements, do miners, signers, pools need to run archival nodes or pruned node sufficient

SIP-038 Status Update (Zenitron’s Encrypted NFT Proposal)

  • Coordination:

    • Already reviewed, waiting for next coordination step

    • Foundation restructuring taking on the governance responsibilities

    • Next step: Foundation needs to coordinate Technical CAB vote

Consensus-Breaking SIP Approval Process

  • Review Practice:

    • Current practice: Only relevant CABs review (technical/economic/governance)

    • PeaceLove proposed to discuss/consider: All CABs should review consensus-breaking SIPs

    • Rationale: consensus-breaking SIPs requires broader perspective before community vote

    • If appropriate, make suggestion to SIP-000-1 upgrade

SIP-039 Clarity 5 Concerns

  • Haddy raised the topic of potentially needing Gas Fee Optimization:

    • No gas fee optimization built in for this proposal

    • Could potentially lead to DDoS attack vector with cheap transactions

    • Edge case: 128-level contract calls could block legitimate users transactions

    • @Haddy to post questions on forum about this concern to see if this has validity

Bitcoin Governance Reference

  • Ordinals BIP number assignment Rejection:

    • Casey Rodarmor’s proposal to request a BIP number denied by BIP editors

    • Protocol continues functioning without official Bitcoin Core repo “certification” number assignment

    • Learning opportunity for Stacks SIP editors

:link: Resources & References

:megaphone: Call To Action

→ Previous weeks recaps