[ANN][BFX] BitFinite — Point your Bitaxe at a chain where it finds blocks

[bitfinitechain]

Point your Bitaxe at a chain where it actually finds blocks

bitfinitechain.org  •  bitfinitechain.org/bitaxe

TL;DR
BitFinite (BFX) is a small, fair-launched SHA-256d proof-of-work chain built for hobbyist miners — the Bitaxe / home-ASIC / tinkerer crowd. Point a Bitaxe at Bitcoin and you're playing a lottery with astronomical odds: the expected time to a solo block runs into the tens of thousands of years. A lucky few solo miners have famously beaten those odds — but realistically, you won't. Point that same Bitaxe at BitFinite and the odds flip entirely: the network is small enough that your device has a real, everyday shot at a full 50 BFX coinbase block. That's the whole pitch: point your Bitaxe somewhere it can actually win. (Plug your exact device into the live odds calculator for your expected time-to-block.)

Straight talk: this is a young, low-hashrate network — a few TH/s total, less than a handful of Bitaxes. It is not "secure money", not an investment, and it is 51%-attackable by anyone renting hashrate. We're not pretending otherwise. It's a fair-launch playground for people who like running their own miners. If that's you, read on.


Why point a Bitaxe here

• You actually find blocks. Solo-mine real 50 BFX coinbase rewards with modest hardware.
• Own your hashrate. No cloud, no custodian — your Bitaxe, your address, your coins.
• See your odds live. The odds calculator takes your device and the live network difficulty and shows your expected time-to-block — computed from the real chain, not a guess.
• Wall of Fame. Recently solved blocks and who solved them, live from the pool.

Point your Bitaxe (AxeOS)

Code:

Stratum URL : stratum+tcp://solo.bitfinitechain.org
Port        : 3333
User        : bfx:YOURADDRESS.bitaxe
Password    : x

The .bitaxe worker suffix floors the pool difficulty so small devices submit shares steadily; version-rolling (ASICBoost) is supported. Grab a bfx: address from any wallet below.

Live odds + step-by-step config: bitfinitechain.org/bitaxe
Pool status: ckpool.bitfinitechain.org


Specs

• Ticker: BFX
• Algorithm: SHA-256d — Bitaxe / ASIC friendly
• Block reward: 50 BFX
• Block time: ~5 min · ASERT retarget (6h half-life, absorbs hashrate swings)
• Max supply: 21,000,000 BFX · halving every 210,000 blocks
• Address: CashAddr (bfx: prefix) · CashTokens-capable
• Codebase: Bitcoin Cash Node (BCHN) fork · open source
• Premine: none

Wallets

• Android: signed release — github.com/bitfinitechain/bitfinite-wallet/releases (v1.3.0, non-custodial — your keys never leave the device)
• Web wallet (PWA): wallet.bitfinitechain.org — runs in your browser
• Full node / CLI / Qt: github.com/bitfinitechain

Ecosystem

• Site + Bitaxe page: bitfinitechain.org · /bitaxe
• Explorer: explorer.bitfinitechain.org
• Mining pool: ckpool.bitfinitechain.org
• Source (GitHub): github.com/bitfinitechain
• X: @bitfinitechain

Transparency: where the coins are
BitFinite is only ~2 weeks old. About 350,000 BFX have been mined so far — roughly 1.7% of the 21,000,000 that will ever exist. In the first blocks the two developers, plus a bootstrap/test address, did almost all the mining, because until this week there was almost no one else on the network.

• Dev 1: bfx:ffdwzfex3g058z4zl4ntphkmxue3ecpesu0jqu0ek0 — ~142,750 BFX
• Dev 2: bfx:frs8exzd4ajq60uz687xmuza7sztddzp5v4hhme0sm — ~106,548 BFX
• Bootstrap / test: bfx:frazyrzg50rpdcmc2rn5f553f2tyvtk3kgjszd0v33 — ~26,450 BFX

That's ~275,750 BFX together. We won't cherry-pick — both of these are true: it's about 79% of the coins mined so far (high — a young, thinly-mined chain), and about 1.3% of the eventual 21M supply. Early distribution is concentrated; that's the honest reality of a new PoW chain with almost no hashrate at launch (Bitcoin's first months were the same). It dilutes every block as you mine.

• How the coins exist: every one was PoW-mined via SHA-256d at live difficulty — no premine, no genesis allocation, no pre-sale, no ICO.
• What they fund: development, exchange listings / liquidity, and community bounties.
• Our commitment: no open-market dumps. These coins move only for a stated purpose — a listing, a liquidity pair, or a paid bounty — and we'll post every outflow from these addresses in this thread first, with the reason. Watch them; hold us to it.
• Going forward: as your hashrate grows, our own mining scales back. The goal is a chain secured by its miners, not the devs.
• Verify: every address above is public — watch them on the explorer.

And to the early miners who found us from the X launch and pointed hashrate here before we'd announced anywhere — thank you. You're why this is a network and not a dev testnet.

We'd rather tell you this up front than have you find it on-chain. Ask anything.


BitFinite is an experimental, community-run proof-of-work project. It is not an investment or a store of value, and nothing here is financial advice. The network is small and 51%-attackable — treat any BFX as a hobby experiment, not savings. Run your own node, verify everything, and never risk more than you can afford to lose.

[fibonacciopstan]

Hello, this is an interesting project, and I appreciate the unusually direct transparency about the current hashrate, early coin distribution, and network risks.

I wanted to ask one thing: do you have any permanent and verifiable place where people can follow the project’s roadmap, development plans, public promises, major announcements, and later see whether those commitments were fulfilled?

X, Discord, Telegram, forums, and even websites are useful for updates, but posts can usually be edited or deleted later. For a young PoW project, I think a public history that cannot be quietly changed would be valuable, especially for building long-term reputation and trust.

Are you currently using anything like that, or do you plan to create such a record for BitFinite?

[bitfinitechain]

Hey — I run Chainquiry, a searchable crypto project directory, and I’d like to invite your team to submit a free listing.  

It includes your official links, network, launch date and project information after editorial review:

https://chainquiry.com/list-your-project/

Thanks, we'll take a look 👍

Hello, this is an interesting project, and I appreciate the unusually direct transparency about the current hashrate, early coin distribution, and network risks.

I wanted to ask one thing: do you have any permanent and verifiable place where people can follow the project’s roadmap, development plans, public promises, major announcements, and later see whether those commitments were fulfilled?

X, Discord, Telegram, forums, and even websites are useful for updates, but posts can usually be edited or deleted later. For a young PoW project, I think a public history that cannot be quietly changed would be valuable, especially for building long-term reputation and trust.

Are you currently using anything like that, or do you plan to create such a record for BitFinite?

Good question, and thanks for the kind words on the transparency.

Right now the chain itself is our immutable record. The dev/bootstrap holdings and all issuance are on-chain, so you can check the ANN figures against the explorer any time. Node, wallet, explorer and pool are all open source on GitHub too, so the dev history is public.

You're right that posts and sites can be edited. An unchangeable commitments log makes sense, and the obvious home for it is our own chain, so we'd rather set that up properly than rush it.

Same reason there's no Discord yet. We want proper anti-scam and verification in place before opening it, not patched in later once it's too late. Slower, but safer for a young project.


Cheers

Bitfinite

[fibonacciopstan]

Hello, this is an interesting project, and I appreciate the unusually direct transparency about the current hashrate, early coin distribution, and network risks.

I wanted to ask one thing: do you have any permanent and verifiable place where people can follow the project’s roadmap, development plans, public promises, major announcements, and later see whether those commitments were fulfilled?

X, Discord, Telegram, forums, and even websites are useful for updates, but posts can usually be edited or deleted later. For a young PoW project, I think a public history that cannot be quietly changed would be valuable, especially for building long-term reputation and trust.

Are you currently using anything like that, or do you plan to create such a record for BitFinite?

Good question, and thanks for the kind words on the transparency.

Right now the chain itself is our immutable record. The dev/bootstrap holdings and all issuance are on-chain, so you can check the ANN figures against the explorer any time. Node, wallet, explorer and pool are all open source on GitHub too, so the dev history is public.

You're right that posts and sites can be edited. An unchangeable commitments log makes sense, and the obvious home for it is our own chain, so we'd rather set that up properly than rush it.

Same reason there's no Discord yet. We want proper anti-scam and verification in place before opening it, not patched in later once it's too late. Slower, but safer for a young project.


Cheers

Bitfinite

Thanks for the reply. BitFinite already shows a serious approach to transparency.

The explorer proves what happened on-chain, and GitHub preserves the code history. But a strong project also needs a permanent record of its official plans, promises, news and updates.

With Opstan, every publication is stored permanently in a Proof-of-Work blockchain and cannot be edited or deleted. Simply publish your news, plans and important statements, and they remain available as part of BitFinite’s public history. No single website, social network or administrator can quietly remove or rewrite that blockchain record.

This gives BitFinite stronger credibility: nobody can later claim that the team secretly changed its plans, because all original statements remain visible. Your channel and its messages can be accessed worldwide through Opstan-compatible interfaces.

Using it is simple. You can publish directly through the online version without downloading the blockchain, then add the BitFinite channel link to your website, GitHub and ANN thread.

Website: https://opstan.org
Online version: https://app.opstan.org

For a project focused on safety and trust, this could significantly strengthen its reputation from the very beginning.

[bitfinitechain]

Appreciate it, and Opstan looks like a neat idea. Since BitFinite is its own PoW chain though, if we set up a permanent record like that the obvious home is BFX itself rather than another network. Feels right to use our own tech for it.

Thanks for the nudge either way, good reminder to get that in place.

BitFinite

[fibonacciopstan]

Appreciate it, and Opstan looks like a neat idea. Since BitFinite is its own PoW chain though, if we set up a permanent record like that the obvious home is BFX itself rather than another network. Feels right to use our own tech for it.

Thanks for the nudge either way, good reminder to get that in place.

BitFinite

I understand your point, but Opstan is not asking BitFinite to move its protocol or integrate another blockchain into BFX.

It is simply a decentralized social network for permanent public communication. You create an official BitFinite channel linked to your wallet and publish normal updates such as:

“Hello, we are the BitFinite team. Today we completed this milestone, released this feature, or changed this plan.”

That message is then preserved permanently in the Opstan blockchain and cannot be silently edited or deleted later.

BFX can remain the home of BitFinite’s own consensus, transactions and technical records. Opstan would only serve as the public communication layer where users can follow your news, ideas, achievements and roadmap while knowing the original posts will always remain visible.

There is nothing complicated to integrate. Just create the BitFinite channel, publish important updates, and place the channel link on your website, GitHub and ANN thread.

That gives users a simple reason to trust the project’s public history, not only its code and on-chain data.

[bitfinitechain]

Appreciate the clarification, and no knock on Opstan. It's just not something we need — our own chain covers it for us.

Best of luck with the project though 👍

BitFinite

[weesdr]

I was mining as non-solo on your pool earlier today, but without worker name. I could see that I was finding blocks but I didn't get any payouts, until I realized I had to enter the worker. Now can you please payout those blocks?

Address: bfx:fzx63zyd39jzrl582lrsnwa29vmkmnrtrc69m77zye

[fibonacciopstan]

I was mining as non-solo on your pool earlier today, but without worker name. I could see that I was finding blocks but I didn't get any payouts, until I realized I had to enter the worker. Now can you please payout those blocks?

Address: bfx:fzx63zyd39jzrl582lrsnwa29vmkmnrtrc69m77zye

Where else do you mine and in what projects?

[bitfinitechain]

I was mining as non-solo on your pool earlier today, but without worker name. I could see that I was finding blocks but I didn't get any payouts, until I realized I had to enter the worker. Now can you please payout those blocks?

Address: bfx:fzx63zyd39jzrl582lrsnwa29vmkmnrtrc69m77zye

You've actually been paid — solo mining pays the full block reward straight to your address via the coinbase, there's no separate payout. Your address bfx:fzx63… has received ~4,850 BFX from the ~98 blocks you've solved (check it on the explorer).

Note recently-found blocks need 100 confirmations (~8h) before the coins are spendable, so your "available" balance lags your total — that's normal coinbase maturity, not a missed payment.

[weesdr]

You misunderstood. Yes, I'm currently mining solo and receiving payouts

I was talking about at first I was mining pplns on your pool without worker name. I couldn't search my wallet in your pool because there was no worker name entered in my rigs. However, my wallet still appeared in the pool workers list. I could also see blocks were found under my wallet in blocks section. But there were no payouts at all, until I reconfigured my rigs with the worker name "bitaxe"

[bitfinitechain]

Update: you were 100% right — thank you for pushing on it. We found the bug: our PPLNS pool was collecting block rewards but never distributing them to contributors. It's fixed, and we've just back-paid everyone who mined the pool, including you — 6,392.26 BFX to bfx:fzx63… in tx 0054f7e7e4f2dfeea293bb7b73d06ed860dd08b762c586c30cd31b29e2d88454. All 13 pool contributors got their proportional share (31,064.5 BFX total). Automated payouts are going in next so this never recurs.

You caught a real one — appreciate it. 🙏


Update on the payout issue weesdr raised:
Our shared PPLNS pool was collecting block rewards but not distributing them to contributors. A real bug, on us.
It's fixed. We've back-paid all 13 pool contributors their full proportional share — 31,064.5 BFX total — on-chain. weesdr's share: 6,392.26 BFX (tx 0054f7e7…). Every payment is verifiable; happy to post any miner's txid.
We've also deployed automated hourly payouts so it can't recur.

Thanks weesdr for catching it — we'd rather fix this loudly than hide it.

[knurled]

This is an awesome setup you have, with a great feature set. Will it be listed on miningpoolstats? Thanks for building this!What do we use for a worker name if we have more than one bitaxe?


e.g.
Wallet00.bitaxe
Wallet01.bitaxe

or

Wallet00.bitaxe
Wallet00.bitaxe01

or

Wallet00.bitaxe
Wallet00.bitaxe


Thanks!

[bitfinitechain]

Hi

Keep one wallet, give each Bitaxe its own suffix:

Code:

bfx:yourwallet.bitaxe01
bfx:yourwallet.bitaxe02

So your second example is the right idea. Payouts are the same either way (everything goes to the address before the dot) — the suffix just keeps the stats per device. Avoid identical names though: the pool merges them into one worker, so if one Bitaxe dies you won't see it.

No registration needed, password can be anything or just x

And on miningpoolstats — yes, working on the listing. Will post here when it's live.

BitFiniteThanks knurled — glad it's useful. Speaking of which, here's a release that should make it easier to join in:

BitFinite Core v3.0.1 is out — and it's the first release with binaries you can actually download. The source has been public since day one, but earlier builds were sitting as drafts on GitHub, so if you went looking for a ready-made node and found nothing, that's why. Fixed.

What's new

• Automatic peer discovery. seed.bitfinitechain.org is now a built-in DNS seed. A fresh node finds the network by itself — no more hunting for an addnode line.
• Help/docs links point at the real BitFinite channels.
• Security contact: bitfinitechain@proton.me
• Reproducible Docker cross-build (Linux + Windows), stripped and checksummed.

Download
https://github.com/bitfinitechain/bitfinite-core/releases/tag/v3.0.1

Linux x86_64 and Windows x86_64, with SHA256SUMS — verify before you run it:

Code:

sha256sum -c SHA256SUMS

Quick start

Code:

tar xzf bitfinite-v3.0.1-x86_64-linux.tar.gz
./bitfinite-v3.0.1-x86_64-linux/bin/bitfinited -daemon

That's it — it syncs on its own.

Also this week
Fixed a bug in the shared pool's payouts — a batching error was aborting the hourly run. All affected miners have been paid in full, and the payout daemon is now monitored so it can't fail quietly again. You can see your own rewards, payouts and their confirmation status at https://analytics.bitfinitechain.org (My Miner tab — free, just paste your mining address).

Mining
Everything a miner or pool directory needs is on one page: https://bitfinitechain.org/pools — stratum endpoints, fees, live pool APIs, explorers.

Running a node is the most useful thing you can do for a small chain besides pointing hashrate at it.

[knurled]

Can I install v3.0.1 right over the top of v3.0.0? Or what do you recommend?

[bitfinitechain]

Yes — straight over the top. Drop-in binary swap: no reindex, no wallet migration,
no config changes. Your chain data and wallet.dat carry over untouched.

Grab v3.0.2 rather than v3.0.1 — same chain changes, plus it fixes a build bug
where the binaries reported the wrong version number. Includes the GUI wallet.

Linux

Code:

bitfinite-cli stop
sleep 10

cp ~/.bitfinite/wallets/wallet.dat ~/wallet.dat.bak 2>/dev/null || \
cp ~/.bitfinite/wallet.dat ~/wallet.dat.bak

sha256sum -c SHA256SUMS
tar xzf bitfinite-v3.0.2-x86_64-linux.tar.gz
sudo install -m755 bitfinite-v3.0.2-x86_64-linux/bin/* /usr/local/bin/

bitfinited -daemon

Windows
Close it, back up wallet.dat, unzip over the old folder, start it again.

What changed since v3.0.0

• New DNS seed seed.bitfinitechain.org — faster, more reliable peer discovery.
• Sync trust anchors (nMinimumChainWork / defaultAssumeValid) — were
  0x00, so a syncing node would accept any chain handed to it. Now pinned to a
  buried block.

No consensus rules changed, so upgraded and non-upgraded nodes stay on the same chain
— nothing to coordinate. If you're already synced, the anchors are a no-op for you.

https://github.com/bitfinitechain/bitfinite-core/releases
Pool update — worker difficulty fix + a ckpool patch

Two pool-side fixes deployed in the last few hours, both found because miners
reported something looking wrong. Node side is unchanged — v3.0.2 from earlier
today is still current.

1. Shared pool was assigning far too low a difficulty
A miner running multi-TH/s hardware reported their rig warning about low share
difficulty. They were right, and it was our misconfiguration.

The shared pool started every worker at difficulty 42 with a floor of
1, while solo used 16,384 with a floor of 1,000. For a ~4 TH/s rig that
is roughly 200x too low — a flood of trivial shares instead of sensible ones.

Vardiff would normally climb out of that within a minute, but the rig was
reconnecting every few minutes and every reconnect reset it back to 42,
so it never got there.

Shared pool now matches solo: startdiff 16384, mindiff 1000.
Nothing to do at your end — you are already on the new values, and the warning
should have cleared by itself.

2. ckpool: an invalid address no longer looks like a dead node
While looking into the above we found ckpool treating "this miner's address is
invalid" as "our bitcoind is unreachable" — marking the node dead and trying to
fail over. It had fired 899 times on the solo pool, all from a single miner
retrying a mistyped address.

To be clear: this caused no outage and nobody lost shares or payouts. With one
upstream node configured the failover had nowhere to go, so it was noise in the
logs. But it would have become a genuine problem the moment we add a second node
for redundancy — one mistyped address could have flapped the pool's connection.

Now an invalid address is rejected as exactly that, and only a real RPC failure
marks the node unhealthy. Deployed to all three instances (solo, shared, rental).
Patch is public: github.com/bitfinitechain/ckpool-bitfinite

Worth knowing if you use third-party address tools
BitFinite's cashaddr alphabet swaps q and f relative to Bitcoin
Cash. Real BFX addresses start bfx:f… — never bfx:q…. A standard
BCH address generator will happily produce a bfx:q… string that looks
right and that this chain rejects.

We swept every pool user while investigating: one account out of 76 was
affected, and that miner had already switched to their correct address. So this
is not a widespread problem — but if you see bfx:q… anywhere in your
mining config, it is wrong and any solo block found under it would be unpayable.

[bitfinitechain]

v3.0.2 binaries now on the download page

Correction to our earlier post: we linked the source repo, but the download links
on bitfinitechain.org point to the binaries repo — and that one was still
serving v3.0.0.3 from 11 July. Fixed, v3.0.2 is up there now:

https://github.com/bitfinitechain/bitfinite-core-binaries/releases/latest

If you downloaded before today, you likely have v3.0.0.3 — that build
reports its version wrong, has no DNS seed and no sync trust anchors. Worth
upgrading; it is still a drop-in swap.

Also fixed: the SHA256SUMS file on v3.0.2 listed the wrong filenames, so
sha256sum -c SHA256SUMS was verifying nothing. It works properly now —
both files should report OK.

[knurled]

Not sure if I updated within the timeframe you mentioned... If I open Core and go to Help>About BitFinite and I have the correct version (3.0.2), is it safe to assume that's accurate?

[bitfinitechain]

Yes — if About says 3.0.2, you're running 3.0.2.

The version bug I mentioned hardcoded it to 3.0.0, so affected builds always
reported *lower* than they really were (that's how v3.0.1 shipped calling itself
3.0.0). It couldn't report anything newer, so nothing older can fake "3.0.2".

If you want to double-check: `bitfinite-qt --version` prints the same string, and
the SHA256SUMS on the release page now matches the actual files — the old one
didn't, so it passed without really checking. Fixed.

Hope that helps

[knurled]

That helps a lot! Thank you for your help and guidance!