This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
Releases: Consensys/ethsigner
Releases · Consensys/ethsigner
21.3.2
Bugs Fixed
- Fix nonce too low retries and added support for "replacement underpriced" and "Known transaction" RPC responses
Binaries
21.3.1
Features Added
- Update transaction signing to handle GoQuorum private transactions
- Azure remote signing now supports new Azure keys using the curve name P-256K and signature algorithm
name ES256K. The deprecated keys using the SECP256K and signature algorithm name ECDSA256 are still supported.
Bugs Fixed
- Fixing nonce too low retries and added support for replacement underpriced rpc response
Binaries
21.3.0
Features Added
- Upgraded besu-metrics library
- Publish ethsigner module jars to cloudsmith maven repo
- Update Besu latest version for Acceptance Tests
- Add gzip compression support
Binaries
21.1.0
Features Added
- Publish artifacts to cloudsmith.
- Added support for sending GoQuorum private transactions via "eth_sendTransaction" JSON-RPC
- Improve error message if HTTP server fails to start
Binary packages
20.10.0
Features Added
- Added "eth_signTransaction" JSON RPC
- Docker namespace updated to reflect "consensys/quorum-ethsigner"
- Strip ACCESS_CONTROL_ALLOW_ORIGIN header from responses received from the web3provider
- Added a Prometheus metrics endpoint, reporting basic application metrics
Bugs Fixed
- Transactions were not being handled in parallel, triggering poor performance under load
0.7.1
Features Added
- Support for using config file and environment variables as default values for cli options
- Updated signers library to the latest version
- Accessing Azure signing service requires tenant id as part of Azure configuration
- Communication details moved to Discord
Bugs Fixed
0.7.0
Features Added
- Added "eth_sign" JSON RPC
- Added "--http-cors-origins" commandline option to allow browser based apps (remix/metamask) to connect to EthSigner
- Added "--downstream-http-path" commandline option to allow Ethsigner to connect to a downstream web3 provider not on root path (eg web3 provider running in infura)
- If inbound request contains the "Host" header, it is renamed to "X-Forwarded-Host" and added to downstream request
- Code base split, crypto operations moved to "Signers" repository
- First line of Password file (stripping EOL) is treated as the password (rather than whole file content)
Bugs Fixed
- Create invalid signature when Signature field was treated as negative BigInteger #247
0.6.0
0.5.0
Changelog
0.5.0
Known Issues
Features Added
- Added TLS support for incoming and outgoing RPC endpoints
- Added TLS support for connecting to Hashicorp vault
- Upgraded PicoCLI to 4.1.4
Bugs Fixed
0.4.0
Changelog
0.4.0
Known Issues
Features Added
- Multi-key signing: Ethsigner is initialised with a directory containing a number of TOML metadata files, each of which describe a key which may be used for signing. Upon reception of a Transaction, Ethsigner loads the corresponding metadata file, and signs the Transaction with the key defined therein.
- Relaxed definition of 'optional' when parsing eth_SendTransaction (empty string, null an "0x" are deemed a missing optional parameter).
- All endpoints (not just "/") are proxied to the downstream web3j provider (eg. "/login")
- CI moved from Jenkins to CircleCI
- Updated to Web3j 4.5.5
- Updated to JUnit 5
Bugs Fixed
- When a private transaction is submitted without a nonce, a nonce is generated and inserted. However, if the supplied nonce is too low, the transaction is not resubmitted with a new nonce. Rather an error is returned to the caller (resolved in Besu 1.2.5).
- Removed intermittent "out of memory" failure during integration testing.
- Resolved an issue whereby a missing optional field in eth_SendTransaction would fail