namespaces icon indicating copy to clipboard operation
namespaces copied to clipboard

Chain-Agnostic Namespaces host informative specs and profiles of CAIPs (Chain-Agnostic Improvement Proposals) per blockchain ecosystem

Results 27 namespaces issues
Sort by recently updated
recently updated
newest added

Aligned with the ripple-keypairs implementations for signing and verification.

gotta have some basic precedents so that other namespaces can define THEIR caip-25 profiles in turn!

I realized that "polkadot:-:{address}" scheme would break CAIP-2 because `-` is no more a valid `chainID` than ` ` or null would be; then I re-read [Tim's comment](https://github.com/ChainAgnostic/namespaces/pull/6#issuecomment-1064299030) and realized...

Only in draft because I'm waiting on real-world examples for the ## Examples section from a prototyping team. Big thanks to the many contributors so far. Can't assign for review...

Looks like some work already started in https://github.com/ChainAgnostic/CAIPs/pull/43

I am not sure this is the right repo, or if I should open an issue on the `CAIP` repo. I know there's an [open ticket](https://github.com/ChainAgnostic/namespaces/issues/56) for updating the CAIP-2...

Both as a template for other caip25 profiles and as a test-case for L1-vs-L2 RPC dictionaries 😬

not intuitive, but will save us a hassle if this has to move off GH some day. also SEO/pagerank

1.) DIDs and VCs are examples of very blockchain-like capabilities that a blockchain wallet might want to support, without requiring any communications with nodes. Currently, CAIP-169 tries to update some...

Thanks to @ntn-x2 for point out [the new GenesisHash function](https://github.com/paritytech/polkadot/blob/master/xcm/src/v3/junction.rs#L42) in xcm v3 , and patiently explaining to me the problems with existing CAIP-2 spec! I merged the existing draft...

help wanted