Parity Technologies (@paritytech) header
Parity Technologies (@paritytech) profile picture

We're the Web3 innovators, core engineers, and Rust devs powering the decentralized web by developing @Polkadot. Here since 2015. Here to stay.

Berlin/London/Lisbon/Zug
Joined September 2015
Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)Photo by Parity Technologies (@paritytech)
Faster blocks are a win for users. For anything that counts time in blocks, they’re a trap. When a parachain speeds up with elastic scaling, its block count runs ahead. A deadline set for “100 blocks from now” arrives early. @Polkadot SDK handles this: pallets like vesting, multisig, proxy and treasury can count time in relay chain blocks, which keep a steady rhythm however fast the parachain runs. How elastic scaling works 👇 docs.polkadot.com/reference/…
i guess we're doin 500ms blocks now
5
18
3
78
7,239
On the afternoon of 7th Nov, @Polkadot Assembled with - 160+ serious folks - 8 speakers - Invite-only roundtable discussion for onchain carbon credits with a director of Morrow Suss Solutions - 6 MoU signing ceremonies with academic partners Started as just the new age conference, ended up becoming a genesis for many meaningful impacts to follow …
16
26
3
137
6,144
A signed transaction that never expires is a liability. If it’s stuck, leaked or forgotten, it can still be submitted long after you’ve moved on. @Polkadot SDK transactions can come with an expiry date. Each one is valid for a set window of blocks, and it’s also tied to the runtime it was signed for, so an upgrade invalidates anything signed under the old rules. github.com/paritytech/polkad…
4
25
137
8,113
Of the 143 organisations behind an ordinary day: - 83% say they use data for marketing - 80% combine it across sources - 76% use it for profiling - 66% keep it with no fixed end date Read the white paper by the @Web3foundation 👇 web3.foundation/insights
2
6
3
61
2,507
Bringing Solidity to a new chain shouldn’t mean guessing what works. @Polkadot Hub gives you two paths: → run existing contracts on the EVM with the tools you know → compile for PVM with revive when you want a RISC-V target
2
26
126
6,356
The usual way to scale an app is to split it across chains. Then every piece needs messaging, bridges and fee juggling just to talk to the rest of itself. JAM takes another route: hundreds of cores working in parallel, feeding one shared state. Your app gets more compute and stays in one piece. parity.io/blog/jam-what-it-i…
6
23
2
146
6,679
Hardcoded gas is a bet that every chain prices execution the same way. One token sale left $1.7M stuck because .transfer() only forwards 2,300 gas, and that wasn’t enough. If your contract assumes a gas cost, test that assumption on every chain. docs.polkadot.com/smart-cont…
6
17
2
137
5,284
Your contract compiled. It deployed. Then it behaved differently. “EVM-compatible” chains can still change what some opcodes and block values return. One study of 900k+ contracts found warning signs of this kind of code in 17.7% of them, on average. dl.acm.org/doi/10.1145/37289…
5
14
1
67
4,606
On @Polkadot Hub, the EVM path runs standard EVM bytecode on REVM. Your existing contracts deploy with the Hardhat, Foundry and Remix setup you already use. And you can test against a real Polkadot Hub node locally before anything touches mainnet 👇 docs.polkadot.com/smart-cont…
3
14
480
Some conferences get merch hunters. At @Web3summit we got code and chain hunters. 190 people shipped a dapp on @Polkadot in two days, claimed 272 .dot domains and forked 49 apps from each other. The merch was great too. But that was the best swag we’ve ever handed out.
4
22
1
114
5,963
Nothing unusual happens in your day. You commute, work, shops watch TV. By bedtime, 68 organisations may have collected, generated or inferred data about you. Which model household is your day closest to? 👇 web3.foundation/your-day-in-…
4
13
3
106
4,836
Every chain you add means another RPC provider, another bill and another endpoint that can go down. smoldot is an open-source light client that runs inside your app. It connects to the network directly and verifies what it receives, so there are fewer hosted endpoints to depend on. github.com/paritytech/smoldo…
8
31
74
5,463
Parity Technologies retweeted
Everything is open source now
1
2
1
16
1,462
An app that holds keys is an app that can leak them. Apps built with the Product SDK never touch keys. They ask the host for a signature, and the host checks every chain call and signing request before anything leaves. docs.polkadot.com/reference/…
4
30
2
115
4,522
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…
1
22
49
4,217
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
3
24
5
122
5,595
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
8
20
2
92
5,360
Web3’s final frontier: proving you’re a real person while keeping everything else private. Humanity is an open-source proof of concept for the @Polkadot ecosystem that takes it on, building on host code that already gives apps accounts and signing without exposing keys.
7
12
4
113
5,355
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.
5
14
1
84
3,139