@oussamachaabouni When eth_accounts is called on EthSigner, ethSIgner responds with the list list of addresses that it is able to sign transactions for; otherwise:
When you create a new network, the initial accounts and their balances are specified in the genesis file. It is critical the private keys associated with each account are known by the people who control said account.
When you create a new network, the initial accounts and their balances are specified in the genesis file. It is critical the private keys associated with each account are known by the people who control said account.
@alluminoustech Ethsigner is able to sign transaction using the private keys loaded at startup (file, hashicorp vault or azure). Ethsigner is able to submit signed transactions to any web3 provider, no matter which network it is connected to.
Can you clarify what you mean by "transctions from a contract"?
Can you clarify what you mean by "transctions from a contract"?
Hi everyone, I went through the EthSigner source code and extended it to support Infura (Rinkeby), Azure Key Vault and signing messages using Azure Key Vault through EthSigner. I wrote a long article about it which I hope will be useful to everyone. https://medium.com/@corgi.desu/a-study-on-blockchain-key-management-systems-part-1-a668eedee058?source=friends_link&sk=f888e20f58b769bb638f427eaf5306ec
@sprect8 nice work with the ethsigner mods! I'm thinking the change you made with URL vs IP should be rolled into the main repo, definitely useful - care to raise it as a PR?
@arash009 on besu, the private key used is stored plain, with the reference of the file location in the node's config. It would have been better to have it more secret.
By the way ; I saw in the source code that :
By the way ; I saw in the source code that :
- for Azure, ethsigner initializes a connexion to Azure KeyVault ; calling its signature API endpoint
- for HashiCorp Vault, ethsigner extracts the private key to generate a web3j credentials.
Is there a way to link EthSigner to be able to use not a single but several key from these Keystores?
like, extracting the 'from' field in a transaction and then look for its associated file/keyvault endpoint/vault secret -- or is it working that way currently and I did not find it?
@ArvsIndrarys Ethsigner has a "mult-key" signing mode (https://docs.ethsigner.pegasys.tech/en/latest/Reference/Multikey-Parameters/) - it allows you to specify a directory which is to contain toml files - each of which describes/defines how a key can be loaded (file-based, azure, hashicorp etc).
Btw - Azure supports the secp256k1 curve, and thus the signing operation is performed in azure - Hashicorp (At the time of code-creation) did not support the curve, so the private key is extracted, and signatures produced locally.
Btw - Azure supports the secp256k1 curve, and thus the signing operation is performed in azure - Hashicorp (At the time of code-creation) did not support the curve, so the private key is extracted, and signatures produced locally.
Hi guys does EthSigner support multi signature transaction? By multi signature, i meant a transaction that is signed by multiple independent private keys belonging to different public keys (not a transaction signed using multiple private keys that belong to the same public key /address). I am trying to implement an app that requires multiple parties to sign a transaction offline before sending it to the Blockchain. I am using Hyperledger Besu.
@rain-on Thank you . Yes i think you are right. I was also thinking the same. But i asked this question to Hyperledger Besu guys first. They said yes and they referred me to here for more details. May be they thought i was asking multisignature address transaction. Anyways, do you know any other Blockchain platform that supports what i looking for?
@juharahmed I suspect the Besu response meant - "Ethsigner can manage multiple keys (but only use one per transaction, based on the "from" field) - unfortunately I don't know of a multi-sig blockchain platform - but suspect you could implement something like this in a smart-contract (unfortunately, that is where my expertise comes to an end).
Hi everyone, I added an article for integration Ethsigner, Infura and Hashicorp Vault for those interested and having troubles with it. https://medium.com/@corgi.desu/a-study-on-blockchain-key-management-systems-part-2-hashicorp-vault-ec11013cd765
@arash009 it's just
eth_signTypedData indeed. We're defining a process for EIP-1812 (Verifiable Claims) that heavily relies on an EIP-172 implementation, for a private network (LACChain). Last night a gave it a try at diega/ethsigner@7986cbe. I didn't want to make any refactor like renaming the TransactionSignerProvider to something more general, but most of the functionality I think it's there. It's just for eth_sign but it's a beginning. It needs a lot of testing though
@diega Just had a flick through your branch, and am impressed at how little you had to touch to make it work. I think you're right, there's some testing required to back it up, but otherwise the change looks simple enough to be put up as a PR (if you're happy to have this in the core code base).
Only comment from my initial read is that we use "final" everywhere, variables, function parameters - so I'd recommend adding where possible (otherwise I suspect it'll be the one of the first comments!). Lovely work :thumbsup:
Only comment from my initial read is that we use "final" everywhere, variables, function parameters - so I'd recommend adding where possible (otherwise I suspect it'll be the one of the first comments!). Lovely work :thumbsup:
@diega @sprect8 We'll wait for your PRs to come in, but it's worth saying/warning that Ethsigner is probably going to be split into two more explicit halves:
- Http Handling and Ethereum-oriented functions
- Keyloading and management
The goal of this, is to allow the signing engine to be reused more effectively in other applications (and TransactionSigner will probably be changed to Signer, or something similarly generic)
These changes won't be ready until after your PRs have gone through, so should not affect what you're currently doing.
@rain-on no worries, thanks for the advice. I just sent PegaSysEng/ethsigner#263 but there is a failure running the acceptance tests that seems unrelated to what I made
GPG error: https://cli-assets.heroku.com/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5DC22404A6F9F1CAlet me know if I miss something for this or you'll like some changes to the code
here is the output of the failure if you want to take a look https://app.circleci.com/pipelines/github/PegaSysEng/ethsigner/598/workflows/0b2c82c0-dda6-45a7-a64b-c70c4d779324/jobs/1972/parallel-runs/0/steps/0-104
Once we merge it, all you need to do is rebase your PR and it should be good to go :+1:
(assuming my fix works…) :)