Parity Technologies

Final call: The @Polkadot Solidity Hackathon 2026 submissions close tomorrow. If you’ve been building on Polkadot Hub using Solidity, now’s the time to ship. An essential moment for: • onboarding EVM developers • testing app-first workflows • turning ideas into live applications Next signal: what gets built and what happens after. Huge thanks to @openguildwtf and @Web3foundation.

Cross-chain shouldn’t mean fragile bridges and external trust. The @Polkadot docs now clearly explain native chain interaction, how chains communicate, how assets are transferred, and how they coordinate securely. This isn’t an add-on. It’s part of the design. 👉 docs.polkadot.com

Instead of compressing everything into a single gas value, these are tracked across multiple dimensions, giving developers more visibility into trade-offs while maintaining compatibility with existing workflows. As execution models mature (e.g., PVM), these dimensions can become more explicit.

@paritytech It would be great to add what this means for developers rather than just describing the implementation and how estimation differs if choosing PVM

Ethereum measures execution with a single gas value. Polkadot measures resources differently. On Polkadot Hub, developers interacting through Ethereum wallets still see familiar gas values. Under the hood, however, the runtime tracks resources across multiple dimensions: • ref_time → computational time • proof_size → state data validators must verify • storage → persistent on-chain state, requiring deposits to reserve space Because Ethereum tooling expects a single gas value, exposing this model directly would break compatibility. Challenge accepted 🧑‍💻 Polkadot Hub solves this through gas mapping. At the RPC layer, Ethereum-style gas is translated into Polkadot’s internal weight and storage deposit model. When a wallet calls eth_estimateGas, the system performs a dry-run of the transaction to measure: • computation • state verification • storage footprint These resources are then mapped to gas, presenting the user with a familiar value while developers use familiar Ethereum wallets and tooling. Meanwhile, the runtime tracks computation, state verification, and storage usage separately. Ethereum compatibility on the outside. Multi-dimensional resource metering underneath.

🚧 Please be advised that the Polkadot community is currently voting on upgrading the Polkadot system to v2.1.1. This is a major runtime upgrade that provides support for Phase 1 of the Dynamic Allocation Pool (DAP), an issuance buffer configured as a multi-asset account (or sets of accounts) that collects all newly minted DOT and protocol revenue, enabling specific outflows in both DOT and other assets. 🔴Important note for Ecosystem participants: This release introduces numerous changes around staking and issuance which will stop treasury burns and redirect slashes in the first instance. This release also provides the prerequisites for making nominators non-slashable, allowing them to unbond funds in two eras, and enforcing a minimum self-stake and a minimum commission for validators. All these new parameters will be activated through subsequent OpenGov referenda. Additional note for Ecosystem builders: A Polkadot Technical Fellowship calendar has been set up to log basic information about upcoming runtime releases. You can subscribe to the Google calendar to access advance notices in real time. The projected enactment date for this runtime upgrade is around 26th March 2026.

@Polkadot Start building ↓ wizard.openzeppelin.com/polkadot

@Polkadot In this walkthrough: • Explore the wizard UI • Generate an ERC-20 with common extensions • Deploy to Polkadot using Remix or your preferred workflow youtu.be/WtkamOUxSms?si…

Ethereum-compatible smart contracts are expanding across the @Polkadot ecosystem. The OpenZeppelin Contract Wizard now lets developers generate Solidity contracts ready for deployment on Polkadot.

The first reduced issuance event happened today. You can see here, compared to the previous era, a much smaller amount of DOT was minted.

It’s happening. March 14, Pi Day, marks the issuance model change for Polkadot. One of the specifications is the maximum supply of DOTs, which is visualised below.

Participate in, and watch the development journey of RevX: forum.polkadot.network/t/revx-a-rust-…

RevX continues to evolve as a tool that makes it easier to get started with smart contract development while enabling the ecosystem to contribute directly to its growth. revx.dev

RevX also introduces a Contract Hub so developers can: • Save templates • Share them with the ecosystem • Contribute reusable contract patterns

Over the past few weeks, several updates have been shipped to RevX, our IDE designed for beginners, new joiners, and students, with a focus on making it easier to get started with smart contract development on Polkadot. Straight off the bat. RevX now starts with an AI prompt rather than dropping users directly into the editor, shifting the experience from editing code first to describing what you want to build.

What you’re seeing is the synchronization of a globally distributed system in real time. A new block on the relay chain is produced roughly every 6 seconds. In this telemetry view, each small flash represents a node, somewhere on earth, reporting activity as the block propagates through the network. This is the heartbeat of Polkadot.

can also try out one of my projects: pixfix. it does auto-splitting of sheets and generates animated gifs and allows for pixel normalization as well in a nice desktop UI. PRs welcome! github.com/lovelaced/pixf…

Builders expect solid tooling and clear documentation to match. The @Polkadot docs now bring SDKs, tooling, and integrations into one coherent, navigable experience. Fewer missing pieces. Fewer dead ends. 👉 docs.polkadot.com

Just spent time staring at Polkadot's live telemetry (telemetry.polkadot.io) and I can't stop thinking about this: 🌍 Block propagation times — RIGHT NOW, live: • Europe: ~100ms • Tehran: 155ms • Singapore: 150ms • Japan: ~300ms circumference of 🌍 via fiber optic ~130ms