Transparency report

What we see.
What we don't.

Updated May 2026 · Covers network alpha period

Network status

Active exit nodes

Devnet alpha — mainnet nodes pending operator onboarding

Countries covered

0 live / 12 planned

US, GB, DE, JP, SG, NL, CA, AU, FR, BR, IN, KR

Requests proxied (all time)

Testnet only — no production traffic yet

Total bandwidth served

0 GB

USDC paid to operators

$0.00

Staking and payouts activate with mainnet launch

Network uptime (30d)

N/A

Pre-launch

What AEGIS logs

The following is the complete list of data we retain per request. If it is not listed here, we do not log it.

Timestamp

Not stored — not useful to us without identity

Source IP address

Never written to disk; only used for the TCP handshake

Target domain or URL

Encrypted in transit; exit node sees destination, not identity

Wallet address (for billing)

Yes

Required for deducting balance; not linked to traffic

Bytes consumed

Yes

Aggregated per session for billing; no per-request breakdown

Session duration

Yes

Start/end time only, for metering

Country requested

Yes

Used to route to the correct exit node

Payment transactions

On-chain

Immutable Solana ledger; not controlled by AEGIS

How the routing works

When you make a request through AEGIS, your traffic takes the following path. No single hop in this chain can see both who you are and what you are fetching.

Client → OrchestratorAuthenticated with your API key. The orchestrator knows your wallet but never sees your target URL — it only assigns you a node.

Orchestrator → Exit nodeThe orchestrator tells the exit node to expect a connection. The node does not know your identity — only the session ID and requested country.

SOCKS5 tunnelYour client connects directly to the exit node via an encrypted SOCKS5 tunnel. The orchestrator is no longer in the path.

Exit node → InternetThe exit node forwards your request from a residential or datacenter IP in the target country. The destination server sees only the exit node IP.

Metering → BillingByte counts are reported back to the orchestrator. Your wallet is debited. No traffic content is logged.

Legal requests received

We publish every government or law enforcement request we receive. Because our architecture is designed so we have nothing to hand over, our response to all data requests is the same: we have no data responsive to this request.

PeriodReceivedCompliedChallenged

Q1 2026000

Q2 2026000

Warrant canary: as of May 2026, AEGIS has never received a national security letter, FISA order, or gag order of any kind. This statement will be removed if that changes.

Source code

AEGIS is open source. The smart contracts, orchestrator, node daemon, SDKs, and this web app are all publicly auditable. We encourage security researchers to review our code and disclose vulnerabilities responsibly.

Smart contracts (Anchor/Solana)Public

Orchestrator serverPublic

Node daemonPublic

TypeScript SDKPublic

Python SDKPublic

Chrome extensionPublic

Smart contract auditPending — pre-mainnet