AeroNyx Privacy Network ve geleneksel VPN
AeroNyx acik protokolu ile tek saglayici VPN'in trust, metadata, encryption, mevcut maturity ve limits uzerinden gercekci karsilastirmasi.
AeroNyx Privacy Network daha genis open privacy protocol icinde private-routing sunar. Geleneksel VPN'den compatible infrastructure operatorleri, capability/health kaniti ve routing ile encrypted messaging/client-sealed memory ayrimi bakimindan farklidir. Bu trust model farkidir; gorunmez network veya mutlak anonimlik vaadi degildir.
Kisa yanit
VPN genelde client, gateway fleet, policy, telemetry ve account kontrolunu tek provider'a verir. AeroNyx, AeroNyx ve bagimsiz operatorlerin uygulayabilecegi protocol tanimlar. Official products halen coordination, discovery, admission ve default experience saglar; bu nedenle sifir operational trust/central service degil, gelisen open privacy network'tur.
Trust model farki
VPN tek operatorun internal controls ve no-log policy'sine guven ister. AeroNyx trust'in bir kismini dagitir; signed capability, version, health, capacity, discovery, relay, recovery evidence gorunur olur. Tek fleet bagimliligi azalir ama independent-node, route-selection, software-supply-chain, endpoint ve metadata riskleri eklenir.
Mimari karsilastirma
| Boyut | Geleneksel VPN | AeroNyx |
|---|---|---|
| Operators | Tek provider/contractors | AeroNyx-operated ve independent nodes |
| Admission | Provider server list | Discovery, compatibility, health, reachability, capacity, policy, abuse controls |
| Evidence | Private records | Signed/aggregate node/protocol health |
| Content | Tunnel gateway'de biter; HTTPS gerekir | Tunnel path'te biter; HTTPS/App E2E gerekir |
| Scope | Private internet routing | Routing ile ayri messaging, operation, sealed memory |
Bugun ne calisiyor
Reference network registered nodes, encrypted tunnel, health/capacity, policy, aggregate packet/byte, peer discovery, signed descriptors ve Nodeboard destekler. Bazi deployments messaging icin relay candidates/multi-hop evidence gosterir. Bu tum internet traffic onion-routed, tum nodes independent veya tum relay/storage/commitment aktif demek degildir.
Routing node ne gorebilir
Gateway/exit forwarding icin network metadata isler: topology'ye gore source connection address, destination IP/port, size, timing, duration, volume. Single-hop timing korelasyonu yapabilir. Encrypted DNS yoksa node/resolver queries gorebilir. Destinations/payloads'i public/backend stats'e gondermemek non-collection politikasidir; metadata teknik olarak yok olmaz.
Ne sifreli kalir
Tunnel client ile node/path arasini korur. Exit sonrasinda confidentiality destination protocol'a baglidir. HTTPS/TLS content'i exit'e karsi sifreli tutar; HTTP plaintext okunabilir/degistirilebilir. AeroNyx chat E2E envelopes, strict MemChain upload oncesi client encryption kullanir. Bunlar ayri garantilerdir.
Bagimsiz nodes ve route eligibility
Law, hosting, security ve technical requirements ile herkes compatible node calistirabilir ama selection garanti degildir. Official discovery/App signed identity, version, endpoint, fresh heartbeat, capacity, abuse protection, policy, probe stability, route evidence ile filtreleyebilir. Yeni node warm-up ister; multi-hop icin operator diversity ve anti-Sybil onemlidir.
User surveillance olmadan public evidence
Public surfaces aggregate encrypted bytes, packets, availability, regions, capacity, relay/probe outcomes, restart recovery, freshness gosterebilir; user activity log olamaz. Client IP activity, per-user sessions, destination IP/domain, DNS, routes, message IDs, payloads, private memory, wallet traffic, keys, vouchers yayinlanmaz. Missing/stale healthy zero degildir.
Messaging ve MemChain daha guclu sinirlara sahiptir
Encrypted messaging ve MemChain internet traffic'in otomatik ozelligi degil, ayri services'tir. Messages E2E keys kullanir; official App simdi default AeroNyx-operated relay kullanir, decentralized/multi-hop paths optional ve gelismektedir. Strict MemChain node-blind client-sealed records icindir; external AI/readable modes ayri plaintext trust'tir.
Autonomous agent protokolu neden kullanir
Agents requests route etmek, signed encrypted message alisverisi, private state ve cross-operator coordination icin tum content keys'i tek service'e vermek istemeyebilir. AeroNyx routing, identity, relay, storage, health, evidence primitives sunar. Yine endpoint authentication, authorization, application encryption, key protection, replay defense, policy ve safe tool boundaries gerekir.
Sinirlar ve sorumluluk
AeroNyx absolute anonymity, zero metadata, kesintisizlik, her yerde legality, fixed performance, compromised device korumasi veya tum traffic-analysis/malicious-node direnci garanti etmez. User traffic/content'ten, operator node'dan sorumludur. HTTPS, uygun encrypted DNS, current client, protected identity ve threat model'e uygun route kullanin.
AeroNyx nasil degerlendirilir ve kullanilir
Node list, region, operator/route diversity, health freshness, capacity, software version ve workload'un single-hop, optional multi-hop relay veya application E2E kullanimini degerlendirin. Disabled/not reported unavailable/no evidence'dir, proven safe degildir.