Node update for existing node operators - April 2025
If you've already set up a Webhash node, please rerun the updated setup script to apply three important changes:
Provide your own Base Sepolia WebSocket URL.
Provide your own Ethereum Mainnet WebSocket URL.
Choose a custom storage directory.
🛠 Step-by-Step for Existing Users
1️⃣ Rerun the Setup Script
Open your terminal and run:
curl -fsSL https://raw.githubusercontent.com/WebHash-eth/hash-node-setup/refs/heads/main/scripts/setup.sh > setup.sh && chmod +x setup.sh && ./setup.sh2️⃣ Enter Base Sepolia WebSocket URL & Ethereum Mainet WebSocket URL
🔹 Option A: Using Alchemy (Recommended)
You only need one app to get both URLs:
Go to the Alchemy Dashboard and log in
Click "Create App"
Name: Webhash Node
Chain: Base
Network: Base Sepolia
After the app is created, click "Configure" (top right)
Under "Add Chains", enable Ethereum → Mainnet
Now go back to the app dashboard:
Click the "Network" tab
Copy the WebSocket URL for Base Sepolia
Then switch to Ethereum Mainnet and copy its WebSocket URL
✅ Examples:
Base Sepolia:
wss://base-sepolia.g.alchemy.com/v2/your-api-keyEthereum Mainnet:
wss://eth-mainnet.g.alchemy.com/v2/your-api-key
📌 Ensure both URLs start with wss://. HTTP URLs are not supported.
🔹 Option B: Using QuickNode
Go to QuickNode
Create two endpoints:
One for Base Sepolia
One for Ethereum Mainnet
Go to each endpoint’s dashboard
Copy the WebSocket URL from the WebSockets tab
✅ Examples:
Base Sepolia:
wss://your-node.base-sepolia.quiknode.pro/your-key/Ethereum Mainnet:
wss://your-node.ethereum.quiknode.pro/your-key/
📌 Again, make sure to copy the wss:// URLs only. HTTP endpoints won't work.
4️⃣ Enter Your Email for Updates
After entering your Ethereum Mainnet WebSocket URL, you’ll be prompted to enter your email: Please enter your email address: This helps us send you important updates, community news, and reward announcements related to your node activity. 📌 Your email is stored securely and never shared.
5️⃣ Select Storage Directory You'll see this prompt:
Do you want to use a separate disk for storage? (y/n)Type
yto specify a custom directory (e.g.,/mnt/webhash)Type
nto use the default path:/root/.webhash-node-data
The script will continue automatically after your input.
✅ Example Output:
✓ Using default path: /root/.webhash-node-data
Moving IPFS data to /root/.webhash-node-data/ipfs
Existing IPFS dir: /var/lib/docker/volumes/webhash-node_node_data/_data
Moving export data to /root/.webhash-node-data/export
Existing export dir: /var/lib/docker/volumes/webhash-node_node_export/_data
Starting node with public IP: xxx.xxx.xxx.xxx...6️⃣ Confirm Node Is Running
After setup completes, your terminal will show:
✔ Container node Healthy
✔ Container pinner Started
Waiting for node container to be ready...
Configuring node...
Node started with peer ID: 12D3KooW...
Registering node with peer ID: 12D3KooW...
Node registered successfully with peer ID: 12D3KooW...✅ If you see “Node registered successfully”, your node is running perfectly!
🧹 Optional: Clean Up Old Docker Volumes
Free up space by removing legacy volumes after confirming your new setup is working:
sudo docker volume rm webhash-node_node_data
sudo docker volume rm webhash-node_node_export⚠️ Only perform this cleanup after verifying your node is healthy and registered.
📢 Final Step – Join the Webhash Community
Once your node is successfully registered, you’ll see a message prompting you to join our official Discord and Telegram channels. 👉 Join our Discord to claim your exclusive “🥷Node Ninja” role and connect with other node operators!
Stay connected, get support, and earn early contributor perks by being part of the Webhash community.
⚠️ Troubleshooting & Support
If you run into any issues while doing this, we’re here to help!
📌 Create a support ticket on discord – Our team will assist you instantly.
Last updated