Igra Network Community

I want to share my honest experience running an Igra full node and attester. I have spent a lot of time setting up the node, five RPC workers, five kaswallets, Traefik routing, Docker auto-start, and Windows recovery after a reboot. The attester was eventually running correctly, all five wallets were processing transactions, rewards were increasing, and there were no slashes. However, after a power-loss reboot, kaspad, Traefik, and the attester did not all restart properly. The dashboard continued to show my attester as Active, but the local infrastructure was not fully operational. I did not know there was a problem until I checked manually, and another missed-attestation penalty of approximately 34.7 IGRA was added. My total penalties are now 312.68 IGRA, even though I have made a serious effort to follow the documentation and keep the system running properly. Earlier in the setup process, I also lost approximately 40 KAS because placeholder return addresses were still present. There was also confusion over whether only wallet 0 should be funded or whether all five wallets should be used through Traefik. My main frustration is that the dashboard can show “Active” even when kaspad, Traefik, Docker, or the attester is not actually functioning. There is no obvious built-in alert warning the operator that attestations have stopped, yet penalties can still be challenged and applied. I believe attester operators need: One official and fully tested auto-recovery/startup procedure. Dependency checks so the attester does not start until kaspad, Traefik, and the RPC workers are healthy. An official alert when an Active attester stops submitting. Clearer documentation about single-worker versus five-worker configurations. Strong warnings about placeholder wallet return addresses. Clear instructions for pausing safely before maintenance or power-down. I support what Igra is building, but the current operator experience has been stressful and expensive. I am now considering pausing or exiting my attester because I do not want to continue receiving penalties for failures I cannot immediately see. I hope the team can improve the monitoring, documentation, and recovery tools for regular node operators. Also, My attester was registered recently, but the dashboard shows only 1 month 11 days remaining on a stated six-month lock. What exact date or event started my lock period, and what steps and cooldown apply when it reaches zero?