Where do you want to start?

Community hub

BTX.community

A community page for everyone interested in BTX: what it is, how to mine it, how to run a node, and where to find help. Run by community members, not by a company.

Network right now

Full status page →
Status
–
Block height
–
Latest node release
–
Nodes on it
–
Average block time (24 h)
–
Active signers
–
  • Stable: Unknown
  • Performant: Unknown
  • Secure: Unknown

BTX in numbers

Mined so far
–
Block reward
–
Next halving
–
Transactions (24 h)
–
Size of the chain
–

Loading live data …

What is BTX?

Fixed supply

At most 21 million BTX, as with Bitcoin. A block comes about every 90 seconds; its reward of 20 BTX halves every 525,000 blocks, roughly every 18 months.

Source ↗

Mining by matrix multiplication

Instead of hashing, miners multiply large matrices, the work AI accelerators are built for. Since block 185,000 every block needs a complete, exactly reproducible run on a qualified NVIDIA (CUDA) or Apple (Metal) GPU. There is no CPU mining.

Source ↗

Post-quantum signatures

Coins are locked with signatures meant to withstand quantum computers: ML-DSA-44 (NIST FIPS 204) for everyday spending, SLH-DSA (FIPS 205) as a hash-based fallback. These P2MR addresses start with btx1z.

Source ↗

Built on Bitcoin Core

The node is a fork of Bitcoin Core. btxd, btx-cli, the RPC interface and PSBTs work the way Bitcoin users know them; what differs is the proof-of-work and the signatures.

Source ↗

Where do you want to start?

Mining

Mining needs a GPU. You can mine alone against your own node and keep every block, or join a pool for steadier payouts.

  1. Pick a miner - easyBTX (one app for Mac, Windows, Linux) or matador (open source).
  2. Prefer a smaller pool. When one pool finds most blocks, the network depends on it; the status page shows the current shares.
  3. matador's examples still name the minebtx pool, which is offline. Use a pool from the list below instead.
  4. Problems with an NVIDIA card? The official CUDA troubleshooting guide helps.

Running a node

Every node checks the chain for itself and makes the network harder to fool. A home computer is enough; signers have much higher requirements.

  1. Easiest start at home - easynode installs and supervises btxd for you.
  2. On a server - the official release for Linux needs glibc 2.38 or newer (Ubuntu 24.04, Debian 13).
  3. Catch up in minutes with a daily signed snapshot instead of syncing from genesis.
  4. Node stuck at a height? The node help explains each known case and its fix.
  5. Signers (GPU attestors) need an NVIDIA Blackwell card (sm_120) and must follow the developers' operator runbook.

Coming soon: v0.35

Release candidate v0.35.0rc1 since 13 October 2026. The developers call it not release-qualified; the current release stays v0.34.15. Nothing below is final.

Swaps without staying online

A swap party can sign its HTLC claim in advance and hand it to a watchtower. Today every buyer has to keep a node and wallet online for the whole swap; this is what makes non-custodial swaps practical for most people.

Source ↗

The model network moves into the node

The network for AI models has run beside the node since v0.34.9 (btx-modeld). In 0.35 it runs inside btxd, and a research lab joins it: identities with recovery keys, git workspaces for models, evaluations. Off with -modelnet=0; it does not spend coins.

Source ↗

Safer auto-update

A node behind a proxy or Tor no longer checks for updates by itself, so it does not reveal its address to the update server. The update helper runs isolated.

Source ↗

Desktop app and ZeroMQ

The official archives include the graphical wallet btx-qt and ZeroMQ notifications for services that follow the chain.

Source ↗

Not ready yet

  • rc1 has no Linux CUDA archive. A GPU node started with it falls back to the CPU and can stall at the next block. Miners and signers stay on v0.34.15.
  • The desktop app of rc1 needs glibc 2.43 and does not start on Ubuntu 24.04.
  • CUDA on Windows was neither built nor tested.

Read from the development branch on 2026-11-05. Release notes ↗

Check first

Before you buy or receive BTX

  1. Create the wallet first and write the backup down offline. Restore it once, so you know the backup works before money depends on it.
  2. Check the receiving address in full, not just its start and end. BTX addresses start with btx1z.
  3. Send a small test amount first and wait until it is confirmed.
  4. Before you use an exchange or an OTC seller, check that withdrawals really work. A price on a website is not a market you can sell into.
  5. A "model" or "reference" price is an estimate, not an offer that anyone has to honour.
  6. Nobody legitimate asks for your seed. Messages offering help, "recovery" or guaranteed returns are scams.

Before you install a node release

  1. Download only from github.com/btxchain/btx/releases.
  2. Recent releases come without a signed checksum file; the last one with SHA256SUMS.asc was v0.34.6. GitHub shows a SHA-256 for each file on the release page: compare it with "shasum -a 256 <file>" ("sha256sum" on Linux).
  3. That proves the file is the one on GitHub, not who built it. If that matters to you, build the tagged source yourself.
  4. Read the release notes before upgrading. Some releases change the rules at a fixed block height; this page shows a countdown when one is coming.
  5. Release candidates (rc) are for testing. Do not run them on a mining or signing node.

Documents

What this community has written down. Every one of them lives in the repository, so each change is visible as a commit and anyone can correct a figure.

Roadmap

What the community can do by itself and what depends on the core team, in two columns, with a place to put your name against a lane.

Open for edits

Read it ↗

The bootstrap window and the 1,000,000 BTX deployment reward

The first question most newcomers ask, answered from chain data: what the first 50,000 blocks produced, under which consensus rules, and what public data can and cannot show.

Draft - under review

Read it ↗

Network fund

How the network could pay for its own infrastructure: contributions, multisig custody, published rules and payouts against verified uptime.

Discussion paper

Read it ↗

Venue structure and the licensing boundary

What a decentralised exchange can be on a chain without a virtual machine, where the regulatory line runs, and the models that remain open. Not legal advice.

Draft for discussion

Read it ↗

How to change something here

What you can edit freely, what needs a second pair of eyes, and how to report a wrong figure if git is not your thing.

Read it ↗

All of it, including the source of this page ↗