ChainVerse2

ChainVerse2 is a decentralized blockchain network that demonstrates peer-to-peer communication and distributed ledger management. This project allows multiple nodes to communicate via WebSockets, mine blocks, and synchronize their chains, ensuring a secure and immutable blockchain.

Features

Peer-to-Peer Communication: Nodes use WebSockets to exchange data, broadcast transactions, and synchronize chains.
Proof of Work (PoW): Implements mining with cryptographic puzzles to add new blocks to the blockchain.
Decentralized Transactions: Nodes can independently create and broadcast transactions, which are added to the blockchain through mining.
Chain Validation: Each node independently validates the blockchain to ensure its integrity and security.
Genesis Block: The initial block of the blockchain is created upon startup.

Technology Stack

Node.js: JavaScript runtime for server-side scripting.
Express.js: Web framework for handling HTTP requests.
WebSocket: Protocol for real-time, bidirectional communication between nodes.
Crypto: Provides cryptographic hashing (SHA-256) for block validation.

Getting Started

Prerequisites

Node.js installed on your machine.

Installation

Clone the repository:

git clone https://github.com/yourusername/multinode-blockchain.git
cd multinode-blockchain

Install dependencies:
```
npm install
```

Running the Application

Start a node (specify a port if needed):
```
node app.js 3000
```
For each additional node, open a new terminal window and run:
```
node app.js <port>
```
The WebSocket server will automatically run on port + 1 (e.g., if you run on port 3000, the WebSocket server will use port 3001).

Testing the Blockchain

Transactions are created and mined at each node.
Nodes automatically sync their chains when a peer joins or broadcasts.
Example transactions (Alice sending 50 to Bob, Bob sending 25 to Charlie) are pre-configured to demonstrate functionality.

API Endpoints

GET /chain: Returns the current blockchain.
POST /transaction: Adds a new transaction to the pending transactions (requires JSON body with sender, receiver, and amount).