Namada namespace request or use cosmos?

[maxpower-01]

I’m trying to figure out how Namada should be represented here.

Namada is CometBFT/IBC-based, but it’s not Cosmos-SDK, and it also has different account/address behavior (transparent vs shielded).

• Should Namada get its own namespace (namada), or should it be covered under the existing cosmos namespace?
• If namada is OK, what should the CAIP-2 “reference” be (can we use the current chain id string namada.5f5de2dd1b88cba30586420)?
• For CAIP-10, should we document both transparent and shielded account identifiers, and how should they be expressed?

[bumblefudge]

Hey there:

I know dangerously little about Cosmos OR Namada, but I can answer on behalf of the namespaces/CAIP-109 system in general and hopefully that's enough to guide you to opening a PR, whether it's to add a namada namespace or extend the cosmos one.

Basically, the boundaries between namespaces are like the language/dialect distinction. If the Cosmos VM and interop system works with everything except the addressing system, it's probably fair to think of the shielded addresses as an extension that other Cosmos-based networks could eventually upgrade to, right? So that would be an argument for adding a "shielded addresses" section to Cosmos/caip10.md (which mentions limited support and links to the authoritative specs). But if there are other, more structural differences to the runtime or VM or security assumptions, it might actually be a distinct namespace of networks.

Is that enough to go on? If not, please provide some links so I can go further into the stuff; otherwise I'll just wait until the PR is opened to read up on it 😅

[bumblefudge]

(can we use the current chain id string namada.5f5de2dd1b88cba30586420)?

It seems periods are not allowed in Cosmos SDK and they recommend this format, so the existing CAIP-10 profile for Cosmos might need to be updated. Are chainIds shielded (in some way other than the hashed- prefixes are)? I'm starting to wonder how difficult interop with Cosmos SDK chains (and tooling/CEXs) would be...

https://docs.cosmos.network/evm/next/documentation/concepts/chain-id#1-cosmos-chain-id-string