You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| -n, --fork-network-name [NAME]| Name of the network to fork; optional. By default, it starts a new chain from genesis block. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet") |
40
+
| -n, --fork-network-name [NAME]| Name of the network to fork; optional. By default, it starts a new chain from genesis block. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet") |
41
41
| -b, --fork-block-num [number]| Block number to fork at. By default, it's the latest block. |
42
42
| -r, --reset-on-change | Resets the entire local blockchain when any code is changed; for forked mode, it resets back to forked block number; NOT DEFAULT. |
43
43
| --only-smart-contracts | Deploys only smart contracts (having started local test chain) and updates Smart contract configs for frontend; does not start frontend dev environment. |
| -n, --network-name | Name of the network to deploy smart contracts to. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet") |
69
+
| -n, --network-name | Name of the network to deploy smart contracts to. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet") |
70
70
| --only-smart-contracts | Deploys only smart contracts and updates Smart contracts config for frontend. |
71
71
| --only-frontend | Deploys only frontend; smart contracts data is read from Smart contracts config which must pre-exist. To generate these manually, use generate smart-contracts-config |
| -e, --environment <ENV> | Environment where this config would be used (choices: "development", "production", default: "development") |
117
-
| -n, --network-name | Name of the network to generate config for. (choices: "ethereum", "goerli", "polygonPos", "polygonMumbai", "polygonZkevm", "polygonZkevmTestnet") |
117
+
| -n, --network-name | Name of the network to generate config for. (choices: "ethereum", "goerli", "polygonPos", "polygonAmoy", "polygonZkevm", "polygonZkevmTestnet") |
Copy file name to clipboardExpand all lines: docs/tools/dApp-development/launchpad/common-pitfalls.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,22 @@
2
2
comments: true
3
3
---
4
4
5
-
## MetaMask transactions fail with a nonce error in dev environment
5
+
###MetaMask transactions fail with a nonce error in dev environment
6
6
7
7
Every time the dev environment starts, a new local test chain is started. Metamask maintains a cache of "latest block number" and "account transaction nonce". Since every run of `dev` creates a new chain, it never matches with this cache.
8
8
9
9
To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
10
10
11
-
## MetaMask transactions fail with a nonce error when using the **reset on change** option in dev environment
11
+
###MetaMask transactions fail with a nonce error when using the **reset on change** option in dev environment
12
12
13
13
The reset on change option resets the blockchain on every code change.
14
14
15
15
MetaMask maintains a cache of *latest block number* and *account transaction nonce*. After resetting the chain, the latest block number and account transaction nonce should go back to the initial state as well, but MetaMask does not update this cache on its own.
16
16
17
17
To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
18
+
19
+
### Error: could not coalesce error (error={ "code": -32603, "message": "Internal JSON-RPC error." })
20
+
21
+
Clear your wallet cache and try again.
22
+
23
+
To clear the cache, follow the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015488891-How-to-clear-your-account-activity-reset-account).
0 commit comments