Skip to content
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

Sign transactions for other chainIds using Geth local keystore files #29352

Closed
mvcastellari opened this issue Mar 26, 2024 · 2 comments
Closed

Comments

@mvcastellari
Copy link

We have a running Geth node on main network, with chainId = 1 and we would like to use this node as well to sign (just sign) transactions using the same keystore but for another chainIds (Polygon (0x89) in this case). What is the best way to achieve this?

I've tried calling the method "personal_signTransaction" with the custom parameter "chainId" but it gives me the error: "chainId does not match node's (have=137, want=1)".

Any helps will be appreciated.

@jyap808
Copy link
Contributor

jyap808 commented Mar 26, 2024

Copy the keystore files over to your Polygon node with ChainID 137.

Or use a SDK library and code up the solution.

@MariusVanDerWijden
Copy link
Member

Yep, its a security measure that you can not sign transactions for other chainids from your node. I don't think we should allow for this use case, copying the keystore to your polygon node or coding a solution is your best bet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants