# BNT hashrate fell over 24 hours: a gap, a zero, or one machine

The address line is bntpool.com's 24-hour samples. Worker lines are samples collected from lookups over the last 24 hours, not a continuous curve. A gap is not zero.

- Canonical: https://iotahome.site/en/learn/bnt-24h-hashrate-drops
- Publisher: IOTA Watch
- Topics: Blocknet
- Published: 2026-10-24
- Updated: 2026-10-24

## At a glance

Separate three shapes: the whole address fell, only one machine fell, or a stretch of the line has no sample. A missing sample is not drawn as zero and is not proof the miner stopped.

## Three drops, three next steps

| Shape you see | Closer to | Next step |
| --- | --- | --- |
| Every Worker loses recent shares | The site or the connection | Check power, the Seine process, and bntpool.com |
| One machine drops, address rate remains | That machine or its name | Check the backend and the Worker name |
| A gap in the line | No sample | Do not draw it as 0. Wait for the next real point |
| A point sitting on 0 | The source reported 0 | Then check whether that Worker has a share inside 15 minutes |

## Start with the 24-hour range

Open the 24-hour chart for this full mainnet address in [BNT monitoring](https://iotahome.site/en/projects/bnt). This page explains why hashrate looks lower. It does not say how much BNT you earned today. Amounts are in [immature, queued, and paid](https://iotahome.site/en/learn/bnt-pending-queued-payouts).

The address line uses the public hashrate history bntpool.com publishes for that address. The ranges are 24 hours, 7 days, and 30 days. The chart to read here is the 24-hour range. Each point is the pool's estimate in H/s, not a stopwatch reading from your machine. If the pool leaves hashrate empty at a time, the line breaks. That empty value is not rewritten as 0. A long hole between neighboring samples also breaks the line. That break is a missing sample, not a measured zero. A point that sits on zero is a time the source actually reported zero.

## The Worker line is not continuous

Each Worker has a separate line for the last 24 hours. Those points are samples kept when this address is looked up. They are not a continuous official curve from the pool, and they are not the machine's local log. If no lookup stored a point, the stretch between points is a gap. Do not connect the gap as zero, and do not describe it as “hashrate was zero for those hours”. The numbers below are an illustrative example.

On one address with several machines, money is still counted once. Hashrate can be read per Worker. See [several machines on one address](https://iotahome.site/en/learn/bnt-address-workers-devices).

Illustrative example: at 14:00 the address is 16 H/s, with `desk` at 12 and `shelf` at 4. At 15:00 the address is 4 H/s, `desk` has no new point, and `shelf` is still 4. At 16:00 the address line is a gap, not a zero. Check whether `desk` is still running and whether its worker name and backend are still the CPU or NVIDIA you set. Do not read the gap as “the whole farm has been 0 since 16:00”, and do not turn the fall from 16 to 4 into “12 BNT less”. A hashrate difference is not coins.

## Three shapes, three checks

- If every Worker loses recent shares together, check power, the Seine process, and that the pool is bntpool.com. Change the miner only after that check shows a mismatch.

- If only one machine drops and the others remain, check that machine's backend and that `--pool-worker` matches the name on the list.

- If the address estimate is 0 while a Worker still has a share inside about 15 minutes, the estimate can sit at zero when shares are sparse. That alone does not prove the process exited.

- If the whole row is stale or unavailable, do not treat the previous number as a current zero, and do not add it into the totals.

Crash notes are free to read. They cannot restart Seine. The device agent controls only IOTA Train at Home on a Mac. It does not operate a Blocknet miner. Free saves 5 devices per project; Pro saves 50.

The 24-hour line does not convert into BNT or dollars, and it does not prove the next hour will recover. When the chart is empty or broken, read the address and backend in the Seine log before you change the miner. The documented default pool is `stratum+tcp://bntpool.com:3333`. Next, return to the machine and the backend: [Seine on CPU or NVIDIA](https://iotahome.site/en/learn/bnt-seine-cpu-nvidia-setup).

## Common questions

### Is a break in the line a hashrate of zero?

No. A break means no usable sample at that time. Only a point that sits on zero is a zero the source reported.

### Is the Worker 24-hour line a continuous pool record?

No. It is samples kept when that address is looked up, covering only the last 24 hours. The space between lookups is not a measured zero.

### Can a hashrate drop be converted into BNT I did not earn?

No. The chart has no coins and no dollars. Missing H/s is not an income line. Income is still the four amounts on the address, and those amounts are not a 24-hour bill.

## Sources and implementation

- [bntpool.com start](https://bntpool.com/start)
- [Seine miner](https://github.com/zpalmtree/seine)
- [Blocknet protocol](https://blocknetcrypto.com/)