Engineering Dispatches

Operational announcements, carrier integration architecture notes, and privacy engineering updates from the XMRShip team.

Operational & Engineering Log

We publish technical post-mortems, carrier API routing rules, and security hardening updates here so shippers understand exactly how their parcels and payments are processed. Browse the monthly archive in the left column or select one of our three most recent dispatches below.

November 09, 2026 • Carrier Engineering 9 Comments

Preventing Carrier Multi-Piece Consolidation with UUID Disambiguation

When multiple single-piece parcels are dispatched on the same calendar date with matching sender and recipient addresses, automated sorting systems (notably Purolator Automated Parcel Sorting / ARC, UPS Hundredweight, and FedEx Multiweight) frequently merge those separate tracking numbers into a consolidated Multi-Piece Shipment (MPS) consignment. Weeks later, the carrier re-rates the batch at freight tariffs and issues retroactive adjustment invoices.

To guarantee every parcel travels as an isolated single-piece shipment, ShipStationService injects an 8-character uppercase hexadecimal hash derived from the shipment UUID into both the consignee name (Nancy Gabriel (Ref: 42A74C4B), strictly capped at 40 characters) and address_line2 (Apt / Ste / Unit 42A74C4B). Simultaneously, all metric dimensions are converted to imperial inches using (int) ceil($cm * 0.393701) to match optical parcel scanner rounding rules.

November 02, 2026 • OpSec & Tor Infrastructure 6 Comments

Session-Isolated Rate Limiting & Zero-JS Hardening on Tor v3

Operating a Laravel application behind a Tor hidden service introduces two subtle failure modes: first, all incoming .onion connections originate from the local Tor daemon socket (127.0.0.1), meaning naive IP-based rate limiters allow one noisy circuit to lock out all concurrent Tor users. Second, .onion traffic uses end-to-end encrypted HTTP without TLS certificates, so a static SESSION_SECURE_COOKIE=true directive causes Tor Browser to drop authentication cookies silently.

XMRShip resolves both issues in AppServiceProvider: when the request host ends in .onion, session.secure is dynamically set to false, and registration/login rate limiters key off the session cookie hash rather than the shared loopback IP.

October 24, 2026 • Payment Pipeline 14 Comments

Non-Custodial Monero Settlement & Live Carrier Price Verification

Every Monero checkout on XMRShip communicates with our self-hosted BTCPay Server Greenfield API and internal monerod node. QR codes are rendered server-side as inline base64 SVGs via App\Utils\PHPQRCode so no third-party QR image APIs are ever contacted. When the HMAC-verified webhook confirms settlement, ProcessShipmentJob performs a live uncached rate verification (forceRefresh = true) before purchasing the carrier label.

October 11, 2026 • Authentication 5 Comments

Implementing GnuPG Challenge-Response 2FA Without Client JavaScript

Standard WebAuthn and TOTP authenticators either require browser JavaScript APIs or centralized mobile ecosystems. Our PgpService uses an isolated ephemeral GnuPG keyring per operation to encrypt random 16-byte hexadecimal challenges against your verified public key fingerprint. Rate limit counters remain active until the decrypted challenge is verified, preventing password-spraying bypasses.

September 18, 2026 • Carrier Network 11 Comments

Dual-Origin Commercial Routing Across Canadian & US Carrier Accounts

To support both domestic Canadian shipping (Purolator, Canada Post, UPS CA, FedEx CA) and domestic United States shipping (USPS, GlobalPost, UPS US, FedEx US), XMRShip dynamically toggles ShipEngine V2 API credentials via $shipStation->useUsaAccount() based on the sender's origin country code, paired with a 15-minute active rate cache and 2-hour stale fallback cache.