Skip to content

Expanding CAIP10, CAIP19 charset to include underscores #385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tristan-bp wants to merge 1 commit into from
Closed

Expanding CAIP10, CAIP19 charset to include underscores #385

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions CAIPs/caip-10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ discussions-to: https://github.com/ChainAgnostic/CAIPs/pull/10
status: Final
type: Standard
created: 2020-03-13
updated: 2022-10-23
updated: 2025-11-06
requires: 2
---

Expand Down Expand Up @@ -45,10 +45,10 @@ The `account_id` is a case-sensitive string in the form
```
account_id: chain_id + ":" + account_address
chain_id: [-a-z0-9]{3,8}:[-_a-zA-Z0-9]{1,32} (See [CAIP-2][])
account_address: [-.%a-zA-Z0-9]{1,128}
account_address: [-_.%a-zA-Z0-9]{1,128}
```

Note that `-`, `%` and `.` characters are allowed, but no other
Note that `-`, `_`, `%` and `.` characters are allowed, but no other
non-alphanumerics such as `:`, `/` or `\`. Implementers are recommended to use
"URL encoding" (% + 2-character codes, canonically capitalized) as per [Section
2][rfc3986sec2.1] of [RFC 3986][rfc3986] to escape any further non-alphanumeric
Expand Down Expand Up @@ -125,6 +125,7 @@ of specification for details.

## Changelog

- 2025-11-06: expanded charset to include `_`
- 2022-10-23: expanded charset to include `-`,`.`, and `%`; also added
canonicalization section and links
- 2022-03-10: update RegEx to incorporate CAIP-2 reference
Expand Down
11 changes: 6 additions & 5 deletions CAIPs/caip-19.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ discussions-to: https://github.com/ChainAgnostic/CAIPs/pull/19
status: Review
type: Standard
created: 2020-06-23
updated: 2020-06-23
updated: 2025-11-06
requires: 2
---

Expand Down Expand Up @@ -46,10 +46,10 @@ The `asset_type` is a case-sensitive string in the form
asset_type: chain_id + "/" + asset_namespace + ":" + asset_reference
chain_id: Namespace+Blockchain ID as per [CAIP-2][]
asset_namespace: [-a-z0-9]{3,8}
asset_reference: [-.%a-zA-Z0-9]{1,128}
asset_reference: [-_.%a-zA-Z0-9]{1,128}
```

Note that `-`, `%` and `.` characters are allowed in `asset_references`, which
Note that `-`, `_`, `%` and `.` characters are allowed in `asset_references`, which
include on-chain addresses like those specified in [CAIP-10][], but no other
non-alphanumerics such as `:`, `/` or `\`. Implementers are recommended to use
"URL encoding" (% + 2-character codes, canonically capitalized) as per [Section
Expand All @@ -73,11 +73,11 @@ The `asset_id` is a case-sensitive string in the form

```
asset_id: asset_type + "/" + token_id
token_id: [-.%a-zA-Z0-9]{1,78}
token_id: [-_.%a-zA-Z0-9]{1,78}

```

Note that `-`, `%` and `.` characters are allowed, but no other
Note that `-`, `_`, `%` and `.` characters are allowed, but no other
non-alphanumerics such as `:`, `/` or `\`. Implementers are recommended to use
"URL encoding" (% + 2-character codes, canonically capitalized) as per [Section
2][rfc3986sec2.1] of [RFC 3986][rfc3986] to escape any further non-alphanumeric
Expand Down Expand Up @@ -173,6 +173,7 @@ hedera:mainnet/nft:0.0.55492/12

## Changelog

- 2025-11-06: expanded charset to include `_`
- 2022-10-23:
- expanded charset to include `-`,`.`, and `%`
- added canonicalization section and links
Expand Down