README.md (1044B)
1 # CRYPTO DEV SIGNER 2 3 This package is written because at the time no good solution seemed to exist for solving the following combined requirements and issues: 4 5 * A service has custody of its users' private keys. 6 * The are a large number of private keys involved (hundreds of thousands and up). 7 * Need to sign transactions conforming to EIP-155, with the ability to arbitrarily specify the "chain id". 8 * Do not want to store the keys inside an ethereum node, especially not the one connected to the network. 9 * Want to use the "standard" web3 JSON-RPC interface, so that the component can be easily replaced later. 10 * Multiple providers don't work on either web3.js and/or web3.py. 11 * As a bonus, provide a practical keystore solution for testing in general for web3 projects. 12 13 ## TECHNICAL OVERVIEW 14 15 ### keystore 16 17 - **Keystore**: Interface definition 18 19 ### transaction 20 21 - **Transaction**: Interface definition. 22 23 ### signer 24 25 - **Signer**: Interface definition. Its `signTransaction` method expects an object implementing the `Transaction` interface.