Deploy MVP to Paseo Next V2

TODO

• First
  • Revisit and merge https://github.com/paritytech/web3-storage/pull/26 (contains the MVP)
  • https://github.com/paritytech/web3-storage/issues/51
    • https://github.com/paritytech/web3-storage/pull/410
  • Revisit actual implementation and issues + finalize design vs pallets https://github.com/paritytech/web3-storage/pull/376
• Fine-tune UIs
  • Deploy Web3 UI as github pages https://github.com/paritytech/web3-storage/issues/49
• AssetHub Parachain for Paseo Next V2
  • Find out the actual version of AssetHub Paseo V2
  • Deploy pallet-storage-provider to that runtime (fix all requirements - align PolkadotSDK version, setup crates.io release stuff, release the version 0.X.Y)
• PreviewNet
  • find out which asset hub is used here, maybe we can go with our paseo runtime?
    • system parachain?
  • onboard the new parachain to Paseo (fill the issue for SRE team)
• Get Providers
  • 1 operated by team
    • Request new dedicated machine or reuse https://github.com/paritytech/devops/issues/4964 (this has just 100-200GiB disk)
    • Find you how big disk we want/need?
    • Setup and run provider there
  • Prepare docs/tutorial for external (Claude-aware)
    • Docs needs to be perfect (how to run, how it work, how the incetives)
    • Public forum post asking for providers
  • Prepare some tool (stress-tool), that will create agreements and search for new providers and automatically create buckets/agreement (if any provider is registered on chain, we will automatically create bucket and make a deal with it)
  • Prepare maybe some on-boarding interactive tutorial/game (as Playground) - setup primary, receive data, setup primary, ...
• Build the Storage dApp/SPA with Products framework for managing storage for users (TrUAPI)
  • Request storage, referencing the content, show-casing features and L1 layers, sharing the secret content