Separate project / evolutionary direction
How Yamnweb evolves the path.
Yamnweb is not YAMN. It is a separate Virebent project that prepares a YAMN-compatible encrypted message, carries that opaque envelope through Nym, and only then hands it to the current public YAMN remailer network.
01 / THE CONCEPT
Nym is Yamnweb's transport boundary.
The current YAMN software, represented by crooks/yamn, submits a prepared packet toward the first remailer using ordinary mail transport. Yamnweb explores a different front-end path: it inserts a separate Nym transport layer before that first public YAMN hop. The browser submits message fields to Yamnweb, the service builds a compatible layered YAMN envelope, and a persistent sender passes only that envelope into Nym Network.
The receiving component is called the Entry. It accepts the opaque YAMN envelope from Nym and hands it to an allowlisted YAMN Entry remailer. It is not the YAMN Exit and does not perform final email or Usenet delivery.
Two projects and two networks. Yamnweb uses Nym to protect its transport path to the application Entry. The existing YAMN network then performs layered remailer routing, mixing, delay and final SMTP delivery. Yamnweb does not rename or replace current YAMN.
02 / MESSAGE ROUTE
From browser to delivery.
- The user composes a plain-text email or Usenet article in Yamnweb.
- The server validates the fields and builds a fixed-format, layered YAMN v2 envelope.
- A bounded, memory-only queue passes the prepared envelope to the persistent Nym sender.
- Nym transports the opaque envelope to the application Entry through the controlled Virebent Nym Entry.
- The application Entry forwards the envelope to an allowlisted YAMN Entry remailer.
- Each YAMN remailer removes one routing layer, mixes and delays traffic, then forwards to the next hop.
- The YAMN Exit exposes the ordinary destination only at final delivery, then uses SMTP for email or a configured Mail-to-News gateway for Usenet.
03 / CONTROLLED INFRASTRUCTURE
Virebent Nym Entry
The Yamnweb transport path uses the controlled Nym node at nym-gateway.virebent.art. The node declares only the Entry role. It is not a Nym Internet exit, open proxy or WireGuard service.
Nym node identity
CXDHLYJwjVnHsaD889B6GANTQHYhBFnP77ZSNb9aRpRT
This is the public Nym node identity used to identify the Virebent Entry. The application Entry recipient used internally by Yamnweb is fixed deployment configuration and is never browser input.
04 / COMPOSER
One form, two destinations.
Yamnweb uses one send-only composer. An email recipient selects ordinary email delivery. A non-empty Newsgroup field selects Usenet delivery and causes the server-configured Mail-to-News destination to be placed inside the encrypted message.
The interface lets the user choose Entry, Middle and Exit roles from currently usable YAMN remailers. A wildcard lets the encoder select a compatible remailer using current statistics and valid public keys.
Onion access: open http://ai63yqfo2wu2j3ey7nmatyel52jjvcmfg4e4kkxp2y7x3bc6nue6czyd.onion:4343/ directly in Tor Browser. Keep port 4343 in the address. This is an access layer for the composer; Nym remains the primary transport for the prepared YAMN envelope.
05 / PRIVACY BOUNDARIES
What the design does not promise.
No single transport or cryptographic format makes unsafe behavior anonymous. Message wording, timing, browser state, recipient choice, compromised endpoints and operational mistakes can reveal information outside the protected envelope.
Do not treat submission as final delivery. Public remailer queues introduce delay and can fail. Confirmation from Yamnweb means local handoff, not proof that an email or Usenet article arrived.
Do not submit passwords, private keys or material that must not leave your device. Use a dedicated privacy-preserving environment for sensitive work and make your own threat assessment.