Bumblefudge

@ligi has anyone ever tried registering a NEGATIVE chainId, or a float/decimal chainId? it's kind of odd how little eip155 actually says about the data type or domain of chainId...

Closing because addressed by ^ the corresponding PR (now merged) on `/namespaces`

I think CAIP-122 was modeled on EIP-4361, where "address" was used-- it would be more consistent with CAIP-10 (and more chain-agnostic) to call it an account_id tho, since that's what...

As of now, just checked some stuff, some kind of PR on CAIP-122 is probably necessary. pinging @ukstv to see if the message format in #236 was implemented by ceramic,...

@oed @haardikk21 @chris13524 you guys have opinions on reconciling these? i'm happy to open a PR and get a review from @jdsika off the top of my head but I've...

> This seems like a conflict to me between making the protocol "efficient" against avoiding deprecating EIP-4361, seems like there's intention to avoid breaking changes in Ethereum. I think if...

valid yes; user-friendly, not so much. Designating official aliases could be done in a PR to `solana/caip2.md` in the namespaces project, if it had demonstrable support from the Solana community....

> > > 5\. Verifiable Credentials are missing the credentialSchema and context fields. > > > > > > Does this imply that we should include the @context field for...

> > 1. There could be some advantages to using DIDs for software components as well. Some DID methods allow the insertion of additional data into the DID Document, which...

> > > I meant only the schemas. Since the standard defines how the attestations look like (structure/JSON schema), it could make sense to have some registry for the schemas,...