Skip to content

Conversation

@tristan-bp
Copy link

I would like to expand the charset for account addresses in CAIP 10 and asset references / token ids in CAIP 19 to include underscores (_).

Underscores are used in blockchain addresses (example: telegram's ton) and typically don't require URL encoding for security purposes.

@bumblefudge
Copy link
Collaborator

Hey there:

So, CAIP-10 is "final" because implemented and load-bearing in prod for the entire wallet connect network, minor changes to it would be quite harmful to interop. Generally, when someone wants to make significant/normative changes to a final spec, we recommend just "forking" the CAIP, i.e., creating a new CAIP that "supercedes" the final one and presenting it as an alternative (and upgrade path) to implementers considering or already using the final one.

I would also mention here that CAIP-350/EIP-7930 propose a few minor changes to CAIP-2 and CAIP-10, so it might make sense to bundle together your character-set change with theirs and propose a "drop-in, backwards-compatible" replacement to CAIP-10 as a new CAIP. The hard part isn't defining the specification, it's finding the implementers willing to take it to prod... so working with the CAIP-350/EIP-7930 crowd and/or the TON crowd offline would be highly recommended!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants