Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Trent Mohay
    @rain-on
    @ccolorado Besu is not a hard dependency - ethsigner should work in front of any web3 provider (eg geth, parity; though isn't actively tested), having said that I'm partial to Besu (given I'm a maintainer) :)
    @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?
    Zain
    @sprect8
    @rain-on thanks! I will raise a PR
    Arvs Indrarys
    @ArvsIndrarys
    Hi all!
    Is there a way to sign blocks of hyperledger besu using EthSigner?
    Like instead of giving it a key file, rather make him call EthSigner
    ccolorado
    @ccolorado
    @rain-on thanks
    Arash
    @arash009
    @ArvsIndrarys no unfortunately not. The restriction is more in Besu rather than Ethsigner. Is the concern the security of the node key stored in Besu?
    Arvs Indrarys
    @ArvsIndrarys
    @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 :
    • 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?
    Trent Mohay
    @rain-on
    @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.
    Arvs Indrarys
    @ArvsIndrarys
    @rain-on thanks !
    juharahmed
    @juharahmed
    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.
    Trent Mohay
    @rain-on
    @juharahmed Unless I'm much mistaken, an Ethereum Transaction can only be signed by a single private key - i.e. the unsigned transction contains a "from" field which contains a single address, and the derived RawTransaction contains only a single signature (not a multi-sig).
    juharahmed
    @juharahmed
    @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?
    Trent Mohay
    @rain-on
    @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).
    Zain
    @sprect8
    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
    Trent Mohay
    @rain-on
    Hey @sprect8, 2 things:
    1. Loving your work :)
    2. Sorry for not getting onto your PR - its on the radar, but we're a bit swamped :(
    Zain
    @sprect8

    @rain-on just glad I can contribute to the great work you're doing and to help the community a bit; sometimes starting out can be daunting

    no worries on the PR, take your time. better to do things right than to rush it

    Diego López León
    @diega
    Hello there, is there any plan to support EIP-712 eth_signTypedData? Do you think there is room for collaboration there? (or maybe the plain to begin eth_sign)
    Arash
    @arash009
    Hi @diega . Yes we are currently in the process of defining some additional functionality around ethsigner and signing in general. Whats the specific context you re looking to support? Just the eth_sign and eth_signTypedData?
    Diego López León
    @diega
    @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
    Diego López León
    @diega
    @arash009 do you think my changes are well oriented? does it worth I continue that work so I can make a pull request?
    Arash
    @arash009
    Let us have a look and we'll let you know shortly.
    Trent Mohay
    @rain-on
    @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:
    Diego López León
    @diega
    Excellent! I'll add testing and such and send a PR then. Thanks for your feedback!
    Trent Mohay
    @rain-on
    @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:
    1. Http Handling and Ethereum-oriented functions
    2. 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.
    Diego López León
    @diega

    @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 5DC22404A6F9F1CA

    let me know if I miss something for this or you'll like some changes to the code

    Diego López León
    @diega
    I tried rebuilding the pipeline many times with push force but it fails everytime the acceptance tests at the "Install Packages - Java 11" step. Aren't you experiencing the same in some other CI environment?
    Lucas Saldanha
    @lucassaldanha
    Hi @diega This doesn’t seem to be related to your changes. I’ll follow up with the team and get back to you!
    Diego López León
    @diega
    Thanks @lucassaldanha! maybe a quick check can be running the pipeline for master directly in CircleCI, it should fail the same way. I'll rebase the PR if anything new goes into master
    Lucas Saldanha
    @lucassaldanha
    We have experienced this similar issue in other projects. So I believe we need the same fix here :)
    Diego López León
    @diega
    oh, cool, I'll keep tuned :)
    Lucas Saldanha
    @lucassaldanha
    I have put up a fix on PegaSysEng/ethsigner#265
    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…) :)
    Diego López León
    @diega
    Excellent, I just rebased and everything passes :) I also fixed some missing finals from a review
    Diego López León
    @diega
    Thank you for merging my PR! I'll move forward to implement eth_signTypedData
    Oussama Chaabouni
    @oussamachaabouni
    hello . i am trying to start ethsigner after creating the password file and the key file ... but he sait that file password is not found althought i am sure that the path is true , it s in the same path of the key file
    that s my error
    2020-05-31 17:53:19.655+02:00 | main | INFO | SignerSubCommand | Version = ethsigner/v0.6.1-dev-82352575/linux-x86_64/oracle-java-13
    2020-05-31 17:53:19.669+02:00 | main | ERROR | FileBasedSignerFactory | File not found: /config/password
    Failed to construct a signer from supplied arguments.
    Cause: File not found: /config/passwor
    d
    Oussama Chaabouni
    @oussamachaabouni
    now he gace me this error
    020-05-31 18:48:22.623+02:00 | main | INFO | SignerSubCommand | Version = ethsigner/v0.6.1-dev-82352575/linux-x86_64/oracle-java-13
    2020-05-31 18:48:23.515+02:00 | vert.x-eventloop-thread-2 | ERROR | HttpServerService | HTTP server service failed to listen
    java.net.BindException: Adresse déjà utilisée
    Oussama Chaabouni
    @oussamachaabouni
    can someone please explain to me how to use ethsigner ... i juste want to interact with my contract via a script node js .. trying to execute a function of my contract vi eth.send ... but he said to me that i must use sendRawTransaction .... i am using Besu on localhost:8545
    Trent Mohay
    @rain-on
    Hi @oussamachaabouni, from the initial log, it looks like the /config/password file is indeed missing - can I ask you to rerun ethsigner, but with "-l trace" in the command line? That will provide much more information regarding the issue.
    With regard your second issue - I'm suspecting that the port you've requested (defaults to 8545) is already in use, and the HTTP server is unavailable. Have you set the --http-listen-port on the EthSigner commandline?
    Oussama Chaabouni
    @oussamachaabouni
    thank you , your answer help me to understand my problem . actualy i am just trying to interact with my contract , i want to call a set function to add some infomation in my contract ; i am using web3.js library
    Trent Mohay
    @rain-on
    If you ensure that the ethsigner port is free - does it now work? If need be - you can set "--http-listen-port=0", then a file called ethsigner.ports will be created, and will show which free ports were selected by EthSigner for listening on.
    Manuel Montenegro
    @manumonti

    Hi! I have a problem that I'm unable to resolve... I'm trying to connect Remix (Web3 provider) to EthSigner, because I'm working with a permissioned Besu network. In order to get that, I'm running EthSigner on a Docker container. I know that EthSigner - Besu node connection is working properly, because if I run this command, I can get this result:

    curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":51}' http://192.168.43.125:9101

    {
    "jsonrpc" : "2.0",
    "id" : 51,
    "result" : "0xfe89"
    }

    But if I try to connect with Remix (Web3 provider), I get this error from Remix pop-up: Cannot get account list: Error: Invalid JSON RPC response: ""

    And if I open the firefox console, i get this: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.43.125:9101/. (Reason: CORS header 'Access-Control-Allow-Origin' missing)

    I'm using http version of Remix, so I don't know what is the problem. What can I do? Maybe EthSigner isn't compatible with Remix Web3 Provider? Any ideas?

    Manuel Montenegro
    @manumonti
    Update: I installed firefox add-on: "Allow CORS: Access-Control-Allow-Origin" and it's working now. But I think EthSigner should have any option for setting up this
    3 replies
    Lucas Saldanha
    @lucassaldanha
    This message was deleted
    2 replies