funga-eth
Ethereum implementation of the funga signer interface.
See https://git.defalsify.org/funga for more details.
Tools
When installed as a python package, three tools are installed in the python executable script path.
funga-ethd- Signer daemon (see below for details).eth-keyfile- Ethereum keyfile en- and decoder, and en- and decrypter.eth-msg-sign- Signer tool for arbitrary messages (ERC-191).
funga-ethd
A Unix socket IPC server as funga-ethd implementing the following web3 json-rpc methods:
- web3.eth.personal.newAccount
- web3.eth.personal.signTransaction
- web3.eth.signTransaction
CLI tools
Please use --help as argument to the eth-keyfile and eth-msg-sign tools to learn the arguments the tools accept.
Funga interface implementations
- ReferenceKeystore: Implements the
Keystoreinterface, with a postgresql backend expecting sql schema as defined inReferenceKeystore.schema - ReferenceSigner Implements
Signer, accepting a single argument of typeKeystoreinterface. - EIP155Transaction: Creates transaction serializations appropriate for EIP155 replay protected signatures. Accepts a web3 format transaction dict as constructor argument together with nonce and optional chainId.
Metadata
Release files for funga-eth 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| funga-eth-0.8.0.tar.gz | 31.8 kB | Without provenance | Details |
Release files / funga-eth-0.8.0.tar.gz
| Download URL | funga-eth-0.8.0.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38a9c64c67ceda5439a5638b577d385335edae686fddfb8dc27ea13c83bc4d4a
|
|
BLAKE2b-256 checksum How to use checksums |
a9803a90169ed118b603be22e9fbed52d229e8498ae4e70ce1c3f194c94d6a5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.8
|
Security for funga-eth 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.