GRID // DISCLOSURE
About This Torzon Grid: Who Runs It, How a Node Gets Checked
This grid is a maintained Torzon status board and verification reference. It is not run by Torzon's team. This page names who runs it, states how a node earns Online instead of Checking, and says plainly where the grid's responsibility stops.
Why run a status grid at all
A Torzon search turns up clones before it turns up the real address. A clone copies the layout and the badges, then swaps the one string that matters. One maintained grid — the current address, an honest per-node status, and a way to check both — removes most of that guesswork. It works by staying boring: one probe method, run the same way every pass.
How a node earns a place on the grid
- Confirm the onion answers over Tor and serves Torzon, not a parking page.
- Diff the full 56-character string against the last confirmed-good copy.
- Match it to the signed record once the canon key ships in Phase 0.
- Mark 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 grid checks it, which is why the address plus your own signature check outranks any status word here.
What this grid does not do
This grid does not run Torzon, takes no cut, holds no funds, and cannot see a Torzon account. It cannot reset a password, release an order, or recover coins. Any page off Tor offering "support" in this grid's name is not this grid — report it the same way you would a fake mirror.
Who writes and checks this grid
Two people maintain this grid and the pages linked from it. 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 access sequence, the PGP/signature bench, and the onion-routing primer. Focus: what a reader can verify themselves.
Mira Kessel
market operations — maintains the status grid itself and the probe method behind it. Focus: honest uptime reporting, no inflated Online counts.
A byline credits whoever 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 how often the grid refreshes
No paid slots
Nothing on this grid is sponsored. No vendor, forum, or third party buys a higher rank, a faster load, or a skip past verification. Row order reflects node role — primary, then failover — never a payment.
What forces an off-cycle probe
Nodes re-probe on a fixed 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 check described above.
What pulls a node off the grid
A node 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 row stays visible and honestly labeled.
Who pays for this grid
No ads, no paid placement in the node table, no payment from Torzon or anyone else to adjust a status. The grid stays useful by staying accurate. The honest risk is drift — a grid that quietly stops re-checking itself — which is why status here defaults to caution (Checking, Dead) rather than an optimistic Online when a probe has not actually completed.
Reaching this grid, and checking the key
The one durable trust signal here is the PGP signature on the mirror list. The canon 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.
Next: how to reach Torzon, or back to the status grid.
Check the grid itself
See which nodes answered on the latest pass.