CAIPs

Chain Agnostic Improvement Proposals (CAIPs) describe standards for blockchain projects that are not specific to a single chain.

Contributing

1. Review CAIP-1.
2. Fork the repository.
3. Add your CAIP to your fork of the repository. There is a template CAIP here.
4. Submit a Pull Request to Chain Agnostics's CAIPs repository.

Your first PR should be a first draft of the final CAIP. An editor will manually review the first PR for a new CAIP and assign it a number before merging it. Make sure you include a discussions-to header with the URL to a discussion forum or open GitHub issue where people can discuss the CAIP as a whole.

If your CAIP requires images, the image files should be included in a subdirectory of the assets folder for that CAIP as follows: assets/caip-N (where N is to be replaced with the CAIP number). When linking to an image in the CAIP, use relative links such as ../assets/caip-1/image.png.

CAIP Status Terms

• Draft - an CAIP that is undergoing rapid iteration and changes.
• Last Call - an CAIP that is done with its initial iteration and ready for review by a wide audience.
• Accepted - a core CAIP that has been in Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author.

CAIP Index

• CAIP-1 - CAIP Purpose and Guidelines
• CAIP-2 - Blockchain ID Specification
• CAIP-10 - Account ID Specification
• CAIP-19 - Asset Type and Asset ID Specification
• CAIP-20 - Asset Reference for the SLIP44 Asset Namespace
• CAIP-21 - Asset Reference for the ERC20 Asset Namespace
• CAIP-22 - Asset Reference for the ERC721 Asset Namespace
• CAIP-25 - Chain Agnostic Provider Handshake
• CAIP-27 - Chain Agnostic Provider Request
• CAIP-29 - Asset Reference for the ERC1155 Asset Namespace
• CAIP-74 - CACAO: Chain Agnostic CApability Object
• CAIP-104 - Namespace Reference Purpose and Guidelines

Namespaces

Previously there were specific CAIPs for what is now referred to as namespaces. Chain Agnostic Namespaces describe a blockchain ecosystem or set of ecosystems as a namespace, relying as much as possible on the CAIP specifications to minimize the research needed to interact with assets, contracts, and accounts in that namespace.