The Polkadot Cloud

Let’s break down a concrete example to understand: the current Polkadot governance applications.

Following the terminology used here, these apps consist of two tiers:

  1. A Web3 tier that manages the logic of tracks, preimages, voting mechanisms, and onchain actions like transferring funds from the treasury.
  2. A Web2 centralized database and web API that holds the semantic content—essentially, the information about what each proposal entails, including its meaning and the discussions surrounding it.

Switching to IPFS to host this content only slightly changes things. While it eliminates reliance on the web API of a single provider (currently Polkassembly), you’d still need a way to reconstruct the entire structured discussion and content. Related regarding IPFS Seeking Feedback on Minimizing Trust in Decentralized App Distribution

Moreover, if we include elements like identity attestations, historical interactions, and similar factors, the app’s usability will depend on extensive external context.

So, how do Polkadot Cloud and JAM alter this landscape?