Skip to content

Mark 044 and 045 as ratified #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brice-stacks merged 2 commits into from
Jul 30, 2026
Merged

Mark 044 and 045 as ratified #275

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a0cbb0
mark 044 and 045 as ratified
brice-stacks Jul 22, 2026
0f9f04d
formatting
brice-stacks Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
148 changes: 75 additions & 73 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,89 +2,91 @@

The SIPs describe the design, implementation, and governance of the Stacks
blockchain.
The SIP process ([SIP-000](./sips/sip-000/sip-000-stacks-improvement-proposal-process.md)) describes how to make a SIP
and get it ratified. Anyone in the Stacks community may submit a SIP.
The SIP process
([SIP-000](./sips/sip-000/sip-000-stacks-improvement-proposal-process.md))
describes how to make a SIP and get it ratified. Anyone in the Stacks community
may submit a SIP.
[Get Involved](./README.md#how-to-get-involved)

## SIPs


| SIP Number | SIP Title | Status |
| :---------------------| :-------------------- | :----------- |
| [000](./sips/sip-000/sip-000-stacks-improvement-proposal-process.md)| The Stacks Improvement Proposal Process | Ratified |
| [001](./sips/sip-001/sip-001-burn-election.md) | Burn Election | Ratified |
| [002](./sips/sip-002/sip-002-smart-contract-language.md) | The Clarity Smart Contract Language | Ratified|
| [003](./sips/sip-003/sip-003-peer-network.md)|Stacks P2P Network|Ratified|
| [004](./sips/sip-004/sip-004-materialized-view.md)|Cryptographic Commitment to Materialized Views| Ratified|
| [005](./sips/sip-005/sip-005-blocks-and-transactions.md)|Blocks, Transactions, and Accounts| Ratified|
| [006](./sips/sip-006/sip-006-runtime-cost-assessment.md)|Clarity Cost Execution Assessment| Ratified|
| [007](./sips/sip-007/sip-007-stacking-consensus.md)|Stacking Consensus| Ratified|
| [008](./sips/sip-008/sip-008-analysis-cost-assessment.md)|Clarity Parsing and Analysis Cost Assessment| Ratified|
| [009](./sips/sip-009/sip-009-nft-standard.md)|Standard Trait Definition for Non-Fungible Tokens| Ratified|
| [010](./sips/sip-010/sip-010-fungible-token-standard.md)|Standard Trait Definition for Fungible Tokens| Ratified|
| [011](https://github.com/stacksgov/sips/pull/119)|The buy-in-ustx Standard for non-custodial Marketplace traits| Rejected|
| [012](./sips/sip-012/sip-012-cost-limits-network-upgrade.md)|Burn Height Selection for a Network Upgrade to Introduce New Cost-Limits| Ratified|
| [013](./sips/sip-013/sip-013-semi-fungible-token-standard.md)|Standard Trait Definition for Semi-Fungible Tokens| Ratified|
| [014](https://github.com/stacksgov/sips/pull/32)|Contract Documentation Standard| Withdrawn|
| [015](./sips/sip-015/sip-015-network-upgrade.md)|Stacks Upgrade of Proof-of-Transfer and Clarity| Ratified|
| [016](./sips/sip-016/sip-016-token-metadata.md)|Metadata for Tokens| Ratified|
| [017](https://github.com/stacksgov/sips/pull/56)|Schnorr Signatures| Withdrawn|
| [018](./sips/sip-018/sip-018-signed-structured-data.md)|Signed Structured Data| Ratified|
| [019](./sips/sip-019/sip-019-token-metadata-update-notifications.md)|Notifications for Token Metadata Updates| Ratified|
| [020](./sips/sip-020/sip-020-bitwise-ops.md)|Bitwise Operations in Clarity| Ratified|
| [021](./sips/sip-021/sip-021-nakamoto.md)|Nakamoto: Fast and Reliable Blocks through PoX-assisted Block Propagation| Ratified|
| [022](./sips/sip-022/sip-022-emergency-pox-fix.md)|Emergency Fix to PoX Stacking Increases| Ratified|
| [023](./sips/sip-023/sip-023-emergency-fix-traits.md)|Emergency Fix to Trait Invocation Behavior| Ratified|
| [024](./sips/sip-024/sip-024-least-supertype-fix.md)|Emergency Fix to Data Validation and Serialization Behavior| Ratified|
| [025](./sips/sip-025/sip-025-iterating-towards-weighted-schnorr-threshold-signatures.md)|Iterating Towards WSTS| Ratified|
| [026](https://github.com/stacksgov/sips/pull/153)|Clarity DeFi Vault SIP| Accepted|
| [027](./sips/sip-027/sip-027-non-sequential-multisig-transactions.md)|Non-sequential Multisig Transactions| Ratified|
| [028](./sips/sip-028/sip-028-sbtc_peg.md)|Signer Criteria for sBTC, A Decentralized and Programmable Asset Backed 1:1 with BTC| Ratified|
| [029](./sips/sip-029/sip-029-halving-alignment.md)|Bootstrapping sBTC Liquidity and Nakamoto Signer Incentives| Ratified|
| [030](./sips/sip-030/sip-030-wallet-interface.md)|Wallet RPC Standards| Recommended|
| [031](./sips/sip-031/sip-031.md)|Five-Year Stacks Growth Emissions| Ratified|
| [032](https://github.com/stacksgov/sips/pull/211)|Improved stacking| Draft|
| [033](./sips/sip-033/sip-033-clarity4.md)|Clarity Smart Contract Language, version 4| Ratified|
| [034](./sips/sip-034/sip-034.md)|Dimension-Specific Tenure Extend Variants| Ratified|
| [035](./sips/sip-035/sip-secp256r1-verify.md)|Clarification of Clarity's `secp256r1-verify` Behavior| Ratified|
| [036](https://github.com/stacksgov/sips/pull/219)|BTC addresses for Stacks transactions| Draft|
| [037](https://github.com/stacksgov/sips/pull/246)|Agent Coordination Framework| Draft|
| [038](./sips/sip-038/sip-enft-private-layer.md)|Standard Trait Definition for Commitment-Based Private Metadata (Encrypted NFTs)| Draft|
| [039](https://github.com/stacksgov/sips/pull/256)|Clarity 5 and Epoch 3.4| Ratified|
| [040](./sips/sip-040/sip-040-post-conds.md)|SIP for improved post-conditions| Ratified|
| [041](https://github.com/stacksgov/sips/pull/258)|Agent Registries (ERC-8004 on Stacks)| Draft|
| [042](./sips/sip-042/sip-042.md)|Removal of at-block| Ratified|
| [043](https://github.com/stacksgov/sips/pull/266)|Identicons for contracts| Draft|
| [044](https://github.com/stacksgov/sips/pull/267)|Clarity 6, staking and PoX post-conditions, and removal of the cost-voting contract| Accepted|
| [045](./sips/sip-045/sip-045-pox-5-bitcoin-staking.md)|PoX-5: Bitcoin Staking and Emission Schedule Alignment| Accepted|
| SIP Number | SIP Title | Status |
| :--------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------- | :---------- |
| [000](./sips/sip-000/sip-000-stacks-improvement-proposal-process.md) | The Stacks Improvement Proposal Process | Ratified |
| [001](./sips/sip-001/sip-001-burn-election.md) | Burn Election | Ratified |
| [002](./sips/sip-002/sip-002-smart-contract-language.md) | The Clarity Smart Contract Language | Ratified |
| [003](./sips/sip-003/sip-003-peer-network.md) | Stacks P2P Network | Ratified |
| [004](./sips/sip-004/sip-004-materialized-view.md) | Cryptographic Commitment to Materialized Views | Ratified |
| [005](./sips/sip-005/sip-005-blocks-and-transactions.md) | Blocks, Transactions, and Accounts | Ratified |
| [006](./sips/sip-006/sip-006-runtime-cost-assessment.md) | Clarity Cost Execution Assessment | Ratified |
| [007](./sips/sip-007/sip-007-stacking-consensus.md) | Stacking Consensus | Ratified |
| [008](./sips/sip-008/sip-008-analysis-cost-assessment.md) | Clarity Parsing and Analysis Cost Assessment | Ratified |
| [009](./sips/sip-009/sip-009-nft-standard.md) | Standard Trait Definition for Non-Fungible Tokens | Ratified |
| [010](./sips/sip-010/sip-010-fungible-token-standard.md) | Standard Trait Definition for Fungible Tokens | Ratified |
| [011](https://github.com/stacksgov/sips/pull/119) | The buy-in-ustx Standard for non-custodial Marketplace traits | Rejected |
| [012](./sips/sip-012/sip-012-cost-limits-network-upgrade.md) | Burn Height Selection for a Network Upgrade to Introduce New Cost-Limits | Ratified |
| [013](./sips/sip-013/sip-013-semi-fungible-token-standard.md) | Standard Trait Definition for Semi-Fungible Tokens | Ratified |
| [014](https://github.com/stacksgov/sips/pull/32) | Contract Documentation Standard | Withdrawn |
| [015](./sips/sip-015/sip-015-network-upgrade.md) | Stacks Upgrade of Proof-of-Transfer and Clarity | Ratified |
| [016](./sips/sip-016/sip-016-token-metadata.md) | Metadata for Tokens | Ratified |
| [017](https://github.com/stacksgov/sips/pull/56) | Schnorr Signatures | Withdrawn |
| [018](./sips/sip-018/sip-018-signed-structured-data.md) | Signed Structured Data | Ratified |
| [019](./sips/sip-019/sip-019-token-metadata-update-notifications.md) | Notifications for Token Metadata Updates | Ratified |
| [020](./sips/sip-020/sip-020-bitwise-ops.md) | Bitwise Operations in Clarity | Ratified |
| [021](./sips/sip-021/sip-021-nakamoto.md) | Nakamoto: Fast and Reliable Blocks through PoX-assisted Block Propagation | Ratified |
| [022](./sips/sip-022/sip-022-emergency-pox-fix.md) | Emergency Fix to PoX Stacking Increases | Ratified |
| [023](./sips/sip-023/sip-023-emergency-fix-traits.md) | Emergency Fix to Trait Invocation Behavior | Ratified |
| [024](./sips/sip-024/sip-024-least-supertype-fix.md) | Emergency Fix to Data Validation and Serialization Behavior | Ratified |
| [025](./sips/sip-025/sip-025-iterating-towards-weighted-schnorr-threshold-signatures.md) | Iterating Towards WSTS | Ratified |
| [026](https://github.com/stacksgov/sips/pull/153) | Clarity DeFi Vault SIP | Accepted |
| [027](./sips/sip-027/sip-027-non-sequential-multisig-transactions.md) | Non-sequential Multisig Transactions | Ratified |
| [028](./sips/sip-028/sip-028-sbtc_peg.md) | Signer Criteria for sBTC, A Decentralized and Programmable Asset Backed 1:1 with BTC | Ratified |
| [029](./sips/sip-029/sip-029-halving-alignment.md) | Bootstrapping sBTC Liquidity and Nakamoto Signer Incentives | Ratified |
| [030](./sips/sip-030/sip-030-wallet-interface.md) | Wallet RPC Standards | Recommended |
| [031](./sips/sip-031/sip-031.md) | Five-Year Stacks Growth Emissions | Ratified |
| [032](https://github.com/stacksgov/sips/pull/211) | Improved stacking | Draft |
| [033](./sips/sip-033/sip-033-clarity4.md) | Clarity Smart Contract Language, version 4 | Ratified |
| [034](./sips/sip-034/sip-034.md) | Dimension-Specific Tenure Extend Variants | Ratified |
| [035](./sips/sip-035/sip-secp256r1-verify.md) | Clarification of Clarity's `secp256r1-verify` Behavior | Ratified |
| [036](https://github.com/stacksgov/sips/pull/219) | BTC addresses for Stacks transactions | Draft |
| [037](https://github.com/stacksgov/sips/pull/246) | Agent Coordination Framework | Draft |
| [038](./sips/sip-038/sip-enft-private-layer.md) | Standard Trait Definition for Commitment-Based Private Metadata (Encrypted NFTs) | Draft |
| [039](https://github.com/stacksgov/sips/pull/256) | Clarity 5 and Epoch 3.4 | Ratified |
| [040](./sips/sip-040/sip-040-post-conds.md) | SIP for improved post-conditions | Ratified |
| [041](https://github.com/stacksgov/sips/pull/258) | Agent Registries (ERC-8004 on Stacks) | Draft |
| [042](./sips/sip-042/sip-042.md) | Removal of at-block | Ratified |
| [043](https://github.com/stacksgov/sips/pull/266) | Identicons for contracts | Draft |
| [044](./sips/sip-044/sip-044-clarity6.md) | Clarity 6, staking and PoX post-conditions, and removal of the cost-voting contract | Ratified |
| [045](./sips/sip-045/sip-045-pox-5-bitcoin-staking.md) | PoX-5: Bitcoin Staking and Emission Schedule Alignment | Ratified |

## How to Get Involved

There are several ways you can get involved with the SIP process:

* **SIP Editor**. SIP editors help SIP authors make sure their SIPs are
well-formed and follow the right process. They help get SIPs ready for deep
review by advancing it them from Draft to Accepted status. If you want to become a SIP editor,
open an issue with your name and email to ask to be added to the list of SIP editors.
- **SIP Editor**. SIP editors help SIP authors make sure their SIPs are
well-formed and follow the right process. They help get SIPs ready for deep
review by advancing it them from Draft to Accepted status. If you want to
become a SIP editor, open an issue with your name and email to ask to be added
to the list of SIP editors.

* **Joining a Consideration Advisory Board**. SIPs fall under the purview of
one or more considerations, such as "technical," "economic," "governance,"
and so on. A full list is in the `considerations/` directory. Members of SIP
consideration advisory boards use their domain expertise to give Accepted SIPs a
deep read, and give the authors any/all feedback to help make the SIP workable.
If you want to join a board, reach out to the board's chairperson via the
listed contact information.
- **Joining a Consideration Advisory Board**. SIPs fall under the purview of one
or more considerations, such as "technical," "economic," "governance," and so
on. A full list is in the `considerations/` directory. Members of SIP
consideration advisory boards use their domain expertise to give Accepted SIPs
a deep read, and give the authors any/all feedback to help make the SIP
workable. If you want to join a board, reach out to the board's chairperson
via the listed contact information.

* **Creating a Consideration Advisory Board**. Anyone can create a
consideration advisory board by opening a PR to create a new
consideration track, and SIP authors can opt to have you review their work by
adding your consideration to the SIP's list of considerations. You are expected
to vote on such SIPs in a fair and timely manner if you start a board.
- **Creating a Consideration Advisory Board**. Anyone can create a consideration
advisory board by opening a PR to create a new consideration track, and SIP
authors can opt to have you review their work by adding your consideration to
the SIP's list of considerations. You are expected to vote on such SIPs in a
fair and timely manner if you start a board.

* **Steering Committee**. The Steering Committee organizes the consideration
- **Steering Committee**. The Steering Committee organizes the consideration
advisory boards and votes to advance Recommended SIPs to
Activation-in-Progress status, and then to either Ratified or Rejected status.
Once they are in the process of being activated,
they use a SIP's Activation section to determine whether or not the Stacks
ecosystem has ratified or rejected the SIP. Joining this committee requires the
consent of the Stacks Foundation board.
Activation-in-Progress status, and then to either Ratified or Rejected status.
Once they are in the process of being activated, they use a SIP's Activation
section to determine whether or not the Stacks ecosystem has ratified or
rejected the SIP. Joining this committee requires the consent of the Stacks
Foundation board.