Skip to content
91 changes: 46 additions & 45 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,54 +1,54 @@
# Stacks Improvement Proposals (SIPs)

The SIPs describe the design, implementation, and governance
of the Stacks 2.0 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 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.
[Get Involved](./README.md#how-to-get-involved)

## SIPs in the Process of Being Activated
## SIPs

* None

## Ratified 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) | The Clarity Smart Contract Language | 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| Ratified| 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|
| [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|
| [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|
| [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|
| [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|
| [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| Activation-In-Progress|
| [034](./sips/sip-034/sip-034.md)|Dimension-Specific Tenure Extend Variants| Activation-in-Progress|
| [035](./sips/sip-031/sip-031.md)|Clarification of Clarity's secp256r1-verify Behavior| Ratified|
Comment thread
wileyj marked this conversation as resolved.
Outdated
| [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](https://github.com/stacksgov/sips/pull/250)|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| Draft|
| [040](https://github.com/stacksgov/sips/pull/257)|SIP for improved post-conditions| Draft|
| [041](https://github.com/stacksgov/sips/pull/258)|Agent Registries (ERC-8004 on Stacks)| Draft|

* [SIP-000](./sips/sip-000/sip-000-stacks-improvement-proposal-process.md): The
Stacks Improvement Proposal Process
* [SIP-001](./sips/sip-001/sip-001-burn-election.md): Burn Election
* [SIP-002](./sips/sip-002/sip-002-smart-contract-language.md): The Clarity
Smart Contract Language
* [SIP-003](./sips/sip-003/sip-003-peer-network.md): Stacks P2P Network
* [SIP-004](./sips/sip-004/sip-004-materialized-view.md): Cryptographic
Commitment to Materialized Views
* [SIP-005](./sips/sip-005/sip-005-blocks-and-transactions.md): Blocks,
Transactions, and Accounts
* [SIP-006](./sips/sip-006/sip-006-runtime-cost-assessment.md): Clarity Cost
Execution Assessment
* [SIP-007](./sips/sip-007/sip-007-stacking-consensus.md): Stacking Consensus
* [SIP-008](./sips/sip-008/sip-008-analysis-cost-assessment.md): Clarity Parsing
and Analysis Cost Assessment
* [SIP-009](./sips/sip-009/sip-009-nft-standard.md): Standard Trait Definition
for Non-Fungible Tokens
* [SIP-010](./sips/sip-010/sip-010-fungible-token-standard.md): Standard Trait Definition for Fungible Tokens
* [SIP-012](./sips/sip-012/sip-012-cost-limits-network-upgrade.md): Burn Height Selection for a Network Upgrade to Introduce New Cost-Limits
* [SIP-013](./sips/sip-013/sip-013-semi-fungible-token-standard.md): Standard Trait Definition for Semi-Fungible Tokens
* [SIP-015](./sips/sip-015/sip-015-network-upgrade.md): Stacks Upgrade of Proof-of-Transfer and Clarity
* [SIP-016](./sips/sip-016/sip-016-token-metadata.md): Metadata for Tokens
* [SIP-018](./sips/sip-018/sip-018-signed-structured-data.md): Signed Structured Data
* [SIP-019](./sips/sip-019/sip-019-token-metadata-update-notifications.md): Notifications for Token Metadata Updates
* [SIP-020](./sips/sip-020/sip-020-bitwise-ops.md): Bitwise Operations in Clarity
* [SIP-021](./sips/sip-021/sip-021-nakamoto.md): Nakamoto: Fast and Reliable Blocks through PoX-assisted Block Propagation
* [SIP-022](./sips/sip-022/sip-022-emergency-pox-fix.md): Emergency Fix to PoX Stacking Increases
* [SIP-023](./sips/sip-023/sip-023-emergency-fix-traits.md): Emergency Fix to Trait Invocation Behavior
* [SIP-024](./sips/sip-024/sip-024-least-supertype-fix.md): Emergency Fix to Data Validation and Serialization Behavior
* [SIP-025](./sips/sip-025/sip-025-iterating-towards-weighted-schnorr-threshold-signatures.md): Iterating Towards WSTS
* [SIP-027](./sips/sip-027/sip-027-non-sequential-multisig-transactions.md): Non-sequential Multisig Transactions
* [SIP-028](./sips/sip-028/sip-028-sbtc_peg.md): Signer Criteria for sBTC, A Decentralized and Programmable Asset Backed 1:1 with BTC
* [SIP-029](./sips/sip-029/sip-029-halving-alignment.md): Bootstrapping sBTC Liquidity and Nakamoto Signer Incentives
* [SIP-031](./sips/sip-031/sip-031.md): Five-Year Stacks Growth Emissions
* [SIP-033](./sips/sip-033/sip-033-clarity4.md): Clarity Smart Contract Language, version 4
* [SIP-034](./sips/sip-034/sip-034.md): Dimension-Specific Tenure Extend Variants
* [SIP-035](./sips/sip-035/sip-secp256r1-verify.md): Clarification of Clarity's `secp256r1-verify` Behavior

## How to Get Involved

Expand Down Expand Up @@ -80,3 +80,4 @@ 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.