| ID | title | created | status | kind | author(s) | champions |
|---|---|---|---|---|---|---|
| NIP-15 | Nym Exit Policy Update – Opening Port 8000 for Railgun and Community Applications | 27-10-2026 | proposed | standard | Serinko, Head of Network & DevRel serinko@nymtech.net, Merve, Operator technical mentor merve@nymtech.net | Max, Senior DevRel max@nymtech.net, Sudo, Head of community simon.toth@nymtech.net |
Summary
NIP-15 proposes allowing outbound connections to port 8000 under the Nym exit policy. The change supports Railgun desktop application users and other community services that rely on this port.
Motivation
Railgun desktop users have requested access to port 8000 so they can use Railgun through Nym. Railgun is a privacy-focused project aligned with Nym’s goal of reducing network-level metadata exposure.
Port 8000 is also used by a range of other applications, including:
- Web applications and APIs (alternative HTTP endpoints, backends)
- Development and testing servers (Python HTTP, Django)
- Audio streaming (Icecast, SHOUTcast)
- Self-hosted and community services
- Some device and software interfaces
- Some peer-to-peer applications
These are examples, not a guarantee that every service on port 8000 is safe. The port number alone does not determine a service’s purpose or security.
Opening port 8000 would let Nym users reach destinations using this port when those destinations are otherwise reachable. It would not create a service or guarantee that a connection succeeds.
Relation to NIP-14
NIP-14 raised concerns about cumulative impact on exit node operators, risks of broad port ranges, and the need for careful governance. NIP-15 takes these concerns into account: it does not expand the exit policy generally or open a range of ports. It requests one specific destination port and provides context so operators can make an informed decision.
Scope
- Destination port: 8000
- Change: Allow connections to destination port 8000 under the Nym exit policy.
Security and Operational Considerations
Opening a destination port removes a restriction on traffic that can pass through Nym exits. It does not open an inbound port on an operator’s machine or expose a service hosted by that operator.
Not all services on 8000 are equally secure. An incorrectly configured development server or exposed administrative interface may carry risks. The relevant risk depends on the destination service, its configuration, and how it is exposed.
Operators should evaluate the change with a clear understanding of its scope. Opening one port is narrower than opening a range, but it is not a guarantee that all traffic to that port is harmless.
This proposal does not change operators’ existing legal obligations. Operators should continue to follow their usual safeguards and report concerns through established community channels.
Voting Options
Voting takes place at Nym Governator.
- YES: Approve allowing outbound connections to destination port 8000 under the Nym exit policy.
- NO: Reject the proposed change.
The proposal will be evaluated according to the applicable governance requirements, including quorum and approval thresholds.
Process
If the proposal meets the applicable quorum and approval requirements:
- A pull request will update the Nym exit policy to allow destination port 8000.
- The Network Tunnel Manager (NTM) will be reviewed and updated if necessary to keep operator WireGuard exit-policy configuration consistent with the Mixnet policy.
- The approved change will be deployed through the normal implementation process.
- The community may share feedback on application compatibility and operational concerns after deployment.
The change is not a temporary trial. If approved and implemented, port 8000 will remain allowed unless a subsequent governance decision changes the policy.
Background
The Nym exit policy controls which destination ports are accessible through Nym exits. Since NIP-1, exit-policy decisions have been managed through Nym Governator to support transparent and accountable governance.
NIP-15 builds on the NIP-14 discussion by proposing a single, clearly defined port change and explaining its intended use cases and limitations.
