# Where is koopa listed publicly? (Nym / nym.com)

Similar idea to **Tor relay directories**, but Nym uses different explorers and
requires a **bond** on-chain before the node shows up reliably.

## Public directories / explorers

| Site | Role |
|------|------|
| [https://harbourmaster.nymtech.net/](https://harbourmaster.nymtech.net/) | Operator / performance view (search by identity key or node id) |
| [https://explorer.nymtech.net/](https://explorer.nymtech.net/) | Network explorer (mixnodes / components) |
| [https://nym.com/explorer](https://nym.com/explorer) | Nym.com explorer UI |

After bonding, a typical deep link shape is:

`https://nym.com/explorer/nym-node/<IDENTITY_KEY>`

or Harbour Master mixnode pages by numeric id once assigned.

## This host (`koopa-nym`)

| Field | Value |
|-------|--------|
| Container | `koopa-nym` (running, mode **mixnode**) |
| Announced public IP | `212.51.151.254` (WAN / VeciGate) |
| Mixnet | host **1789** tcp/udp |
| Verloc | host **1790** tcp |
| Local HTTP API | `http://127.0.0.1:9080` (not DNATed to WAN) |
| **Ed25519 identity (public)** | `55gPqeyHHj4CwpVZXLEQy9MjSvVTVXM8t2pMmNCH2MsW` |
| Location (aux) | `CH` |
| Operator T&Cs accepted | yes (run flag) |

### How to re-read identity on the host

```bash
podman exec -e HOME=/var/lib/nym koopa-nym \
  nym-node node-details --id koopa-nym
```

Search explorers with the **ed25519 identity** string above.

## When it becomes visible

1. Node process running (done).
2. Ports reachable from the internet (VeciGate DNAT + **firewalld** on koopa).
3. **Bond** the node with the Nym wallet (NYM stake / bond flow).
4. Wait for network / epoch updates; inactive nodes may lag in Harbour Master.

Until step 3, public explorers often show **nothing** for this identity — that is expected.

## Not the same as Tor

| Tor | Nym |
|-----|-----|
| Relay Search / metrics after ORPort publish | Explorer / Harbour Master after **bond** + healthy announce |
| Nickname optional | Identity key is the stable public id |

## Related

- Ops mirror: `configs/nym/`
- Open issues: root [`ISSUES.md`](../../ISSUES.md) (I-2026-07-16-01, I-2026-07-16-02)
- VeciGate NAT: `vecigate-admin-log/ip/firewall/nat/README.md`