RPCs not compliant with the JSON-RPC spec

[josepot]

Dear Composable 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 Composable RPCs that expose the modern JSON-RPC API. Also, I wasn't able to test if your chain works using the light-client provider because it seems the chainspecs don't have any bootnodes.

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 Composable 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

[JafarAz]

Hey @josepot thanks for opening this issue.

Do you know the earliest version of Polkadot SDK that supports the JSON-RPC API?

[josepot]

Do you know the earliest version of Polkadot SDK that supports the JSON-RPC API

The PolkadotSdkCompat middleware that we have built is able to fix/translate the JSON-RPC APIs exposed by PolkadotSDK v1.1.0 or higher.

[josepot]

Why was this issue closed?

[0xThilo]

Why was this issue closed?

sorry sir that was a mistake.. reopened now