Ethereum and Solana showed how much can be built when developers can deploy code directly to a general-purpose blockchain. JAM brings @Polkadot into the same territory with an architecture built around parallel computation. Its cores can work on different jobs at the same time, running smart contracts, agents and other software across a shared environment. This is Polkadot’s evolution into a collective computer that @gavofyork describes.

Polkadot has a lot of moving parts. That complexity can also make the ecosystem harder to navigate for new developers. Use the #PolkadotBuilderMap# interactive map to see how different components connect, explore what each one does, and find the relevant docs in one place.

The cloud is easy to rent and hard to verify. Blockchains are easy to verify and hard to rent. JAM is designed to give you both: 341 cores that anyone can rent and the network verifies. Rent it like the cloud, trust it like a blockchain.

Today, validators working on @Polkadot's cores check that parachain blocks follow their rules, keep that data available for 24 hours, and take part in consensus. To use a core, though, you have to be a parachain. JAM opens that up. Any code built for its virtual machine will be able to rent time on a core directly: smart contracts, agents, media serving, regular software. Parachains keep running as one kind of service among many. Same cores, open to anyone who needs compute. That's what the cloud did for servers.

Your collateral top-up, your trade, or the price update your position depends on shouldn't be at the mercy of a single collator. Without protection, a malicious collator can withhold a block to make the next collator miss their turn, then use that gap to censor transactions. That's enough to get a position liquidated, a trade sandwiched, or a price feed held back. Polkadot hardened parachains against this with multi-slot collation, giving collators a longer window to recover from it.

The web has changed. What people need from the infrastructure underneath it has too. @Polkadot gives developers the tools to build blockchains from the ground up. The Polkadot Products Devnet extends that flexibility to developers who want to start with the product. Identity. Payments. Storage. Signing. Communication. You focus on what people use. Start here:

Three layers, one identity. At the top, chains: People Chain runs the game, score and membership logic. Asset Hub runs the naming. In the middle, your host (the app on your phone or desktop) holds the root key and derives one for each product it talks to. At the bottom, Jollity turns plain protocol calls into an actual game. Play it, and it quietly raises your standing on-chain: Devicehood becomes Membership, one Score point at a time.

The shield color at the top of pages tells you how the page connected. Green means a light client where you verify the data yourself without a middleman. Orange means it fell back to rpc-gateway, which is more reliable, but you're trusting a central node instead. New tabs default to light client per-tab. If you keep landing on orange, check Settings for "Light Client Shared" or "Light Client Per-Tab."

Web3 belongs in the mainstream. @BillLaboon joined Good Morning Britain @GMB yesterday to discuss our latest research on privacy, data, and the everyday internet. This is the work we love! We take the ideas behind Web3 beyond our industry and into the conversations shaping how people think about the future of the web.

The blog now has an RSS feed: Add it to your RSS reader and get every post on JAM, Trinity, the Products Platform, the Statement Store, and more as it goes live.

Push notifications shouldn't be a spam vector. With Avidity, you decide who can notify you. Every notification comes from a signed, backend-verified event, checked against your whitelist before it ever reaches you. Tokens stay on the backend where no peer ever sees yours, and nothing reaches you unless you've approved the sender first.

Not everything your app stores needs to live in the same place. On @Polkadot, you can keep shared state and logic in contract storage, larger files on Levity, live signals in Celerity, and device-specific data locally. You decide what's permanent, what's shared, and what stays on-device.

25 engineers ran a self-hosted open-weight model for one month, generating 13 billion tokens. But our trial continued running because people kept using it, unprompted. Along the way, we uncovered real insights into owning our own AI infrastructure: cost, availability, model choice, data, and future capabilities, instead of depending entirely on external providers.

You can't decentralize a physical computer. It's still a machine in a room, running under someone's control. But you can decentralize computation. If independent machines execute the same deterministic logic and agree on the result, the computation no longer depends on any single computer. That's the deeper idea behind blockchains. The @Polkadot ecosystem is taking this further through its work on JAM and Polkadot Products, spanning permissionless computation, verifiable services, content-addressed storage, identity, and other network capabilities. The point is to decentralize trust in computation, enabling a more human-controlled internet. A thought from the Hong Kong stop of the JAM Tour with @pala_labs.

AI is coming to the @Polkadot Products Devnet. @computefluxAI is now live, giving users and AI agents one interface for accessing multiple AI models and compute providers. Try ComputeFlux on the Devnet 👇

What do you do when your app needs real-time updates without putting every interaction on-chain? Celerity lets you send signed, short-lived messages between users for things like presence, typing indicators, live status updates or announcing new content. Connect directly via p2p layer and your app can send and receive them without depending on a single RPC provider.

What happens when your app doesn’t need to manage the user’s keys? On the @Polkadot Devnet, .dot apps run through the Polkadot App. The Host API gives them access to accounts, signing, chain connections, storage and permissions, while keys stay with the user. Your app asks. The host handles the rest.

Can you trust what you see online? Karim Jedda (@KarimJDDA), Engineering Director at @paritytech, examines a growing problem for the internet: content can now be generated faster than humans can verify it. The challenge is not simply that AI can produce convincing content. A small number of actors can also create the appearance of many independent people through automated accounts, fabricated identities and manipulated reputation signals. Follower counts, ratings and verification badges are no longer sufficient guarantees of authenticity. Karim presents a different approach: cryptographic proof of personhood that allows someone to prove they are a unique human without revealing their identity. Developed at Parity and built on @Polkadot, the Humanity system treats decentralization as a security requirement for this kind of infrastructure. The question becomes less about making information impossible to fake, and more about making its provenance and authenticity verifiable. Watch the full talk (2nd tweet):

AI can use @Polkadot Claude Code can now handle chain connections, transactions, contracts, storage and app scaffolding through the Product SDK. @computefluxAI is already bringing Claude into a Polkadot-native AI stack. Connect the two, and AI moves from helping write the code to interacting with Polkadot itself.