Skip to content
The Chat Archive
sonar-reasoning LMArena Search Arena 24K

paritiy wallet

  1. User

    paritiy wallet

  2. Assistant

    The Parity Wallet is a desktop-based Ethereum and ERC20 token wallet developed by Parity Technologies, a team with deep ties to Ethereum's ecosystem[[1]]. While it offers features like fast blockchain synchronization and a built-in exchange, its history has been marred by critical security vulnerabilities.

    Key Features

    • Fast Sync: Avoids full blockchain downloads by querying full nodes[[1]].
    • Built-In Exchange: Enables token swaps via Shapeshift integration[[1]].
    • Developer Tools: Includes Web3 console, TX-Queue viewer, and dApp browser[[1]].
    • Lightweight Design: Small storage footprint for easier management[[1]].

    Major Security Incidents

    1. **July 2017 Hack (30MStolen)∗∗Aflawinthe"kill"functionofParity’smulti−signaturewalletsallowedattackerstotransferownershipoffundstoanewaddress.Over150,000ETH(30M Stolen)** A flaw in the "kill" function of Parity’s multi-signature wallets allowed attackers to transfer ownership of funds to a new address. Over 150,000 ETH (30M at the time) was stolen, with victims including Aeternity, Edgeless, and Swarm City[[4]][[8]].

    2. November 2017 Freeze (150M–150M–280M Locked)
      A separate vulnerability in the library contract used by Parity’s multi-sig wallets allowed a user ("devops199") to self-destruct the contract, freezing funds in over 500 wallets. This included $90M raised by Parity’s founder Gavin Wood[[2]][[3]][[7]].

    Recent Developments

    • 2024 Fund Movement: The July 2017 hacker transferred 3,050 ETH (9M)throughtheeXchplatform,partoftheoriginal9M) through the eXch platform, part of the original 30M stolen[[6]].
    • Bounty Offer: Victims of the July 2017 hack offered a 60Mbounty(1060M bounty (10% of stolen funds) for the return of 90% of the ETH, now worth ~600M[[5]].

    Security Concerns

    • No 2FA/Hierarchical Determinism: Relies on seed phrases without additional authentication layers[[1]].
    • Smart Contract Risks: Both incidents highlighted vulnerabilities in self-destruct functions and library dependencies[[2]][[4]].

    Impact and Legacy

    The hacks eroded trust in Parity and smart contracts, prompting stricter auditing practices. While Parity addressed vulnerabilities post-2017, the frozen funds from the November 2017 incident remain unrecoverable without a hard fork[[3]][[7]]. The wallet remains functional but is no longer widely recommended for multi-sig use due to its history[[1]][[8]].

  3. User

    full code

  4. Assistant

    The Parity Wallet's source code is available on GitHub, primarily through the Parity Ethereum client repository. Below are key details for accessing and building the code:


    GitHub Repository

    The main implementation is hosted at:
    https://github.com/paritytech/parity-ethereum[[1]][[5]]


    Build Requirements

    To compile the code, you need:

    1. Rust: Install via rustup (minimum version 1.17.0)[[1]][[5]].
    2. Dependencies:
      • Linux: gcc, g++, libssl-dev, libudev-dev, pkg-config[[1]][[5]].
      • macOS: clang (via Xcode or Homebrew)[[1]][[5]].
      • Windows: Visual Studio 2015 with C++ support[[1]][[5]].

    Build Instructions

    1. Clone the repository:
      git clone https://github.com/paritytech/parity-ethereum
      cd parity-ethereum
      
    2. Build in release mode:
      cargo build --release
      
      The compiled executable will be in ./target/release/parity[[1]][[5]].

    Key Components

    • Wallet Functionality: Integrated into the Parity Ethereum client, accessible via http://web3.site/ or http://127.0.0.1:8180/[[1]].
    • Light Client: Uses a lightweight node for faster synchronization[[7]].
    • Smart Contracts: Written in Solidity, with Rust-based wallet logic[[6]].

    Security Audits

    A 2018 audit by Trail of Bits identified vulnerabilities in key generation, cryptography, and data validation, leading to improvements in later versions[[6]].

    For Docker-based deployments, custom configurations (e.g., chain genesis files) can be mounted to containers[[2]].

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.