Add Alephium

[h0ngcha0]

[nop33]

Hey @bumblefudge, a long time ago you commented that we could reach out to you once we are ready! This is a PR to integrate Alephium. Let us know if you have some time to check it out! Thanks a ton!

[h0ngcha0]

This is looking great so far, but the CAIP-10 and CAIP-19 profiles aren't quite conformant, and I am a little too pressed for time to do enough research to recommend more concretely what next steps would make for the best possible CAIP-2 segment to add to them!

Thanks a lot for your time!

Do you think the following would work?

1. For chain id, we use alephium:${network_id}/${group}, because Alephium is a sharded blockchain that contains a number of smaller chains internally, so we want to be able to specify the specific "chain" inside of it through group.

2. For address, we specify alephium:${network_id}:${address}. Because address already have the group information implicitly we don't need to specify it.

What do you think? Any advice would be appreciated, thanks!

[bumblefudge]

2. For address, we specify alephium:${network_id}:${address}. Because address already have the group information implicitly we don't need to specify it.

Actually, I would argue it's still worth encoding group in the CAIP-2 portion of a CAIP-10 because the group information requires quite a bit of sniffing, decoding and transformation to extract, whereas the counterparty handed a CAIP-10 may not have the compute to spare and would probably only do that much compute to verify what they most often can just trust from the counterparty...

Lots of multichain stuff is kind of verbose or redundant in this way, to spare all parties in the system to keep all the tooling from every ecosystem on hand :D

[h0ngcha0]

2. For address, we specify alephium:${network_id}:${address}. Because address already have the group information implicitly we don't need to specify it.

Actually, I would argue it's still worth encoding group in the CAIP-2 portion of a CAIP-10 because the group information requires quite a bit of sniffing, decoding and transformation to extract, whereas the counterparty handed a CAIP-10 may not have the compute to spare and would probably only do that much compute to verify what they most often can just trust from the counterparty...

Lots of multichain stuff is kind of verbose or redundant in this way, to spare all parties in the system to keep all the tooling from every ecosystem on hand :D

Thanks, I have made the update in this commit

[h0ngcha0]

LGTM, waiting on 2nd editor approval or 2 independent approvals

Thanks a lot @bumblefudge for your time and suggestions!

Hey @obstropolos , would really appreciate it if you can take a look at this PR when you have time, thanks very much :pray:

[h0ngcha0]

Small errata - will approve once corrections are made.

Thanks for putting this together!

Both suggestions applied, thanks for your time!