feat: add Moonbeam/Moonriver/Moonbase support

[albertov19]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

We are trying to use WC Provider with Moonbeamand, and the chain is not yet supported.

{
    "status": "FAILED",
    "reasons": [
        {
            "field": "chainId",
            "description": "We don't support the chainId you provided: eip155:1284. See the list of supported chains here: https://docs.walletconnect.com/cloud/blockchain-api#supported-chains"
        }
    ]
}

Requested Behavior

Please add support for Moonbeam/Moonriver and Moonbase Alpha:

Moonbeam (Polkadot):

• ChainID: 1284
• HTTP Endpoint: https://rpc.api.moonbeam.network
• WSS Endpoint: wss://wss.api.moonbeam.network

Moonriver (Kusama):

• ChainID: 1285
• HTTP Endpoint: https://rpc.api.moonriver.moonbeam.network
• WSS Endpoint: wss://wss.api.moonriver.moonbeam.network

Moonbase Alpha (TestNet):

• ChainID: 1287
• HTTP Endpoint: https://rpc.api.moonbase.moonbeam.network
• WSS Endpoint: wss://wss.api.moonbase.moonbeam.network

Anything else?

Happy to help with the integration. I saw Base's PR, and I can replicate it with no problem 😄

[chris13524]

Is there documentation on what rate limits these endpoints have?

[albertov19]

Is there documentation on what rate limits these endpoints have?

Hey @chris13524, for regular calls 250/10 seconds, heavy (get logs) 10/10 seconds. Do you have any specific requirements?

[chris13524]

@albertov19 since we simply proxy the requests, all of the users of our RPC will be subject to the rate limits of a single IP. So if we don't get any special rate limits we need to mention in our supported chains list that this chain may not always be available and we should link to the relevant details on rate limits. Since the rate limit available here is quite limited ~25/s we cannot recommend usage of this chain on RPC for production usage and people should instead use the RPC providers you mentioned above directly in their app.

[albertov19]

Hey @chris13524, thanks for getting back to me so promptly. I'll close this ticket for now because there was a workaround that we were able to do with Safe to make it work.

I'll bring this up again if we feel is worth pursuing. Thanks again!