Mirror canon · signed evidence

Mars Market mirror list: verify the signed canon

A mirror list is trustworthy only to the extent that its source, signing key and exact contents can be verified. This page explains the method without republishing a raw destination address or claiming continuous status.

Evidence matters more than the number of mirrors

Multiple addresses can improve reachability, but quantity is not proof of authenticity. A useful canon records the complete hostnames, the time or version of the statement, the signing key fingerprint and enough context to distinguish a current announcement from an archived one.

A copied directory that removes the signature or publication history turns a verifiable statement into an unsupported claim. Even when every hostname is copied correctly, readers can no longer establish who issued the list or whether a later rotation replaced it.

How to evaluate a Mars mirror announcement

01

Locate the primary publication

Trace reposted text back to the earliest available source. Confirm that the signature belongs to the same message rather than a nearby post or attached screenshot.

02

Check the fingerprint

Compare all fingerprint characters with a value established independently. Do not trust a key merely because it was attached to the mirror list it is supposed to authenticate.

03

Verify without editing

Line endings, added spaces or copied formatting can change signed bytes. Use the original file or clearsigned text and read the verifier output carefully.

04

Compare every hostname

Match the full value from the verified statement. A lookalike can preserve recognizable characters while changing the cryptographic destination entirely.

05

Read replacement language

Determine whether the announcement adds a route, replaces an older route or revokes one. A historically valid address is not automatically current.

06

Preserve an audit record

Store the statement hash, fingerprint and verification result so the check can be repeated when a route changes or conflicting lists appear.

Common mirror signals and their limits

SignalWhat it can supportWhat it cannot prove
56-character v3 hostnameThe string has the expected onion formatWho controls the service
Successful connectionA service answered on that routeThat the responding service is genuine
Valid OpenPGP signatureThe message matches one signing keyThat the key belongs to the intended operator
Independently known fingerprintThe key can be tied to prior evidenceFuture behavior or availability
Recent signed replacementThe signer issued a newer set of valuesThat every listed route is reachable now

Stop when the evidence disagrees

If two lists name different hostnames, compare their signing fingerprints, publication history and replacement language. Do not solve a conflict by choosing the page that loads fastest or looks most familiar. An unresolved identity conflict is a reason not to proceed.

Verify the candidate before opening it

The pre-access checklist condenses source, signature and hostname checks into one final pause before navigation.

Open the checklist

Open the Mars Market route

This reference does not publish a destination address. The handoff starts in this tab only after you press the button.

  • Compare the loaded hostname with independently verified evidence.
  • Do not treat a working page as proof of operator identity.
  • Leave if the destination or login flow differs from what you checked.

A route is not a guarantee of availability, identity or safety.