Verifying on an amnesic system
A system that forgets on shutdown is excellent for this and awkward for one specific step, which is holding the key you verify against.
The awkward part
An imported key lives in a keyring, and on an amnesic system the keyring disappears with everything else. Without persistence you re import the operator key on every session, which means the import step happens exactly when you are least able to compare fingerprints across independent sources calmly.
The fingerprint solves it
Keep the forty character fingerprint outside the system entirely, on paper. Then re importing is safe: fetch the key from anywhere, import, and confirm the fingerprint against what you wrote down. The key can come from a hostile source and the check still works, because the anchor never travelled with it.
If you use persistence
A small persistent area holding the keyring and a text file of saved addresses removes the repetition. It is also the one thing that survives the session, so decide deliberately what goes in it. A keyring and a list of onions is a reasonable set. Anything you would not want found is not.
Why this environment suits verification
Nothing you do persists to be examined later, the network path is uniform, and the tooling is present without installation. For somebody who verifies occasionally rather than daily, it is a cleaner setup than a permanent machine that accumulates state.
The step people skip here
Writing the fingerprint down before the first amnesic session. Without it the whole arrangement collapses into trusting whatever source you happened to reach that evening, which is the situation verification exists to escape.
A note on where the addresses live
Saved addresses face the same amnesia as the keyring. Paper handles both, and a short persistent volume handles both more conveniently. Whichever you choose, decide it before the session where you need it rather than improvising at the point where the system has already forgotten everything.