You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, PAPI offers numerous advantages. You can read more about it here.
We've received feedback from many users who are unable to use PAPI with Parallel. The primary reason is that your nodes are deployed using a very old version of the Polkadot-SDK node. Typically, in such cases, we suggest that our users utilize the light-client (smoldot). However, Parallel doesn't work with smoldot due to an issue with your full nodes.
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 Parallel are using an even older version, which the middleware does not support.
We kindly request that you consider upgrading your Polkadot-SDK node to a more recent version. This upgrade would enable DApp developers to interact with your chain using PAPI, unlocking benefits such as improved performance, lighter 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
The text was updated successfully, but these errors were encountered:
Dear Parallel 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, PAPI offers numerous advantages. You can read more about it here.
We've received feedback from many users who are unable to use PAPI with Parallel. The primary reason is that your nodes are deployed using a very old version of the Polkadot-SDK node. Typically, in such cases, we suggest that our users utilize the light-client (smoldot). However, Parallel doesn't work with smoldot due to an issue with your full nodes.
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 Parallel are using an even older version, which the middleware does not support.
We kindly request that you consider upgrading your Polkadot-SDK node to a more recent version. This upgrade would enable DApp developers to interact with your chain using PAPI, unlocking benefits such as improved performance, lighter 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
The text was updated successfully, but these errors were encountered: