Cryptospecting

VIDEO SUMMARY // VERIFIED 2026-10-17

Run your own PulseChain node: David Feder's walkthrough

Short answer

In an August 2025 video, validator operator David Feder responds to a post by Richard Heart urging developers to run their own node, and shows the hardware and a free install script. A node is an execution client plus a consensus client and needs no PLS deposit; only a validator needs 32,000,000 PLS. Feder also sells hardware and hosted nodes — this summary is not an endorsement.

Source video: David Feder
How to make a PulseChain Node · published 7 Aug 2025 · watch on YouTube

Why run your own node?

Feder opens with a post by Richard Heart on X, shown on screen, telling developers to run their own node (at 0:29). The arguments in that post, as Feder reads them: everything runs faster, the chain fits on less than two terabytes, and you no longer depend on someone else’s RPC endpoint, which may disable features or fail without explanation. Your own node also shows in its logs whether a failed query was your mistake or an upstream problem.

What is a node?

According to Feder, a PulseChain node is simply a computer that runs the client software around the clock, just like a Bitcoin or Ethereum node (at 1:17). Since the Ethereum merge it has two parts: an execution client — Feder calls it Geth, which on PulseChain is the go-pulse fork — and a beacon (consensus) client. Together they make a node (at 5:47). Feder’s setup uses go-pulse with prysm-pulse (at 1:49).

This matches the official code. PulseChain publishes two execution clients (go-pulse, erigon-pulse) and two consensus clients (prysm-pulse, lighthouse-pulse); a node runs one of each. A node only downloads, checks and serves the chain. A validator additionally deposits 32,000,000 PLS and signs blocks — see PulseChain validators. The node in this video is not a validator and needs no deposit.

What hardware does it need?

Feder’s own kit is a small Intel/ASUS NUC computer with 64 GB of RAM and a 4 TB SSD, plus a portable monitor, keyboard and mouse, and a USB stick with Ubuntu 22.04 desktop (at 2:18, at 3:14). By Feder’s estimate the chain took about 1.1 TB at the time, so a 2 TB drive would do for now and 4 TB avoids an upgrade later. The machine also needs a reliable internet connection, a battery backup and a static IP address or a dynamic DNS service, because it has to stay online 24/7 (at 4:17).

The disk figures are Feder’s and Heart’s; Cryptospecting has not measured them, and chain data grows over time.

How does the install work?

Feder points to a free text file of commands on his GitLab: running lines 1 to 19 in a terminal on Ubuntu sets up a node that is not a validator (at 4:42). Feder promises refreshed step-by-step videos later.

A note of caution: this is a third-party script that runs with administrator rights. Read it before running it, and compare it with the official client repositories and the PulseChain node guide listed in the sources.

What does the video sell?

Feder runs ValidatorStore and uses the video to advertise pre-built node kits and a dedicated hosted node with personal support (at 6:40). Feder also says more people running nodes at home makes the chain more decentralized (at 8:53). The portal’s directory lists ValidatorStore as a commercial service; it is mentioned here for disclosure, not as a recommendation.

Sources // last verified 2026-10-17

  1. T3 · Community David Feder — How to make a PulseChain Node (2025-08-07)
  2. T1 · Primary go-pulse — official PulseChain execution client
  3. T1 · Primary prysm-pulse — official PulseChain consensus client
  4. T1 · Primary pulsechain-testnet — official node guide and client choice
  5. T2 · Official pulsechain.com — 32,000,000 PLS per validator

Source tiers are explained in Sources & methodology.