io.net device monitor: GPU details and block rewards
GPU details and block rewards
Plain text versionUse the official Device ID and connect an IO Explorer access token. Never use a wallet private key.
Verify the public identifier in the official dashboard, then look it up on the project page. To follow it regularly, add a device in Devices and link the project. A device name organizes your list; it does not prove that identifiers from different projects belong to one physical machine.
Queries hardware and UTC-day block rewards. Block rewards do not include all rental income. Historical uptime and jobs do not prove current connectivity. Reconnect when the token expires.
If a lookup has no data, check the identifier type and spelling, then compare coverage with the official dashboard. A failed request or stale data means neither zero earnings nor an offline device. This monitor cannot start jobs, change your official account, or guarantee work.
Common questions
Which public identifier should I use?
Use the official Device ID and connect an IO Explorer access token. Never use a wallet private key.
What do these figures measure?
Queries hardware and UTC-day block rewards. Block rewards do not include all rental income. Historical uptime and jobs do not prove current connectivity. Reconnect when the token expires.