Back to collectionOperator update makes reward eligibility depend on software compatibility
Xai released operator version 1.2.0 for desktop and CLI and labelled the update mandatory. The notice warned that incompatible operators would stop receiving rewards. It included a fix for the MacOS client being blocked or flagged and prepared operators for future contract changes intended to enable Sentry Key airdrops. Those contract changes had no announced release date; the team said it would provide at least 7 days notice when a date was set. Software readiness and delivery of an airdrop were therefore separate milestones.
Xai released operator version 1.2.0 for desktop and CLI and labelled the update mandatory. The notice warned that incompatible operators would stop receiving rewards. It included a fix for the MacOS client being blocked or flagged and prepared operators for future contract changes intended to enable Sentry Key airdrops. Those contract changes had no announced release date; the team said it would provide at least 7 days notice when a date was set. Software readiness and delivery of an airdrop were therefore separate milestones.
The release also distinguished deployment paths: Windows desktop users were told the update would be automatic, while Mac, Linux and CLI users needed new builds; CLI operators also had to rerun boot-operator. For holders, this added a concrete operating dependency to expected reward income. The release made maintenance part of the income model: version compatibility and successful reward collection must be monitored alongside machine uptime. A future distribution announcement does not eliminate those recurring operating requirements.