Stacks Improvement Proposals.

This SIP proposes appchains as a scaling solution for the Stacks blockchain. Instead of sharing a single blockchain, different applications can instantiate their own Stacks network, called an _appchain_, which is mined via a smart contract deployed on an existing Stacks network (which can be either the Stacks blockchain, or another appchain). Each appchain has its own native token, its own set of miners (who mine the appchain's token), and most importantly, its own block capacity. Appchain networks are organized hierarchically: the Stacks blockchain is the root of the hierarchy, and each appch…

This document evaluates the consequences of turning the tokens being burnt for minting Stacks into a source of funding for its base chain.

Web applications often provide their services only to authenticated users. In Web2, this was done through username and password or federated logins. In Web3, users can prove their digital identity by cryptographically signing that the user ownes the private key associated with that digital identity. SIP-018 defines the structure of signatures in general. This SIP defines the message format that web applications and similar off-chain services should use for their users to sign.

This standard provides additional functions to digital assets (i.e. tokens) so that they can be made availble to buy from the owners public address. This in effect enables an open, decentralized marketplace for digital assets.

One of the main use cases of Bitcoin Ordinal Inscriptions is the decentralized and censorship-resistant storage of arbitrary data in the Bitcoin blockchain, a feature which is most commonly used by artists and token creators to store artwork or metadata. Given that the Stacks network has a very close relationship to Bitcoin, Stacks developers are looking for a standardized way to reference the contents of inscriptions to use within their smart contracts or applications. This SIP defines a simple URI format that Stacks developers can use to make such a reference so that content can be used in a…

This Stacks Improvement Proposal (SIP) aims to address the issue of commingled collateral positions on the Stacks blockchain's Clarity-based DeFi applications. Currently, due to Clarity's design, it is challenging for users to identify their specific collateral positions within the Stacks Explorer. This SIP proposes the creation of a common interface for contracts that hold SIP-010 assets. Implementing this interface will enable users to view their collateral positions distinctly, improving the overall user experience of Stacks DeFi applications.

This proposal extends the SIP-010 standard trait for fungible tokens on the Stacks blockchain to support composable fungible tokens with allowances. It adds further requirements to the previous standard, which is the bare minimum to have a standard for a fungible token, featuring mainly token tranfers. There are no specifications how to make transfers via third-party services. For atomic and composable transfers we introduce allowances. The new trait includes functions for transferring tokens (transfer limited to the contract-caller sender), approving allowances (approve and revoke), checking…

This SIP proposes the creation of a trust-minimized 2-way peg in which BTC (the tokens of the current Stacks burnchain) can be manifested on Stacks as a SIP-010-compliant fungible token, called sBTC, and later redeemed for the same number of BTC. This proposal redefines the act of Stacking to be the act of maintaining an _sBTC wallet_, which is used to hold BTC and process sBTC redemptions. Stackers are collectively responsible for ensuring that all liquid sBTC are backed by an equal number of BTC, and that redemptions are processed in a timely manner. As a reward, they continue to receive PoX…

Dynamic Dispatch is a pattern that developers can utilize in their smart contracts to enable routing of contract calls at runtime. This routing directs the calls to contracts deployed on the Stacks blockchain subsequent to the initial deployment of the smart contract. This is in contrast to Static Dispatch, where contract IDs are hard-coded into the contract. In the Clarity 1 and Clarity 2 implementations, the contract-call? function can be only be use with a contract ID coming from the list of arguments signed by the transaction author. This SIP reevaluates the existing approach and proposes…

Stacks Pay defines a URL-based payment-request format for the Stacks blockchain. By standardising how payment information is encoded, decoded, and displayed, it guarantees that any wallet or application implementing this specification can interoperate with any other. Stacks Pay is purely an application-layer standard: it introduces no changes to consensus, token emission, or on-chain data structures. Think of it as a shareable wrapper around an ordinary Stacks transaction. > RFC 2119 terminology > The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, > SHOULD, SHOULD NOT, RECOMMENDED, MAY,…

This SIP corrects the behavior of the Clarity keyword burn-block-height inside of an at-block statement.

This SIP defines a minimalist trait interface for liquidity pools on the Stacks blockchain. The standard enables independent implementation of liquidity pools while maintaining a unified interface, facilitating the development of swap aggregators and multi-hop transactions across multiple pools. The standard introduces an extensible opcode buffer system that enables advanced pool operations while maintaining a simple core interface.

A Stacks Improvement Proposal (SIP) is a design document that provides information to the greater Stacks ecosystem's participants concerning the design of the Stacks blockchain and its ongoing operation. Each SIP shall provide a clear and concise description of features, processes, and/or standards for the Stacks blockchain and its operators to adopt, with sufficient details provided such that a reasonable practitioner may use the document to create an independent but compatible implementation of the proposed improvement. SIPs are the canonical medium by which new features are proposed and des…

This SIP proposes a framework for implementing a standardized reputation system on apps or websites. Reputation transactions will result in the minting of Non-Fungible Tokens (NFTs) to provide a verifiable and immutable record of reputation events. The proposal outlines standard attributes for reputation systems, the structure for XML and JSON representation, and the NFT minting process.

This SIP proposes the integration of zero-authority infrastructure into a unified coordination layer enabling decentralized communities to operate without intermediaries. Powered by ConsoleDAO assets, the system introduces agent-driven workflows for events, gigs, bounties, and quests, with transparent onchain reputation and value distribution. By extending existing traction from the Stacks ecosystem into broader networks, the proposal establishes a scalable, permissionless framework for human and AI collaboration. CollectiveOS serves as the interface layer, providing seamless tools for governa…