> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/learn/zh/network-fundamentals/sips.md).
# SIP
### Stacks 改进提案（SIP）
Stacks 改进提案（SIP）旨在描述 Stacks 区块链的实现，以及提出改进建议。
SIP 流程 [（SIP-000）](https://github.com/stacksgov/sips/blob/main/sips/sip-000/sip-000-stacks-improvement-proposal-process.md) 描述如何创建一份 SIP 并使其获得批准。
它们应包含功能或标准的简明技术规范，以及其背后的理由。SIP 旨在成为提出新功能、就系统级问题收集社区意见以及记录设计决策的主要媒介。
SIP 存放在 [stacksgov/sips](https://github.com/stacksgov/sips) 代码库中，作为 [Stacks 社区治理组织](https://github.com/stacksgov).
Stacks 社区中的任何人都可以提交 SIP。
{% hint style="info" %}
Stacks 改进提案社区会议：将 [每周社区 SIP 会议](https://www.addevent.com/event/wS15955379) 添加到你的日历中。
{% endhint %}
### 已批准的 SIP
* [x] [SIP-000：Stacks 改进提案流程](https://github.com/stacksgov/sips/blob/main/sips/sip-000/sip-000-stacks-improvement-proposal-process.md)
* [x] [SIP-001：销毁选举](https://github.com/stacksgov/sips/blob/main/sips/sip-001/sip-001-burn-election.md)
* [x] [SIP-002：Clarity 智能合约语言](https://github.com/stacksgov/sips/blob/main/sips/sip-002/sip-002-smart-contract-language.md)
* [x] [SIP-003：Stacks P2P 网络](https://github.com/stacksgov/sips/blob/main/sips/sip-003/sip-003-peer-network.md)
* [x] [SIP-004：对物化视图的密码学承诺](https://github.com/stacksgov/sips/blob/main/sips/sip-004/sip-004-materialized-view.md)
* [x] [SIP-005：区块、交易与账户](https://github.com/stacksgov/sips/blob/main/sips/sip-005/sip-005-blocks-and-transactions.md)
* [x] [SIP-006：Clarity 执行成本评估](https://github.com/stacksgov/sips/blob/main/sips/sip-006/sip-006-runtime-cost-assessment.md)
* [x] [SIP-007：Stacking 共识](https://github.com/stacksgov/sips/blob/main/sips/sip-007/sip-007-stacking-consensus.md)
* [x] [SIP-008：Clarity 解析与分析成本评估](https://github.com/stacksgov/sips/blob/main/sips/sip-008/sip-008-analysis-cost-assessment.md)
* [x] [SIP-009：非同质化代币标准特性定义](https://github.com/stacksgov/sips/blob/main/sips/sip-009/sip-009-nft-standard.md)
* [x] [SIP-010：同质化代币标准特性定义](https://github.com/stacksgov/sips/blob/main/sips/sip-010/sip-010-fungible-token-standard.md)
* [x] [SIP-012：为引入新成本上限的网络升级选择销毁高度](https://github.com/stacksgov/sips/blob/main/sips/sip-012/sip-012-cost-limits-network-upgrade.md)
* [x] [SIP-013：半同质化代币标准特性定义](https://github.com/stacksgov/sips/blob/main/sips/sip-013/sip-013-semi-fungible-token-standard.md)
* [x] [SIP-015：证明转移与 Clarity 的 Stacks 升级](https://github.com/stacksgov/sips/blob/main/sips/sip-015/sip-015-network-upgrade.md)
* [x] [SIP-016：数字资产元数据的模式定义](https://github.com/stacksgov/sips/blob/main/sips/sip-016/sip-016-token-metadata.md)
* [x] [SIP-018：签名结构化数据](https://github.com/stacksgov/sips/blob/main/sips/sip-018/sip-018-signed-structured-data.md)
* [x] [SIP-019：代币元数据更新通知](https://github.com/stacksgov/sips/blob/main/sips/sip-019/sip-019-token-metadata-update-notifications.md)
* [x] [SIP-020：Clarity 中的位运算](https://github.com/stacksgov/sips/blob/main/sips/sip-020/sip-020-bitwise-ops.md)
* [x] [SIP-021：Nakamoto：通过 PoX 辅助区块传播实现快速可靠的区块](https://github.com/stacksgov/sips/blob/main/sips/sip-021/sip-021-nakamoto.md)
* [x] [SIP-022：PoX Stacking 增加的紧急修复](https://github.com/stacksgov/sips/blob/main/sips/sip-022/sip-022-emergency-pox-fix.md)
* [x] [SIP-023：特性调用行为的紧急修复](https://github.com/stacksgov/sips/blob/main/sips/sip-023/sip-023-emergency-fix-traits.md)
* [x] [SIP-024：数据验证与序列化行为的紧急修复](https://github.com/stacksgov/sips/blob/main/sips/sip-024/sip-024-least-supertype-fix.md)
* [x] [SIP-025：朝着加权 Schnorr 阈值签名迭代](https://github.com/stacksgov/sips/blob/main/sips/sip-025/sip-025-iterating-towards-weighted-schnorr-threshold-signatures.md)
* [x] [SIP-027：非顺序多重签名交易](https://github.com/stacksgov/sips/blob/main/sips/sip-027/sip-027-non-sequential-multisig-transactions.md)
* [x] [SIP-028：sBTC 的签名者标准，一种以 BTC 1:1 支持的去中心化且可编程资产](https://github.com/stacksgov/sips/blob/main/sips/sip-028/sip-028-sbtc_peg.md)
* [x] [SIP-029：Stacks 网络升级期间保持经济激励](https://github.com/stacksgov/sips/blob/main/sips/sip-029/sip-029-halving-alignment.md)
* [x] [SIP-031：五年期 Stacks 增长排放](https://github.com/stacksgov/sips/blob/main/sips/sip-031/sip-031.md)
* [x] [SIP-033：Clarity 智能合约语言，第 4 版](https://github.com/stacksgov/sips/blob/main/sips/sip-033/sip-033-clarity4.md)
* [x] [SIP-034：按维度特定的任期延长变体](https://github.com/stacksgov/sips/blob/main/sips/sip-034/sip-034.md)
* [x] [SIP-035：澄清 Clarity 的 `secp256r1-verify` 行为](https://github.com/stacksgov/sips/blob/main/sips/sip-035/sip-secp256r1-verify.md)
* [x] [SIP-044：Clarity 6、质押和 PoX 后置条件，以及移除成本投票合约](https://github.com/stacksgov/sips/blob/main/sips/sip-044/sip-044-clarity6.md)
* [x] [SIP-045：PoX-5：比特币质押与发行计划对齐](https://github.com/stacksgov/sips/blob/main/sips/sip-045/sip-045-pox-5-bitcoin-staking.md)
### 如何参与
你可以通过几种方式参与 SIP 流程：
* **加入每周 SIP 会议**, [此处](https://community.stacks.org/events).
* **SIP 编辑**。SIP 编辑帮助 SIP 作者确保其 SIP 结构正确并遵循正确流程。他们通过将 SIP 从草案推进到已接受状态，帮助其进入深入审查阶段。如果你想成为 SIP 编辑，请以你的姓名和邮箱创建一个 issue，申请加入 SIP 编辑名单。
* **加入 CAB** （考量咨询委员会）。SIP 归属于一个或多个考量范围。完整列表见 [这个 GitHub](https://github.com/stacksgov/sips/tree/main/considerations) 目录中。目前它们包括：多样性、经济、伦理、治理和技术。SIP 考量咨询委员会成员会运用其领域专业知识，对已接受的 SIP 进行深入阅读，并向作者提供任何/所有反馈，以帮助该 SIP 变得可行。如果你想加入某个委员会，请通过列出的联系信息联系该委员会主席。
* **指导委员会**。指导委员会组织考量咨询委员会，并投票将推荐的 SIP 推进到“激活中”状态，然后再进入“已批准”或“已拒绝”状态。一旦进入激活流程，他们会使用 SIP 的激活部分来确定 Stacks 生态系统是否已批准或拒绝该 SIP。加入该委员会需要获得 Stacks Foundation 董事会的同意。
***
### 更多资源
* [\[Stacks 社区 YT\]](https://www.youtube.com/playlist?list=PLg717Ri_rTnx5kuaWqp3cUAtwQk_yzslT) 已录制的 SIP 会议（旧版）
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.stacks.co/learn/zh/network-fundamentals/sips.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
