# BNT local daemon status versus pool share activity

Daemon reachability, wallet synchronization and miner share submission are different states. A local tool such as bntop and a public pool observe different scopes. A responding node alone does not prove that a pool worker is submitting work.

- Canonical: https://iotahome.site/en/learn/bnt-local-daemon-vs-pool-work
- Publisher: IOTA Watch
- Topics: Blocknet
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

Daemon reachability, wallet synchronization and miner share submission are different states. A local tool such as bntop and a public pool observe different scopes. A responding node alone does not prove that a pool worker is submitting work.

## What to check

Check the active miner process, pool endpoint, payout address and last accepted share, then match the same worker on the pool. Preserve the error category from logs while removing credentials before sharing. A source timeout should retain the last successful observation rather than turning into a measured zero hashrate.

## Example

Example: the daemon syncs normally while the miner points to the wrong pool. Correct-pool shares can remain absent. Verify configuration and fresh shares before marking the device as contributing.

## Continue

[Open project monitor](https://iotahome.site/en/projects/bnt)

## Sources and implementation

- [blocknetcrypto.com](https://blocknetcrypto.com/)
- [bntpool.com](https://bntpool.com/)
- [github.com](https://github.com/blocknetprivacy/bntop)