Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support eth_signTransaction #129

Closed
schmidsi opened this issue Feb 11, 2019 · 7 comments
Closed

Support eth_signTransaction #129

schmidsi opened this issue Feb 11, 2019 · 7 comments
Labels
enhancement New feature or request

Comments

@schmidsi
Copy link
Contributor

When I try to sign a transaction, I get the following error:

Error: Returned error: Method eth_signTransaction not supported.

I assume that this error comes from ganache: The eth_signTransaction method gets forwarded to the underlying node because it is not marked as protectedMethods.

We use this kind of special setup where we separated the signTransaction from the actual send transaction to have more control over the different configurations (especially our in-memory signing).

@schmidsi
Copy link
Contributor Author

Seems like MetaMask does not support this either: MetaMask/metamask-extension#2506

And it is not part of this reference: https://github.com/ethereum/wiki/wiki/JSON-RPC#json-rpc-api-reference

@KPrasch
Copy link

KPrasch commented Sep 12, 2020

Howdy! Thanks for all your wonderful and stylish work on Frame! 🤠

We use this kind of special setup where we separated the signTransaction from the actual send transaction to have more control over the different configurations (especially our in-memory signing).

This issue is also effecting me for the same reason.

While there are lots of similarities, there are some important differences between Frame and MetaMask - most notably frame perform the duty of account management, signing transactions, and runs as a stand-alone OS-level application. 👍

While I do benefit from the convenience of frame also broadcasting my transaction to infura or another web3 endpoint - The main functionality I need from a standalone signer is transaction signing.

Under the hood Frame is a Clef-based signer -- I''d like to be able to take advantage of those aspects of the architecture and have the basic functionality of signing transactions without broadcasting them. I think this can be achieved by exposing clef's account_signTransaction an internal transaction signing endpoint, but I'm interested in what others think.

KPrasch added a commit to KPrasch/nucypher that referenced this issue Sep 12, 2020
@floating
Copy link
Owner

Hey @KPrasch, thanks for the feedback! We can look into this again. Frame is not Clef based and follows a different flow but we could still support this method and add UX to make it clear that it's not the standard transaction signing flow.

@KPrasch
Copy link

KPrasch commented Sep 13, 2020

@floating - Thanks for looking into it!

My mistake about being a clef signer - I believe they have you listed on their Github Readme as an implementation (perhaps outdated): https://github.com/ethereum/go-ethereum/tree/master/cmd/clef#ui-implementations

@floating floating added this to the v0.4.0 milestone Sep 24, 2020
@floating floating removed this from the v0.4.0 milestone Dec 17, 2020
@CucurbitBaby
Copy link

Is "web3.eth.signTransaction" useless ?

@CucurbitBaby
Copy link

"web3.eth.accounts.signTransaction" is ok! oh shit

@goosewobbler goosewobbler added the enhancement New feature or request label Aug 17, 2022
Repository owner locked and limited conversation to collaborators Dec 6, 2022
@goosewobbler goosewobbler converted this issue into discussion #1239 Dec 6, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants