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
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
All smart contracts on both the childchain and the rootchain must be verified for the transparency of our users. Please make sure to deploy flattened smart contract files with constructor arguments on both chains in a way that we can validate them on the block explorer of both chains. Additionally, please provide the deployed sol contract file at addresses 0x0000000000000000000000000000000000000101,0x0000000000000000000000000000000000000102,0x0000000000000000000000000000000000000103,0x0000000000000000000000000000000000001001,0x0000000000000000000000000000000000001002,0x0000000000000000000000000000000000001003,0x0000000000000000000000000000000000001004,0x0000000000000000000000000000000000001010. Thank you.
Your environment
OS and version.
The version of the Polygon Edge.
(Confirm the version of your Polygon edge client by running the following command: polygon-edge version --grpc-address GRPC_ADDRESS)
The branch that causes this issue.
Locally or Cloud hosted (which provider).
Please confirm if the validators are running under containerized environment (K8s, Docker, etc.).
Steps to reproduce
Tell us how to reproduce this issue.
Where the issue is, if you know.
Which commands triggered the issue, if any.
Provide us with the content of your genesis file.
Provide us with commands that you used to start your validators.
Provide us with the peer list of each of your validators by running the following command: polygon-edge peers list --grpc-address GRPC_ADDRESS.
Is the chain producing blocks and serving customers atm?
Expected behavior
Tell us what should happen.
Tell us what happened instead.
Logs
Provide us with debug logs from all of your validators by setting logging to debug output with: server --log-level debug
Proposed solution
If you have an idea on how to fix this issue, please write it down here, so we can begin discussing it
Please provide source of flattened smart contract files and constractors.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[ Subject of the issue ]
Description
All smart contracts on both the childchain and the rootchain must be verified for the transparency of our users. Please make sure to deploy flattened smart contract files with constructor arguments on both chains in a way that we can validate them on the block explorer of both chains. Additionally, please provide the deployed sol contract file at addresses 0x0000000000000000000000000000000000000101,0x0000000000000000000000000000000000000102,0x0000000000000000000000000000000000000103,0x0000000000000000000000000000000000001001,0x0000000000000000000000000000000000001002,0x0000000000000000000000000000000000001003,0x0000000000000000000000000000000000001004,0x0000000000000000000000000000000000001010. Thank you.
Your environment
(Confirm the version of your Polygon edge client by running the following command:
polygon-edge version --grpc-address GRPC_ADDRESS
)Steps to reproduce
polygon-edge peers list --grpc-address GRPC_ADDRESS
.Expected behavior
Logs
Provide us with debug logs from all of your validators by setting logging to
debug
output with:server --log-level debug
Proposed solution
If you have an idea on how to fix this issue, please write it down here, so we can begin discussing it
Please provide source of flattened smart contract files and constractors.
The text was updated successfully, but these errors were encountered: