Skip to content

Commit 6d6c109

Browse files
ritaveritave
authored
Added CC0 license and updated all references (#178)
1 parent 1a390a9 commit 6d6c109

25 files changed

+110
-96
lines changed

‎CAIPs/caip-1.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -147,4 +147,4 @@ This document was derived heavily from [Bitcoin's BIP-0001] written by Amir Taak
147147

148148
## Copyright
149149

150-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
150+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-10.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -85,4 +85,4 @@ n/a
8585

8686
## Copyright
8787

88-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
88+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-104.md

+15-14
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,14 @@ matured and expanded, it has become clear that namespaces are more complex and
1515
multi-dimensional than can be efficiently governed over time in the current CAIP
1616
single-document structure; instead, a Namespace Reference is proposed that
1717
splits out the application of each cross-chain CAIP to a given namespace as a
18-
distinct document with its own ratification/supersession lifecycle. This way,
18+
distinct document with its own ratification/supersession lifecycle. This way,
1919
long-term specifications for low-level primitives like Chain IDs and addresses
2020
can be defined once and not be superseded by the addition or modification of
2121
higher-level specifications for RPC interfaces or multiple asset types.
2222

2323
In practical terms, that means each blockchain ecosystem's namespace is defined
24-
by a folder containing a distinct document for *each CAIP* applied to that
25-
namespace. At a high level, the important facts about a namespace, its
24+
by a folder containing a distinct document for _each CAIP_ applied to that
25+
namespace. At a high level, the important facts about a namespace, its
2626
governance, and its nomenclature can be defined/introduced in a `README.md`
2727
file, and each CAIP can be defined in a `caip{X}.md` file, where X is the number
2828
of the ratified CAIP.
@@ -35,7 +35,7 @@ specification of each feature or variant, as well as a rationale requiring
3535
little namespace-specific context. The namespace reference should include
3636
canonical (and ideally long-lived) links to authoritative documents, both when
3737
relied upon by the specified behavior AND when namespace-specific context is
38-
required to understand the inputs to or assumptions of the behavior.
38+
required to understand the inputs to or assumptions of the behavior.
3939

4040
The reference author is responsible for building consensus within the community
4141
and documenting dissenting opinions or rejected alternatives.
@@ -70,11 +70,12 @@ are included in the namespaces repo folder for easy cloning.
7070
Each reference document must begin with an [RFC
7171
822](https://www.ietf.org/rfc/rfc822.txt) style header preamble, preceded and
7272
followed by three hyphens (`---`). This header is also termed ["front matter" by
73-
Jekyll](https://jekyllrb.com/docs/front-matter/).
73+
Jekyll](https://jekyllrb.com/docs/front-matter/).
7474

7575
Please Note:
76-
- The headers must appear in the following order.
77-
- Headers marked with "*" are optional and are described below.
76+
77+
- The headers must appear in the following order.
78+
- Headers marked with "\*" are optional and are described below.
7879
- All other headers are required.
7980
- Lists/arrays in RFC822 must be encoded in the form `key: ["str1", "str2"]`,
8081
NOT `key: Str1, Str2`, even though single strings can be encoded in the form
@@ -83,7 +84,7 @@ Please Note:
8384

8485
` namespace-identifier:` <{unique lowercase alphanumeric string}[-caip{X}],
8586
where the optional suffix replaces X with the number of the applied CAIP unless
86-
the reference is a base namespace reference>
87+
the reference is a base namespace reference>
8788

8889
` title:` <{string1}[ - {string2}]>
8990

@@ -98,7 +99,7 @@ name and github username or email>
9899

99100
`* review-period-end:` <date review period ends>
100101

101-
` type:` <Standards Track (Core, Networking, Interface, ERC) | Informational | Meta>
102+
` type:` <Standards Track (Core, Networking, Interface, ERC) | Informational | Meta>
102103

103104
` * category:` <Core | Networking | Interface | ERC>
104105

@@ -171,7 +172,7 @@ status.
171172
#### `requires` header
172173

173174
Namespace-CAIPs may have a `requires` header, indicating the CAIP number(s) that
174-
this reference depends on.
175+
this reference depends on.
175176

176177
#### `superseded-by` and `replaces` headers
177178

@@ -215,11 +216,11 @@ This document was derived heavily from [CAIP-1][], which was in turn influenced
215216

216217
### Bibliography
217218

218-
[CAIP-1]: caip-1.md
219+
[caip-1]: caip-1.md
219220
[markdown]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
220-
[Bitcoin's BIP-0001]: https://github.com/bitcoin/bips
221-
[Python's PEP-0001]: https://www.python.org/dev/peps/
221+
[bitcoin's bip-0001]: https://github.com/bitcoin/bips
222+
[python's pep-0001]: https://www.python.org/dev/peps/
222223

223224
## Copyright
224225

225-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
226+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-122.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ The data model _MUST_ contain the following fields:
3939
| `version` | string | ✓ | Current version of the message. |
4040
| `statement` | string | | Human-readable ASCII assertion that the user will sign. It _MUST NOT_ contain `\n`. |
4141
| `nonce` | string | | Randomized token to prevent signature replay attacks. |
42-
| `issued-at` | string | | [RFC 3339][rfc 3339] `date-time` that indicates the issuance time. |
43-
| `expiration-time` | string | | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message is no longer valid. |
44-
| `not-before` | string | | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message starts being valid. |
42+
| `issued-at` | string | | [RFC 3339][rfc 3339] `date-time` that indicates the issuance time. |
43+
| `expiration-time` | string | | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message is no longer valid. |
44+
| `not-before` | string | | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message starts being valid. |
4545
| `request-id` | string | | System-specific identifier used to uniquely refer to the authentication request. |
4646
| `resources` | List of strings | | List of information or references to information the user wishes to have resolved as part of the authentication by the relying party; express as [RFC 3986][rfc 3986] URIs and separated by `\n`. |
4747
| `signature` | bytes | ✓ | Signature of the message signed by the wallet. |
@@ -167,4 +167,4 @@ Not applicable.
167167

168168
## Copyright
169169

170-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
170+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-13.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ To resolve a blockchain reference for the Polkadot namespace, make a JSON-RPC re
5454
"result": "0x91b171bb158e2d3848fa23a9f1c25182fb8e20313b2c1eb49219da7a70ce90c3"
5555
}
5656
```
57+
5758
The response will return as a value for the result a hash for the block with height 0 that should be sliced to its first 16 bytes (32 characters for base 16) to be CAIP-13 compatible.
5859

5960
## Rationale
@@ -85,4 +86,4 @@ Not applicable
8586

8687
## Copyright
8788

88-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
89+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-19.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -115,4 +115,4 @@ eip155:1/erc721:0x06012c8cf97BEaD5deAe237070F9587f8E7A266d/771769
115115

116116
## Copyright
117117

118-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
118+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-2.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -105,4 +105,4 @@ chainstd:8c3444cf8970a9e41a706fab93e7a6c4
105105

106106
## Copyright
107107

108-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
108+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-20.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -69,4 +69,4 @@ cosmos:iov-mainnet/slip44:234
6969

7070
## Copyright
7171

72-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
72+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-21.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ created: 2020-06-23
99
updated: 2020-06-23
1010
requires: 19
1111
superseded-by: https://github.com/ChainAgnostic/namespaces/tree/main/eip155/caip19.md
12-
1312
---
1413

1514
## Simple Summary
@@ -57,4 +56,4 @@ eip155:1/erc20:0x8f8221afbb33998d8584a2b05749ba73c37a938a
5756

5857
## Copyright
5958

60-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
59+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-22.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,4 +60,4 @@ eip155:1/erc721:0x06012c8cf97BEaD5deAe237070F9587f8E7A266d/771769
6060

6161
## Copyright
6262

63-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
63+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-23.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,12 @@ superseded-by: https://github.com/ChainAgnostic/namespaces/tree/main/fil
1515
This document is about the details of the Filecoin network namespace and reference for CAIP-2.
1616

1717
## Abstract
18+
1819
In CAIP-2 a general blockchain identification scheme is defined. This is the
1920
implementation of CAIP-2 for Filecoin network.
2021

2122
## Motivation
23+
2224
See CAIP-2.
2325

2426
## Specification
@@ -60,4 +62,4 @@ fil:f
6062

6163
## Copyright
6264

63-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
65+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-25.md

+34-34
Original file line numberDiff line numberDiff line change
@@ -59,17 +59,17 @@ given set of parameters by calling the following JSON-RPC request
5959
...
6060
}
6161
},
62-
62+
6363
}
6464
```
6565

6666
The JSON-RPC method is labelled as `provider_authorization` and expects one or
6767
more objects each named after the pertinent ChainAgnostic namespace and each
6868
containing with three parameters:
6969

70-
* chains - array of CAIP-2 compliant chainId's
71-
* methods - array of JSON-RPC methods expected to be used during the session
72-
* events - array of JSON-RPC message/events expected to be emitted during the
70+
- chains - array of CAIP-2 compliant chainId's
71+
- methods - array of JSON-RPC methods expected to be used during the session
72+
- events - array of JSON-RPC message/events expected to be emitted during the
7373
session
7474

7575
### Response
@@ -85,11 +85,11 @@ An example of a successful response should match the following format:
8585

8686
```jsonc
8787
{
88-
"id": 1,
89-
"jsonrpc": "2.0",
90-
"result": {
91-
"accounts": ["eip155:1:0xab16a96d359ec26a11e2c2b3d8f8b8942d5bfcdb"],
92-
}
88+
"id": 1,
89+
"jsonrpc": "2.0",
90+
"result": {
91+
"accounts": ["eip155:1:0xab16a96d359ec26a11e2c2b3d8f8b8942d5bfcdb"]
92+
}
9393
}
9494
```
9595

@@ -107,40 +107,40 @@ An example of an error response should match the following format:
107107

108108
```jsonc
109109
{
110-
"id": 1,
111-
"jsonrpc": "2.0",
112-
"error": {
113-
"code": 5000,
114-
"message": "User disapproved requested chains",
115-
}
110+
"id": 1,
111+
"jsonrpc": "2.0",
112+
"error": {
113+
"code": 5000,
114+
"message": "User disapproved requested chains"
115+
}
116116
}
117117
```
118118

119119
The valid error messages codes are the following:
120120

121-
* When user disapproves exposing accounts to requested chains
122-
* code = 5000
123-
* message = "User disapproved requested chains"
124-
* When user disapproves accepting calls with the request methods
125-
* code = 5001
126-
* message = "User disapproved requested methods"
127-
* When user disapproves accepting calls with the request events
128-
* code = 5002
129-
* message = "User disapproved requested events"
130-
* When wallet evaluates requested chains to not be supported
131-
* code = 5100
132-
* message = "Requested chains are not supported"
133-
* When wallet evaluates requested methods to not be supported
134-
* code = 5101
135-
* message = "Requested methods are not supported"
136-
* When wallet evaluates requested events to not be supported
137-
* code = 5102
138-
* message = "Requested events are not supported"
121+
- When user disapproves exposing accounts to requested chains
122+
- code = 5000
123+
- message = "User disapproved requested chains"
124+
- When user disapproves accepting calls with the request methods
125+
- code = 5001
126+
- message = "User disapproved requested methods"
127+
- When user disapproves accepting calls with the request events
128+
- code = 5002
129+
- message = "User disapproved requested events"
130+
- When wallet evaluates requested chains to not be supported
131+
- code = 5100
132+
- message = "Requested chains are not supported"
133+
- When wallet evaluates requested methods to not be supported
134+
- code = 5101
135+
- message = "Requested methods are not supported"
136+
- When wallet evaluates requested events to not be supported
137+
- code = 5102
138+
- message = "Requested events are not supported"
139139

140140
## Links
141141

142142
n/a
143143

144144
## Copyright
145145

146-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
146+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-26.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ The namespace "tezos" refers to the Tezos open-source blockchain platform.
3333
#### Reference Definition
3434

3535
The definition for this namespace will use the `genesis-block-hash` as an indentifier for different Tezos chains. The method for calculating the chain ID is as follows
36+
3637
```
3738
tezosB58CheckEncode('Net',
3839
firstFourBytes(
@@ -63,6 +64,7 @@ tezos:NetXm8tYqnMWky1
6364
## Links
6465

6566
- [Implementation](https://gitlab.com/tezos/tezos/blob/e7612c5ffa46570cdcc612f7bcead771edc24283/src/lib_crypto/chain_id.ml)
67+
6668
## Copyright
6769

68-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
70+
Copyright and related rights waived via [CC0](../LICENSE).

‎CAIPs/caip-27.md

+17-15
Original file line numberDiff line numberDiff line change
@@ -31,35 +31,37 @@ The application would interface with a provider to make request as follows:
3131

3232
```jsonc
3333
{
34-
"id": 1,
35-
"jsonrpc": "2.0",
36-
"method": "caip_request",
37-
"params": {
38-
"chainId": "eip155:1",
39-
"request": {
40-
"method": "personal_sign",
41-
"params": ["0x68656c6c6f20776f726c642c207369676e2074657374206d65737361676521", "0xa89Df33a6f26c29ea23A9Ff582E865C03132b140"]
42-
}
34+
"id": 1,
35+
"jsonrpc": "2.0",
36+
"method": "caip_request",
37+
"params": {
38+
"chainId": "eip155:1",
39+
"request": {
40+
"method": "personal_sign",
41+
"params": [
42+
"0x68656c6c6f20776f726c642c207369676e2074657374206d65737361676521",
43+
"0xa89Df33a6f26c29ea23A9Ff582E865C03132b140"
44+
]
4345
}
46+
}
4447
}
4548
```
4649

4750
The JSON-RPC method is labelled as `caip_request` and expects two parameters:
4851

49-
* chainId - CAIP-2 compatible chainId
50-
* request - an object containing the fields:
51-
* method - JSON-RPC method to request
52-
* params - JSON-RPC parameters to request
52+
- chainId - CAIP-2 compatible chainId
53+
- request - an object containing the fields:
54+
- method - JSON-RPC method to request
55+
- params - JSON-RPC parameters to request
5356

5457
### Response
5558

5659
The wallet will respond to the requested with the targeted chain connection and it will return a response with a success result or error message.
5760

58-
5961
## Links
6062

6163
n/a
6264

6365
## Copyright
6466

65-
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
67+
Copyright and related rights waived via [CC0](../LICENSE).

0 commit comments

Comments
 (0)