Add more testnets to dropdown

[cmichi]

We are on more testnets now: https://github.com/paritytech/awesome-ink/blob/main/README.md#testnets.

These should be added to the dropdown menu in the top left.

To make it clearer which are production chains and which are testnets I suggest this labeling:

• Shibuya (Production)
• Contracts on Rococo (Testnet)
• Shiden (Testnet)
• Aleph Zero (Testnet)
• …

[Yasir761]

Shibuya (Production) Contracts on Rococo (Testnet) Shiden (Testnet) Aleph Zero (Testnet)

Did you only want to add this list in dropdown ?

[cmichi]

All the ones that are listed in the awesome-ink repository under Testnets.

[Yasir761]

Rococo Shibuya Phala Aleph Zero peaq network t3rn Pendulum These ?

[cmichi]

Yes, a dropdown box like this would be best:

The categories would be Production and Testnets.

Production is only Shibuya, the rest are testnets.

[Yasir761]

okay, but how I do connect all these with endpoints?

[Yasir761]

It look like this

[statictype]

See this PR Also, please add them in alphabetical order, the list is getting bigger

[cmichi]

Please also use the correct capitalization and use groups as I explained in my comment above (with the screenshot). On your screenshots it's completely intransparent to the user that those are test networks and production networks mixed.

[Yasir761]

Are these ok now?

[ashutoshvarma]

Production is only Shibuya, the rest are testnets.

fyi, Shibuya is a testnet -https://docs.astar.network/docs/build/wasm/nodes-clients/#testnet-node-shibuya Shiden is production, it's a parachain on Kusama - https://parachains.info/details/shiden_network

[cmichi]

@Yasir761 Can you implement the comment by @ashutoshvarma and write "t3rn" (so lowercase). It's good besides that, so feel free to create a PR.

[statictype]

@cmichi I reviewed the PR and some things are not clear. Can't connect to phala, t3rn and Pendulum. I think the rpc urls are not correct. The naming seems off as well. Shouldn't we use the name of the actual testnets? For example Foucoco for the Pendulum testnet. Not sure which Phala testnet has the contracts pallet. The PR tried to introduce Khala, which is a Kusama parachain not a testnet.

[cmichi]

Oh yeah, @statictype you're right, I'll comment on the PR.

[peetzweg]

So there are multiple sources to get information about parachains. All of them don't offer an easy way to obtain a RPC endpoint nor even giving you multiple options of RPCs. Furthermore it's not super convenient to find out which parachain has which pallets. I

s there parachain registry or parachain discovery mechanism available in substrate @cmichi, @statictype ?

So far I've found the following sources to find out more about parachains:

• https://parachains.info/
• mentioned awesomelist => https://github.com/paritytech/awesome-ink#testnets
• polkadot.js.org source => https://github.com/polkadot-js/apps/tree/a5d6bea31f2eec023c397b63cf49ba54f22208e7/packages/apps-config/src/endpoints

They all don't really feel great as a source for parachains. Parachains.info the most but does not offer RPCs nor proper filtering by chain capabilities. 🤔