Pulse Node Manager

INDEPENDENT PULSECHAIN TOOLING

Your node, with a clear path.

Pulse Node Manager turns hardware checks, Docker setup, sync visibility, and local RPC handoff into one calm workflow.

Choose your platform Open release page
Engineering preview macOS · Linux · Windows Loopback RPC only

INSTALLATION

Install it one small step at a time.

This is a command-line app with a local dashboard. There is no graphical installer yet. Choose your computer below and copy the commands exactly.

What this public pre-preview does

It tests downloading, checking, unpacking, and platform binary startup. The archive includes the signed runtime manifest needed to start a real Testnet V4 node on each computer. Sync speed and recovery behavior are still being qualified, so keep the local RPC private.

⌘MACOS

macOS (Apple silicon)

Use this on a Mac with an Apple M-series chip. Intel Macs need a later package.

  1. Install Docker Desktop. Follow the official macOS instructions. Open the downloaded DMG, drag Docker to Applications, open it, and accept Docker's terms. If macOS asks for a password or permission, that is Docker's installer asking; approve it only in the official Docker app. Wait until Docker says it is running.
  2. Download two files. On the release page, download the macOS arm64 `.tar.gz` file and its `.sha256` file. Do not download the GitLab “source code” archive.
  3. Open Terminal. Terminal is in Applications → Utilities. Put both downloaded files in Downloads.

Run each command one line at a time in this same Terminal window, in the order shown.

cd ~/Downloads
shasum -a 256 -c pulse-node-manager-macos-arm64.tar.gz.sha256
tar -xzf pulse-node-manager-macos-arm64.tar.gz
chmod +x pns-macos-arm64
./pns-macos-arm64 --version
./pns-macos-arm64 --help

The checksum must say `OK`. A version number and help text mean the package started correctly.

Apple silicon · arm64 · Terminal
◈LINUX

Linux (x86_64)

These commands are written for Ubuntu and Debian on an Intel or AMD 64-bit computer.

  1. Install Docker Engine. Follow the official Ubuntu instructions in Terminal. When Ubuntu asks for your password after `sudo`, type the password you use to sign in; the characters stay invisible, then press Enter. Verify with `sudo docker run hello-world`. If you want to type `docker` without `sudo`, follow Docker's official Linux post-install steps. The manager does not change your user groups.
  2. Download two files. On the release page, download the Linux x86_64 `.tar.gz` file and its `.sha256` file. Do not download the GitLab “source code” archive.
  3. Open Terminal. Put both downloaded files in Downloads.

Run each command one line at a time in this same Terminal window, in the order shown.

cd ~/Downloads
sha256sum -c pulse-node-manager-linux-x86_64.tar.gz.sha256
tar -xzf pulse-node-manager-linux-x86_64.tar.gz
chmod +x pns-linux-x86_64
./pns-linux-x86_64 --version
./pns-linux-x86_64 --help

The checksum must say `OK`. A version number and help text mean the package started correctly.

Ubuntu/Debian · x86_64 · Terminal
⊞WINDOWS

Windows (x86_64)

Use a 64-bit Intel or AMD Windows computer and a normal PowerShell window. Do not double-click the file or choose Run as administrator for these package commands.

  1. Install Docker Desktop. Follow the official Windows instructions. Run the installer, keep the recommended WSL 2 option selected, restart Windows if it asks, then open Docker Desktop from Start. Accept Docker's terms. If Docker asks you to sign in or Windows shows a permission popup, follow Docker's official screen; PNS has no Docker account and cannot complete that step for you. Wait until Docker says it is running.
  2. Download two files. On the release page, download the Windows x86_64 `.zip` file and its `.sha256` file. Do not download the GitLab “source code” archive.
  3. Open normal PowerShell. Click Start, type PowerShell, and choose Open, not Run as administrator. Put both downloaded files in Downloads. The box below lists separate commands: run one line, press Enter, wait for it to finish, and then run the next line in this same window.

Run each command one line at a time in this same normal PowerShell window, in the order shown.

Set-Location $HOME\Downloads
$expected = ((Get-Content .\pulse-node-manager-windows-x86_64.zip.sha256).Trim() -split '\s+')[0].ToLower()
$actual = (Get-FileHash .\pulse-node-manager-windows-x86_64.zip -Algorithm SHA256).Hash.ToLower()
if ($expected -ne $actual) { throw "Checksum does not match" }
Expand-Archive .\pulse-node-manager-windows-x86_64.zip -DestinationPath .\pns
Set-Location .\pns
.\pns-windows-x86_64.exe --version
.\pns-windows-x86_64.exe --help

This block uses your normal user permissions. No error from the checksum block, a version number, and help text mean the package started correctly. Docker's installer may separately ask for administrator approval.

Windows 10/11 · x86_64 · PowerShell (normal user)

START TESTNET V4

Run the real node after the package check.

Extract the archive, leave the signed manifest beside the binary, and run one command at a time. The app checks Docker, resources, disk, ports, and image policy before downloading node data.

macOS Terminal
./pns-macos-arm64 up --network testnet-v4 --data-root "$HOME/pns/testnet-v4" --manifest ./pulsechain.candidate.signed.json
Linux Terminal
./pns-linux-x86_64 up --network testnet-v4 --data-root "$HOME/pns/testnet-v4" --manifest ./pulsechain.candidate.signed.json
Windows PowerShell
.\pns-windows-x86_64.exe up --network testnet-v4 --data-root "$HOME\pns\testnet-v4" --manifest .\pulsechain.candidate.signed.json

When the dashboard says Synced, it will show the chain ID and local RPC for wallet setup. If startup fails, add --debug and share the redacted report after reviewing it.

BEFORE YOU START

Check these four things.

  • At least 32 GiB of computer memory and 8 CPU cores
  • At least 1.5 TB free for mainnet or 1 TB for Testnet V4
  • Docker is installed, open, and allowed to use the required memory
  • Stable internet access and a local SSD for chain data
If Docker is not installed yet Use Docker's official instructions for macOS, Ubuntu Linux, or Windows. PNS checks Docker and explains the missing requirement before it downloads node data.

NETWORKS

Know what your local RPC will hand off.

Mainnet and Testnet V4 use separate ports, data folders, Docker projects, and labels so a wallet connection is unambiguous.

MAINNETPLS

PulseChain mainnet

Chain ID
369
Local RPC
127.0.0.1:8545
Default pair
Go-Pulse + Prysm-Pulse
Initial storage
1.5 TB free
TESTNET V4tPLS

PulseChain Testnet V4

Chain ID
943
Local RPC
127.0.0.1:18545
Default pair
Go-Pulse + Prysm-Pulse
Initial storage
1 TB free
When the dashboard says Synced, add the local RPC to MetaMask or Rabby on the same computer. Follow MetaMask's custom network guide or open Rabby's official app site. Use the exact network name, RPC URL, chain ID, currency and explorer values shown by the dashboard. Never share a seed phrase or private key.

THE PATH

Understand every step before it runs.

The manager explains the consequences first, then keeps the local node observable from setup through RPC handoff.

01

Check this computer

See Docker, disk, memory, ports, and architecture before anything is downloaded.

02

Choose where data lives

Pick a folder for separate execution and consensus data. Mainnet and testnet stay apart.

03

Watch the sync

Follow clients, peers, disk growth, and clear readiness states from the dashboard.

04

Use your node

When readiness is proven, copy the loopback RPC, chain ID, currency, and explorer link.

RELEASES YOU CAN TRACE

One release page connects the build to the install.

Each version is built through the GitLab pipeline on Linux, macOS, and Windows jobs. The release page collects the packages and notes in one place, while this page keeps prerequisites and platform steps in view.

Browse release notes
◆Linuxx86_64 archiveCI
⌘macOSarm64 archiveCI
⊞Windowsx86_64 archiveCI
Rust gates, browser tests, and secret scanning run before release metadata.

DESIGNED FOR SAFE LOCAL USE

No seed phrases. No silent host changes.

The manager never asks for wallet secrets, installs Docker without consent, opens remote RPC, or silently adopts an existing data directory.

Read the source