Skip to main content

Server-Based Nodes

Conduct Protocol aims to create a mobile-first blockchain while addressing uptime challenges through server-based nodes. Here's a detailed guide to setting up these nodes.

Overview​

Conduct Protocol strives to be a mobile-first blockchain, but the uptime restrictions imposed on mobile devices introduces complications

Server-based nodes provide:

  • Full uptime maintenance - Continuous operation without mobile power constraints
  • Guaranteed P2P synchronization - Reliable source for network synchronization
  • Staking participation - Full participation in the staking process (with same restrictions as mobile stakers)

Prerequisites​

Before setting up a server-based node, ensure you have:

  • Docker - Container runtime for running the node
  • Google Cloud Platform (recommended, but not required)
  • Stable internet connection - For consistent network participation
  • Adequate storage - For blockchain data storage

Setup Instructions​

1. Create Data Directory​

First, create a directory to store blockchain data:

mkdir -p $HOME/conduct_data

2. Create Docker Container​

Run the following command to create and start your Conduct Protocol node:

docker run -d \
  --name=conduct-node \
  --restart=unless-stopped \
  --pull=always \
  -v $HOME/conduct_data:/data \
  -p 5467:5467/tcp \
  -p 5468:5468/udp \
  conductprotocol/node:latest \
  --conduct-is-awesome \
  --data-dir /data \
  --config http://storage.googleapis.com/conduct-protocol-testnet

Container Arguments Explained​

  • --name=conduct-node: Assigns a stable container name for easy management
  • --restart=unless-stopped: Automatically restarts the container on failure
  • --pull=always: Always pulls the latest Docker image before starting
  • -v $HOME/conduct_data:/data: Mounts local directory for persistent data storage
  • -p 5467:5467/tcp: Exposes the RPC port for API access
  • -p 5468:5468/udp: Exposes the P2P port for network communication

Next Steps​

Once your server-based node is running, you can:

  1. Monitor the node logs: docker logs -f conduct-node
  2. Check the node status via the JSON-RPC API
  3. Participate in the network's consensus mechanism

Troubleshooting​

Common Issues​

  • Port conflicts: Ensure ports 5467 and 5468 are available
  • Storage issues: Verify sufficient disk space in $HOME/conduct_data
  • Network connectivity: Check firewall settings for the required ports

Monitoring​

To monitor your node's health and performance:

# View container logs
docker logs -f conduct-node

# Check container status
docker ps | grep conduct-node

# View resource usage
docker stats conduct-node