Possible overlaps/interop targets at Chain Agnostic Standards Alliance?

[bumblefudge]

Hey there:

Great project, interested to follow along and help where I can. I saw on the mission statement interest in API/interface design, and in particular standard interfaces for L1-namespaced wallet<>dapp RPC methods and for JSON-RPC API. I wanted to mention a few things that might be of interesting to this group:

1. The Wallet Connect v2 network is actually an implementation of a more general JSON-RPC standard that WC (the company) specified in public at CASA as CAIP-25. If anyone in this community is prototyping or researching that kind of thing, feel free to reach out, and/or open a thread on the discussion board for CAIP-25.
2. The mechanism that we advocate for "namespacing" various L1s for interoperability and multichain use-cases is the "namespaces" project, where researchers and community devs from each L1 self-document the applicability of CASA standards like CAIP-25, CAIP-10 and CAIP-2. The spec that defines this process can be found at CAIP-104. Contributions that complete and update the very preliminary documentation for Stacks and for BTC+forks would be very welcome!
3. Re: wallet UX and end-user empowerment, CASA also hosts a secure design WG that might be of interest. The community around EIPs includes an informal "WG" of sorts for wallet interfaces and design issues, which includes representatives from a lot of multi-chain wallets-- the best place for now to compare notes with those devs/designers would be in the AllWalletDevs Discord.
4. More info on our org can be for at alliance.chainagnostic.org.