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
Comments
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 |
Howdy! Thanks for all your wonderful and stylish work on Frame! 🤠
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.
|
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. |
@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 |
Is "web3.eth.signTransaction" useless ? |
"web3.eth.accounts.signTransaction" is ok! oh shit |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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 asprotectedMethods
.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).
The text was updated successfully, but these errors were encountered: