Review bulletin westend's xcm config

[franciscoaguirre]

Addresses part of #168

• No DOT teleports, DOT reserve transfers
• Remove superuser from the relay
• Removed unnecessary barrier
• Changed Bulletin's para id to that of a non-system parachain

TODO

• test that reserve transfers of DOT between Asset Hub and Bulletin work
• fresh weights for bulletin-westend
• change 1006 paraId where possible to 2487

[bkontur]

@franciscoaguirre thank you :)

cc: @rosarp @x3c41a Let's wait with merge for fresh weights for bulletin-westend.

And later (for bulletin-polkadot) we should add integration test for reserve-transfer: #195

[franciscoaguirre]

@bkontur We have a convention that any parachain with id < 2000 is a system parachain. Even though Bulletin doesn't accept teleports it is still a system parachain because of its id (1006) but also because it's tightly integrated in the system.

[bkontur]

@bkontur We have a convention that any parachain with id < 2000 is a system parachain. Even though Bulletin doesn't accept teleports it is still a system parachain because of its id (1006) but also because it's tightly integrated in the system.

@franciscoaguirre yes, good point, you're right. For Westend we have 2,487.

• @rosarp please, change 1006 paraId where possible to 2487 (you can do it on the top of this branch or master as seprate PR)

[franciscoaguirre]

Specifying westend-runtime as a direct dependency is necessary even if we're not importing anything from it since we need it for correctly propagating the runtime-benchmarks and try-runtime features

[bkontur]

Specifying westend-runtime as a direct dependency is necessary even if we're not importing anything from it since we need it for correctly propagating the runtime-benchmarks and try-runtime features

Locally, it worked for me without westend-runtime, see this is not the problem:
https://github.com/paritytech/polkadot-bulletin-chain/actions/runs/21339451305/job/61416738419?pr=195#step:9:1121

I suspect this: https://github.com/paritytech/polkadot-bulletin-chain/pull/195/files#diff-55f05888fd854d9962bdd4d8ccf23a07b610990f58174397b2586b58f8937428R116
SKIP_WASM_BUILD: 1

[bkontur]

Specifying westend-runtime as a direct dependency is necessary even if we're not importing anything from it since we need it for correctly propagating the runtime-benchmarks and try-runtime features

aha, you're right, I see, cargo check is failing without it: https://github.com/paritytech/polkadot-bulletin-chain/actions/runs/21339928957/job/61417862733?pr=195#step:5:1156

[bkontur]

Specifying westend-runtime as a direct dependency is necessary even if we're not importing anything from it since we need it for correctly propagating the runtime-benchmarks and try-runtime features

aha, you're right, I see, cargo check is failing without it: https://github.com/paritytech/polkadot-bulletin-chain/actions/runs/21339928957/job/61417862733?pr=195#step:5:1156

@franciscoaguirre nice, thank you, everything works now, and also thank you for that integration test 🚀

[franciscoaguirre]

@bkontur We're only missing running the weights on a specific VM now

[bkontur]

@bkontur We're only missing running the weights on a specific VM now

Yes, I wanted to have code-complete ready - @rosarp is running those as separate PR