[ZK Stack] - Errors with zkstack ecosystem init on Sepolia #914
Replies: 3 comments 5 replies
-
|
Try Alchemy free tier as well? |
Beta Was this translation helpful? Give feedback.
-
|
It is not recommended to use public rpcs given the amount of requests so your intuition to use infura and the suggestion above for alchemy as well is correct. To resolve the error of |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for taking a look @bogatyy and @dutterbutter! Alchemy so far doesn't complain about too many requests and I think the single address trick for testing is neat. Now when running |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the trouble friend. Can you try make using of a different account and re-try. I would be happy to send some testnet ETH if the would be helpful, just provide the address. Also if you want to simplify things just to try out zkstack - running locally is also available. The issue is that there is a slight race if you submit multiple transactions currently. Transaction N enters the pool but will be marked as executable a bit later (hundreds of millisecs I think), in which time N+1 might be rejected as described in ethereum/go-ethereum#26890. That being said we will look into preventing this for future users as it seems to happen intermittently during deployment of L1 contracts from |
Beta Was this translation helpful? Give feedback.
-
|
Hey @dutterbutter no worries at all and thanks so much for debugging with me! I tried
Since I can't easily create a new alchemy account (need to go through phone number verification) and can't easily delete my current alchemy account (looks like only support can do that), are there alternative ways of dealing with the error other than paying for alchemy/infura accounts? |
Beta Was this translation helpful? Give feedback.
-
|
You don't need to change the rpc but rather the funded ethereum address in the wallets.yaml files. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding "future transaction tries to replace pending", check this thread. You cannot deploy with infura free RPC. You need to upgrade your plan. If you plan to use other rpc providers like Alchemy or chainlink, most probably you will encounter this error "initcode too large". |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dutterbutter and @sachanayush47, thanks for taking a look. I did change RPCs along with the wallet addresses and did fund the necessary accounts. After some experimentation what I found to be working reliably was to get a paid account (infura in my case) and if running first |
Beta Was this translation helpful? Give feedback.
-
Team or Project
No response
Module Affected
Rust Version
1.82.0
Operating System
Issue Description
Hello! I'm trying to deploy on Sepolia with
zkstack ecosystem init --l1-rpc-url=[RPC_URL]but getting numerous errors depending on RPC chosen. Tried all on RPCs from https://sepolia.dev/ and failed. Then created account on https://www.infura.io/ and tried with my key https://sepolia.infura.io/v3/[API_KEY] and also failed.Expected Behavior
Successful deployment
Current Behavior
Just going to copy a couple of examples here
Example 1
Example 2: error despite moving > 5 Sepolia ETH to the address
Example 3: too many requests error
For which I'm getting too many requests error
│ your allowed throughput limit. Reduce the amount of requests per second or upgrade for more capacity."}}
Repository Link (if applicable)
No response
Additional Details
No response
Prior Research
Beta Was this translation helpful? Give feedback.
All reactions