Skip to content

Commit 6beec4d

Browse files
author
Bumblefudge
authored
Feat/scope expansion in CAIP-1 (ChainAgnostic#99)
* to add non-blockchain language * rephrasing for clarity
1 parent 1b6b08d commit 6beec4d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

CAIPs/caip-1.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,15 @@ updated: 2019-08-31
1010

1111
## What is an CAIP?
1212

13-
CAIP stands for Chain Agnostic Improvement Proposal. An CAIP is a design document providing information to the community or describing a standard to be used across multiple chains. The CAIP should provide a concise technical specification of the feature and a rationale for the feature. The CAIP author is responsible for building consensus within the community and documenting dissenting opinions.
13+
CAIP stands for Chain Agnostic Improvement Proposal. An CAIP is a design document providing information to the community or describing a standard to be used across multiple "chains." To be more precise, a CAIP may describe capabilities applicable to any sequential orderings of cryptographically hashed commitments, including non-blockchain systems that can interoperate with blockchains productively, such as DAGs, sharded systems, git systems using keyserver-based PKI, etc. The CAIP should provide a concise technical specification of the feature and a rationale for the feature. The CAIP author is responsible for building consensus within the community and documenting dissenting opinions.
1414

1515
## CAIP Rationale
1616

1717
Currently it is often the case that a standard defined in one chain is also used in another chain. E.g. the usage of BIP39 in Ethereum applications. Also there is no real place to propose a standard that can be used for multiple chains (like mnemonics) currently. CAIPs are intended to fill this gap and be a place where such standards can live.
1818

1919
## CAIP Formats and Templates
2020

21-
CAIPs should be written in [markdown] format.
21+
CAIPs should be written in [markdown][] format.
2222
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`.
2323

2424
## CAIP Header Preamble

0 commit comments

Comments
 (0)