Skip to content
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

[New chain]: Cronos zkEVM Testnet #1287

Closed
ElvisKrop opened this issue Aug 21, 2024 · 7 comments · Fixed by #1293
Closed

[New chain]: Cronos zkEVM Testnet #1287

ElvisKrop opened this issue Aug 21, 2024 · 7 comments · Fixed by #1293

Comments

@ElvisKrop
Copy link
Contributor

Summary

Chain ID

282

Chain detail URL

https://chainlist.org/chain/282

RPC URL

https://testnet.zkevm.cronos.org

Blockscout Client URL

No response

Etherscan Client URL

No response

Etherscan Client API URL

No response

Version

1.3.0

Address (Master copy)

0xB00ce5CCcdEf57e539ddcEd01DF43a13855d9910

Deployment Tx hash (Master copy)

0xb289acc00b404156e69a56691f486a409c6c531131c6a53fb748a218aed92255

Block explorer URL (Master copy)

No response

Address (Master copy L2)

0x1727c2c531cf966f902E5927b98490fDFb3b2b70

Deployment Tx hash (Master copy L2)

0x5e4d062b1d443f2699530dd1970c875922f9bc73893665559f575111da86fea8

Block explorer URL (Master copy L2)

No response

Address (Proxy factory)

0xDAec33641865E4651fB43181C6DB6f7232Ee91c2

Deployment Tx hash (Proxy factory)

0x909ed7d6527bc36343429afb8914a55014d32ad30438ae922a757f958a201e42

Block explorer URL (Proxy factory)

No response

Copy link
Contributor

Validation has failed with the following errors:

  • Master copy address 0xB00ce5CCcdEf57e539ddcEd01DF43a13855d9910 is not valid for version 1.3.0
  • Master copy address 0x1727c2c531cf966f902E5927b98490fDFb3b2b70 is not valid for version 1.3.0+L2
  • Proxy address 0xDAec33641865E4651fB43181C6DB6f7232Ee91c2 is not valid for version 1.3.0
  • Master copy address obtained from Tx is diferent than provided 0xB9D37a6040F8C3BD191248818e926a0e4F51764b
  • Master copy L2 address obtained from Tx is diferent than provided 0xC16b400D746e01f94dc9B06B166FF16F8b60cCbD
  • Proxy factory address obtained from Tx is diferent than provided 0xab968705A5Eca95a76Ec618eF33fE6D11846A2AD

Validation failed!❌

@ElvisKrop
Copy link
Contributor Author

Hello @falvaradorodriguez 👋
This network is based on zkSync and it seems the github action doesn't take into account such case. Could you advice ho to proceed better?

@falvaradorodriguez
Copy link
Contributor

Hi @ElvisKrop ,

Yes, we are aware of this and we have to update it to support these cases. In the meantime, please can you indicate me in a comment the block number in which each deployment (Master copies and Proxy Factory) was made?

With that, we will take care of doing the PR.

Thanks

@ElvisKrop
Copy link
Contributor Author

ElvisKrop commented Aug 22, 2024

Thank you 🙏

  • Master copy L1 - 163814
  • Master copy L2 - 163812
  • Proxy Factory - 163805

@falvaradorodriguez
Copy link
Contributor

/execute

Copy link
Contributor

🚀 Starting to apply the changes for the new address!

Copy link
Contributor

✅ Execution finished, please review the PR and merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants