sip-standards

Explain SIP-009 and SIP-010 token standards with Clarity code examples.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/developerfred/bitcoin-yield-copilot --skill sip-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sip-standards
Source: https://github.com/developerfred/bitcoin-yield-copilot/tree/main/.skills/sip-standards
Command: npx skills add https://github.com/developerfred/bitcoin-yield-copilot --skill sip-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a comprehensive overview and practical examples of Stacks Improvement Proposals (SIPs) relevant to the VibeStamp project, focusing on token standards and contract interfaces.

Core Features & Use Cases

  • Token Standards: Explains SIP-009 (NFTs) and SIP-010 (Fungible Tokens) with VibeStamp-specific applications.
  • Contract Interfaces: Demonstrates how to define and use traits (SIP-013) for contract interoperability.
  • Use Case: Developers can use this skill to understand and implement Stacks token standards for creating NFTs (like VibeStamp certificates) and interacting with other contracts on the Stacks blockchain.

Quick Start

Review the SIP-009 NFT standard implementation example for VibeStamp certificates.

Frequently Asked Questions about sip-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement the SIP-009 NFT standard in Clarity?

To implement the SIP-009 NFT standard in Clarity, you define trait definitions for non-fungible tokens and include practical code examples for minting NFTs like VibeStamp certificates, ensuring contract interoperability on the Stacks blockchain.

What is the difference between SIP-009 and SIP-010 token standards?

SIP-009 defines the standard for non-fungible tokens (NFTs) on the Stacks blockchain, while SIP-010 specifies the interface for fungible tokens. Both provide trait definitions to ensure contract interoperability across different applications.

How do I use SIP-013 traits for contract interoperability in Stacks?

You use SIP-013 traits for contract interoperability in Stacks by defining and implementing standard trait interfaces in your Clarity contracts, allowing your tokens to interact seamlessly with other contracts on the blockchain.

How do I format token URIs and metadata for Stacks NFTs?

To format token URIs and metadata for Stacks NFTs, you follow the metadata standards specified in the SIP documentation, which define how token information is structured and retrieved for assets like VibeStamp certificates.

Can I use Clarity traits to make my Stacks contract interoperable with other tokens?

Yes, you can use Clarity traits to make your Stacks contract interoperable. By implementing SIP-009, SIP-010, and SIP-013 trait definitions, your contract can interact with other contracts respecting those standards on the Stacks blockchain.

What are the limitations when implementing Stacks Improvement Proposals for token contracts?

When implementing Stacks Improvement Proposals, limitations arise from strict trait compliance requirements. Your Clarity contract must precisely match SIP-009, SIP-010, or SIP-013 interface definitions to ensure interoperability without causing execution errors.