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

Pick a platform. Follow the same safe path.

Every package starts with the same read-only preflight. Choose a supported local folder, keep Docker running, and let the dashboard show what happens next.

◈LINUX

x86_64

Linux archive for supported local distributions. Make the binary executable before the first run.

  1. Open the latest GitLab release.
  2. Download the Linux x86_64 archive.
  3. Extract it and run preflight.
Open Linux package Ubuntu/Debian · native runner · x86_64
⊞WINDOWS

x86_64

Windows archive for PowerShell. Extract the package, then use the same preflight flow.

  1. Open the latest GitLab release.
  2. Download the Windows x86_64 archive.
  3. Open PowerShell and run preflight.
Open Windows package Windows 2022 · native runner · x86_64

BEFORE YOU START

Know the local requirements.

  • Docker Engine or Docker Desktop already installed and running
  • At least 1.5 TB free for mainnet or 1 TB for Testnet V4
  • A supported local filesystem for chain data
  • Outbound network access for pinned client images

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

Testnet data and sync state can reset.

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