Power the Web³ Hive - Infrastructure Setup Guide

Complete step-by-step instructions to beecome part of the Web³ Hive infrastructure. Set up your $WHIVE wallet, Web³ node, and start earning honey rewards through distributed computing on Windows, Linux, and macOS systems

📥 Download Web³ Hive Software

Get the latest release from our official GitHub repository to power the Web³ infrastructure

1

Download & Install $WHIVE Wallet

Download the Windows release from GitHub and extract the files to a dedicated folder to beecome part of the hive.

# Create a dedicated folder for your bee mkdir C:\Whive cd C:\Whive # Extract whive-22.2.2-win64.zip here # Run whived.exe to start your bee node daemon
💡 Tip: Windows Defender may flag the executable. Add an exception for the Whive folder to avoid interruptions.
2

Configure Your Web³ Node

Create a configuration file to optimize your Web³ Hive node settings.

# Create whive.conf in your $WHIVE data directory # Usually located at: %APPDATA%\Whive\ server=1 daemon=1 rpcuser=your_username rpcpassword=your_secure_password rpcallowip=127.0.0.1 rpcport=1868
⚠️ Security: Use a strong, unique password for RPC access. Never share your RPC credentials.
3

Deploy Web³ Infrastructure

Deploy your Web³ Hive node and start earning honey rewards ($WHIVE) through distributed computing with your Windows system.

# Open Command Prompt as Administrator cd C:\WHIVE # Start your bee node daemon whived.exe -daemon # Wait for swarm synchronization, then start earning honey rewards whive-cli.exe generate 1 # Check your bee status whive-cli.exe getmininginfo
1

Install Dependencies

Install required packages for building or running your node to beecome part of the hive.

# Ubuntu/Debian (Ubuntu 22+ required for prebuilt binaries) sudo apt update sudo apt install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils python3 # CentOS/RHEL/Fedora sudo yum groupinstall "Development Tools" sudo yum install openssl-devel libevent-devel
💡 Note: Prebuilt Linux binaries require Ubuntu 22.04 or newer. For older distributions, compile from source.
2

Download & Extract Whive

Get the Linux binaries or compile from source to set up your bee.

# Download latest release (Ubuntu 22+ required) wget https://github.com/whiveio/whive/releases/download/22.2.2/whive-22.2.2-x86_64-linux-gnu.tar.gz # Extract files tar -xzf whive-22.2.2-x86_64-linux-gnu.tar.gz # Move to system directory (optional) sudo mv whive-22.2.2/bin/* /usr/local/bin/
3

Configure & Start Node

Set up configuration and start your bee daemon to join the swarm.

# Create data directory mkdir -p ~/.whive # Create configuration file cat > ~/.whive/whive.conf << EOF server=1 daemon=1 rpcuser=miner rpcpassword=$(openssl rand -hex 32) rpcallowip=127.0.0.1 rpcport=1868 gen=1 genproclimit=4 EOF # Start your bee daemon whived -daemon # Check your bee status whive-cli getinfo
4

Monitor Your Bee

Monitor your bee's progress and swarm synchronization.

# Check your bee info whive-cli getmininginfo # Check honey rewards balance whive-cli getbalance # View recent honey reward transactions whive-cli listtransactions # Check swarm connections whive-cli getconnectioncount
1

Install Prerequisites

Install Homebrew and required development tools to set up your bee.

# Install Homebrew (if not already installed) /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" # Install dependencies brew install autoconf automake libtool pkg-config openssl libevent
💡 Note: You may need to install Xcode Command Line Tools: xcode-select --install
2

Download Whive for macOS

Get the macOS binaries from GitHub releases to join the swarm.

# Create directory for your bee mkdir ~/Whive && cd ~/Whive # Download latest macOS release curl -L -O https://github.com/whiveio/whive/releases/download/22.2.2/whive-22.2.2-osx64.tar.gz # Extract files tar -xzf whive-22.2.2-osx64.tar.gz # Make binaries executable chmod +x whive-22.2.2/bin/*
3

Configure Wallet

Set up your bee configuration for macOS.

# Create data directory mkdir -p ~/Library/Application\ Support/Whive # Create configuration file cat > ~/Library/Application\ Support/Whive/whive.conf << EOF server=1 daemon=1 rpcuser=whiveminer rpcpassword=$(openssl rand -hex 24) rpcallowip=127.0.0.1 rpcport=1868 gen=1 genproclimit=2 EOF
⚠️ macOS Security: You may need to allow the application in System Preferences > Security & Privacy when first running.
4

Deploy Web³ Infrastructure

Launch your bee daemon and start earning honey rewards.

# Navigate to Whive directory cd ~/Whive/whive-22.2.2/bin # Start your bee daemon ./whived -daemon # Wait for swarm sync, then check your bee status ./whive-cli getmininginfo # Generate new address for honey rewards ./whive-cli getnewaddress

🔧 Common Bee Issues & Solutions

Problem: Bee won't sync with swarm

Solution:

  • Ensure your internet connection is stable
  • Check firewall settings - allow your bee through port 8372 (P2P) and 1868 (RPC)
  • Try connecting to specific swarm peers: whive-cli addnode "peer_ip" "add"
  • Delete peers.dat and restart your bee if stuck

Problem: Bee shows 0 hashrate

Solution:

  • Ensure your bee is fully synchronized with the swarm first
  • Check if your bee is active: whive-cli getmininginfo
  • Restart your bee: whive-cli setgenerate true 4
  • Verify CPU isn't overloaded by other processes

Problem: High CPU usage

Solution:

  • Reduce bee activity threads: whive-cli setgenerate true 2
  • Add genproclimit=2 to whive.conf
  • Monitor temperature to prevent overheating
  • Consider running your bee during off-peak hours

Problem: RPC connection failed

Solution:

  • Verify whive.conf has correct RPC settings
  • Ensure daemon is running: ps aux | grep whived
  • Check RPC port isn't blocked: netstat -an | grep 1868
  • Restart daemon if configuration changed

⚖️ Terms of Use & Disclaimers

Swarm Participation Disclaimer

Joining the Whive swarm involves computational work and energy consumption. Users are responsible for:

  • Ensuring compliance with local laws and regulations regarding digital mining activities
  • Managing electricity costs and hardware wear from continuous bee operations
  • Understanding that honey rewards ($WHIVE) are not guaranteed and depend on swarm conditions
  • Monitoring system temperature and preventing hardware damage from overheating

Software Disclaimer

Whive Protocol software is provided "as-is" without warranty of any kind. Users acknowledge:

  • The software is experimental and may contain bugs or security vulnerabilities
  • Users are responsible for keeping their wallet and private keys secure
  • The development team is not liable for any loss of funds or damages
  • Users should backup their wallet.dat file regularly

Swarm Risks

Participation in the Whive swarm involves inherent risks:

  • The swarm may experience downtime, forks, or technical issues
  • Difficulty adjustments may affect honey reward production
  • $WHIVE values are volatile and may result in financial loss
  • Swarm consensus changes may require software updates

Privacy Notice

Whive operates on a public blockchain where:

  • All transactions are permanently recorded and publicly visible
  • IP addresses may be associated with network activity
  • Users should implement appropriate privacy measures if desired
  • The protocol does not collect personal information directly

By joining the Whive swarm, you acknowledge understanding and acceptance of these terms and risks.