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.

Engineering preview macOS · Linux · Windows Loopback RPC only

INSTALLATION

Install it with one command.

This is a command-line app with a local dashboard. Choose your computer below and copy one installer command. The prerequisites and official dependency prompts stay visible.

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.

◈LINUX

Linux (x86_64 or ARM64)

The one-command installer supports apt-based Ubuntu and Debian hosts on Intel, AMD, and ARM64. It checks Docker Engine and Compose, offers the official OS package path, verifies the signed release, and installs a user-owned launcher.

  1. Check the prerequisites. Use an Intel, AMD, or ARM64 Linux host with a local SSD, enough memory and disk for the selected network, and a stable connection. Linux dependency setup may ask for your sudo password and a new login after Docker group membership changes.
  2. Copy one command into Terminal. Run it as your normal user. It stops with the exact official Docker link if the distribution is not apt-based.
Installer command
curl --fail --location --proto '=https' --tlsv1.2 'https://gitlab.com/g4mm4org/PulseNodeManager/-/raw/main/installer/install.sh' | sh -s --

Add -y after sh -s -- to accept the install prompts, or add --debug for a private redacted installer report. The official Docker Engine instructions remain the recovery path for unsupported distributions.

Ubuntu/Debian · x86_64 or ARM64 · Terminal
⊞WINDOWS

Windows (x86_64)

The one-command installer uses Windows Package Manager to offer Docker Desktop, verifies the signed release, and installs under your user profile. Use a normal PowerShell window.

  1. Check the prerequisites. Use 64-bit Windows 10 or 11 with WSL 2 and hardware virtualization available. Docker Desktop may ask for administrator approval, terms acceptance, sign-in, WSL setup, or a restart; those prompts belong to Docker.
  2. Copy one command into PowerShell. Run it as your normal user. The script asks before using winget or updating your user PATH.
Installer command
$s=(Invoke-WebRequest -UseBasicParsing 'https://gitlab.com/g4mm4org/PulseNodeManager/-/raw/main/installer/install.ps1').Content; & ([scriptblock]::Create($s))

Add -Yes after the final )) to accept the install prompts, or add -Debug for a private redacted installer report. Docker's own administrator, license, WSL, virtualization, or restart prompts still require its screen.

Windows 10/11 · x86_64 · PowerShell

START TESTNET V4

Run the real node after installation.

Open a new shell if the installer changed your PATH, choose a data folder, and run the user-owned launcher. The app checks Docker, resources, disk, ports, and image policy before downloading node data.

macOS or Linux Terminal
pns up --network testnet-v4 --data-root "$HOME/pns/testnet-v4" --manifest "$HOME/.local/share/pulse-node-manager/vVERSION/pulsechain.candidate.signed.json"
Windows PowerShell
pns up --network testnet-v4 --data-root "$HOME/pns/testnet-v4" --manifest "$env:LOCALAPPDATA/PulseNodeManager/vVERSION/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 setup needs manual help The installer offers Docker first. Use Docker's official instructions for macOS, Ubuntu Linux, or Windows when a license, password, virtualization, WSL 2, or restart step needs its own screen. Review the installer code: POSIX script · Windows PowerShell script.

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 + ARM64 archivesCI
⌘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