75b6a31e87
* Copy modal from keepkey branch and generalize The keepkey PinMatrix modal needs to be the same for Trezor, but we should probably try to keep it general since it can be used for both. * Add trezor communication code This is a result of much trial-and-error and a couple of dead-ends in how to communicate and wire everything up. Code here is still a bit WIP with lots of debug prints and stuff. The test works though, it is possible to sign a transaction. * Extend the basic lib to allow Trezor This is kind of ugly and needs some cleanup and generalization. I’ve just copy-pasted some things to bring in the trezor wallets. I’ve also had to add a lock to the USB API so that only one thing talks to the USB at once. * Add RPC plumbing needed We need to be able to get “locked” devices from the frontend to figure out if we’re going to display the PinMatrix or not. Then we need to be able to send a pin to a device. * Add logic to query backend for Trezor and display PinMatrix There’s a bug somewhere here because signing a transaction fails if you take too long to press the confirm button on the device. * Change back to paritytech branch As my fork has been merged in. * Converting spaces to tabs, as it should be * Incorporate correct handling of EIP-155 Turns out the Trezor was adjusting the v part of the signature, and we’re already doing that so it was done twice. * Some circular logic here that was incorrect BE-encoded U256 is almost the same as RLP encoded without the size-byte, except for <u8 sized values. What’s really done is BE-encoded U256 and then left-trimmed to the smallest size. Kind of obvious in hindsight. * Resolve issue where not clicking fast enough fails The device will not repeat a ButtonRequest when you read from it, so you need to have a blocking `read` for whatever amount of time that you want to give the user to click. You could also have a shorter timeout but keep retrying for some amount of time, but it would amount to the same thing. * Scan after pin entry to make accepting it faster * Remove ability to cancel pin request * Some slight cleanup * Probe for the correct HID Version to determine padding * Move the PinMatrix from Accounts to Application * Removing unused dependencies * Mistake in copying over stuff from keepkey branch * Simplify FormattedMessage * Move generated code to external crate * Remove ethcore-util dependency * Fix broken import in test This test is useless without a connected Trezor, not sure how to make it useful without one. * Merge branch 'master' into fh-4500-trezor-support # Conflicts: # rpc/src/v1/helpers/dispatch.rs * Ignore test that can't be run without trezor device * Fixing grumbles * Avoiding owning data in RPC method * Checking for overflow in v part of signature * s/network_id/chain_id * Propagating an error from the HID Api * Condensing code a little bit * Fixing UI. * Debugging trezor. * Minor styling tweak * Make message type into an actual type This makes the message type that the RPC message accepts into an actual type as opposed to just a string, based on feedback. Although I’m not 100% sure this has actually improved the situation. Overall I think the hardware wallet interface needs some refactoring love. * Split the trezor RPC endpoint It’s split into two more generic endpoints that should be suitable for any hardware wallets with the same behavior to sit behind. * Reflect RPC method split in javascript * Fix bug with pin entry * Fix deadlock for Ledger * Avoid having a USB lock in just listing locked wallets * Fix javascript issue (see #6509) * Replace Mutex with RwLock * Update Ledger test * Fix typo causing faulty signatures (sometimes) * *Actually* fix tests * Update git submodule Needed to make tests pass * Swap line orders to prevent possible deadlock * Make setPinMatrixRequest an @action |
||
|---|---|---|
| .github | ||
| chainspec | ||
| dapps | ||
| devtools | ||
| docker | ||
| ethash | ||
| ethcore | ||
| ethcrypto | ||
| ethkey | ||
| ethstore | ||
| evmbin | ||
| evmjit | ||
| hash-fetch | ||
| hw | ||
| ipc | ||
| ipc-common-types | ||
| ipfs | ||
| js | ||
| json | ||
| local-store | ||
| logger | ||
| mac | ||
| nsis | ||
| panic_hook | ||
| parity | ||
| price-info | ||
| rpc | ||
| rpc_cli | ||
| rpc_client | ||
| scripts | ||
| secret_store | ||
| snap | ||
| stratum | ||
| sync | ||
| updater | ||
| util | ||
| whisper | ||
| windows/ptray | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| license_header | ||
| README.md | ||
| rust-toolchain | ||
| rustfmt.toml | ||
| SECURITY.md | ||
| test.sh | ||
Parity - fast, light, and robust Ethereum client
Join the chat!
Get in touch with us on Gitter:
Be sure to check out our wiki and the internal documentation for more information.
About Parity
Parity's goal is to be the fastest, lightest, and most secure Ethereum client. We are developing Parity using the sophisticated and cutting-edge Rust programming language. Parity is licensed under the GPLv3, and can be used for all your Ethereum needs.
Parity comes with a built-in wallet. To access Parity Wallet simply go to http://web3.site/ (if you don't have access to the internet, but still want to use the service, you can also use http://127.0.0.1:8180/). It includes various functionality allowing you to:
- create and manage your Ethereum accounts;
- manage your Ether and any Ethereum tokens;
- create and register your own tokens;
- and much more.
By default, Parity will also run a JSONRPC server on 127.0.0.1:8545. This is fully configurable and supports a number of RPC APIs.
If you run into an issue while using parity, feel free to file one in this repository or hop on our gitter chat room to ask a question. We are glad to help!
For security-critical issues, please refer to the security policy outlined in SECURITY.MD.
Parity's current release is 1.7. You can download it at https://github.com/paritytech/parity/releases or follow the instructions below to build from source.
Build dependencies
Parity requires Rust version 1.19.0 to build
We recommend installing Rust through rustup. If you don't already have rustup, you can install it like this:
-
Linux:
$ curl https://sh.rustup.rs -sSf | shParity also requires
gcc,g++,libssl-dev/openssl,libudev-devandpkg-configpackages to be installed. -
OSX:
$ curl https://sh.rustup.rs -sSf | shclangis required. It comes with Xcode command line tools or can be installed with homebrew. -
Windows
Make sure you have Visual Studio 2015 with C++ support installed. Next, download and run the rustup installer from https://static.rust-lang.org/rustup/dist/x86_64-pc-windows-msvc/rustup-init.exe, start "VS2015 x64 Native Tools Command Prompt", and use the following command to install and set up the msvc toolchain:
$ rustup default stable-x86_64-pc-windows-msvc
Once you have rustup, install parity or download and build from source
Install from the snap store
In any of the supported Linux distros:
sudo snap install parity --edge
(Note that this is an experimental and unstable release, at the moment)
Build from source
# download Parity code
$ git clone https://github.com/paritytech/parity
$ cd parity
# build in release mode
$ cargo build --release
This will produce an executable in the ./target/release subdirectory.
Note: if cargo fails to parse manifest try:
$ ~/.cargo/bin/cargo build --release
Simple one-line installer for Mac and Ubuntu
bash <(curl https://get.parity.io -Lk)
Start Parity
Manually
To start Parity manually, just run
$ ./target/release/parity
and Parity will begin syncing the Ethereum blockchain.
Using systemd service file
To start Parity as a regular user using systemd init:
-
Copy
parity/scripts/parity.serviceto your systemd user directory (usually~/.config/systemd/user). -
To pass any argument to Parity, write a
~/.parity/parity.conffile this way:ARGS="ARG1 ARG2 ARG3".Example:
ARGS="ui --identity MyMachine".