Bumblefudge

> Thank you. I would be interested to hear opinions of other CAIP-122 implementers. > > I decided to not display full CAIP-10 identifier when I implemented Monero CAIP-122 authentication...

I'd like "two reviewers - rough consensus" on all uses of the CASA logo; I'd prefer no event at a conference be called a CASA event unless someone who's gotten...

@0xproflupin anything jump out at you as patently wrong? @obstropolos said you might know a thing or two about Solana interop

@vaskos thank you very much for this review-- I wish it had come in earlier! > @bumblefudge If I understand the spec correctly, the `SolanaTransactionVersion` and `SolanaTransactionCommitment` fields are locked...

> @bumblefudge If the idea is to be fully compatible with the Wallet Standard, I think `SolanaTransactionVersion` (or some alternative name) should be a list of available versions, just like...

@vsakos -- eloquently explained, thanks so much. I came to more or less the same conclusion after re-reading the RPC docs and the wallet adapter repo. I tagged you in...

> The whole hash is 32 bytes long, which is 64 HEX characters. How can we fit that into CAIP-2 without truncating? We would have to update the CAIP-2 spec...

Awesome, we're making good time here! So a migration would change the networkId that is returned by `ByGenesisHash`, right? so NetworkId is mutable over time, but querying today's NetworkId for...

Got it. I think what's unique here is that in most blockchain namespaces, chainID is static and immutable, and confirmable by the node; here, networkID (and multiLocation base) are mutable,...

hey @sebastinez - I thought of this issue while tightening up CAIP-104 to be more explicit about what a CAIP-2 is addressing. I would love to discuss both this issue...