Add Bulletin chainspecs for Polkadot, Westend, and Paseo

[mudigal]

Summary

• Add chainspecs/ directory with Bulletin chain specifications copied from paritytech/chainspecs
• Includes Polkadot, Westend, and Paseo networks
• Each network has chainspec.json and raw.json (Polkadot also includes genesis-head)

Structure

chainspecs/
├── paseo/
│   ├── chainspec.json
├── polkadot/
│   ├── chainspec.json
└── westend/
    ├── chainspec.json

Enables

• Merging of Add polkadot-bulletin-chain as submodule chainspecs#1263

Closes

• Partially addresses [Cleanup] Have all bulletin code base in a single repository as much as possible #499

[bkontur]

We don't need raw.json or genesis head, they can be generated.

[bkontur]

Also thinking about flat structure should be enough - like polkadot-sdk: https://github.com/paritytech/chainspecs/blob/main/polkadot/parachain/asset-hub/chainspec.json

./chainspecs/bulletin-polkadot.json
./chainspecs/bulletin-westend.json
./chainspecs/bulletin-paseo-next.json
./chainspecs/bulletin-paseo-next-next.json

btw. which paseo version is:

chainspecs/
├── paseo/
│   ├── chainspec.json

@karolk91 wdyt?

[mudigal]

https://github.com/paritytech/chainspecs/blob/main/polkadot/parachain/asset-hub/chainspec.json

Actually even Asset Hub has genesis and genesis-values. https://github.com/paritytech/polkadot-sdk/tree/master/cumulus/parachains/chain-specs

[karolk91]

do we need the chainspec copies here? I think the source of truth is https://github.com/paritytech/chainspecs

[bkontur]

do we need the chainspec copies here? I think the source of truth is https://github.com/paritytech/chainspecs

I thought the same first, but looks like this this repo just doing submodules and symlinks

[karolk91]

do we need the chainspec copies here? I think the source of truth is https://github.com/paritytech/chainspecs

I thought the same first, but looks like this this repo just doing submodules and symlinks

Oh, ok, thanks I haven't noticed that

Also thinking about flat structure should be enough - like polkadot-sdk: https://github.com/paritytech/chainspecs/blob/main/polkadot/parachain/asset-hub/chainspec.json

./chainspecs/bulletin-polkadot.json ./chainspecs/bulletin-westend.json ./chainspecs/bulletin-paseo-next.json ./chainspecs/bulletin-paseo-next-next.json

btw. which paseo version is:

chainspecs/
├── paseo/
│   ├── chainspec.json

@karolk91 wdyt?

1. Regarding structure - I don't have any preference here, so I think following polkadot-sdk pattern makes sense for consistency
2. As for Paseo - there are 2 chainspecs currently:
   https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin-next
   https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin
   so I guess we can focus on the bulletin-next since bulletin will get decommissioned. Current chainspecs/paseo/chainspec.json file in this PR has paraid 5118 so we need to change that to the bulletin-next variant

[bkontur]

2. As for Paseo - there are 2 chainspecs currently:
https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin-next
https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin
so I guess we can focus on the bulletin-next since bulletin will get decommissioned. Current chainspecs/paseo/chainspec.json file in this PR has paraid 5118 so we need to change that to the bulletin-next variant

Let' clean this Paseo first and also reflect that here: paritytech/chainspecs#1263
Either 1.:
chainspecs/paseo/next-chainspec.json
chainspecs/paseo/next-v2-chainspec.json
chainspecs/polkadot/chainspec.json
chainspecs/westend/chainspec.json
Or 2.:
chainspecs/paseo-next-chainspec.json
chainspecs/paseo-next-v2-chainspec.json
chainspecs/polkadot-chainspec.json
chainspecs/westend-chainspec.json

I am voting for 2., no need for subdirs just for four json files

[bkontur]

Per #523 (comment)

[mudigal]

2. As for Paseo - there are 2 chainspecs currently:
   https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin-next
   https://github.com/paritytech/chainspecs/tree/main/paseo/parachain/bulletin
   so I guess we can focus on the bulletin-next since bulletin will get decommissioned. Current chainspecs/paseo/chainspec.json file in this PR has paraid 5118 so we need to change that to the bulletin-next variant

Let' clean this Paseo first and also reflect that here: paritytech/chainspecs#1263 Either 1.: chainspecs/paseo/next-chainspec.json chainspecs/paseo/next-v2-chainspec.json chainspecs/polkadot/chainspec.json chainspecs/westend/chainspec.json Or 2.: chainspecs/paseo-next-chainspec.json chainspecs/paseo-next-v2-chainspec.json chainspecs/polkadot-chainspec.json chainspecs/westend-chainspec.json

I am voting for 2., no need for subdirs just for four json files

Options sounds good. Will update according to that.

[bkontur]

@karolk91 @x3c41a I am just thinking about some simple CI tests, that will:

• download polkadot-omni-node (version by env)
• matrix try to connect to all polkadot-omni-node --chain <chain-specs>
• wait it starts syncing/downloading few blocks

wdyt? Follow-up?

[x3c41a]

@karolk91 @x3c41a I am just thinking about some simple CI tests, that will:

• download polkadot-omni-node (version by env)
• matrix try to connect to all polkadot-omni-node --chain <chain-specs>
• wait it starts syncing/downloading few blocks

wdyt? Follow-up?

looks like a good smoke test! worth adding.
I'll do it as a follow up PR