Node Communication & Architecture

The Webhash Node Network consists of decentralized storage nodes responsible for storing, verifying, and distributing website data on the IPFS-based Webhash Protocol. These nodes participate in Selective Replication, Content Retrieval, and On-Chain Verification, ensuring permanent and censorship-resistant website hosting.

This document provides a detailed technical overview of the architecture, communication protocols, and verification mechanisms used by Webhash Storage Nodes. Node Type: Storage Nodes

• Function: Store and serve website content via IPFS.

• Responsibilities:

  • Pin website data and confirm on-chain storage verification.

  • Participate in Selective Replication to ensure redundancy.

  • Provide content upon retrieval requests from Webhash users.

Node Communication Protocols: Nodes within the Webhash Network communicate using a combination of IPFS DHT, Libp2p PubSub, and blockchain-based registries to ensure efficient content storage, retrieval, and verification.

A. IPFS DHT (Distributed Hash Table)

• Purpose: Enables nodes to locate content stored across the network.

• Functionality:

  • Each node maintains a routing table to find peers storing a specific CID.

  • When a user requests content, the closest node with the required CID serves it.

  • Reduces network congestion by routing queries to the most efficient storage node.

B. Libp2p PubSub (Publish-Subscribe Messaging)

• Purpose: Enables real-time event broadcasting between nodes.

• Functionality:

  • Nodes subscribe to relevant content topics (CID updates, storage status).

  • When new content is uploaded, it is broadcasted to eligible storage nodes.

  • Validator nodes listen for storage confirmations and perform audits.

C. Webhash On-Chain Registry (Ethereum Smart Contract)

• Purpose: Stores metadata and verification proofs for decentralized content storage.

• Functionality:

  • Records which nodes store which CID.

  • Nodes submit storage proofs periodically to confirm they are storing data.

  • Validator nodes flag underperforming or fraudulent nodes for penalties.

Node Identification & Registration: Each Webhash node is uniquely identified using two-layer authentication:

A. IPFS Peer ID

• Each storage node has a Peer ID derived from its public key.

• Ensures secure communication within the IPFS network.

B. Webhash Node ID (On-Chain Identity)

• Nodes register using an EVM-compatible address.

• The Ethereum smart contract links:

  • Peer ID → Unique IPFS node identity.

  • Node Address → On-chain representation of the node.

• Benefits:

  • Prevents Sybil attacks by linking nodes to stake-based verification.

  • Allows transparent tracking of storage contributions.

Content Pinning & Storage Verification: To ensure content remains permanent and verifiable, Webhash nodes use on-chain proof mechanisms.

A. Pinning Process

1. A user uploads website content to Webhash.

2. A CID (Content Identifier) is generated and assigned to a set of storage nodes.

3. Nodes pin the content using IPFS pinning services.

B. On-Chain Storage Confirmation

1. Storage nodes submit cryptographic proofs that they have pinned the CID.

2. The proof is recorded on-chain, associating the CID with the responsible nodes.

3. Validator nodes periodically verify content availability using zk-SNARKs.

4. If a node fails verification, it is:

   • Penalized in the reputation system.

   • Replaced with a new storage node using Selective Replication.