Fig Search

This network protocol enables fully encrypted, anonymous data transmission through decentralized nodes without relying on centralized servers.

When a browser sends a request, it passes through a local proxy that encrypts the data and sends it via Yellow RPC nodes over WebSocket. The request reaches a miner, who processes it and, if needed, stores large encrypted data on IPFS. The response then travels back to the browser through the same path, while the proxy automatically tracks usage and pays for the service in DataCoin.

Unlike VPNs or Tor, this protocol doesn’t route traffic through fixed or traceable relay servers. Each transaction is ephemeral, end-to-end encrypted, and unlinkable, meaning:

No single entity can observe both source and destination.

Requests can’t be correlated or tracked across sessions.

Payments and data flow are handled autonomously, removing trust in intermediaries.

In short, it’s a self-paying, decentralized, and untraceable network layer for private browsing and data exchange — faster, more private, and harder to surveil than traditional VPN or Tor systems.

Full Flow with Encryption & Data Handling

1. Browser → Local Proxy

The browser generates an ephemeral session key (per session) and optionally a long-term identity key for signing.

Each request is encrypted end-to-end using the miner’s public key (asymmetric encryption) or a hybrid scheme:

Generate a random symmetric key for the request.

Encrypt the request payload with the symmetric key.

Encrypt the symmetric key with the miner’s public key.

The encrypted payload, along with metadata (nonce, session ID, signature), is sent to the local proxy.

Proxy increments its internal request counter for micropayments.

1. Local Proxy → Yellow RPC Nodes

Proxy maintains a persistent WebSocket connection to the Yellow RPC network.

Requests are forwarded as encrypted blobs; Yellow nodes cannot decrypt content.

Routing headers are minimal and ephemeral to prevent correlation of source/destination.

Yellow nodes select a miner based on load, latency, and capability.

1. Miner Receives & Decrypts

Miner receives the encrypted request via Yellow RPC nodes.

Decryption steps:

Use miner’s private key to decrypt the symmetric session key (if hybrid encryption is used).

Use the decrypted session key to decrypt the actual request payload.

Miner verifies the request signature to ensure authenticity.

Request is now ready for processing.

1. Miner Processing & Storage

Miner performs the requested operation:

Computation or data retrieval.

For large results, the miner generates a new symmetric key for encrypting the data.

Data is split into chunks (if needed), encrypted, and stored on IPFS.

The miner generates a manifest (CID + metadata) that describes the encrypted chunks.

1. Response Encryption

For small responses, the miner may use the browser’s public key for asymmetric encryption.

For large responses via IPFS:

The symmetric key encrypting the chunks is itself encrypted with the browser/session public key.

Only the intended client can decrypt the symmetric key and reconstruct the data.

The encrypted response or IPFS manifest is sent back through Yellow RPC nodes to the proxy and then to the browser.

1. Proxy & Browser Receive Response

Proxy may partially decrypt metadata for accounting.

Browser uses its session private key to decrypt the session key, then decrypts the payload.

If the payload points to IPFS, browser fetches the encrypted chunks and decrypts them locally.

End-to-end encryption guarantees that intermediaries never see the plaintext.

1. Payment & Accounting

Proxy batches request counts and prepares DataCoin micropayment commitments.

Settled off-chain via state channels or periodically on-chain.

This ensures miners are compensated without exposing usage patterns externally.

1. Security & Privacy Highlights

Asymmetric encryption ensures only the miner can read the request.

Ephemeral session keys prevent linking multiple requests.

Hybrid encryption optimizes for large data.

Stateless Yellow nodes prevent metadata leakage.

Chunked encrypted storage on IPFS ensures large data remains secure and unlinkable.