Register Alephium chain in WalletConnect Cloud

[nop33]

TL;DR

For our mobile wallet to appear in the list of wallets in the WalletConnect QR code modal of each dApp we need to register the Alephium chain to WalletConnect.

If you don't see your chain listed in this list, then you will need to create an issue in GitHub to to get the process started. You can do so by clicking here. Once your chain is added to this list, wallets & dapps will be able to indicate support for your chain via WalletConnect's Cloud. https://docs.walletconnect.com/advanced/multichain/overview https://docs.walletconnect.com/cloud/chains/overview

This is a blocker for this issue: #55

Details

To solve point (1) for iOS of this issue (https://github.com/alephium/alephium-frontend/issues/55), I've been working on registering our mobile wallet app to the WalletConnect Explorer, but I am stuck at this step. "Alephium" is not listed in the supported chains:

Click here to see screenshots


Examples of other chains

https://github.com/WalletConnect/walletconnect-monorepo/issues?q=is%3Aissue+is%3Aopen+label%3A%22type%3A+new+chain+request%22

TODO

• [ ] Create issue on WalletConnect monorepo with following info

  • [x] JSON-RPC spec for Wallets (only if one doesn't already exist). For more information, please review the Ethereum JSON-RPC API docs. GitHub Link:

    • https://github.com/alephium/alephium/blob/master/api/src/main/resources/openapi.json
    • https://github.com/alephium/explorer-backend/blob/master/app/src/main/resources/explorer-backend-openapi.json

  • [x] Write a CASA namespace spec if not already available for this namespace. GitHub Link:

    • https://github.com/ChainAgnostic/namespaces/tree/main/alephium

  • [x] namespaces: known chain namespaces (e.g. eip:155 for Ethereum/EVM-based chains, solana, ...)

    • alephium

  • [x] chains: *known chains, where the primary key is a compound key composed of namespace + reference (e.g. ETH mainnet is eip155:1). Please provide labels for each chain (e.g. mainnet, testnet, devnet, ...)

    Alephium's chain id follows this format alephium + ":" + group + "_" + network_id where group can be 1, 2, 3 or 4 which represent individual group, or -1 which represent all groups. The value of network_id could be mainnet, testnet or devnet. Here are a few examples of chain ids:

    # Alephium mainnet, group 0
    alephium:0_mainnet
    
    # Alephium testnet, any group
    alephium:-1_testnet

  • [x] RPC endpoints *list of common/canonical RPC endpoints for the chain(s)

    • https://docs.alephium.org/infrastructure/public-services

  • [x] SLIP-0044 coin type: * slip44 coin type used in the namespace

    • 1234

References To ensure timely processing of your request, please provide the following references:

• [ ] Source of RPC endpoints (e.g. RPC docs): [link]
• [ ] Source of namespace (if non-EIP155) chain information (particularly chainIds): [link]

[bumblefudge]

Grüezi! As for the namespace docs, start here and let me know if i can help! If you know Ergo well enough to help close my pending questions on their PR, that would also be appreciated and perhaps even a stitch in time cuz you'll already know what corner-cases and nits I look for when editing these things😅

[nop33]

Now that we have registered Alephium to the CASA Namespace let us try and create an issue on WalletConnect to get listed in their Explorer so that our mobile app is shown in the QR code and iOS UX is improved.

This is the WalletConnect page listing all supported chains: https://docs.walletconnect.com/cloud/chains/chain-list

[nop33]

Issue submitted: https://github.com/WalletConnect/walletconnect-monorepo/issues/5283

Thank you @h0ngcha0 🙏 🤜 🤛