-
Notifications
You must be signed in to change notification settings - Fork 227
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
The code hash is not known #304
Comments
I can find PoolAddressProvider on zksync era explorer: https://goerli.explorer.zksync.io/address/0x0291BFc54EE9048D97Ea88be1230751865121fE1, it's deployed so I dont know why this error is raised |
Full error:
|
My zksolc setting is:
|
hi @ly0va would you be able to help? looking forward to the zksync deployment |
Hi! I'm currently struggling with the same error. Maybe you have success, how to fix it? I just found is that there is a _ensureBytecodeIsKnown function in the contractDeployer.sol (zksync system contracts) that causes "The code hash is not known". But now I can't figure out what this check is for... |
Can you confirm the libraries defined in the hardhat config file are deployed to zkSync as well and that the addresses are correct? |
Hey! Based on the error message you are getting, it seems that this issue is not connected to the hardhat plugins. Instead, the execution is reverted from the system contract deployer. |
I checked they are definitely deployed to zksync, the addresses should be correct |
@mpopovac-txfusion hi, thanks for the hints and I tried it on my branch, now I get a very different error: now the issue is:
and call it before call |
Are you sure you are getting a good signer here? Because based on the error it seems that you are missing some methods. |
hi @mpopovac-txfusion I dont think it's a signer issue here because similar deployment script I can successfully deploy to goerli The main issue is more:
The error message is very verbose and containing no information |
The reason I asked for the signer is because |
hi @mpopovac-txfusion yesterday I tried your advice, though it's still not working. I'm facing huge issue as the rpc server will not give any error message. basically I dont know what to fix, and I dont know what I'm doing right or wrong....this is really annoying would zksync devs be able to sync with me? my tg handle is: https://t.me/alexcj96 |
@GopherJ please share the error you're getting now and the specific script/line that is failing. Also, have you tried running this using the local-setup? |
@uF4No @mpopovac-txfusion I managed to return back to this topic and made some progress. Now in ParaSpace we can successfully deploy to step 11, if this step succeed then it's mostly done, the rest of deployment step is optional. The way I debug is to launch
Now I'm failing on initReserves call, here the trace: here the js call The bytecode hash asking is: but in artifacts-zk there is no bytecode with such hash |
I looped over all our contracts but didn't find any bytecode with such hash |
I think this can be closed as long as we put correct factoryDeps |
trying to deploy https://app.para.space to zksync (goerli), I work on this PR: parallel-finance/paraspace-core#393. Although most of the contracts work, I do get some strange error like:
while calling
PoolAddressProvider#updatePoolImpl
: https://github.com/para-space/paraspace-core/blob/c0931e1a35d6ba4c6c978ee14fca2e42cab6be86/contracts/protocol/configuration/PoolAddressesProvider.sol#L105-L113The text was updated successfully, but these errors were encountered: