Permanent record keeper, explained for home and pro operators

Every operation eventually argues about its permanent record keeper, and for good reason — it sits on the critical path between the watts coming in and the useful work going out.

What a permanent record keeper actually does

Think of a permanent record keeper as the layer that owns verifying work on the network. When it works you forget it exists; when it fails, you feel it in your uptime and your power bill.

On a public network a permanent record keeper is judged by the protocol, not the brochure — a correct result counts and a wrong one is simply discarded.

What to look for

When you put a permanent record keeper through its paces, weigh it against the things that bite in production rather than the ones that demo well:

• Whether the implementation follows the protocol spec exactly
• How it behaves under high difficulty and contested conditions
• Latency from finished work to an accepted, confirmed result
• Resilience to reorgs, stale work and orphaned effort
• Whether rewards and shares are accounted for transparently

Common mistakes

The usual trap is optimising for the happy path. A permanent record keeper that looks great on the bench can fall apart the moment heat, dust and 24/7 load build up — which is exactly when it matters most. Test it under sustained load, in real ambient conditions, and on the messiest power you actually have.

The bottom line

There is no universally "best" permanent record keeper — only the one that matches your space, your power budget and the scale you actually run. Start from your constraints, not the spec sheet.