When several fly.ai machines share one wallet, month points are counted once
Several machines can use one public payout address. Month points and share on the monitor are that one wallet row. Copying the row onto each machine and adding those copies counts the same points twice.
| What you did | Month points | Saved-device slots |
|---|---|---|
| Two PCs linked to one 0x | Still one month-point row for that address | Does not grow just because two machines were seen |
| One saved device, this address filled in | Read that one row; do not copy it | Counts as 1 fly.ai device |
| A separate saved device per machine, each with fly.ai | The same wallet is still deduped, not added twice | Each saved device counts as 1. Free is five saved devices per project; Pro is 50 |
| fly.ai linked again on the same saved device | Same wallet total | Does not add another device |
| Other projects on the account | Unrelated to these points | Each project has its own five or 50 |
Several computers can use one fly.ai public payout address. The month points belong to that address once. They are not a copy for each machine. On fly.ai monitoring a match is one wallet row: month points and share. Copying that row onto every computer and adding the copies counts the same points again.
A wallet is not a saved device
The public month record lists points by 0x address. It has no column for “this PC” and “that PC”. The official Compute page is where you look at one machine’s jobs. A saved device in the monitor is a record you created. It is not a fly.ai account, and it is not every miner the network happens to see.
Slots count saved devices
- On Free, saved devices that include fly.ai stop at five. Pro is 50 per project. Other projects have their own counts.
- Reading this wallet on one saved device, or linking fly.ai again on that same device, does not add a device.
- A new saved device you create for a second machine, with fly.ai filled in, counts toward the five or the 50.
- If two saved devices use the same address, income still shows the one wallet row. The month points are not added twice.
When you need one machine
If today’s work differs between two machines, the month total cannot explain the gap. Open the official Compute page and check jobs, checked work for the day, and whether the wallet is linked, one machine at a time. The monitor row still reports only that address’s month points. Do not paste a per-machine secret into the monitor. See public wallet vs secret.
Example
Illustrative, not a measured fleet: address A has 100 month points. PC 1 and PC 2 both use address A. The monitor should show 100, not 200. If you also saved two devices that both include fly.ai, the slot count is 2 and the points stay 100.
Next step
Read the month points once, by address, on fly.ai monitoring. How to read the month and the share is in the current month. To see whether one machine is running, use the official Compute page. A wallet total is not proof that a machine is online.
The monitor cannot show today’s points per machine, and it does not turn one wallet into several devices by itself. When the project slots are full, another new saved device with fly.ai is refused. Records you already have stay.
Common questions
Should I add the points from two computers?
No. The public month keeps one row per wallet. If both machines use the same 0x, the month points on the monitor are already that wallet’s total.
If one device lists several workers, does that use up the five slots?
Not by itself. Slots count saved device records that include fly.ai. Free is five saved devices per project. Pro is 50 per project. A new saved device that you create and fill with fly.ai counts as another. Linking fly.ai again on the same saved device does not.
How do I see what one machine did today?
The month row cannot answer that. Use the official Compute page for that machine’s jobs and that day’s points. The monitor cannot split a wallet total back into machines.