pgp_verification.md
Cryptographic verification of Nexus Market onion addresses using PGP signatures. Prevents phishing clone attacks. Covers key import, signature verification and address comparison protocols.
load moduleComplete security research archive for Nexus Market access, PGP verification and operational security. All onion addresses verified against cryptographic signatures.
Nexus onion addresses are rotated and verified server-side to defeat phishing clones. Open the current PGP-verified address through our access gateway.
View Verified Address →Opens the verified access gateway. Use Tor Browser only.
system_status
Current security implementation status for Nexus Market platform components.
| Component | Implementation | Threat Mitigated | Status |
|---|---|---|---|
| auth.pgp_2fa | PGP-encrypted challenge per login session | Credential theft, account hijacking | [ACTIVE] |
| payment.monero | XMR stealth addresses, RingCT, ring signatures | Transaction tracing, blockchain analysis | [ACTIVE] |
| network.onion_v3 | 56-char v3 hidden service with ed25519 keys | Traffic analysis, IP exposure | [ACTIVE] |
| escrow.multisig | Funds held until buyer confirms delivery | Exit scams, vendor fraud | [ACTIVE] |
| ddos.mirror_rotation | Multiple simultaneous onion endpoints | DDoS-based availability attacks | [ACTIVE] |
| js.disabled_mode | Full functionality with JavaScript disabled | Browser exploits, fingerprinting | [ACTIVE] |
quickstart.sh
Minimum required steps for safe Nexus Market access. Execute in order.
Fetch Tor Browser exclusively from torproject.org. Verify GPG signature. Set security_level = SAFEST. Disable all extensions. Run in dedicated environment.
Import Nexus Market admin PGP key. Locate latest signed mirror announcement on Dread. Run gpg --verify. Compare address against verified output char-by-char. Abort if mismatch.
Generate RSA-4096 or ed25519 PGP keypair. Upload public key to Nexus Market account. Activate 2FA. Store private key offline. Test decryption before relying on it.
modules
Security research documentation for Nexus Market users. Each module covers a specific threat vector.
Cryptographic verification of Nexus Market onion addresses using PGP signatures. Prevents phishing clone attacks. Covers key import, signature verification and address comparison protocols.
load moduleOperational security protocols for Nexus Market users. Device isolation, network compartmentalization, Monero acquisition without KYC and threat modeling for darknet market participants.
load moduleStep-by-step Nexus Market access protocol. Tor Browser installation and hardening, onion address verification, account creation and PGP 2FA activation sequence.
load modulefaq.json
How do I access Nexus Market safely?
Install Tor Browser from torproject.org with security level set to Safest. Verify the Nexus Market onion address against a PGP-signed announcement on Dread. Copy the address manually into Tor Browser — never click links. Enable PGP 2FA on your account immediately after registration.
What makes Nexus Market onion addresses different from regular URLs?
Nexus Market onion addresses are v3 Tor hidden service addresses — 56 characters of base32-encoded ed25519 public key material followed by .onion. The address itself cryptographically authenticates the server, making man-in-the-middle attacks impossible when using a verified address with Tor Browser.
How does Nexus Market PGP 2FA protect my account?
After entering your password, Nexus Market generates a unique random challenge and encrypts it to your PGP public key. Only someone with your private key can decrypt this challenge and complete login. An attacker with only your password cannot pass this second factor.
Why is Monero required for Nexus Market transactions?
Nexus Market recommends Monero because its privacy is enforced at the protocol level through ring signatures, stealth addresses and RingCT. Bitcoin transactions are publicly visible on the blockchain and can be traced back to exchanges and real-world identities through chain analysis.