Open haerker opened 6 months ago
Possible Reasons Why Things Aren't Working
Your Blockchain Setup Needs Tweaking:
Homemade Blockchain: If your blockchain isn't the standard Ethereum kind, double-check that it has all the 'parts' that Ethereum expects (especially something called "sealFields"). Official Test Network: If you're using a standard setup like Sepolia, make sure your code is using the right settings for that particular network. Software Issues:
Out-of-sync Tools: Make sure your 'ethers.js' library (and 'zksync-ethers') plays nicely with your blockchain setup. Look for newer versions that might work better. Handle Unexpected Data: If you can edit your code, consider adding bits to deal with weird "sealFields", just in case that's the problem.
great ......
somewhat took me some time to understand but Great :)
udpaded my library too. now some problems are solved
When I run the example of L1 and L2 communication provided on the official website, the contracts are successfully deployed to both L1 and L2. However, when I call increment-counter.ts,
yarn ts-node ./scripts/increment-counter.ts
I encounter errors of incorrect types.When I set up my local private chain with Buse as L1, the following error occurs:
When my L1 is provided by sepolia on the official website, the following error occurs: