EASYNODE FOR BTX · GUIDE

Run a BTX node in 5 steps

No terminal, no config files. If you can install an app, you can run a full node.

1. 1

   Download and open

   Grab easyNode for BTX from the download buttons for your platform:

   Mac (Apple Silicon): open the .dmg and drag the app to Applications. It installs under the name easyBTX Node, so that is what you will see in Applications and in the paths below. The first time, right-click the app and choose Open. macOS asks once because the build is community-signed.
   Windows (x64): run the installer, or run the Linux build under WSL2. Both work; the note below says which to pick.
   Linux (x86_64): make the AppImage executable and run it, or install the .deb with sudo apt install ./BTX-Node_0.6.23_amd64.deb.

   If macOS instead says easyBTX Node is “damaged” or “can’t be opened,” that’s just the download-quarantine flag on an unsigned app. Clear it once in Terminal (Applications → Utilities → Terminal), then open the app normally:

   xattr -dr com.apple.quarantine "/Applications/easyBTX Node.app"

   Copy

   That command only clears the “downloaded from the internet” tag; it doesn’t change the app. It’s safe.

   One honest warning before you start, for every platform. Each published build follows the chain up to a block and then stops. Which block depends on the build.

   Mac. The published Mac build is 0.6.23, released 15 September with the BTX 0.34.6 engine, the same engine commit the Linux and Windows builds carry. It shows you in amber when a longer chain exists that your node cannot obtain blocks for, it follows the chain with the most work instead of parking a deep reorganisation, and it dials two seeds measured on the live chain. Which chain any reachable node follows is measured on the node census. A Mac still on 0.6.12 or earlier stops at block 199,299: BTX published a change to a difficulty rule at that height on 25 August 2026 and withdrew it two days later, and those builds still carry the withdrawn rule. Your coins are not affected. A node reads the chain, it does not hold your keys. Updating is what starts such a Mac again: download 0.6.23 from the node page. The app's own update check runs when you open it and every six hours after that. 0.6.22 and 0.6.23 shipped for Linux and Windows first, so for part of 15 September a Mac was offered nothing and pressing Check now reported a connection problem, which it was not. The Mac build of 0.6.23 closes that gap.

   Windows, the way that works. Run the Linux build under WSL2. This is exactly how we run and verify it ourselves, on a Windows machine with WSL2 and an RTX 3060. Once, in PowerShell: wsl --install -d Ubuntu, then reboot and open Ubuntu from the Start menu. Inside Ubuntu, download the AppImage from the node page, make it executable with chmod +x BTX-Node_0.6.23_amd64.AppImage, and run it. Your NVIDIA card is visible inside WSL2 with the standard Windows driver, nothing extra to install. A copy run this way also updates itself like any Linux copy.

   Windows, natively. 0.6.23 is the current native Windows build; 0.6.21 was the first since 0.6.6. 0.6.23 carries BTX's tagged 0.34.6 engine, the same commit as Linux. BTX publishes no Windows binaries of its own engine, so we cross-compile it and smoke it on a real Windows machine before it ships. A copy still on 0.6.6 is offered this update directly, and wants it: that engine predates the BTX consensus release of 17 August 2026, so it syncs normally and then parks at block 191,713, or at 184,999 if it checks blocks on the processor. Which route to pick: WSL2 is what we have verified against a GPU, the native build is not, so on a machine with an NVIDIA card WSL2 is still the measured choice.

   Linux. The published Linux build is 0.6.23, with BTX's tagged 0.34.6 engine, one commit past the build 0.6.18 through 0.6.22 carried. 0.6.22 tells you when its own newest block is more than two hours old, which a stuck set of peers cannot fake; 0.6.23 shows which role your node fills and writes every self-update check to a log. 0.6.20 added one thing worth switching on: your node can answer which block sits at a given height, which is how a wallet checks it is on the right chain. It costs almost nothing and works on a node of any size, because it reads the list of blocks rather than the blocks. On 5 September the network split at block 210,496 and our own validator sat on the minority branch for twenty hours before rejoining the live chain; 0.6.21 shows you in amber when a longer chain exists that your node cannot obtain, follows the chain with the most work, and carries a seed on the live chain. With a suitable NVIDIA card (verified on an RTX 3060) the node proves itself at startup and validates blocks as a full consensus validator. Without one, since 0.6.23, the node runs as a trusted mirror: it follows the chain the network's validators have signed and serves history to other nodes, but it does not check the block maths itself. Earlier builds on such a machine started, followed headers, and stalled. The download is about 466 MB because the engine and its GPU math library travel inside the app.

   On any platform, the free BTX Node Guardian tells you which kind of stall you are looking at, whether the network is waiting or your own node is behind.

   Updates reach Mac, Linux and Windows today. 0.6.23 carries a build for all three, so copies from 0.6.0 onward are offered it. That includes a Windows copy still on 0.6.6, and a Mac still on 0.6.21. That is not always the state here: single-platform releases are the normal cadence, and a platform a release skips checks, finds nothing for itself, and stays put. The automatic check stays silent about that; pressing Check now on a skipped platform reports it as a connection problem, which it is not. When that happens, download by hand from the node page.

2. 2

   Click "Set up my node"

   The app checks your free disk space first and tells you before it starts, not after: the chain itself measured about 124 GiB in early September, and the app asks for 140 GiB free so the sync has room to finish. One click begins the setup.

   
3. 3

   Watch it come alive

   The app downloads a checksum-verified snapshot of the blockchain (9.3 MB on the newest builds, ~450 MB on older ones), starts your node, and loads the snapshot. Your node is usable the same evening; the full history keeps filling in quietly in the background.

   
4. 4

   Green means helping

   When the orb turns green, your node is live: verifying blocks, relaying to peers, holding its own copy of the chain. The frequency line under the orb plays a gentle note each time a new block arrives.

   
5. 5

   Let it live in the corner

   Close the window; the node keeps running in your menu bar or system tray. Or press the compact button and keep just the little light on your desktop. Settings has two looks (a calm line or an energy pulse), launch-at-login, keep-awake, four colors, and one-click disk reclaim. Stop anytime; nothing is locked in.