What should a Polkadot product feel like?
You shouldn't need to understand the infrastructure behind it.
A URL should be enough to open it. Interfaces should feel familiar. Your identity should remain coherent across the experience. And privacy shouldn't disappear just because you interact with someone else.
That's the product standard Gavin Wood described during the @Web3summit for Polkadot Products.
The technology underneath can be complex.
The experience shouldn't be.
What exactly is Polkadot's JAM?
JAM, the Join-Accumulate Machine, is specified as a protocol in the Gray Paper, combining elements of Polkadot’s cryptoeconomic machinery with a more programmable, Ethereum-oriented service model.
The important shift is that JAM does not just make computation programmable. It also makes the way computational elements are joined together and their effects accumulated programmable.
As @gavofyork explains, that is the idea behind the Join-Accumulate Machine: a protocol that provides a foundation for permissionless services at the protocol level.
Browse is the app directory for the Polkadot Products Devnet.
It uses an on-chain registry to make published `.dot` apps discoverable. Browse then resolves each app's name, description and icon from its `.dot` records.
Listing is opt-in. An app can still be live and reachable through its `.dot` domain without appearing in Browse.
See what developers are building:
https://t.co/vW99nzXjUg
Chat and calls are built into the Polkadot app.
Messages use the People chain's Statement Store. Media is stored on Bulletin. Calls use WebRTC.
These are the same building blocks Products can use for their own apps.
One ecosystem, shared infrastructure: https://t.co/WsntYkshQS
Chat and calls are built into the Polkadot app.
Messages use the People chain's Statement Store. Media is stored on Bulletin. Calls use WebRTC.
These are the same building blocks Products can use for their own apps.
One ecosystem, shared infrastructure: https://t.co/WsntYkshQS
Polkadot has a new strategy.
Proposed by the Polkadot Community Foundation (PCF) and approved by 97% of votes on 11 November via Polkadot’s decentralised governance system.
It focuses on direct user acquisition for the upcoming Polkadot product platform.
Must read 👇
“Bitcoin doesn't have owners. And that's the beauty of Bitcoin.”
At the @web3summit, Yanis Varoufakis (@yanisvaroufakis) contrasts Bitcoin with what he calls “cloud capital”: systems that learn from their users and can ultimately be used to influence their behavior in the interests of their owners.
Whatever your view on Bitcoin's monetary design, the distinction is important.
A network without a central owner creates a fundamentally different relationship between the infrastructure and the people using it.
That idea of removing dependence on a single owner is also part of the broader thinking behind decentralized infrastructure like Polkadot.
What does self-sovereign technology actually mean?
It means control stays with the individual.
The tools should help you do more, not make you dependent on the provider behind them. And when those tools connect you with other people, the interaction should be as direct as possible.
This is one of the principles behind Polkadot Products: technology designed to give people more control over how they interact with the digital world.
For Gavin Wood, self-sovereignty is not just a feature.
It is the point.
What does self-sovereign technology actually mean?
It means control stays with the individual.
The tools should help you do more, not make you dependent on the provider behind them. And when those tools connect you with other people, the interaction should be as direct as possible.
This is one of the principles behind Polkadot Products: technology designed to give people more control over how they interact with the digital world.
For Gavin Wood, self-sovereignty is not just a feature.
It is the point.
One Polkadot account and three clients.
The Polkadot app runs on Android, iOS, and Desktop.
Your keys stay on your device, while apps run in a separate, protected environment.
Same account, same apps and three ways to use them: https://t.co/WsntYkshQS
There are two ways to build the internet.
One where platforms own your account, your data, and your reach.
And one where users keep control.
That's the direction Polkadot is pushing toward.
Applications and platforms should compete to serve users, not own them.
Build on the Polkadot Products Devnet and help create a more humane internet: https://t.co/Uti7yCC0XS
For years, the mental model of Polkadot has been simple:
The relay chain sits at the center, and parachains connect to it.
JAM flips that model.
Instead of building the system around parachains, JAM is designed around services. Parachains can still exist, but they become one type of service running on top of JAM.
That’s where the Parachain Service comes in.
It gives parachains a place to live inside this new architecture, while JAM takes care of the underlying consensus, security and execution.
So the transition isn't really “parachains vs JAM”.
It’s parachains becoming one piece of a much bigger system.
Learn more ⤵️
Reserve your .dot name.
On the Polkadot Products Devnet, a .dot name is registered on-chain and owned by the account that registers it.
Names with a stem of 9+ characters are open to everyone. 6–8 character stems require proof of personhood, while stems of 5 characters or fewer are reserved.
Registration uses commit-reveal, so the name stays hidden until the reveal.
Once registered, the name is yours. It can be transferred, but the registration itself cannot simply be overwritten or deleted.
Learn more: https://t.co/mA07TgJP5L
Code can define the rules of a protocol.
Culture helps determine whether those rules are defended.
At the @web3summit, the Cypherpunk Culture panel discussed how a blockchain community's shared values shape what it considers acceptable, especially when attempts at centralization or capture emerge.
That makes decentralization more than a technical property. It also depends on the people who recognize when the underlying principles are being compromised.
For protocols like Polkadot, that social layer matters too.
You can see that social layer play out through governance every day. OpenShore follows those decisions across the Polkadot ecosystem, helping you understand the OpenGov context at https://t.co/LfjxuMscmj.
Code can define the rules of a protocol.
Culture helps determine whether those rules are defended.
At the @web3summit, the Cypherpunk Culture panel discussed how a blockchain community's shared values shape what it considers acceptable, especially when attempts at centralization or capture emerge.
That makes decentralization more than a technical property. It also depends on the people who recognize when the underlying principles are being compromised.
For protocols like Polkadot, that social layer matters too.
You can see that social layer play out through governance every day. OpenShore follows those decisions across the Polkadot ecosystem, helping you understand the OpenGov context at https://t.co/LfjxuMscmj.
We live in the information age, the age of the sovereign individual, but the services available to us are not aligned with that.
@gavofyork argues that Polkadot’s core technology is now ready to deliver the applications people will actually use in this new age.
Solidity contracts can run on Polkadot, end to end.
Write in Solidity or Rust, compile to PolkaVM, deploy through `pallet-revive`, and call the contract from your frontend with the Product SDK.
The current developer flow covers the whole path, from funding an account to deploying and interacting with a live contract. Learn more: https://t.co/AijywDEOai
What should a Polkadot product feel like?
You shouldn't need to understand the infrastructure behind it.
A URL should be enough to open it. Interfaces should feel familiar. Your identity should remain coherent across the experience. And privacy shouldn't disappear just because you interact with someone else.
That's the product standard Gavin Wood described during the @Web3summit for Polkadot Products.
The technology underneath can be complex.
The experience shouldn't be.
What should a Polkadot product feel like?
You shouldn't need to understand the infrastructure behind it.
A URL should be enough to open it. Interfaces should feel familiar. Your identity should remain coherent across the experience. And privacy shouldn't disappear just because you interact with someone else.
That's the product standard Gavin Wood described during the @Web3summit for Polkadot Products.
The technology underneath can be complex.
The experience shouldn't be.