$PI Dear Pi Pioneers, here is a unified explanation regarding the inability of some nodes to fully light up all three green checkmarks after upgrading to Pi Node version 0.6.1: 👇

Root cause: This new version restructures the consensus container. After a Docker backend restart, the Ports-Checker port detection component will briefly report an unknown status. This is not a node malfunction but a transitional adaptation period following the version iteration. As long as the backend shows Consensus container: running and the block status Synced!, the node is still participating normally in consensus operations — no need to worry excessively. Troubleshooting steps:
First, restart the Pi-Node client; check router port forwarding and ensure Windows Firewall allows the corresponding Pi ports; let it sit for 3-8 hours, allowing the component to complete the adaptation — the green checkmarks for the vast majority of Pioneers will automatically recover. Long-term core advantages of version 0.6.1:
Optimizes consensus operation logic, improves the synchronization stability of nodes across the entire network, and upgrades the protocol to the latest version; strengthens node network interoperability. After the port adaptation is complete, the number of inbound connections increases, and the weight of the node in the distributed network rises. In conjunction with the officially launched App-Studio backend persistent storage feature, high-quality node clusters provide computing power support for the data storage of ecosystem DApps. The iterative improvement of the underlying infrastructure is the foundation for Pi's long-term development — do not be disturbed by short-term adaptation issues or market fluctuations. 👨🏻‍🏫