Web3 Development

FX CoreGo Blockchain Node for Pundi AIFX on Windows

Open source Cosmos SDK node for Pundi AIFX on Windows. Learn what it does, its maintenance status, and how to install it safely.

Free Open source Windows: Yes v8.7.0 Updated 22 Apr 2026
8 min read Last update 22 Apr 2026 github.com/functionx/fx-core

FX Core is an open source blockchain project for developers and node operators who work with the Pundi AIFX network. It is written in Go and built on the Cosmos SDK and Cometbft, so it suits people who already know the Cosmos ecosystem and want to run or study a chain node on their own machine.

Before you download anything, note the project's status. Official maintenance of this repository and the reference fxcored binaries ended on March 1, 2026. After that date the core team does not guarantee security fixes, upgrade coordination, or release support. The code was last updated on April 22, 2026, and the latest version is v8.7.0, but treat the software as something you maintain yourself rather than a supported production product.

02

What Is FX Core and Who Is It For?

FX Core is the reference implementation of the Pundi AIFX chain logic. It is aimed at blockchain developers, validator operators, and researchers who want to understand how a Cosmos-style chain behaves in practice. It is not a consumer app with a graphical interface for everyday payments.

Typical users fall into a few groups. Some are engineers studying chain architecture before building their own network. Others are operators who already run nodes and need the exact binaries for a given release. A third group consists of teams who forked the code and want to compare their changes against the original.

03

How Cosmos SDK Chains Are Structured

A Cosmos SDK application is split into modules, each handling a specific area such as staking, governance, or token transfers. Cometbft runs the consensus engine that orders transactions and finalizes blocks among validators. Together they let a chain developer focus on application logic instead of writing consensus from scratch.

For a developer, this separation is useful. You can read the staking module to understand delegation rules, or inspect the governance module to see how upgrades are proposed and voted on. The same design is why many chains in the ecosystem look similar at the code level.

04

Running a Node: What to Expect

A full node stores the chain history and verifies blocks, while a validator also signs blocks and earns rewards. Running either role requires steady uptime, reliable storage, and monitoring. A node that falls behind or stops signing can be penalized by the protocol, so operators usually automate restarts and alerts.

If you only want to experiment, a local test network is a safer starting point than connecting to a live chain. You can spin up a single node, make a few transactions, and observe how blocks are produced without risking real assets.

05

Decommissioning and Archiving Data

Stopping a node is more than closing a window. Before shutting down, export any accounting records, logs, or state snapshots you may need later. Once the hardware is wiped or repurposed, recovering that data can be impossible.

Keep a checklist: confirm that your validator has unbonded, disable any process managers such as systemd or Cosmovisor so they do not restart the binary, and then stop fxcored. Document the date and the software version you were running. This record helps if you later need to explain your history to an auditor or community.

06

Key features

Open source under Apache 2.0

The source code is published on GitHub under the Apache License 2.0, which allows you to read, modify, and redistribute the code under permissive terms. Developers can audit the node logic, fork it for experiments, or study how a Cosmos-based chain is assembled.

Built on Cosmos SDK and Cometbft

The project uses the Cosmos SDK for application logic and Cometbft for consensus and networking. Anyone familiar with these frameworks will find the module structure and tooling recognizable, which shortens the learning curve.

Tagged release workflow

Supported builds are published as tagged releases. The main branch is not intended for production use, so you should always pick a specific release that matches the network version you are targeting.

Documented exit procedure

The repository includes a validator exit guide covering unbonding, key handling, and shutting down the node. It is a practical reference if you decide to stop operating a validator.

Windows-compatible builds

Windows support is available through a Windows build or installer, so you can run the node without a Linux virtual machine. Advanced users can also compile the code from source with Go.
07

Supported coins

The repository documentation mentions Cosmos (ATOM) in the context of the broader ecosystem. FX Core itself is a chain node implementation rather than a multi-asset wallet, so its role is to run and verify the Pundi AIFX network state rather than to manage a list of tokens.

08

How to install FX Core on Windows

  1. 1

    Choose the correct release

    Open the project's Releases page on GitHub and select a tagged version that matches the network you intend to join. Do not build from the main branch for production use, because it is not a supported release.

  2. 2

    Download the Windows build

    Download the Windows build or installer from the official GitHub Releases page. Avoid mirrors and third-party download sites. If you prefer, clone the repository and compile the code with Go 1.23 or later.

  3. 3

    Verify the file

    Compare the SHA-256 checksum of the downloaded file with the value published alongside the release, and check any available signature. If the values do not match, delete the file and do not run it.

  4. 4

    Install and configure

    Run the installer or extract the archive to a dedicated folder. Initialize the node with the appropriate chain configuration, then review the generated config files for peers, ports, and data directories before starting the process.

  5. Start and monitor

    Launch fxcored and watch the logs during the first sync. Confirm that the node connects to peers and that block height increases. Set up alerts so you learn quickly if the process stops.

09

System requirements

  • Windows with enough free disk space for chain data, which grows over time
  • Stable internet connection with open ports required by your node configuration
  • Go 1.23 or later, only if you choose to build from source
10

How to use FX Core

Running FX Core is mostly about configuring a node and keeping it healthy. The steps below assume you have already downloaded a verified release and want to start a node on your Windows machine.

  1. Open a terminal in the folder containing fxcored and check the version to confirm you have the release you expect.
  2. Initialize the node directory so that configuration and data files are created in a known location.
  3. Edit the configuration files to set the moniker, seeds or persistent peers, and the ports your firewall allows.
  4. Start the node in a terminal window or as a background service, and keep the log output visible during the first sync.
  5. Check that the block height is increasing and that the node has peers connected.
  6. Back up your key files and node configuration before making any changes to the setup.
  7. Schedule regular checks of disk space and logs, because a full disk is one of the most common reasons a node stops.
  8. When you are ready to stop, unbond any validator stake first, then shut down the process cleanly so it does not sign blocks after you have left.
11

Pros & cons

Pros
  • Open source under a permissive Apache 2.0 license
  • Clear separation between application logic and consensus through Cosmos SDK and Cometbft
  • Tagged releases make it easier to reproduce a specific version
  • Includes a documented validator exit procedure
  • Windows builds avoid the need for a Linux virtual machine
Cons
  • Official maintenance ended on March 1, 2026, so security fixes are not guaranteed
  • Requires ongoing operational work: monitoring, updates, and incident response
  • Documentation may be out of date and must be checked against your node version
  • Not designed for casual users who only want a simple wallet
12

Is FX Core safe?

Because FX Core runs a blockchain node and handles validator keys, treat it with the same care as any software that controls assets. Download only from the official GitHub Releases page of the project, and verify the SHA-256 checksum or signature before running the file. Never enter a seed phrase or private key into a third-party website, and do not share key files with anyone who asks for them.

Because the project is no longer officially maintained, you should assume that any newly discovered vulnerability will not be patched by the core team. Plan for that by keeping backups, limiting the funds exposed to a node, and watching community channels for forks. If you are unsure whether a given release is still appropriate, check the latest status on the official website before you proceed.

  • Official source only. Download from github.com/functionx/fx-core. 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.
13

Alternatives

FX Core is best understood as a chain node for the Pundi AIFX network, whereas several of the similar programs in this catalog focus on different parts of the stack. Local Interchain is aimed at spinning up a local IBC test environment, which is useful for developers testing cross-chain flows before going live. Cosmos SDK is the framework that many chains, including this one, are built on, so it suits people who want to design their own application from the ground up.

Native Evmos and Ethermint bring Ethereum-compatible execution into Cosmos-based chains, which matters if your goal is to run Solidity contracts rather than maintain a Pundi AIFX node. If you are mainly writing or debugging smart contracts, tools such as Remix Desktop or the Visual Studio Code Solidity extension may fit your workflow better than a full node.

14

Specifications

Price
Free
Type
Open source
License
Apache 2.0
Latest version
v8.7.0
Last update
22 Apr 2026
Windows support
Yes (Windows build or installer)
Source code
github.com/functionx/fx-core
15

Frequently asked questions

Official maintenance of the repository and the reference binaries ended on March 1, 2026. The core team no longer guarantees security fixes, upgrade coordination, or release support. Community forks may continue development, but you should evaluate them independently before relying on them.

Yes. The project provides a Windows build or installer through its GitHub Releases page. You can also compile the source code with Go 1.23 or later if you need a custom build. Always verify the file checksum before running it.

FX Core is written in Go. This is important if you plan to modify the code or build from source, because you will need a compatible Go toolchain installed on your system.

The project is released under the Apache License 2.0. This permissive license allows you to use, modify, and redistribute the code, subject to the license terms, including the requirement to keep copyright notices.

No. You can run a node to study the network, test configurations, or observe block production without staking. A validator role requires stake and carries additional responsibilities, including uptime and penalties for misbehavior.

Start by unbonding your validator stake according to the protocol rules. Then disable any process managers such as systemd or Cosmovisor, and shut down fxcored. Archive any logs or records you need before wiping the hardware.

It is not advisable. Download only from the official GitHub Releases page, verify the SHA-256 checksum or signature, and be cautious of unofficial mirrors that may contain modified binaries.

16

Verdict

FX Core suits developers and experienced node operators who want to study or run a Cosmos-based Pundi AIFX node on Windows. Its open source code and documented exit procedure are useful, but the end of official maintenance means you take on full responsibility for updates and incidents. If you are a beginner looking for a simple wallet or a supported production service, this software is not the right starting point.

Download now