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. parity.io/blog/self-hosted-a…

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 👇 computeflux.ai/

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. parity.io/blog/how-to-get-st…

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.

Asset Conversion activity on Polkadot Asset Hub is getting easier to follow. Subscan has added DEX analytics for tracking swaps, exploring pools, checking liquidity and following token prices in one place. Useful if you’re building with Asset Conversion, or just want to see what’s happening across its pools.

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. github.com/turboflakes/suno

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. github.com/paritytech/produc…

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. polkadart.dev/

⚠️ A major Polkadot Product Devnet update is rolling out. A big update is coming to the @Polkadot Product Devnet, along with new mobile and desktop apps. If you’re already using the Devnet, there are a few quick things you need to do: 1. Back up your recovery phrase if you want to keep access to deployed sites 2. Clear your existing backup 3. Uninstall the app 4. Install the new version Full details 👇 docs.polkadotcommunity.found…

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. parity.io/blog/what-is-polka…

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.