We've implemented a fix to address the IP address exposure issue following the XDC 2.0 upgrade. It’s important for all node operators to fetch the latest changes from Git to ensure your node remains secure.
Thank you for your prompt response and for addressing the IP address exposure issue. I have successfully updated my node following the instructions provided.
Additionally, I noticed that the issue with the line "./start-node.sh:/work/start-node.sh" in the docker-compose.yml file has now been correctly changed to "./start-node.sh:/work/start.sh". I was planning to report this today, but I’m glad to see that it has already been fixed.
I truly appreciate the quick action taken by the team.
Best regards,
11ppm
For further actions, you may consider blocking this person and/or reporting abuse
Hello,
The development team is aware of the issue, and we're confident it will be resolved in the next few hours.
Hello,
We've implemented a fix to address the IP address exposure issue following the XDC 2.0 upgrade. It’s important for all node operators to fetch the latest changes from Git to ensure your node remains secure.
Run the following command to update:
bash mainnet/upgrade.sh
Dear Anil and the XDC Team,
Thank you for your prompt response and for addressing the IP address exposure issue. I have successfully updated my node following the instructions provided.
Additionally, I noticed that the issue with the line
"./start-node.sh:/work/start-node.sh"in thedocker-compose.ymlfile has now been correctly changed to"./start-node.sh:/work/start.sh". I was planning to report this today, but I’m glad to see that it has already been fixed.I truly appreciate the quick action taken by the team.
Best regards,
11ppm