ChainAgnostic
Expanding and/or finalizing CAIP-10?
Hive and Hedera both use .s and -s in their native addresses-- there may also be corner-cases or testnets or checksums or other places where CAIP-10 is too constrictive. Would be worth discussing:
- needs for and pro's of less constrictive CAIP-10
- costs and breakage to existing CAIP-10 tooling (did:pkh, didkit, walletconnect, etc)
It would be good to discuss this at our next meeting!
See https://github.com/ChainAgnostic/CAIPs/pull/95 and the hedera/caip10.md file
Given the conversation about adding query parameters to CAIP-19 (as a superseding new CAIP) and/or adding a new CAIP for attaching query parameters to CAIP URNs, perhaps a new CAIP should supercede CAIP-10 rather than breaking it? I'm hoping to open PRs for all these new CAIPs before the next meeting (even though I'll miss the next meeting) to start the ball rolling...
Building on the above suggestion. We would like to find a path to modify/expand the CAIP-10 account_address syntax to include the URI RFC's unreserved characters. As such the "new" CAIP-10 account address syntax could read: "account_address: [-.~a-zA-Z0-9]{1,64}"_ or "account_address: [a-zA-Z0-9.~-]{1,64}"_
@bumblefudge Look forward to your continued input on how we can deliver this update. Please me know how I can be of support.
@shemnon
We're holding a session on this next week at our miniconference in Berlin! I'll try to get the ball rolling with a strawman PR later today when I'm back at my desk