Nodes & Blockchain Clients

Nibiru NodeFree Cosmos Ecosystem Daemon for Windows

Free, open-source nibid daemon for running a Nibiru full node on Windows. Specs, install steps, safety tips and FAQ.

Free Open source Windows: Yes v2.22.0-rc.1 Updated 29 Oct 2026
9 min read Last update 29 Oct 2026 github.com/NibiruChain/nibiru

Nibiru node is the nibid daemon, a free and open-source program that runs a full node for the Nibiru network within the Cosmos ecosystem. It is aimed at developers, infrastructure operators and technically minded users who want to run their own node on a Windows PC instead of relying entirely on someone else's endpoint. The source code is published under the BSD-2-Clause license, so you can read, build and modify it.

Running a node means your machine keeps its own copy of the blockchain data, checks transactions independently and talks to other peers on the network. That requires disk space, memory and a steady connection, so the setup behaves more like server software than a typical desktop app. The newest listed version is v2.22.0-rc.1, a release candidate, and the code was last updated on October 29, 2026.

02

What Is Nibiru Node and How Does It Work?

Nibiru node is a program that runs a full copy of a blockchain on your own computer. The core component is the nibid daemon, a background process that connects to other computers on the network, downloads blocks, checks every transaction against the network rules and keeps the resulting state on disk. Once it is running, it can answer questions about the chain without asking a third-party service.

The Cosmos ecosystem is a family of separate blockchains designed to communicate with each other. Each chain has its own rules and validators, so a node must follow the specific network it belongs to. This is why a Nibiru node is not interchangeable with an Ethereum client or with Cosmos Hub software, even though they share a broad design philosophy.

For a beginner, the easiest way to picture it is as a local archive. Instead of trusting a remote server to report a balance or a transaction status, your node checks the data itself. That independence is the main reason developers and infrastructure teams choose to run their own nodes.

03

Who Nibiru Node Is For and Real-World Use Cases

Nibiru node fits people who already know their way around a terminal and want more control over their blockchain access. Typical users include developers building applications that read chain data, teams that need a dependable RPC source for internal tools, and technically minded enthusiasts who want to see how a Cosmos-based network behaves in practice.

Here are a few realistic scenarios. A developer testing an application can point a local front end at their own node, which reduces dependence on public endpoints and makes debugging easier. A small team running monitoring dashboards can keep a node on a dedicated PC to collect data continuously. A student or researcher can sync a node to study block production and network traffic firsthand.

It is less suited to casual users who only check a balance once in a while. Running a node means keeping the machine powered on, managing disk space and updating the software when new releases come out. If that sounds like more maintenance than you want, a hosted service or a lightweight wallet may be a better match. Choosing a tool that fits your real workload prevents frustration later.

04

How a Full Node Syncs and Why Hardware Matters

When a full node starts, it first has to catch up with the network. It connects to peers, requests missing blocks and verifies each one, starting from the beginning of the chain's history. This process is heavy on disk input and output, which is why an SSD is recommended over a traditional hard drive.

Storage needs grow over time as the chain adds blocks. The recommended minimum of 100 GB of SSD space is a starting point, so leave headroom for growth and logs. Keep the data on a drive with plenty of free space, and avoid placing it on a removable USB stick, because interruptions can corrupt data or slow the process dramatically.

Memory and CPU matter as well. Two CPU cores and 4 GB of RAM are the recommended minimums for a full node, and they are enough to keep verification moving on a modest machine. If you plan to serve RPC requests to other applications at the same time, consider going above the minimum, because query traffic adds load on top of the sync itself.

05

Key features

Official documentation hub

The project maintains a documentation site at nibiru.fi/docs that covers technical reference, core concepts and product details. It is the most complete starting point for understanding how the node is configured and how the network is organized, and it is the first place to look when something is unclear.

Go reference documentation

The blockchain implementation is documented as Go packages on pkg.go.dev, so developers can look up functions, types and interfaces without reading every source file. This is useful when you want to build tooling, scripts or monitoring around the node.

RPC endpoints

The node exposes RPC endpoints that other applications can query for chain state and use to submit transactions. Dashboards, scripts and wallets can connect to your own node instead of a public service, which gives you more control over the data you read and how often you query it.

Core tools and language clients

The project includes core tools and client libraries for interacting with the network from different programming languages. They help developers write scripts and services without implementing the network protocol from scratch, which saves time during early prototyping.

Repository specifications

The source repository contains internal technical records that describe how its components are meant to work. Reading them alongside the code helps contributors and auditors follow design decisions and makes the project easier to review over time.
06

Supported coins

The official documentation references Ethereum (ETH) and Cosmos (ATOM) as part of its coverage. Treat these as examples of the assets and networks discussed in the docs rather than a complete list, and check the documentation for the current scope of the network before planning an integration.

07

How to install Nibiru node on Windows

  1. 1

    Get the file from the official source

    Download only from the official website or the project's GitHub Releases page at github.com/NibiruChain/nibiru. Avoid mirrors, file-sharing sites and links posted in chats, even when they look legitimate.

  2. 2

    Choose the Windows build

    Pick the Windows build or installer that matches your processor architecture. Most modern PCs run 64-bit Windows, so check your system settings before choosing the file.

  3. 3

    Verify the download

    Compare the file's SHA-256 checksum with the value published on the release page, or check the signature if one is provided. A mismatch means the file should not be run, and you should download it again from the source.

  4. 4

    Run the installer or extract the files

    Run the installer and follow its prompts, or extract the archive to a folder you control. Keep the nibid program in a location you will remember, because you will launch it from a terminal.

  5. Read the node setup guide

    Open the documentation at nibiru.fi/docs and follow the node setup instructions before starting the daemon. Prepare an SSD with at least 100 GB of free space so the chain data has room to grow.

08

System requirements

  • 2 CPU cores (recommended minimum for running a full node)
  • 4 GB RAM (recommended minimum for running a full node)
  • 100 GB SSD storage
09

How to use Nibiru node

Once the daemon is installed, you work with it from a terminal. The steps below cover the general flow, while the official documentation at nibiru.fi/docs has the exact commands and flags for your version.

  1. Open PowerShell or Command Prompt in the folder that contains the nibid program.
  2. Run the version command described in the documentation to confirm which build you installed.
  3. Initialize the node's home directory following the setup guide, and choose a name that identifies your node in logs and tools.
  4. Start the daemon and leave the window open while it runs. The first sync can take a long time and will keep your disk busy.
  5. Watch the log output for sync progress and any errors, and fix configuration problems before moving on.
  6. If you want applications to query your node, enable the RPC endpoints in the configuration and limit access to the local machine unless you deliberately expose them.
  7. Stop the daemon cleanly before shutting down Windows so the database closes properly.
10

Pros & cons

Pros
  • Free to use and released as open source under the BSD-2-Clause license
  • Documentation hub and Go reference docs make the codebase easier to explore
  • Lets you run your own node and serve RPC queries to local tools
  • Clear hardware baseline for planning a full node
  • Source code is available for review and modification
Cons
  • Requires sustained disk space and a fast SSD over time
  • Setup assumes comfort with a terminal and configuration files
  • The newest listed version is a release candidate, so it may not suit production use yet
  • Supported networks and assets are mentioned only briefly, so check the docs before planning an integration
11

Is Nibiru node safe?

Download Nibiru node only from the official website or the project's GitHub Releases page, and never from a mirror or a link shared in a chat. Once the file is on your computer, compare its SHA-256 checksum against the value published on the release page, or verify the signature if one is offered. If the values do not match, delete the file and download it again from the source.

A node can hold keys and sensitive configuration, so keep wallet backups and validator material offline. Never type a seed phrase into a third-party website, app or support chat, because scammers often impersonate node projects and ask for recovery phrases. Running a node also does not guarantee any particular outcome, and nothing on this page is financial advice.

  • Official source only. Download from github.com/NibiruChain/nibiru. Ignore ads and lookalike domains.
  • Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
  • Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
12

Alternatives

Nibiru node sits in the node-software category alongside clients built for other networks, so the right choice depends mostly on which chain you need to connect to. Geth, Erigon and Nethermind are Ethereum execution clients, so they target Ethereum rather than Cosmos-based networks. Cosmos Hub's gaiad and Celestia App are node software for their own networks, while Evmos is a separate node in the Cosmos space. OpenEthereum, the former Parity client, is closed and is not a current option. Pick the program that matches your target network first, then compare hardware needs and documentation quality.

13

Specifications

Price
Free
Type
Open source
License
BSD-2-Clause
Latest version
v2.22.0-rc.1
Last update
29 Oct 2026
Windows support
Yes (Windows build or installer)
Source code
github.com/NibiruChain/nibiru
14

Frequently asked questions

Yes. The program is free and released as open source under the BSD-2-Clause license, a permissive license that lets you use and modify the code under its terms. Download it only from the official website or GitHub Releases to make sure you get the genuine build.

Yes, Windows is supported through a Windows build or installer. The project also lists macOS, Linux and Docker, so you can choose another platform if it suits your setup better or if you already run a server environment.

The recommended minimum for a full node is 2 CPU cores, 4 GB of RAM and 100 GB of SSD storage. Chain data grows as blocks are added, so plan for extra space beyond the minimum, especially if you intend to keep the node running for months.

It can be, provided you download it from the official website or GitHub Releases and verify the SHA-256 checksum or signature before running it. Never enter a seed phrase on a third-party website, and keep any wallet or validator backups offline.

The nibid daemon is the background program that runs the Nibiru node. It connects to peers, downloads and verifies blocks, stores the chain state and serves RPC queries to applications that need data from the network.

The official documentation references Ethereum (ETH) and Cosmos (ATOM). These are examples from the docs rather than a full list, so review the current documentation to understand the scope of the network before you build on it.

Yes, they run as separate programs for different networks, so they can coexist on one machine. Keep in mind that both need disk space, memory and CPU time, so confirm that your hardware can handle the combined load.

15

Verdict

Nibiru node suits developers and technically experienced users who want to run their own node for the Nibiru network on Windows. It is free, open source and well documented, but it asks for real disk space and comfort with a terminal. If you only need to query data occasionally, a hosted service may be simpler. Before installing, confirm on the official website or GitHub Releases page that you have the stable build, since the newest listed version is a release candidate.

Download now