Experiment: Bulletin as a system parachain deployment

[bkontur]

Based on elastic scaling. The parachain should deploy pallet-transaction-storage and collator should run with --ipfs-server.

TODO

• What and how to measure?
• Create Bulletin parachain runtime
  • check the collator IPFS support (pokladot-omni-node or polkadot-parachain) [B_as_Para] polkadot-omni-node setup inherent data provider (conditionally) #82
  • pallet-transaction-storage move/merge to polkadot-sdk (at least for polkadot-fellows potential PR, but can be developed here) pallet-transaction-storage merge to Polkadot-SDK's one #86
• Deploy on Westend? (Check and measure here?)
• Potential migration - when we start with the solochain and then later switch to the parachain
  • Do we need to migrate data (which are ephemeral)?
  • Compatibility for dApps (Nova should change endpoints) - unless we have some Bulletin API library (based on PAPI/Paraspell)

Requirements for the launch

• Add transaction_index::HostFunctions with NO-OP impl to the polkadot-prepare/execute-worker polkadot-sdk#10370
• [B_as_Para] polkadot-omni-node setup inherent data provider (conditionally) #82
• configurable StoragePeriod [pallet-transaction-storage] Configurable RetentionPeriod polkadot-sdk#10656
• handle IPFS idle timeout as for bulletin node (TODO: create issue) (should be fixed by IPFS DHT auto-discovery suppport)