Scope. These findings are generated by the current Trace Lab engine from the synthetic sample trace. They describe requests captured in one HAR file. They do not describe network-layer metadata, on-chain data, or what any host does after receiving a request.
Three exposure surfaces
| Surface | What may be exposed | Who may observe it | What NODAL shows today |
|---|---|---|---|
| Network | IP address, contacted hosts (DNS, TLS server name), timing and size of requests | Internet, Wi-Fi and VPN providers; every receiving server; anyone on the network path | Not covered |
| Request | Wallet addresses, transaction hashes, ENS names and chain IDs in URLs, headers and bodies | The receiving host and anyone it shares data with | Verified in sample |
| On-chain | Addresses, balances, transaction history and contract interactions | Anyone | Partial · via requests |
Network privacy systems, such as the Nym mixnet, address the network surface. NODAL addresses the request surface. They are different exposure surfaces; NODAL is not integrated with, endorsed by or working with Nym. A combined network-and-request analysis is Exploring: not implemented and not tested.
Per finding: sample trace
Values are redacted. The same findings are explorable in Trace Lab.
What NODAL cannot show
| Not shown | Why |
|---|---|
| The user’s IP address, network path or timing patterns | A HAR file records requests, not the network. This is the network layer. |
| On-chain data itself | NODAL does not read the chain. It only sees on-chain identifiers that appear inside requests. |
| What a host does after receiving data | Storage, sharing and retention happen on the host’s servers, outside the capture. |
| Response bodies, WebSocket frames, service-worker and extension traffic | Not analysed by the current engine, or not present in the HAR. |
| Hashed, encrypted, compressed or obfuscated values | Detection works on visible text forms (exact, lower-case, without 0x). |
| Other journeys, builds, browsers or regions | A report covers one capture of one scenario. |
| Whether a flow is intended, lawful or compliant | NODAL shows evidence. Triage and legal judgement belong to the team. |
| Combined network-and-request analysis | Exploring Not implemented or tested. |