Which chain am I on? Which token pays the fee? Most users can’t answer that, and they shouldn’t have to. With the Product SDK, apps hand chain connections and signing to the host. The app asks, and the host connects, shows the request and signs. Early-stage and open source 📷 github.com/paritytech/produc…

Today, every dapp rebuilds the same plumbing: wallet connection, signing, chain access, hosting. Users connect the same wallet again and again. With the Product SDK, the Host handles it once for every app: • less setup, more time on the actual feature • one approval flow on your phone • no keys inside apps to leak

What would you build with one Rust library on any @Polkadot chain? - A bot that reacts to every finalized block - An indexer that keeps decoding through runtime upgrades - A browser app that verifies chain data through a light client subxt handles transactions, storage, runtime APIs, and block subscriptions. Typed or dynamic, your choice. github.com/paritytech/subxt

Traditional blockchains make every node repeat the same work. Add more machines, and you get more copies doing the same thing, but not more compute. That model has a ceiling, especially as the internet shifts toward AI, agents, and increasingly compute-heavy applications. JAM is built differently. Work can happen in parallel across the network and be verified by other validators, turning many machines into something resembling one shared computer. As the network grows, its computing power can grow with it.

Hashing public keys into your message topics seems private. It isn’t. Take the open-source code and the account list from chain state, and an observer can compute every topic in seconds on a laptop. How to protect chat metadata on @Polkadot’s Statement Store, and where the limits are 👇 parity.io/blog/encrypted-mes…

Already write Solidity? Revive brings Solidity compilation for PolkaVM to the @Polkadot ecosystem. Revive compiles Solidity contracts to run on PolkaVM, Polkadot's RISC-V virtual machine. Your contracts can work with the assets and apps on Polkadot Hub, without having to learn a new language. Keep the tools you use, with a Hardhat plugin and an npm package. It's experimental and open source, published for developers to test, build on and shape: 🔗 github.com/paritytech/revive

Bitcoin showed an open network can agree on who owns what, with no bank in charge. Humanity on @Polkadot takes on the next problem: recognising that an account belongs to one real person without anyone learning who they are.

⚠️ Scam Alert: Fake Parity Wallet Website We've been made aware of a fraudulent website, parity-wallet[.]com, impersonating Parity Technologies and offering potentially malicious wallet software downloads. This website is not affiliated with Parity. Do not visit the site, download any files or run software obtained from it. Please stay vigilant and verify sources before downloading any software.

Building for the Human Web3 means a layer that keeps working when one server, one region or one company doesn’t. Apps served from the browser. Chain data checked by a light client. Signing that never hands keys to the app. All open-source code, out in the open for anyone to build on.

As products like the @Polkadot app bring more people on-chain, the network underneath has to grow with them. Today, the nodes serving users are run by separate groups, each funded on its own terms. What if validators, already a large and accountable fleet, took on more of that work, and were paid for the extra capacity? Validators, we'd like to hear from you: - If you ran an extra node alongside your validator, what would break first? - How much notice would you need to add hardware? - What would make it worth doing, beyond covering the cost? forum.polkadot.network/t/met…

Your old phone can keep your keys safer than your new one. In 2018, Parity Signer turned a spare smartphone into an offline signing device for @Polkadot. Keys never touch the internet. Transactions travel in and out by QR code, and the phone signs them without ever going online. The project lives on as Polkadot Vault, now developed and maintained by @NovasamaTech. wiki.polkadot.com/general/po…

Levity brings decentralised hosting and storage code to the @Polkadot ecosystem. Authorise. Store. Retrieve via IPFS. Data is retained by default for ~14 days, renewable before expiry. Content is addressed by hash, not by server location. Experimental, open-source, and published for developers to explore. 🔗 github.com/paritytech/polkad…

Web3 arrived with technology that could change how we interact, build, connect, communicate, and own our data. Then it got complicated before most people could grasp what it was actually for. Jollity starts from people. Once a week, you play a quick game on camera with a handful of strangers. They confirm you're a real person and nobody learns who you are. One piece of a larger direction. Trinity. Playground. Product SDK. Each solves a different problem. Together they describe the same thing: a decentralised web that works for people rather than asking people to work for it.

Most apps reach you through someone else's server. If that server goes down or gets blocked, the app goes with it. dot.li skips that step. Open a .dot name in any browser, and your browser fetches the app straight from the network, with no gateways or proxies in between. You get exactly what was published, and you can check it. See how Polkadot.com could be hosted entirely on-chain. dot.li/