> For the complete documentation index, see [llms.txt](https://dozza.gitbook.io/pulsechain_node_guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dozza.gitbook.io/pulsechain_node_guide/readme.md).

# Introduction

![PulseChain Node Guide](/files/5pmcpGPVuEclpu3XbfEe)

## Building a PulseChain Full Node in a Hyper-V VM

A complete, reproducible build guide.

**Execution client:** go-pulse (Geth) · **Consensus client:** Lighthouse · **Host:** Windows 11 Pro + Hyper-V

Based on the [install\_pulse\_node](https://github.com/tdslaine/install_pulse_node) project by tdslaine.

{% hint style="info" %}
**Useful PulseChain links** — these are tools I personally use — always verify URLs yourself and DYOR.

* [PulseChain — official site](https://pulsechain.com/)
* [Official node documentation (GitLab)](https://gitlab.com/pulsechaincom/pulsechain-mainnet#advanced-users-running-a-pulsechain-node)
* [ZKX Wallet](https://zkxwallet.com/)
* [LibertySwap — multi-chain bridge](https://libertyswap.finance/)
  {% endhint %}

***

This guide reproduces, step by step, the setup of a fully synced **PulseChain full RPC node** running inside a Hyper-V virtual machine on a Windows 11 Pro host. The node runs two clients in Docker containers: **go-pulse (Geth)** for execution and **Lighthouse** for consensus. The result is a private RPC endpoint on your local network that wallets, scripts, or bots can use without rate limits or reliance on a third-party provider.

{% hint style="info" %}
**Placeholders:** Throughout this guide, `***` and `<user>` replace environment-specific values — your VM's LAN IP, your username, and so on. The example LAN IP is shown as `192.168.1.***`. Substitute your own values.
{% endhint %}

### Hardware used

| Component       | Specification                                |
| --------------- | -------------------------------------------- |
| CPU             | Intel Core i5-14400F (10 cores / 16 threads) |
| RAM             | 32 GB (24 GB assigned to the VM)             |
| Node storage    | 4 TB NVMe (2 TB+ recommended minimum)        |
| OS drive (host) | 1 TB NVMe                                    |
| Motherboard     | mATX with 2× M.2 slots (PCIe 4.0)            |
| GPU             | Discrete GPU (unused by the node)            |
| Host OS         | Windows 11 Pro                               |

{% hint style="warning" %}
**Storage is the critical spec.** A PulseChain full node needs **1 TB minimum, 2 TB+ recommended**, because PulseChain carries the entire Ethereum state through the fork block. It **must be NVMe/SSD** — a mechanical hard drive cannot keep up with the node's random I/O and will never finish syncing. A synced node uses \~1.1 TB.
{% endhint %}

### What you'll end up with

* A fully synced PulseChain full node (Geth + Lighthouse in Docker)
* A private RPC endpoint on your LAN, firewalled off from the internet
* Auto-recovery on reboot and graceful shutdown protecting the database
* Optional mempool/WebSocket tuning for bots
* Optional Telegram monitoring that pings you if the node stalls

> This guide documents one specific, working build. Software versions, default ports, and the installer's prompts may change over time — always cross-check against the install\_pulse\_node repository and official PulseChain documentation. Nothing here is financial advice.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dozza.gitbook.io/pulsechain_node_guide/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.