2

We are running public relaychain rpc endpoints and are further deploying polkadot-parachain endpoints, starting with statemine/statemint/westmint.

Everything works but when using our endpoints in polkadot.js they don't show the identities of stashes but only the stash itself while in other endpoint the stashed translate to identities.

So ours only show "HPUEzi4v3YJmhBfSbcGEFFiNKPAGVnGkfDiUzBNTR7j1CxT" while the other endpoints show "LUCKYFRIDAY.IO". See also stakeworld rpc versus parity rpc

It could be that this lookup only works when our node get's included in polkadot.js but I doubt thats the problem.

The nodes are running on dedicated updated ubuntu 22.04 servers, latest polkadot-parachain running via systemctl, open p2p/ws/wss ports, no errors in the logs. Besides the identity problem everything works perfectly.

What i've tried so far:

  • checked that all ports are open
  • direct connection vs load balancer
  • relaychain connection via rpc --relay-chain-rpc-urls= vs running relaychain native via polkadot-parachain binary
  • relaychain archive node vs pruned node
  • downgraded binary (so tried v0.9.420 and v0.9.400)
  • Looked at chrome developer tool/console to see if there are specific errors (no difference)

Anybody an idea where to look?

1

1 Answer 1

1

After inclusion of the endpoints in the polkadot.js code the identity lookups started working so apparently identity for parachains is linked with inclusion in polkadot.js.

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.