Replies: 1 comment 3 replies
-
I would recommend using ethers.js for offline transactions, there you can prepare your transactions, sign them offline as long as you have the private key, and send it later. Do not forget to change the chainId accordingly. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a backend service that encodes and signs transactions and then sends them to the chain. This service works well when I need to submit the transactions to the same chain at all times.
I have a requirement now where I want to be able to use the same backend service but the transactions only needs to be encoded and signed. The problem, however, is that the transaction is to be submitted to another chain which is an Ethereum fork.
Is it possible to do this in web3js where the same service connected to one chain (itself an Ethereum fork) but the tx is encoded and signed (but not submitted) for a different chain without having to connect to the different chain's node?
Beta Was this translation helpful? Give feedback.
All reactions