Added CC0 license and updated all references (#178)

Author: ritave

CAIPs/caip-1.md

@@ -147,4 +147,4 @@ This document was derived heavily from [Bitcoin's BIP-0001] written by Amir Taak
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-10.md

@@ -85,4 +85,4 @@ n/a
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-104.md

@@ -15,14 +15,14 @@ matured and expanded, it has become clear that namespaces are more complex and
 multi-dimensional than can be efficiently governed over time in the current CAIP
 single-document structure; instead, a Namespace Reference is proposed that
 splits out the application of each cross-chain CAIP to a given namespace as a
-distinct document with its own ratification/supersession lifecycle.  This way,
+distinct document with its own ratification/supersession lifecycle. This way,
 long-term specifications for low-level primitives like Chain IDs and addresses
 can be defined once and not be superseded by the addition or modification of
 higher-level specifications for RPC interfaces or multiple asset types.
 
 In practical terms, that means each blockchain ecosystem's namespace is defined
-by a folder containing a distinct document for *each CAIP* applied to that
-namespace.  At a high level, the important facts about a namespace, its
+by a folder containing a distinct document for _each CAIP_ applied to that
+namespace. At a high level, the important facts about a namespace, its
 governance, and its nomenclature can be defined/introduced in a `README.md`
 file, and each CAIP can be defined in a `caip{X}.md` file, where X is the number
 of the ratified CAIP.
@@ -35,7 +35,7 @@ specification of each feature or variant, as well as a rationale requiring
 little namespace-specific context. The namespace reference should include
 canonical (and ideally long-lived) links to authoritative documents, both when
 relied upon by the specified behavior AND when namespace-specific context is
-required to understand the inputs to or assumptions of the behavior.  
+required to understand the inputs to or assumptions of the behavior.
 
 The reference author is responsible for building consensus within the community
 and documenting dissenting opinions or rejected alternatives.
@@ -70,11 +70,12 @@ are included in the namespaces repo folder for easy cloning.
 Each reference document must begin with an [RFC
 822](https://www.ietf.org/rfc/rfc822.txt) style header preamble, preceded and
 followed by three hyphens (`---`). This header is also termed ["front matter" by
-Jekyll](https://jekyllrb.com/docs/front-matter/). 
+Jekyll](https://jekyllrb.com/docs/front-matter/).
 
 Please Note:
-- The headers must appear in the following order. 
-- Headers marked with "*" are optional and are described below.
+
+- The headers must appear in the following order.
+- Headers marked with "\*" are optional and are described below.
   - All other headers are required.
 - Lists/arrays in RFC822 must be encoded in the form `key: ["str1", "str2"]`,
   NOT `key: Str1, Str2`, even though single strings can be encoded in the form
@@ -83,7 +84,7 @@ Please Note:
 
 ` namespace-identifier:` <{unique lowercase alphanumeric string}[-caip{X}],
 where the optional suffix replaces X with the number of the applied CAIP unless
-the reference is a base namespace reference> 
+the reference is a base namespace reference>
 
 ` title:` <{string1}[ - {string2}]>
 
@@ -98,7 +99,7 @@ name and github username or email>
 
 `* review-period-end:` <date review period ends>
 
-` type:` <Standards Track (Core, Networking, Interface, ERC)  | Informational | Meta>
+` type:` <Standards Track (Core, Networking, Interface, ERC) | Informational | Meta>
 
 ` * category:` <Core | Networking | Interface | ERC>
 
@@ -171,7 +172,7 @@ status.
 #### `requires` header
 
 Namespace-CAIPs may have a `requires` header, indicating the CAIP number(s) that
-this reference depends on. 
+this reference depends on.
 
 #### `superseded-by` and `replaces` headers
 
@@ -215,11 +216,11 @@ This document was derived heavily from [CAIP-1][], which was in turn influenced
 
 ### Bibliography
 
-[CAIP-1]: caip-1.md
+[caip-1]: caip-1.md
 [markdown]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
-[Bitcoin's BIP-0001]: https://github.com/bitcoin/bips
-[Python's PEP-0001]: https://www.python.org/dev/peps/
+[bitcoin's bip-0001]: https://github.com/bitcoin/bips
+[python's pep-0001]: https://www.python.org/dev/peps/
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-122.md

@@ -39,9 +39,9 @@ The data model _MUST_ contain the following fields:
 | `version`         | string          | ✓         | Current version of the message.                                                                                                                                                                   |
 | `statement`       | string          |           | Human-readable ASCII assertion that the user will sign. It _MUST NOT_ contain `\n`.                                                                                                               |
 | `nonce`           | string          |           | Randomized token to prevent signature replay attacks.                                                                                                                                             |
-| `issued-at`       | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates the issuance time.                                                                                                                                   |
-| `expiration-time` | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message is no longer valid.                                                                                           |
-| `not-before`      | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message starts being valid.                                                                                           |
+| `issued-at`       | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates the issuance time.                                                                                                                                |
+| `expiration-time` | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message is no longer valid.                                                                                        |
+| `not-before`      | string          |           | [RFC 3339][rfc 3339] `date-time` that indicates when the signed authentication message starts being valid.                                                                                        |
 | `request-id`      | string          |           | System-specific identifier used to uniquely refer to the authentication request.                                                                                                                  |
 | `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`. |
 | `signature`       | bytes           | ✓         | Signature of the message signed by the wallet.                                                                                                                                                    |
@@ -167,4 +167,4 @@ Not applicable.
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-13.md

@@ -54,6 +54,7 @@ To resolve a blockchain reference for the Polkadot namespace, make a JSON-RPC re
   "result": "0x91b171bb158e2d3848fa23a9f1c25182fb8e20313b2c1eb49219da7a70ce90c3"
 }
 ```
+
 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.
 
 ## Rationale
@@ -85,4 +86,4 @@ Not applicable
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-19.md

@@ -115,4 +115,4 @@ eip155:1/erc721:0x06012c8cf97BEaD5deAe237070F9587f8E7A266d/771769
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-2.md

@@ -105,4 +105,4 @@ chainstd:8c3444cf8970a9e41a706fab93e7a6c4
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-20.md

@@ -69,4 +69,4 @@ cosmos:iov-mainnet/slip44:234
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-21.md

@@ -9,7 +9,6 @@ created: 2020-06-23
 updated: 2020-06-23
 requires: 19
 superseded-by: https://github.com/ChainAgnostic/namespaces/tree/main/eip155/caip19.md
-
 ---
 
 ## Simple Summary
@@ -57,4 +56,4 @@ eip155:1/erc20:0x8f8221afbb33998d8584a2b05749ba73c37a938a
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).

CAIPs/caip-22.md

@@ -60,4 +60,4 @@ eip155:1/erc721:0x06012c8cf97BEaD5deAe237070F9587f8E7A266d/771769
 
 ## Copyright
 
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+Copyright and related rights waived via [CC0](../LICENSE).