Skip to content

Conversation

@delaaxe
Copy link
Contributor

@delaaxe delaaxe commented Nov 18, 2022

Adding support for underscores in the chain id reference allows using StarkNet chain ids as-is (SN_MAIN, SN_GOERLI) without having to do error-prone translations in both dapps and wallets.

Such a change shouldn't impact the existing requirements for the reference.

@oed
Copy link
Collaborator

oed commented Nov 18, 2022

Could you also add a PR to add starknet to the namespaces repo?
https://github.com/ChainAgnostic/namespaces/

@delaaxe
Copy link
Contributor Author

delaaxe commented Nov 19, 2022

Could you also add a PR to add starknet to the namespaces repo? https://github.com/ChainAgnostic/namespaces/

Will do the PR.

Drafting this one for now as there may be better ways of representing StarkNet chain ids that don't require this change.

@delaaxe delaaxe marked this pull request as draft November 19, 2022 08:12
@oed
Copy link
Collaborator

oed commented Nov 19, 2022

@pedrouid any reason not to add support for _?

@oed oed requested a review from pedrouid November 19, 2022 09:33
@delaaxe delaaxe marked this pull request as ready for review November 21, 2022 11:40
@delaaxe
Copy link
Contributor Author

delaaxe commented Nov 21, 2022

@oed @pedrouid here is PR for namespaces: ChainAgnostic/namespaces#39

Copy link
Member

@pedrouid pedrouid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@bumblefudge bumblefudge self-requested a review December 2, 2022 18:18
@bumblefudge
Copy link
Collaborator

bumblefudge commented Dec 2, 2022

@delaaxe this LGTM but maybe we can get the namespace finalized by thursday the 15th so that we don't have an example in a CAIP that isn't backed up by a namespace entry? I'm applying 14-day merge tag so that this breaking change gets triaged in the same bump to the last breaking change to this CAIP.

@bumblefudge bumblefudge added the 14-day merge hoping to merge in 14days or sooner if rough consensus in relevant subgroup label Dec 2, 2022
@bumblefudge bumblefudge merged commit 8091ad4 into ChainAgnostic:master Dec 14, 2022
ntn-x2 added a commit to KILTprotocol/kilt-node that referenced this pull request Feb 22, 2023
Fixes https://github.com/KILTprotocol/ticket/issues/2458.

- CAIP-19 asset reference max length was increased to 128:
ChainAgnostic/CAIPs#179
- CAIP-2 chain reference now supports underscores:
ChainAgnostic/CAIPs#180
- CAIP-19 asset reference and asset identifier now support `.` and `%`
symbols: ChainAgnostic/CAIPs#160

Not a breaking change since it just relaxes some requirements.
webguru9178 pushed a commit to webguru9178/kilt-node that referenced this pull request Jan 8, 2024
Fixes https://github.com/KILTprotocol/ticket/issues/2458.

- CAIP-19 asset reference max length was increased to 128:
ChainAgnostic/CAIPs#179
- CAIP-2 chain reference now supports underscores:
ChainAgnostic/CAIPs#180
- CAIP-19 asset reference and asset identifier now support `.` and `%`
symbols: ChainAgnostic/CAIPs#160

Not a breaking change since it just relaxes some requirements.
hacker-nova7431 added a commit to hacker-nova7431/kilt-node that referenced this pull request Sep 29, 2025
Fixes https://github.com/KILTprotocol/ticket/issues/2458.

- CAIP-19 asset reference max length was increased to 128:
ChainAgnostic/CAIPs#179
- CAIP-2 chain reference now supports underscores:
ChainAgnostic/CAIPs#180
- CAIP-19 asset reference and asset identifier now support `.` and `%`
symbols: ChainAgnostic/CAIPs#160

Not a breaking change since it just relaxes some requirements.
infra-riderju74 added a commit to infra-riderju74/kilt-node that referenced this pull request Oct 27, 2025
Fixes https://github.com/KILTprotocol/ticket/issues/2458.

- CAIP-19 asset reference max length was increased to 128:
ChainAgnostic/CAIPs#179
- CAIP-2 chain reference now supports underscores:
ChainAgnostic/CAIPs#180
- CAIP-19 asset reference and asset identifier now support `.` and `%`
symbols: ChainAgnostic/CAIPs#160

Not a breaking change since it just relaxes some requirements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

14-day merge hoping to merge in 14days or sooner if rough consensus in relevant subgroup

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants