Joel Thorstensson
Joel Thorstensson
@rvagg I think that's a good idea and could bring a lot of benefits. I guess the main drawback for CAIP-50 specifically would be that we can't use the one...
@pedrouid thoughts on @rvagg's comment?
> Sounds good to me 👍 Cool, are you planning to do a PR to reserve a range inside of the multicodec table for them?
Registered where exactly? The only place CAIPs use secp256k1 is for CACAO which relies on EIP191.
Would be good if there was a registry of well known prefixes. Could be a simple `*.csv` file in this repo?
@pedrouid I didn't get a chance to comment on your other CAIP for `getSupportedChains` but I think it excludes use cases. For example, the [`did_*`](https://eips.ethereum.org/EIPS/eip-2844) prefix is not associated with...
> Technically CAIPs should be about blockchains hence its name but I would like to include other distributed network protocols given they have their own namespace and reference that could...
All blockchain specific specifications are moving to the namespaces repo: https://github.com/ChainAgnostic/namespaces/pulls Please submit a PR there for this to be added!
This is really interesting! There's also some intersection between this and representing the ethereum blockchain in IPLD. With that you can essentially generate a merkleproof of any state at any...
I think the vulcanize team / https://www.laconic.com/ are about to release a light client doing what you mention using ETH-IPLD.