The time has come. Grid 3 mainnet is live and we are encouraging DIY farmers to migrate their nodes. This thread is for logging the latest updates on the migration process and known issues with booting nodes on Grid 3.
For instructions on how to start farming on Grid 3, see the farming section of the manual.
Certified Titans will need a special process to join Grid 3. Non certified Titans can be migrated, but we encourage you to wait for an official process and instructions
We did not plan to start logging the token price for farmers’ v3 minting until the new minting was actually activated. That means you shouldn’t stress about timing your migration to Grid 3
For certified nodes, the lock in price will be the token price when you bought your node, as previously promised. For DIY nodes, we are discussing an “early adopter” rate for all nodes registered in the month of January. Nothing is set in stone, and we welcome your input on the forum: Farming Reward Calculation
The Grid 3 mainnet explorer is not reporting whether nodes are online or offline correctly. For now, your best bet is to connect a screen and check the node console. Look for IP addresses in the network section. If they show “not configured”, please wait at least 10 minutes and then contact support
Update - January 7: a new version of the explorer has been deployed and most nodes appear to be displayed correctly now. Our dev and ops team will continue working on this.
Failed to get node twin
If your node shows “failed to get node twin” after booting, it probably just needs more time to register itself on TF Chain. One farmer reported this issue resolved after enabling IPv6 in their network.
Please wait ten minutes and then contact support if the issue persists.
Hardware not detected/utilized
Some nodes that were working on Grid 2 are not utilizing their disks on Grid 3. Other nodes are not reporting their system resources correctly. If your node shows this behavior, please contact support.
Update - January 10: The ping check has been replaced with a check that Zos can download a website. This may take some time to be deployed to mainnet
During boot, Zos attempts to ping Google to check internet connectivity. If the ping fails, booting halts even if the node is online. Try pinging the same site from another computer in your network. Issues at your ISP can interfere with pings, and some block them altogether.
The “limited cache” message either means that the node has no SSD or is not utilizing the installed SSD. If your node has SSD, try wiping the disk. Nodes without cache are not able to function on Grid 3.
On some systems, it may be necessary to update your BIOS to successfully migrate from Grid 2 to Grid 3. If your node crashes while booting Grid 3 or has other issues, updating the BIOS may resolve this issue.