TL;DR: The official Parity Technologies blog will no longer be replicated on Medium. Visit parity.io/blog for all future updates.
In the interest of data sovereignty, privacy, and open-source values, we’ve decided to only host our blog at parity.io/blog.
We’re committed to building the future of Web3 — an open and decentralized internet — and our choice of publication platforms should reflect this as much as possible. With this in mind, we’d like to begin moving away from centralized intermediaries whose incentives and practices may not always align with our own.
Update 15/2/2019: It has come to our attention that the scope of the fixed Parity Ethereum vulnerability is wider than we originally thought, and it could be exploited from a regular node-to-node connection without RPC access. While the previously released 2.2.10-stable and 2.3.3-beta protect against this wider scope, the wider scope means that everyone who runs Parity Ethereum, not just those who serve JSON-RPC publicly, should update as soon as possible. Download the update here.
The 2.2.10-stable and 2.3.3-beta releases protect Parity Ethereum nodes from potentially being able to be crashed by a targeted attack. …
On February 3rd, we received several reports that an attacker can send a specially-crafted RPC request to a public Parity Ethereum node (any version pre 2.2.9-stable and pre 2.3.2-beta) and that node will crash.
Who’s affected?
Affected Parity Ethereum nodes are those that serve JSONRPC as a public service.
Who’s not directly affected?
Parity Ethereum nodes who don’t serve JSONRPC to third parties on the internet — i.e., most nodes — should not be directly affected. The default mode is to not serve JSONRPC publicly.
Fix available — update ASAP
Releases 2.2.9-stable and 2.3.2-beta are now available and fix this issue. Download them here.
Please update your nodes to the newest…
Parity Technologies supports the consensus reached to postpone the Constantinople upgrade. Stay updated on the latest Constantinople and Parity Ethereum developments at @ParityTech or this blog post, originally published on Ethereum.org.
The Ethereum Core Developers and the Ethereum Security Community were made aware of the potential Constantinople-related issues identified by ChainSecurity on January 15, 2019. We are investigating any potential vulnerabilities and will follow with updates in this blog post and across social media channels.
Out of an abundance of caution, key stakeholders around the Ethereum community have determined that the best course of action will be to delay the…
The Thiel Foundation announced the 2018 class of Thiel Fellows, and Parity’s own Robert Habermeier has been selected as a recipient. The 20-year-old Washington D.C. native will receive $100,000 over the next two years to further the development on his current project Polkadot, as well as mentorship from the foundation’s large network of entrepreneurs, inventors, and scientists.
Gavin Wood, founder of Polkadot alongside Rob said, “Rob’s decision to halt formal education and pursue a path-less-trodden in co-founding the Polkadot project was a decision I very much supported. …
After assisting many ICOs and token sales last year, we are sad to announce that Parity ICO Passport Service (PICOPS) will no longer be operational as of May 24th, 2018. PICOPS is a service which enables individuals to associate a single Ethereum address with their unique identity. More precisely, the service offers an open means to validate that the owner of an Ethereum wallet has passed an ID background check stating that they are not part of a restricted set of users (e.g. citizen of a specific country or individual on a official watchlists).
After a long, cold January, Polkadot has been making headway and we are rapidly approaching our PoC-1 milestone. This encompasses a basic Proof-of-Stake relay chain which can have its block execution logic upgraded without hard forks and it also includes the groundwork for adding parachains, although the implementation of those will be left to PoC-2.
Other work on Polkadot that is ongoing at Parity Tech’s HQ is the integration of the WASM-based “runtime” code with existing type definitions. Additional changes are being made to the Parity Ethereum implementation to allow it to spin up a parachain. …
First of all we would like to wish everyone a very Happy 2018 from the team at Parity Tech! The holiday break didn’t stop our devs from working away on the Polkadot build, so here is our update with the latest progress.
The foundations of the Bridge development (Ethereum-Like <-> Ethereum-Like) is ongoing. This will enable us to create parachains which provide their own consensus, instead of relying on Polkadot’s native security and will connect smart contract capable blockchains to Polkadot without any modification to their protocol. …
A Brief History
Since Ethereum went live two and a half years ago, users and developers have often struggled with the usability and building on this new ‘Frontier’ of development.
The issues began almost immediately as the first users of Ethereum had to grapple with a command line interface that was extremely unforgiving of mistakes. It saw thousands of Ether sent to address 0x0, as any transaction with an ill-formed “to” address was interpreted by the client as a send to 0x0.
Then a few months later a bug was discovered in a library of Javascript utilities written by the…
It has been non-stop in the Parity Tech offices since our last update. We have been making plenty of progress, and as per the previous post our team is still split working on the Parity Client, aaaaand we are really excited because the building of the Polkadot Network has officially begun! We have set up a Riot channel for those who wish to follow the team during the building of the Polkadot Network to join the Riot channel: #polkadot-technical:matrix.org
We have been working on the initial version of the Polkadot spec, which is available here: https://github.com/w3f/polkadot-spec/blob/master/spec.md.
There is still a…
