Blog of Parity Technologies

As announced earlier this year, Parity Technologies enlisted Trail of Bits, a top-tier security auditing firm specialising in smart contract security, Rust, and Solidity, to review our codebase. The scope of the audit

Recently there’s been a lot of discussion around using Wasm for blockchain development. Here's what the buzz is about: The issues with current tech Ethereum pioneered the field of decentralised application platforms

Summary: A consensus issue on the public test network Ropsten has revealed a consensus vulnerability that can be triggered by a malformed transaction. Severity: Critical Product affected: Parity Ethereum client Affected versions: stable

A potential consensus issue with Parity Ethereum has been identified. Severity: Critical Product affected: Parity Ethereum client Affected versions: stable track up to 1.10.5-stable beta track: up to 1.11.2-beta

We founded Parity Technologies with the aspiration to write the best and safest software we can. We’ve learned a lot from our past mistakes. The wallet bugs, in particular, lead us to

After receiving many proposals from security auditing firms, we are excited to announce that we have chosen Trail of Bits to review and, if indicated, improve the security of our code. With the

On Monday November 6th 2017 02:33:47 PM UTC, a vulnerability in the “library” smart contract code, deployed as a shared component of all Parity multi-sig wallets deployed after July 20th 2017,

This week, as has been widely reported, a vulnerability in the Parity Wallet library contract of the standard multi-sig contract was found by an anonymous user. This user managed to gain access to

Severity: Critical Product affected: Parity Wallet (multi-sig wallets) Summary: A vulnerability in the Parity Wallet library contract of the standard multi-sig contract has been found. Affected users: Users with assets in a multi-sig

A quick update on the status of Parity Ethereum client. Bug Bounty There is now a significant amount in our bug bounty programme (many thanks to all contributors). As mentioned in a previous