A Golem node id is not the same field as the GLM wallet
Copy the node id from Golem Stats first. The receiving wallet only says where GLM should arrive. It does not replace the node record.
| What you hold | What install calls it | How the monitor uses it |
|---|---|---|
| Node id | Provider id on Stats; status also shows a node name | Must be 0x plus 40 hex characters, and it opens this record |
| Receiving address | YA_ACCOUNT, shown as Wallet in status | Not the lookup key. It is the ERC-20 address GLM is meant to enter |
| Address created when left blank | Install notes: leaving it out creates an address in local data | That address can still differ from the Stats node id. Use Stats |
| Node name | NODE_NAME, shown as Node Name | A human label. It cannot replace the node id |
The Golem monitor opens the node id published on Golem Stats. It does not open “any string that looks like Ethereum.” YA_ACCOUNT at install is an Ethereum address whose keys you hold. GLM is meant to arrive there. Both strings can start with 0x, and they still do different jobs.
What each field means
The node id is the provider’s identifier in the public stats. This monitor accepts 0x plus 40 hexadecimal characters. The node name is the label you set as NODE_NAME, printed on its own line in status. The Wallet line is the ERC-20 receiving address. The install guide says that leaving YA_ACCOUNT empty creates an address in the local provider data. You still compare that address with the node id on Stats. A shared 0x prefix is not a reason to paste it into the monitor.
Status also lists mainnet or testnet, a total, and on-chain and Polygon amounts. Those lines summarize GLM for the receiving wallet inside provider status. They are not the node id, and they are not the rolling 24-hour figure on the monitor.
What to inspect
- Open your provider on Golem Stats and copy the node id. Do not copy a different account from the browser.
- Run provider status on the machine and compare Wallet with Node Name. When Wallet and the Stats node id differ, the monitor uses only the Stats string.
- The data volume holds both node identity and wallet keys. The install guide warns that deleting the volume drops the wallet. That is key custody on the machine. The monitor cannot recover a private key.
What to do next
- The monitor will not open the record: count 40 hex characters after 0x, and confirm the string came from Stats rather than an exchange deposit address.
- The record opens but GLM disagrees with a wallet app: the two monitor figures are explained in rolling 24 hours and lifetime. The wallet app reads chain balances.
- Status shows testnet: testnet GLM has no real value. Mainnet income requires the payment network to be set to mainnet. See GLM payments and capacity.
Example
Illustrative, not a real node: call the Stats node id a 0x plus 40 hex “node side” sketch, and the Wallet line a different 0x “payout side” sketch. Pasting the payout side into the Golem project page does not open the node-side record. The node name “studio-a” replaces neither string.
Related tool
Save only the Stats node id as one device. Free allows five saved devices per project, Pro 50. Another source on that same device does not take a second slot. Do not save a second “wallet device” for the same receiving balance. That spends a slot, while the balance stays shared on the one record and is not a second copy of income.
Common questions
What if the receiving address and the node id are the same string?
You can monitor that string, because it is also the node id on Stats. Still confirm it on Stats, not only inside a wallet app.
Can I search by node name?
The lookup key in this monitor is the node id. The name only helps you recognize the machine in status and on Stats.
Should I paste a private key into the monitor?
No. The monitor needs only the public node id. Keep the private key in your own provider data and follow the official wallet backup notes.