Disclosure // who runs the card // 2026
About This Torzon Card: Who Runs It, How a Lock Gets Checked
This card is a maintained Torzon access reference, kept for security research. It is not run by Torzon. Below: who writes it, what a lock actually checks before a node goes live, and where this reference's job stops.
Why run this card at all
Search a market name and you hit clones before you hit anything real. A clone copies the layout, the badges, the whole look — then swaps one string. This card exists to be the one thing that does not move: a current address, an honest status, and a way to check both yourself instead of taking the page's word for it.
What actually happens before an address goes on the card
- Confirm the onion answers over Tor and serves Torzon, not a parking page or a squat.
- Diff the full 56-character string against the last confirmed-good copy, character by character.
- Match it to the signed record once the canon key ships in Phase 0.
- Mark the status by what the probe returned this pass — never a hard-coded green light.
A probe is a timestamp, not a promise. A node can drop a minute after this card checks it — the address plus your own signature check outranks any word on this page.
Who writes and checks this card
Two people maintain this card. Neither is affiliated with Torzon or any market operator, and neither holds funds or an account on any market.
Alex Ferran
Security research. Writes the lock sequence, the signature bench, and the clone teardown. The constant question: what can you verify yourself, without trusting this card's word for it.
Mira Kessel
Market operations. Maintains the mirror status legend and the probe method behind it — honest uptime reporting, no inflated green.
A byline names who wrote or last revised a page. It does not mean that person placed a Torzon order or has any relationship with Torzon's operators.
Independence, and what triggers a re-check
No paid slots
Nothing on this card is sponsored. No vendor, forum, or third party buys a higher spot, a faster load, or a skip past the lock sequence above. Row order reflects role — primary, then failover — never a payment.
What forces an off-cycle check
Nodes re-probe on a routine schedule by default. Outside that: a reader flags a mismatch, a node drops for an extended stretch, or a new address surfaces claiming to be an official failover. None of those post until they clear the same lock described above.
What pulls an address off the card
An address comes off — marked, not silently deleted — the moment it stops serving the real market: a seizure banner, a parking page, a login that no longer matches. The retired entry stays visible and honestly labeled.
Who pays for this card
No ads, no paid placement in the node table, no payment from Torzon or anyone else to adjust a status. It stays useful by staying accurate. The honest risk is drift — a card that quietly stops re-checking its own claims — which is why status here defaults to caution (Checking, Dead) instead of an optimistic Online when a probe has not actually completed.
Reaching this card, and checking the key
The one durable trust signal here is the PGP signature on the mirror record. The signing key ships in Phase 0; until then the fingerprint reads pending (Phase 0) and addresses get compared by eye. Once the key is live, import it once and run the check yourself — do not take this card's word for it.
Next: how to open Torzon, or back to the card.
Run the lock yourself
See how a node actually clears the check, start to finish.