Back to blog

Announcing Parity 1.1

A short 6 weeks since Parity 1.0, I'm happy to announce Parity 1.1, codename Alacrity. This is a mid-term release (we're half-way to 1.2 Civility) with mostly "under-the-hood" improvements and optimisations since 1.0.

Our main features for Alacrity are:

  • New JSONRPC APIs for tracking, tracing and inspecting all message-calls and balance transfers, including those that happen as "internal transactions";
  • a simple web front-end to inspect how far you've synced, what your mining rate is and play around with the JSON RPC (just head over to http://localhost:8080/ once you're running parity -jw);
  • for miners, a gas-price based upon the price of Ether, with automatic fetching from the web;
  • auto option for --pruning, so after the first sync it'll automatically find the right method.

In addition, under-the-hood improvements include:

  • Ubuntu 16.04 support;
  • builds for ARM with Ubuntu Snappy packages available through our CI system;
  • substantial refactoring and optimisation of the widely-used JSON codec;
  • optimised mining code that allows acceptance of old nonces and yet keeps up to date with all incoming transactions.

We're very excited to get this out to you; you can find binaries on the website and GitHub release page. Get support in the Parity Gitter channel.

Civility is now in active development and has features including full IPC compatibility for the wallet/Mist, a "bulletproof" actor/hypervisor architecture and an initial Proof-of-Authority consensus method. Look out for it in 6 weeks' time.

The Parity team.

Read more

  • On Classes of Stuck Ether and Potential Solutions

    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.

  • A Postmortem on the Parity Multi-Sig Library Self-Destruct

    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, was found by an anonymous user. The user decided to exploit this vulnerability and made himself the “owner” of the library contract. Subsequently, the user destructed this component.

  • Parity Technologies Multi-Sig Wallet Issue Update

    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 the smart contract, effectively making themselves the owner of the contract.

Back to blog