We have multiple testnet runtimes configured for the node. A new pallet I'm building is only available for testing in one testnet. There is also a new custom RPC I have written to call into the new pallet. How do I prevent errors caused by some of the runtimes not implementing the RPC interface because they don't have the new pallet included/configured when building the node?

I wonder if cargo features might help here, but not sure how to use it

  • Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking.
    – Community Bot
    Apr 8, 2022 at 16:44

1 Answer 1


you can just define some empty/dummy impl of the rpc interface, e.g beefy pallet is enabled in rococo but not yet in polkadot

or you can define particular rpc collections for each runtime

  • I guess I will go with the dummy impl approach for now. Thanks. But can you elaborate on how rpc collections approach would solve the problem?
    – vim
    Apr 8, 2022 at 10:46
  • just try dummy impl, with rpc collections approach much more effort
    – Ron
    Apr 8, 2022 at 11:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.