I think it’s time to open a thread dedicated to the ideas which have been spreading like wildfire (very much by intention) around the Polkadot Hub and Polkadot Cloud.
First, before we even get started, it is important to note that this is just a discussion of ideas. Nothing here is locked in yet, official, or anything like that. The point of these conversations is to get community alignment of ideas, terminology, vision, and direction.
The phrase I have been using is that Polkadot is like a bunch of cats in a room, totally doing their own thing. We need a laser pointer for us all to focus on a long-term vision, and to move together towards that goal.
Such a vision should allow us to:
- make better decisions as a community
- better represent Polkadot outside of our community
- ensure that we are building things that are relevant for our needs
What is also important is that our vision is not made up. It must be something we can actually achieve, and that we have ideas to support.
The present letter is a very long one, simply because I had no leisure to make it shorter. - Blaise Pascal
I am sorry for the length of this post. It is in many ways a full brain dump of every conversation I have had around the Polkadot Cloud and Polkadot Hub to this date.
I think best to digest all the top level content, and then dig deeper where you have the appetite. I have hidden those deeper details behind a Read more details...
button that you need to click to see the full text.
What is Polkadot?
Polkadot is not a blockchain. Polkadot of course, has a blockchain, and a token, but the meaning of Polkadot extends far beyond that.
Polkadot is a vision toward a world with less trust and more truth.
This is the friendly way to tell people that we are trying to build and innovate with Web3 principles.
I think if you look at all that Polkadot has done in the past, is doing now, and will do into the future, this single vision will permeate every decision and action we take.
This vision will likely never change, nor should it. I think Polkadot is defined by the journey we take toward this vision.
Polkadot has a mission, which describes the direction we go in achieving that vision. Our mission can change, but practically, changes in our mission should only occur over long periods of time. Only when what is needed to reach our vision changes, or we have achieved our current mission.
We can describe Polkadot’s mission up until now and into the near future:
Polkadot’s mission is to provide a scalable, secure, and resilient platform for Web3 applications and services.
An image to put in your mind is:
That is to say, Amazon Web Services has fundamentally changed the internet today by making it cheap, easy, and scalable to launch Web2 applications and services into the cloud.
Polkadot’s current mission is to do the same thing, but for Web3 services. We believe this is the way that the Polkadot ecosystem can currently bring this vision of a world with less trust and more truth to the world, and while we acknowledge achieving this vision requires more than just technology, we think it is the first primitive the world needs to get started.
So what does it mean to have a vision towards less trust and more truth?
To answer this, we must ask “What is Web3?”.
What is Web3?
Web3 is a fundamental shift of removing trust from Web2, the technology stack that we currently use to power the internet.
In my recent presentation, I represented this as a difference in resilience.
But in fact, there are other principles of Web3 we should not forget:
As quoted by Gav:
Driving Factors and Web3 Maxims
- Resilience
- Generality
- Performance
- Coherency
- Accessibility
I would also like to include the 5 pillars of open blockchains from Andreas Antonopoulos, which was certainly the predecessor to Web3 ideologies:
- Open
- Public
- Borderless
- Neutral
- Censorship Resistant
This post is probably not best suited to be the introduction into the principles and philosophies of Web3.
If there are nice posts which consolidate and teach the ideas of Web3 which can be linked here, please feel free to post them in this thread. Otherwise, perhaps look at the old youtube videos of Gav or other Web3 leaders about their vision of the space.
Polkadot’s Products
So we have established our vision, and have a clear mission to bring technologies into the world which can power Web3 applications and services.
How does this actually manifest into products?
Well my perspective is that Polkadot has always been building toward two products, which attempt to satisfy this mission:
- The Polkadot Cloud
- The Polkadot Hub
NOTE: It is important at this point to not get too attached to these specific names. Many resonate with the Polkadot Cloud, but some have opinions about the “Polkadot Hub”, and this is the time to discuss those opinions and come to a consensus. I personally prefer these two names, and would be happy to have those discussions with anyone here in this thread.
Unfortunately the history of developing the Polkadot, we had not clearly defined these two products. But it does not change the fact that if we think about what we have been building so far and the vision we are going toward, we have ALWAYS been building these two products.
So, what is the Polkadot Cloud and the Polkadot Hub?
The Polkadot Cloud
The Polkadot Cloud is a secure, scalable, and resilient platform for Web3 applications and services.
The Polkadot Cloud is our current mission.
If you were to make a sales pitch for the Polkadot Cloud, it might look something like this:
The Polkadot Cloud is a platform for Web3 applications and services.
On the Polkadot Cloud, we provide services with high throughput, native interoperability, and shared security. Our cloud platform is elastic, dynamic and multi-core.
With over 100 execution cores we are able to achieve 150,000 transactions per second across the Cloud, and over 150 MB/s data availability throughput!
The Polkadot Cloud offers a number of different Web3 Services such as:
- Cloud Execution Service
- Settlement / Finality Service
- Data Availability Service
- Object Storage Service
- Blockchain Hosting Service
- and more!
All of these services work together seamlessly to create an all-in-one platform for deploying your app. We provide everything you need, so you can focus on what you are building.
Using the Polkadot Cloud, you are able to deploy any kind of Web3 application or service cheap, easy, and at scale.
Note here that the Polkadot Cloud represents all that we have accomplished so far, and even looks into what we want to do in the future.
It also breaks down the various features of Polkadot into separate services that are offered and bundled by the Cloud. And this better represents what you can actually do, rather than what we have currently built.
There are teams already experimenting with using our individual services like data availability or cloud execution to secure rollups on other ecosystems. We could be part of every “modular blockchain” story. It’s just that we have been focused on building an all-in-one solution.
Read more details about the Polkadot Cloud
History of the Polkadot Cloud
With this framing of the Polkadot Cloud, I think we are able to actually look back at history, and define a clear story of what we have been building so far.
Not to make up history, but to re-frame what we’ve done.
- Polkadot Cloud - Genesis: May 2020
- Polkadot Cloud - Milestone I (Parachains): November 2021
- First Cloud Services Deploy: December 2021
- Polkadot Cloud - Milestone II (Elastic): October 2024
- Polkadot Cloud - Milestone III (JAM): TBD
So really, the initial Polkadot launch was really around creating an all-in-one blockchain hosting service for other blockchains on the Polkadot Cloud.
Initially that blockchain hosting service was very simple in how it created, allocated, and used blockspace.
Our work since the launch of Polkadot have been to make our hosting service more agile, elastic, and flexible. This is what we previously called “Polkadot 2.0”, but it really isn’t a new product at all! It is an iteration of the Polkadot Cloud vision.
Just like JAM is also not a brand new idea, even though the architecture of the Polkadot Cloud will change significantly from it. It is yet another iteration on the mission to create the best platform for Web3 applications and services.
With the third milestone of the Polkadot Cloud (codename JAM), we are looking to extend functionality of our Web3 Cloud platform to support even applications and services which are NOT blockchains.
I think this kind of positioning helps explain to the world what the heck is going on with things like JAM, which we have really struggled to explain in respect to the existing Polkadot Cloud.
And certainly there will be milestone 4, 5, 6, etc… The development and improvement of the Polkadot Cloud will always continue. It is wrong to look at the development of Polkadot as “building new products”. The product is the same, it is just iteratively (or sometimes radically) getting better.
The question you need to ask when digging into technical development, is:
“How does this improve the Polkadot Cloud?”.
This is what we need to be communicating.
Comparisons to Web2 Clouds
I think that this vision of the Polkadot Cloud allows us to evaluate what we have been building, and where we should be building toward. Thankfully, we have large businesses like Amazon, Google, and Microsoft who have all built Web2 clouds, of which I argue we are not that different from an architectural standpoint.
For example, look at the service offerings for Amazon:
- Amazon EC2
- EC2 = Elastic Compute Cloud
- “Amazon EC2 is AWS’s service that provides secure, scalable computing capacity in the cloud.”
- “Reliable and scalable infrastructure on-demand, with 99.99% availability SLA”
- “purchase model to help you best match the needs of your workload”
- Amazon S3
- S3 = Simple Storage Service
- “Amazon S3 is an object storage service offering industry-leading scalability, data availability, security, and performance.”
- Benefits:
- Scalability
- Durability and availability
- Security and data protection
- Lowest price and highest performance
- AWS Lambda
- “Run code without thinking about servers or clusters”
- “AWS Lambda is a serverless computing service that runs your code in response to events without requiring provisioning or management of servers. It automatically scales compute resources and you pay only for the compute time used. The main benefits are no server management, automatic scaling, pay-per-use billing, and performance optimization options.”
Doesn’t this draw a lot of parallels to:
- Our execution service
- Our data availability service
- The proposed “CorePlay” service
Take a look at the Google Cloud landing page. Couldn’t you see this structure and style being an effective way to explain and sell the Polkadot Cloud?
Imagine all that we can learn about creating a better Web3 cloud for the world by really framing ourselves as a product architected similar to the traditional cloud services we want to replace.
A “10 Year” Vision of the Polkadot Cloud
What is important about this broad narrative for the Polkadot Cloud, is that it allows us to not be limited by what we are doing today, and think about what we could be building tomorrow.
Many teams around the Polkadot ecosystem are looking for the right ideas to support, and decentralized organizations like the Polkadot DAO have a hard time understanding if we really need some of those things.
With the Polkadot Cloud mentality, we can easily ask the question: “How are you looking to improve the experience for applications and services using the Polkadot Cloud?”
We can also get ourselves out of the gutter of thinking we are just a blockchain product. The Web3 Cloud will have many services that are NOT blockchain based! (or at least not directly related to Parachains)
For example:
- Mix Nets (a la Nym)
- Privacy Layers (a la ZCash)
- Oracle Services (a la Chainlink)
- P2P Communication Services (a la Whisper)
- Persistent File Storage Services (a la IPFS)
It’s really not crazy to think that the Polkadot Cloud would want to build or directly integrate these services into our offerings and how such services will bring better experiences to our users, and allow them to build more secure, scalable, and resilient Web3 applications and services.
The Polkadot Hub
The Polkadot Hub is the home for the Polkadot community, the DOT token, and other tokens across the Polkadot ecosystem.
If you were to make a sales pitch for the Polkadot Hub, it might look something like this:
The Polkadot Hub is a Layer 1 blockchain that supports smart contracts and is deployed on and secured by the Polkadot Cloud.
The Polkadot Hub has native features such as:
- Smart Contracts
- Staking
- Governance
- Treasury
- Stablecoins
- Token Registry
- etc…
The Polkadot Hub uses a Ethereum-compatible smart contract platform. This allows anyone to add their own programmable layers to Polkadot.
The purpose of the Polkadot Hub is to bring coordination, funding, and direction for the development and future of the Polkadot Cloud.
So the primary vibe of the Polkadot Hub should be community.
Every part of the Polkadot Hub is about tapping into the Polkadot community, and using them as a coordination machine bringing decentralization to the Polkadot Cloud.
Read more details about the Polkadot Hub
History of the Polkadot Hub
Our mission to create a platform for Web3 applications and services necessitated the creation of the Polkadot Hub.
You cannot have a decentralized platform without having a decentralized set of decision makers. In many ways, the Polkadot Hub is what separates the Polkadot Cloud from products which are “blockchain” or “web3” only by name.
So let’s again re-frame our history with this product in mind:
- Features launched on the Polkadot Cloud, but no Hub yet
- Creation of the Polkadot Hub, with Token Registry (Asset Hub)
- Proper Launch of the Polkadot Hub with Ethereum-compatible smart contracts (TBD, see launch details below)
- Transition Staking, Governance, and Treasury to the Polkadot Hub (TBD)
Since the genesis of the Polkadot Cloud, features of the Polkadot Hub have always been present. But these features lived directly in the Cloud, and were initially built this way because the Polkadot Cloud did not have its Hosting Service ready to use yet.
A number of projects have been ongoing, which would now be captured by the idea of the Polkadot Hub:
- The Asset Hub
- Token Registry
- Pay fees with any token
- Hold tokens without DOT
- The Minimal Relay Chain
- Smart Contracts on Polkadot
- etc…
Again, these projects were mostly being done in parallel, but without a clear vision of the goal and how they will all work together to paint a cohesive story. The Polkadot Hub brings a vision of what we are trying to build, and gives meaning to these various features.
Launch of the Polkadot Hub
The Polkadot Hub is an opportunity to “relaunch” the Polkadot brand.
For the first time, Polkadot will be open season for any developers, tinkerers, or builders to be able to quickly and easily deploy applications and contracts to the Polkadot Ecosystem. You no longer need to be a “cloud developer” in order to use Polkadot. Making smart contracts is easy, and thus building in Polkadot is easy.
Imagine messaging like the following:
Polkadot is proud to announce the Polkadot Hub.
The Polkadot Hub is a new L1 blockchain running on the Polkadot Cloud, and a launchpad for builders to tap into over 6 billion dollars in tokens across the Polkadot ecosystem.
The Polkadot Hub will be Ethereum-compatible, meaning you can deploy your favorite Solidity smart contracts directly to the Polkadot ecosystem.
The Polkadot Hub has native access to stable coins like USDC and USDT, as well as all of the tokens from the Polkadot ecosystem. The Polkadot Hub also has trustless bridges to Ethereum and other top blockchain ecosystems, meaning that you have worry-free access to essentially any token within the crypto market.
On the Polkadot Hub, you can pay transaction fees with any of these tokens, meaning you can even hold and use stablecoins without needing any other token!
The Polkadot Hub is a brand new, untapped resource for explosive product growth by tapping into one of the largest developer communities in the blockchain ecosystem.
With millions of users at your fingertips, there is no better place to launch than the Polkadot Hub. You can have your launchpad ready In: 3, 2, 1…
The Launchpad
A relaunch is not something that can be done without planning.
I would expect a number of specific initiatives to make the Polkadot Hub feel new, exciting, and like a proper launchpad for the next big projects in Web3.
-
The Polkadot Wallet
The goal is to have a clear and concise story around how users onboard into our ecosystem, and use applications and services across the Polkadot Cloud.
- It should have fiat onboarding flows.
- It should allow you to purchase in the real world with your Polkadot ecosystem tokens.
- It should give you a mobile gateway into the hub.
- It should allow you to “log in” to any Polkadot Ecosystem application or service.
- With a standard like Wallet Connect.
-
“Polkadot Bundle” Token Sale
The goal is encourage people to buy and use Polkadot ecosystem tokens, thereby rebooting the ecosystem.
- A new token sale coming from the Polkadot Treasury.
- Sold at the market price of the DOT token.
- “Bundled” with ecosystem tokens which are provided by ecosystem teams.
- Some amount of compensation from the treasury can be used.
- Many should contribute just based on it being a bootstrapping event.
- Very much “airdrop” vibes.
- Fully locked for 1 year. Fast vesting period afterward.
- But with the ability to participate or spend the tokens on the various Polkadot Services.
- Sold tokens go back to the treasury as stables, or to purchase more ecosystem tokens to include with the bundle.
-
Micro-grants
The goal is to get a bunch of people building in the Polkadot Hub, bringing and executing new ideas.
- Bounties for different application verticals:
- DAO templates for opengov
- staking pools templates
- account abstractions (on top of our native abstractions)
- cross chain messaging templates
- memecoin communities
- on-chain games
- etc…
- Rewards to the top teams in each vertical driving organic growth, and sustained usage for 6 months, as reviewed by a DAO / curator set.
- Bounties for different application verticals:
-
Participation Lotteries
The goal is to drive engagement of the Hub by end users.
- Imagine some percentage of all transaction fees get funneled into a special smart contract which holds weekly lotteries.
- You receive tickets from the lottery by submitting proofs that you have interacted with the Polkadot Hub.
- Any interaction where you Pay a fee should qualify, for a ticket.
- Users get a proportional number of tickets to the fees they have paid.
- This should not be gameable or exploitable.
- The contract selects a winner at random from among the tickets.
- Can’t really expect the lottery to be lifechanging, but is certainly a non-zero incentive.
- This adds some positive EV to simply using the Polkadot Hub!
-
Hackathons and Education
The goal is to radically shift entry level hackathons and education from the Polkadot Cloud (as it is today) to the Polkadot Hub.
- Create and work with teams to build new entry level educational material about the Polkadot Hub.
- Tutorials, videos, guides, templates, etc…
- Hackathon kits, which can be deployed by around the world for their local communities.
Journey To Scale
The Polkadot Hub will now be an entry point for developers into the Polkadot ecosystem. But we know that the true power of Polkadot lies in the Polkadot Cloud.
We must have a story for how we transition these developers and teams from the Hub to the Cloud.
For this, there are two components:
- Unified Programming Language
- Universal Tokens
The Unified Programming Language
I won’t go into too much detail about the unified programming language, because I have already written about it before here.
The short summary is that we need a language (like ink!), which can be used to both program on Smart Contracts on the Hub, and Services on the Cloud.
With such a language, we can literally tell the story about how your developers, team, and codebase can all seamlessly transition into the cloud whenever the time is right.
Obviously, building a contract and building a cloud service won’t offer the same functionality, but it should be a smart contract is a subset of whatever a cloud service could do, so we really should aim to make that experience as seamless as possible.
Universal Tokens
Universal tokens is the idea on how we should support tokens in the Polkadot ecosystem through the Polkadot Hub. As noted above, one of the native features of the Polkadot Hub is a token registry system.
Today, when new Cloud Services launch, they mint their own token local to their blockchain, and then transfer them over to the hub for interoperability.
In smart contract ecosystems, they mint tokens in storage specific to smart contracts.
Also, unfortunately, the DOT token is not treated the same as other tokens on the Polkadot Hub today.
If we allowed this to continue, the Polkadot Hub would have like 4 different kinds tokens across the product!
Universal Tokens is a vision toward having all tokens in the Polkadot Ecosystem natively minted and managed on the Polkadot Hub. Ownership of those tokens can then be assigned to contracts on the Hub or services on the Cloud.
What is key here is that Universal Tokens will allow a seamless pathway to transition ownership of the tokens from a contract to a cloud service. So even without a Unified Programming Language, end users of a product in the Polkadot ecosystem, will feel no pain at all when a transition like this happens. And in the scenario where we do have a Unified Programming Language, it might literally be seamless.
The other key feature of Universal Tokens is universal compatibility! If you launch your token natively on the Polkadot Hub, any contract or cloud service should be able to recognize and interact with that token in a standard way.
Imagine getting an NFT from a gaming service in the Polkadot Cloud, and then easily using or trading it on the Polkadot Hub, thanks to the fact that it is built using the Universal Token standard.
A “10 Year” Vision of the Polkadot Hub
This is where I will put some ideas in your head about the immense vision of what the Polkadot Hub could be. Not that this is what SHOULD happen, but it is perfectly possible given the mission of the Polkadot Hub.
If we are imagining a community centered product, it is easy to see how it could manifest similar to Web2 social networks. Why not when you open up the “Polkadot Hub”, it could land you on a page similar to Facebook?
Imagine seeing an activity feed of everything going on in the Polkadot Hub and broader Polkadot Ecosystem:
- What proposals are currently being discussed.
- Latest announcements / features.
- Technical discussions / RFCs.
- Collectives reporting their activity.
- Ambassadors providing proof of their work.
- Memes and marketing.
- Education and tutorials.
- etc…
Now imagine in your head the left sidebar:
- Groups: The various DAOs / chat groups you are a part of.
- Events: The next in-person or online meetups for the Polkadot ecosystem.
- Marketplace: A place to use cryptocurrency trade for digital or real-world goods!
- Finance: A home for all things DeFi.
- Apps: Gateways to other applications and services hosted on the Polkadot Cloud.
- Games: A portal into Web3 enabled games and communities.
Imagine in the top right, clicking your avatar, and managing your settings / profile:
- The accounts, wallets, and balances you have control of.
- Various account abstraction settings, like multisigs and proxies.
- Contracts you have deployed and their activity (users, revenue)
- Posts you have made in the Hub, and revenue generated from engagements.
- Your public identity.
- Your private individuality proofs.
- etc…
Finally, a cohesive and familiar experience for all the craziness we currently feel in the space.
And all of these features would be built with the principals of Web3! There is not a single team which builds this whole portal. It is a collection of work from the Polkadot ecosystem, unified by the Hub’s vision and mission.
We can literally rebuild the systems which spy on and extract profits from us, with trust free alternatives!
Key terms to use in discussion:
- Polkadot Hub
- Smart Contract
- Polkadot Cloud
- Cloud Service
- Universal Token
Key terms to avoid in discussion:
- Asset(s)
- Use Token(s)
- Plaza
- Use Polkadot Hub
- If needed, use additional qualifiers about what features you are referring to.
- JAM
- Use Polkadot Cloud
- If needed, refer specifically to the JAM milestone of the Polkadot Hub.
- Parachain
- Use Rollup, or Cloud Service depending
- Polkadot 2.0
- Use Polkadot Cloud with qualifiers around the features you are referring to
- Relay Chain
- Use the appropriate cloud services you want to describe (settlement, DA, execution, …)
- Or refer to the Polkadot Cloud directly
Some additional references:
- Short discussion on these same ideas here: Renaming "Parachains" to a More Generic Term - #31 by shawntabrizi
ACTION ITEM:
The action item for readers of this thread is to participate in the discussion.
- What are your reservations around this plan?
- What did we get wrong / can be improved?
- What is unclear to you?
Let’s start a discussion and create alignment.