search

paritytech / zombienet

A cli tool to easily spawn ephemeral Polkadot/Substrate networks and perform tests against them.
https://paritytech.github.io/zombienet/
GNU General Public License v3.0
159 stars 91 forks source link

Customize `name`, `id`, and `protocolId` in parachain specs #1518

Open JoshOrndorff opened 11 months ago

JoshOrndorff commented 11 months ago

Currently Zombienet does not customize the name, id, or protocolId for the parachains that it launches. That means they all end up with the exact same defaults like "local testnet" and similar.

In parachains based on the node template, zombienet does change the consensus authorities which manages to make the individual specs unique enough to not collide. But it is not guaranteed that all chains will use this configuration. Any chain that uses Nimbus, PoW, or Tuxedo, parachain_staking, etc, for example will not have the aura fields.

So I recommend also customizing the chain specs (both plain and raw) with meaningful names and ids. For example maybe they could be set to "2000-rococo-local-plain", "2001-rococo-local-plain", ..., "2000-rococo-local-raw", ...

pepoviola commented 11 months ago

Hi @JoshOrndorff, wdyt of using this (parachain-name could not be set)

name: <id>-[parachain-name]-<relaychain-name> id: <id>_testent

Thx!

JoshOrndorff commented 11 months ago

That's fine with me. Any reason not to do protocolId as well?

pepoviola commented 11 months ago

That's fine with me. Any reason not to do protocolId as well?

No particular reason, we can also put the para_id, wdyt? Or maybe allow to set from the config, in a new field for the parachain.