TECHNICAL ARCHITECTURE
PROTOCOL VERSION: 9.0 // CLASSIFICATION: PUBLIC
1.0 ABSTRACT
The VNSH Protocol decouples Financial Identity from Network Identity.
Standard mobile networks require a 1:1 link between a user's billing profile (Name, Credit Card) and their device's IMSI. This creates a permanent record of location history.
VNSH acts as an automated financial proxy. We acquire roaming profiles in bulk using non-attributable corporate entities and store them in a blind SQL database.
2.0 THREAT MODEL
WE PROTECT AGAINST
- Billing Association: Linking a credit card to a specific SIM card.
- Access Logs: Linking an IP address to a purchase (Mitigated via Tor).
- Database Seizures: Recovering transaction history (Mitigated via Reaper Daemon).
WE CANNOT PROTECT AGAINST
- Cell Tower Triangulation: The local carrier (AT&T, etc.) knows the physical location of the device.
- IMEI Correlations: If you put a VNSH SIM in a phone previously used with your real SIM, the carrier can link them.
3.0 ARCHITECTURE
The infrastructure is physically segmented into two isolated environments:
- SERVER 1 (Storefront): Handles user interaction. Holds NO private keys.
- SERVER 2 (Bank Node): Handles blockchain consensus. Accessible ONLY via Tor Hidden Service.