Osiris Schedulehow often, not just how Everything this involves, sorted by how frequently you actually do it
Schedule › Once, ever

Pin the fingerprint

the load bearing hour

The task people skip because it produces nothing visible at the time. Every other protection here rests on it.

Osiris addresses

Three published addresses for the same market. Copy rather than retype.

osiriseultmx3so5ef6ayasy4kdyekbywr7pyggpmjazeogxoyaodsyd.onion
osirislivpetlbabbl3zzqhupurfkxxbzbheu3bkrshkaiwg2hcxbyqd.onion
osirisydmlx47esm6ylhzhtnjrucgnymi7beqoyzze5jn3opbr3zy4id.onion

This list is published, not monitored. An address that opens is not an address that is genuine, and the check that settles it belongs to the every time list.

How often
Once. Again only if the key genuinely changes, which is rare and deserves suspicion.
How long
About an hour if you do it properly, which mostly means comparing carefully rather than quickly.
What it prevents
It is what makes the per session check mean anything. Without it that check proves nothing at all.
If you skip it
Every later verification is theatre. You will be checking a signature against whatever key the page handed you.
How you notice you stopped
You cannot stop. What happens instead is that people never start, and then believe they are protected because they run the check.

Why the fingerprint and not the key file

A key is a large blob you cannot meaningfully inspect. A fingerprint is a short hash of it, short enough to compare by eye and long enough that nobody can produce a second key matching it. You pin the fingerprint and treat key files as disposable.

That reverses the usual instinct, which is to save the key file carefully somewhere. The file needs no protection at all. It is public and you can fetch it from anywhere including somewhere hostile, then check it against the fingerprint you hold. Only the fingerprint has to be right.

The circular trapA signature checked against a key taken from the page you are checking proves nothing. The page, the key and the signature all came from one party, and internal consistency costs a forger nothing.

What counts as independent

SourceIndependent?
Different operators, different infrastructureYes. Rare in this space and worth seeking out.
Several sites run by one personNo, and this is very common and rarely disclosed.
Several sites that copied a fourthNo. Aggregation is the default here.
The same value across archived captures over yearsWeakly. Persistence is harder to fake retroactively than a page is to edit now.

Doing it

  1. Collect it from several genuinely independent places.
  2. Compare in full. The whole string, character by character, not the first four and last four, which is the check a forger designs around.
  3. Write it down somewhere you control. Paper is genuinely good here, because nothing running on your machine can alter it.
  4. If they disagree, stop and wait. At least one source is wrong or compromised and you cannot tell which from where you are standing. This is a reason to pause, not to take a vote.