From ece9467d7d75d950abbe996f0660628b7230a9e0 Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 15:43:17 +0200 Subject: [PATCH 1/5] more explicit recommendation to read namespaces in canonicalization section --- CAIPs/caip-10.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/CAIPs/caip-10.md b/CAIPs/caip-10.md index 8ad183b9..912c3669 100644 --- a/CAIPs/caip-10.md +++ b/CAIPs/caip-10.md @@ -71,19 +71,16 @@ The goals of the general account ID format is: ## Canonicalization -Note that some namespaces like the EVM offer canonicalization schemes that use -capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some -other transformation. At the present time, this specification does NOT require -canonicalization, and implementers are advised to consider deduplication or -canonicalization in their consumption of CAIP-addresses. CAIP-10 profiles in -CASA [namespaces][] may contain additional information per namespace. +Note that some namespaces like the EVM offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. +At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. +Furthermore, it is always recommended that implementers read carefully any guidance in the relevant CAIP-10 profiles in CASA [namespaces][] for additional information per namespace about security and canonicalization conventions. ## Test Cases This is a list of manually composed examples ``` -# Ethereum mainnet (canonicalized with [EIP-55][] checksum) +# Ethereum mainnet (canonicalized with [EIP-55][] Checksum Case) eip155:1:0xab16a96D359eC26a11e2C2b3d8f8B8942d5Bfcdb # Bitcoin mainnet @@ -125,8 +122,8 @@ of specification for details. ## Changelog -- 2022-10-23: expanded charset to include `-`,`.`, and `%`; also added - canonicalization section and links +- 2024-07-19: more explicit recommendation to read namespaces in canonicalization section +- 2022-10-23: expanded charset to include `-`,`.`, and `%`; also added canonicalization section and links - 2022-03-10: update RegEx to incorporate CAIP-2 reference - 2021-08-11: switch from `{account id}@{chain id}` to `{chain id}:{account id}` syntax From 53d6365e63a237e700b75f6a418f9617ae5535ba Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 16:17:53 +0200 Subject: [PATCH 2/5] wordsmithing --- CAIPs/caip-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CAIPs/caip-10.md b/CAIPs/caip-10.md index 912c3669..a9ee4aa2 100644 --- a/CAIPs/caip-10.md +++ b/CAIPs/caip-10.md @@ -71,7 +71,7 @@ The goals of the general account ID format is: ## Canonicalization -Note that some namespaces like the EVM offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. +Note that some namespaces like the `eip155` (i.e. ethereum) namespaces offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. Furthermore, it is always recommended that implementers read carefully any guidance in the relevant CAIP-10 profiles in CASA [namespaces][] for additional information per namespace about security and canonicalization conventions. From 731aeb8a820805101d23125183c190d5e2aaa33b Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 16:18:07 +0200 Subject: [PATCH 3/5] wordsmithing --- CAIPs/caip-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CAIPs/caip-10.md b/CAIPs/caip-10.md index a9ee4aa2..b12472aa 100644 --- a/CAIPs/caip-10.md +++ b/CAIPs/caip-10.md @@ -71,7 +71,7 @@ The goals of the general account ID format is: ## Canonicalization -Note that some namespaces like the `eip155` (i.e. ethereum) namespaces offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. +Note that some namespaces like the `eip155` (i.e. ethereum) namespace offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. Furthermore, it is always recommended that implementers read carefully any guidance in the relevant CAIP-10 profiles in CASA [namespaces][] for additional information per namespace about security and canonicalization conventions. From 53e12e1b815b1260cd3ab377e73a1ce702bd85a1 Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 16:18:23 +0200 Subject: [PATCH 4/5] wordsmithing --- CAIPs/caip-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CAIPs/caip-10.md b/CAIPs/caip-10.md index b12472aa..e786e766 100644 --- a/CAIPs/caip-10.md +++ b/CAIPs/caip-10.md @@ -71,7 +71,7 @@ The goals of the general account ID format is: ## Canonicalization -Note that some namespaces like the `eip155` (i.e. ethereum) namespace offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. +Note that some namespaces like the `eip155` (i.e. Ethereum) namespace offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. Furthermore, it is always recommended that implementers read carefully any guidance in the relevant CAIP-10 profiles in CASA [namespaces][] for additional information per namespace about security and canonicalization conventions. From 38f632e023a4afad6557480df373caa0f58859bc Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 16:19:08 +0200 Subject: [PATCH 5/5] wordsmithing --- CAIPs/caip-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CAIPs/caip-10.md b/CAIPs/caip-10.md index e786e766..4f2be6af 100644 --- a/CAIPs/caip-10.md +++ b/CAIPs/caip-10.md @@ -71,7 +71,7 @@ The goals of the general account ID format is: ## Canonicalization -Note that some namespaces like the `eip155` (i.e. Ethereum) namespace offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an option suffix (e.g. [HIP-15][]), or some other transformation. +Note that some namespaces like the `eip155` (i.e. Ethereum) namespace offer canonicalization schemes that use capitalization (e.g. [EIP-55][]), an optional suffix (e.g. [HIP-15][]), or some other transformation. At the present time, this specification does NOT require canonicalization, and implementers are advised to consider deduplication or canonicalization in their consumption of CAIP-addresses. Furthermore, it is always recommended that implementers read carefully any guidance in the relevant CAIP-10 profiles in CASA [namespaces][] for additional information per namespace about security and canonicalization conventions.