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.

All week, you’ve heard about the need for more regulation and safety concerns around AI. We're looking at this through a slightly different lens. Consider this... The biggest beneficiaries of tougher AI rules may actually be the companies those rules are meant to keep in check, because if only the largest labs can afford compliance, regulation can become a moat, and AI governance should reduce concentrated power, not lock it in. Either way, it's a debate. If you’re not sure what we mean by the call for tougher AI rules. Some refs below👇 📸 Credit: Stop the AI Race / Rachel Shu

Suno is a terminal tool for @Polkadot node operators to manage validator operations, including staking, session keys, and validator status. It connects to Polkadot using light clients, so there are no RPC endpoints in sight to configure, and it supports Polkadot Vault for offline signing. Run your validator ops from the terminal, nothing else to set up.

What can you build on @Polkadot? How about a light client small enough to run on an ESP32, powered by a 9V battery? 🔋 It follows the relay chain and verifies finality proofs locally, so it can read parachain state without trusting an RPC provider. Next: connecting it to the Devnet.

How much @Polkadot do you need to know to build on Polkadot? Less than you might think. Underneath your app, Polkadot handles consensus, security, and shared infrastructure. Polkadot Hub provides smart-contract execution. The Product SDK gives your app a way into platform capabilities. You can start at the application layer and go deeper when your project actually needs it.

We’re rebuilding @Polkadot Dart from the ground up. Light-client first, using smoldot's Rust implementation. Audited crypto crates replacing Dart-native operations. Full Trinity and Product SDK support via Rust. That means a production-grade path for Flutter and Dart into the same Polkadot development surface. Signing, storage, identity, and other platform capabilities are available without running a full node or trusting a third-party RPC. Four years on, the tooling has matured enough to do this properly.

What makes a name online mean anything? With DotNS, proof of personhood can be part of the rules governing who can register certain names and what happens when those names change hands. Humanity provides the proof that there's a unique person behind an account. DotNS puts that proof to work. Build products where being human actually means something.

Your app needs messaging. Does it need a server too? Not with Celerity. Messages are signed, kept off-chain and propagated between nodes, with no central service in the middle. Trinity already uses it for decentralized chat. Messaging can be part of the shared infrastructure too.

How do you prove you're a real person online without turning it into a chore? Jollity is experimenting with a very human answer: meet other people. Short video meetups randomly bring people together to establish personhood through participation. Simple. Social. A little more fun than proving you're not a robot. Human Web3 needs humans. Jollity starts there.

Exploring potential solutions for stablecoin infrastructure Donal Murray, Engineering Manager at Parity, joins the Common S3nse stage to explore what past stablecoin failures can teach us about peg, collateral, and oracle design, and how those lessons are shaping a reusable stablecoin layer on @Polkadot, built around the problems existing systems have exposed. Towards Better Stablecoin Infrastructure Building Polkadot’s Stablecoin Layer 📍 Common S3nse, Amsterdam 📅 Friday, September 4

Building on a parachain means giving people a safe way to understand and approve what your app asks them to do. Merkelized Metadata makes that easier, especially on hardware wallets where space is limited. No blind signing. Clearer transactions. Less trust placed in third parties. A small piece of infrastructure that makes building safer apps on @Polkadot easier.

Using Claude Code? The Product SDK plugin can help you scaffold an app and work with signing, contracts, storage, transactions, and chain connections: 🔗 Explore the @Polkadot Devnet and start building: 🔗 More developers are building toward a Human Web and you can too.

The most valuable data about you might be data you never gave anyone. Companies can infer interests, intent and relationships by connecting signals from your activity online. @Web3foundation's The Hidden Price of Free looks at the economy built around turning those signals into commercial value. Human Web3 starts somewhere else: share what's needed. Keep the rest private.

This repo doubles as a Claude Code plugin marketplace. The plugin ships skills that teach Claude Code to use packages for chain connections, transactions, contracts, cloud storage, state storage, utilities, and end-to-end app scaffolding.

Human Web3 requires a system, not a single protocol. Trinity for a coherent user environment. The Product SDK and Host to make capabilities accessible. Celerity and Levity to move information. Bulletin and Capacity to publish and retain it. Avidity to reconnect applications with users. Privity to protect the boundaries between identities. The measure of success for this infrastructure is how rarely users need to think about it.

In the current web, people exchange convenience for surveillance, dependence, and diminished agency. Building an alternative requires a different kind of infrastructure. Identity without a centralized login. Communication without a platform intermediary. Storage without depending on a single company. Notifications without permanent app access. Privacy without trusting every service to behave well. Trinity, Celerity, Levity, Capacity, and Avidity are parts of an attempt to change the underlying bargain of the web.

Not all data is the same. A chat message needs to arrive in seconds. A file needs to survive until both sides are ready. An app needs to load instantly for anyone who opens it. Some data needs to persist for years. We are building the infrastructure Human Web3 needs based on how people actually use and interact with information.

Build your app. Register a .dot name. Publish the bundle once. Your app is live at your .dot name in the @Polkadot app and at a public web address anyone can open in a browser. No hosting infrastructure to manage.