Date: Tuesday, March 3, 2026, at 09:00 AM Eastern Time
Hosted by: Setzeus
Duration: ~45 mins
1. Agenda Overview
- SIP-042 Discussion: At-Block Removal
- SIP-040 Discussion: Improved Post Conditions (Non-Controversial)
- SIP-039 Discussion: Clarity 5 Fixes & Technical Updates (Non-Controversial)
- Clarinet Linter
- Contract Identity Naming Conventions
2. Key Meeting Highlights
SIP-042 Discussion: at-block Removal
- More controversial of the 3 SIPs.
- Good summary of the 3 SIPs and their trade-offs in last Friday SIP call #164
- Current Blockchain State:
- Chain state size reached 1TB (BowTiedRadone’s data point) - major barrier for node operators
at-blockforces all nodes to keep complete chain state data vs allowing pruned nodes
- Proposal: Remove
at-blockFunctionality- Known bugs in at-block function
- Only 7-8 contracts actively use
at-block - Is there any financial value users can’t recover? (raised by HeroG)
- Trade-offs and Safeguards:
- Collective storage savings: millions of dollars across network (Adriano’s estimate)
- Future Considerations:
- Alternative design principle discussed: “fetch less, prove more” - instead of relying on at-block to fetch old chain state directly, contracts should favor proving past state with cryptographic proofs brought into the contract
- Community reporting
- Community should report any severely broken use cases affected by
at-blockremoval (Adriano)
- Community should report any severely broken use cases affected by
SIP-40 Discussion: Improved Post Conditions (Non-Controversial)
- Transaction Security:
- New “originator mode” for wallet asset protection
- Useful for complex DeFi interactions where you only care about your own asset movements
- NFT post conditions enhancement:
- Current: NFT sends or doesn’t send (binary)
- New: “Maybe send” option (equivalent to fungible token’s “less than or equal”)
- Future Considerations:
- Dedicated address/principal specification for smart wallets
SIP-039 Discussion: Clarity 5 Fixes & Technical Updates (Non-Controversial)
- Technical Fixes:
- Fixes Secp256r1 function and at-block issues, and more → See forum post.
- All three SIPs will be voted on together (not individually due to process complexity)
Clarinet Linter
- New Linter Released:
- Detects unused functions and common anti-patterns (announced by Hugo)
- Upcoming: case-enforcement rules for variables/functions/constants
- Hugo will demo the linter in a future ClarityWG call and requested community feedback
Contract Identity Naming Conventions
- Discussion Points:
- Timothy raised interest in stricter naming/case conventions and “identity” cues (e.g., identicons, consistent prefixes) to reduce UX/security confusion
- Safer naming and identity patterns in contracts/principals
- Possible follow-ups: additional linter rules plus written best-practice guidelines
Resources & References
- “At-Block” Change: Forum post: Chain State Pruning and `at-block` Proposed Change
- Improved Post Conditions: Forum post: Improved Post-Conditions
- Clarity 5 and Epoch 3.4: Forum: Clarity 5 (and epoch 3.4)
- Identicons idea: Forum: Identicon for Contracts
- Clarinet Linter
Call To Action
- Feedback on the 3 SIP proposals: Review and feedback to the SIP authors via the Forum or on the relevant SIP proposals in SIP Repo.
- Join next week’s ecosystem calls: see Stacks Events Calendar
- Follow Stacks Foundation X handle for SIP vote updates.