RPCs not compliant with the JSON-RPC spec

[josepot]

Dear Continuum Team,

I hope this message finds you well. My name is Josep, and I'm the technical lead of the Polkadot-API (PAPI) team.

In case you're not familiar with Polkadot-API, it's a modern library designed to replace PolkadotJS, built on top of a properly specified and standardized JSON-RPC API for Polkadot-based networks. The modern JSON-RPC APIs offer many advantages over the legacy ones; you can read more about it here and here.

We've noticed that there are no available public Continuum RPCs that expose the modern JSON-RPC API. At least, the only one that we are aware of (wss://continuum-rpc-1.metaverse.network/wss) doesn't expose it. Also, I wasn't able to test if your chain works using the light-client provider because it seems that your chainspecs are outdated 😞.

Our team has developed a middleware solution to ensure that Polkadot-API can function seamlessly with chains running older versions of the Polkadot-SDK node. Unfortunately, it appears that the RPC providers for Continuum are using an even older version, which the middleware does not support.

We kindly request that you consider working with your RPC providers to upgrade the PolkadotSDK node to a more modern version that supports the new JSON-RPC API. This upgrade would enable DApp developers to easily interact with your chain using PAPI, unlocking benefits such as improved performance, reduced resource usage, out-of-the-box strong type generation for your chain, and the ability for developers to handle runtime upgrades on the fly.

Thank you for your time and consideration.

Best regards,

Josep

[justinphamnz]

Hi Josep,

Thank you for reaching out.

Yes, the reason we haven't pushed the latest RPC yet is that a recent dApp in our ecosystem depends on the current RPC endpoints, which have been seamlessly integrated into their application. We need to evaluate some recent changes in the latest API to avoid any interruptions.

Our engineering team has already pushed some changes to the latest Polkadot-SDK, which are in the branch but haven't been deployed yet due to the above concerns.

We will keep you updated on the release when it is ready.

Regards,
Justin

[josepot]

Yes, the reason we haven't pushed the latest RPC yet is that a recent dApp in our ecosystem depends on the current RPC endpoints, which have been seamlessly integrated into their application. We need to evaluate some recent changes in the latest API to avoid any interruptions.

This makes no sense. The new PolkadotSDK node versions still expose all the old RPCs.

[justinphamnz]

Yes, the reason we haven't pushed the latest RPC yet is that a recent dApp in our ecosystem depends on the current RPC endpoints, which have been seamlessly integrated into their application. We need to evaluate some recent changes in the latest API to avoid any interruptions.

This makes no sense. The new PolkadotSDK node versions still expose all the old RPCs.

Hi Joseph,
Last time we tested, it broke the dApp integration. I will push it through to the team to evaluate.