Changelog

A fresh Mac install no longer starts by dialling a pool that is switched off. The Mac default was Byron Bay, and Byron Bay is not answering: measured on 15 September from the dev box and confirmed through an independent egress, its host drops every packet on all fourteen ports we probed and its own site answers HTTP 503 "Byron Pool is paused". The default is now BTX Pool, the same one Linux and Windows moved to. Byron also leaves the automatic failover chain, by the same rule that removed minebtx — it is dead, not dear. If you chose Byron yourself, easyBTX keeps your choice and still offers it in the switcher, with a live badge that says what is true now rather than what was true when this build was cut.

BTX Pool is not the biggest pool; it is the only one an open client can reach. Of the two pools mining almost all of BTX today, one publishes no address for BTX at all and the other refuses every handshake an open miner can construct.

The census stops calling a pool "offline" when what it means is that it could not reach it. A run that got no usable answer now says "no answer to the census", and the alarm beside it names both possibilities — the pool being down, and the census's own reach falling short — instead of asserting the first. 0.26.0 was the release that brought the census to the Mac; this is the sentence it should have shipped with.

The retired-engine tooltip on the master button now shows the reason the backend actually sent. It was hardcoded to "easyBTX has no Mac engine for it yet", which is not always the reason, and it now renders the same text the warning line beside it already showed.

A few glyphs changed (⏸ → ‖, ✨ → ★, ⓘ → ℹ). They looked fine on a Mac already; they were empty boxes on Linux, and the app draws one set everywhere.

Deliberately not here: the ssl:// pool support added alongside this on Linux and Windows is refused on macOS. The Mac connects to pools itself instead of through MATADOR, and its only TLS path is one hardcoded minebtx host, so a TLS pool offered here would sit on "connecting…" forever. It is refused rather than offered-and-broken.

What a Mac actually earns, so you can decide for yourself. At today's difficulty a modern Apple Silicon Mac mining to a pool produces roughly 0.14 BTX a day — about 50 BTX a year — on a machine you already own and already have switched on. That figure is a reading, not a rate: it is your share of the whole network's work, so it falls as the network grows.

It is not a mining rig and it will not pay for itself quickly. One MatMul v4.7 episode takes about 58 seconds on an M5 while a BTX block arrives every 87, so a Mac is structurally behind a CUDA card on this chain and roughly half its work is overtaken by a new block mid-episode. Shares therefore arrive hours apart, in quiet bursts, and a share counter that has not moved since this morning is the normal state rather than a fault.

Solo mining from the built-in node earns the same per day and skips the pool fee, but it pays in whole blocks roughly every four months, so pool mining is the one to pick. The exception is worth knowing: when every pool on this chain went dark in August, a Mac was the only easyBTX that could keep mining at all, because it carries its own node. Windows and Linux stopped.

Same mining path, same pinned solver, same chain pins.

A new install no longer starts by dialling a pool that is switched off. The default pool was Byron Bay, and Byron Bay is not answering: measured on 15 September from the reference rig and confirmed through a second network, its host drops every packet on all fourteen ports we tried and its own site returns "Byron Pool is paused". A fresh install printed that on screen while sitting on it. The default is now BTX Pool, and Byron leaves the automatic failover chain by the same rule that removed minebtx — it is dead, not dear.

BTX Pool is not the biggest pool; it is the only one an open client can reach. Of the two pools mining almost all of BTX today, one publishes no address for BTX at all and the other refuses every handshake an open miner can construct. If you already chose Byron yourself, easyBTX keeps your choice and still reaches the live pool behind it, so nothing you picked is overridden.

A pool address can now carry ssl://. easyBTX previously could not even save one — the validator read the whole value as host:port and rejected the scheme — so a TLS-only pool was unreachable by construction. It is accepted now, on the platforms where the MATADOR engine is the client. This does not add a new pool; it removes our side of the obstacle, so adding one later is a one-line change.

The retired-engine message stops naming a block height it invented. A pre-Ampere card with no Classic build was told "Classic is retired from block 185000" with the number written into the sentence, while the message beside it read the real activation height from the chain rules. They agreed only by coincidence. Both read it from the same place now.

Nothing else changed. Same mining path, same pinned solver, same census, same chain pins.

The engine we tell you to switch to is now on screen. From block 185000 the status line tells a Linux user the engine they are on is retired and to switch to MATADOR. On a fresh install there was no control to do it. Every engine control was gated on the engine binary already being staged, and the AppImage stages none — matador is about 600 MB and is fetched on first use — so the app named a fix and hid the button for it. The gate is now staged-or-fetchable: a fresh Linux install shows MINING ENGINE / tap to arm. macOS keeps the old behaviour exactly.

The retired-engine tooltip on the master button had the same shape of fault. It was hardcoded to "easyBTX has no Mac engine for it yet" on every platform, including Linux, where that sentence is not the reason. It now shows the reason the backend actually sent, which is the same text the warning line beside it already renders.

Both were found by running the published 0.27.1 AppImage on the reference rig under a fresh HOME — the state a new user is in and the one this rig is not. The same fresh-HOME instance on 0.27.1 refused post-fork jobs and offered no engine control at all.

Nothing else changed. Same mining path, same pinned solver, same census, same chain pins. The code in this release has been on main since 13 September; the release is what was missing.

The empty boxes are gone. 0.27.0 fixed the pause mark and said plainly that several other symbols in the interface still had no font on a stock Linux install and drew as boxes. This finishes that: every remaining one is replaced with a mark the system fonts actually have, so nothing in the interface renders as a tofu box on a clean Ubuntu or WSL machine.

The Linux build bundles a Latin-subset text face, no symbol font and no fontconfig of its own, so any glyph outside that subset falls through to whatever the host has. On the reference rig that is DejaVu and Ubuntu, eight families in total. Six codepoints were outside it, and all six were visible: the ⓘ button beside Accepted shares and four more like it, the pick and the chain link in the status strip, the hourglass on stale shares, the star on the update banner, and a pointing hand in the report-saved message. Each is now a character those fonts can draw, chosen to keep the same meaning: an information mark, a hammer and pick, a stacked-bars mark beside the block height, a dotted circle for pending, a star, an arrow.

The test that shipped in 0.27.0 now enforces the whole set rather than documenting a backlog. Its allowlist of known-unfixed glyphs is empty, and adding to it to silence a failure is called out in the file as the wrong move. Proven the way the first one was: put a real offending character back into index.html at a real call site and watch the real test go red, not by trusting the test's own self-check.

Nothing else changed. Same mining path, same pinned solver, same census, same chain pins. This is a rendering fix.

Everything the Mac got on 10 September now reaches Linux and WSL, plus three faults found by running the build on a real rig. Linux and WSL have been on 0.23.1 since 27 August. Nothing here makes a Linux rig earn today. Measured on release day: Byron Bay, the default, serves HTTP 503 from its own site and its stratum port refuses connections; minebtx's own page is titled "Paused"; btx-pool.com is answering, and reports zero workers and zero hashrate. The one pool the census sees paying, luckypool.io, refuses every connection an open client knows how to make. What this release does is say that on the dashboard, from a source that still works when the pools' own feeds do not, and reconnect by itself the moment a pool returns.

• easyBTX reads the network census. easybtx.com measures every reachable BTX node's own headers every half hour, groups them into chains, says which chain carries the most work, and places each pool on a chain by the block hashes it publishes. The Pool card says whether your pool is paying, paused or not answering, and whether the chain it mines is the one with the most work. It concludes nothing from a census older than three hours, and it keeps three things apart that are easy to collapse into one: the census could not be reached, the census reached no pool, and the census read pools and none is paying. Only the last is a statement about BTX.
• "Paused" and "no answer" replace "connecting…". A rig on a paused pool used to show "Pool: connecting to stratum.btxbyronbay.com…" indefinitely. It now says the pool is paused by its operator, or that the census got no answer from it, and that it will reconnect on its own.
• The pool list shows what each pool is doing right now, as a live badge from the census beside the note written at release time.
• You are told where mining pays, even when it is not here — including luckypool.io, and that easyBTX cannot mine there yet.
• Balances read from btxscan. explorer.minebtx.com has been dead since mid-August, so every balance read "—". Balances and the built-in wallet now read api.btxscan.io; sending broadcasts through the same host.
• Fresh chain pins. 210,497 sits above the 5 September split, on the live chain, where the branch that lost has a different block; 199,298 sits below it, and is the last block every branch since August agrees on. Both were re-read on release day, and api.btxscan.io and this rig's own fully-synced node return the same hash for each. btxscan follows the same signer this node does, so that is one chain view checked twice rather than two independent ones — what makes it worth checking is that the census, measured from other nodes' headers, places that chain as the one carrying the most work.

Three faults, all found by running the build rather than reasoning about it:

• A pool the census could not read was reported to you as "offline". The census has a state for "the pool's own page says it is paused" and a separate one for "no usable answer from the pool's stats endpoint". The second is a fact about the census's reach, not a verdict on the pool, and the interface was printing it as "✕ offline". On release day that was provably wrong: the census could not read btx-pool.com, while btx-pool.com answered, published a block height, and accepted connections on its stratum port. It now says the census got no answer, and says that this can be the pool or the census. The release-time note on that pool, which claimed its own site said it was offline, was wrong for the same reason and has been corrected — the only "offline" on that page describes a wallet tool.
• The pool easyBTX showed as the Linux default was not the pool it mined to. Settings → Mining pool labelled minebtx "Default ·" on Linux and Windows, while the backend has resolved Byron Bay on every platform and takes no per-platform branch at all. The census can describe Byron Bay and btx-pool.com; it has no row for minebtx. So on Linux this release's headline feature had nothing to say about the very row the app called the default, and the selection dot sat on a different row once the real pool resolved. Both now say Byron Bay, which is what the backend was mining to all along.
• The "paused" mark drew as an empty box. The Linux build bundles a Latin-subset text face and no symbol font, and it ships no fontconfig, so any glyph outside that subset falls through to the host. On a stock Ubuntu 22.04 / WSL install the whole font set is DejaVu and Ubuntu, which cover every other mark the census uses but not the pause symbol: the first 0.27.0 build rendered "POOL CHAIN ▯ paused" on the release whose point is saying a pool is paused. It now uses a mark those fonts do have, and a unit test fails CI if that character comes back. That test also revealed that CI never ran this app's frontend suite at all — the job next door ran the node app's — so the miner's tests now run on every push.

Known, and not fixed here: a handful of older decorative symbols elsewhere in the interface (the ⓘ info buttons, the mining and chain marks in the status strip) have no font on a stock Linux install either and draw as empty boxes. They predate this release and shipped that way in 0.23.1. Fixing them properly means bundling a symbol font rather than swapping characters one at a time.

What did not change: the mining path. Linux and WSL mine through matador, the closed third-party solver, exactly as 0.23.1 did; the bundled CUDA pool solver is the same pinned btx-prebuilds-v0.32.11 binary, verified against its hash at build time. When a pool returns, a rig on 0.27.0 mines there without an update.

Version numbering note, and a correction. Mac and Linux alternate minor versions and share one tag namespace. The 0.26.0 notes said "0.25 belongs to Linux" — 0.25 was never cut, and the shared source tree moved to 0.26 with the Mac release, so the next number Linux can take without moving the tree backwards is 0.27.

Every pool this app can reach is down, and the app now says so instead of "connecting…". Byron Bay, the Mac default, is paused by its operator. BTX Pool's own site says it is offline. minebtx says it is paused too. Two other pools are producing blocks — luckypool.io and ninjaraider.com — and easyBTX can reach neither: luckypool's mining port refuses every connection an open client can make, and ninjaraider publishes no address to connect to. Nothing in this release makes a Mac earn today, because no pool a Mac can reach is paying. What it does is tell the truth about that on the dashboard, from a source that still works when the pools' own feeds do not, and reconnect by itself the moment a pool returns.

• easyBTX reads the network census. easybtx.com measures every reachable BTX node's own headers every half hour, groups them into chains, says which chain carries the most work, and places each pool on a chain by the block hashes it publishes. That census is what the node app grew after the 5 September split, when every node, seed and explorer it knew sat on the losing branch looking healthy. The miner now reads the same feed. The Pool card says whether your pool is paying, paused or offline, and whether the chain it mines is the one with the most work. The two older checks, block pins against the pool's own explorer and a height from a second pool, went blind together this week; the census is the one that still answers. It concludes nothing from a census older than three hours.
• "Paused" and "offline" replace "connecting…". A Mac on a paused pool used to show "Pool: connecting to stratum.btxbyronbay.com…" indefinitely, which is literally what it was doing and told you nothing. It now says the pool is paused by its operator, or not answering, and that it will reconnect on its own. The loop underneath is unchanged, so recovery is automatic.
• The pool list shows what each pool is doing right now. Each row in Settings → Mining pool carries a live badge from the census (paying, paused by its operator, offline) beside the note written at release time.
• You are told where mining pays, even when it is not here. The Pool card and the pool list name the pools the census sees paying, including luckypool.io, and say plainly that easyBTX cannot mine there yet.
• Balances read from btxscan. Pool-mode balances and the built-in wallet read explorer.minebtx.com, which has been dead since August, so every balance showed "—". They now read api.btxscan.io, which serves the same routes and, measured on release day, sits on the chain the census places the most work on. Sending from the wallet broadcasts through the same host.
• Fresh chain pins. The verified block pins moved above the 5 September split: 210,497 on the live chain, where the losing branch has a different block, and 199,298, the last block every branch since August agrees on. Both read from btxscan and cross-checked against the census, never from the pool they are used to check.

What did not change: the mining path. TENSORIUM, the Metal solver, carries the same machine code 0.24.0 shipped — the executable text of the two binaries hashes identically — and still speaks Byron Bay's stratum and BTX Pool's own dialect. Its file checksum does differ, because the build lowers the solver's minimum macOS version so older Macs can run it and then re-signs it; that rewrites the header, not the code. When a pool returns, a Mac on 0.26.0 mines there without an update.

A note on luckypool.io, because it is the obvious question. Its BTX port is TLS-only behind a self-signed certificate and, measured on 9 September, closes the connection about 120 ms after any first message an open client knows how to send: stratum subscribe with or without an agent string, the login dialect, BTX Pool's hello, an HTTP upgrade. Its site describes its recommended miner as "TLS-only and certificate-pinned" and says it "rejects protocol changes". Every miner it lists is closed source. Adding it is a conversation with its operators about the protocol, not a code change; the evidence is in docs/2026-09-09-luckypool-btx-v4-transport-probe.md.

Version numbering note, unchanged: Mac and Linux alternate minor versions and share one tag namespace. 0.25 belongs to Linux, so the Mac takes 0.26.

Everything Linux got on 23 and 27 August now reaches Mac. The Mac build has been on 0.22.2 since 23 August, cut hours before the 0.23 line landed, so a Mac has been missing two fixes that matter and a set of numbers that were wrong. Nothing in the mining path itself changed for this release; this is the Linux 0.23 work arriving on the platform it had not reached.

• easyBTX can no longer stop a miner that is working. A background auto start could run unprompted and shut down a healthy session. On the rig where this was caught the machine then mined nothing for 22 hours and never said so. The check that should have prevented it lived in the interface, which does not own the miner. It now sits with the code that does.
• easyBTX tells you when your pool is on a different chain from everyone else. On 24 August the BTX network halted and the two pools easyBTX offers ended up on opposite sides of the split, neither of them moving, while the dashboard stayed green. It now asks a second, independent pool which block it is on and says so plainly when the two disagree. It stays quiet when that second pool cannot be reached, so a pool having a bad minute is not dressed up as a chain split.
• The engine on screen is the engine that is running, the solver switch is live, and the fee shown before you arm it is that engine's own fee.
• Your pool's numbers come from your pool. Miner count, network speed, dominance and block height now follow the pool you actually selected instead of a different one that has been offline for weeks.
• Episodes tried counts your episodes, and the app no longer promises a share in a minute or two. Since the v4.7 fork one episode is the whole unit of work and pools set a floor on your difficulty, so on a slower card a first share can take an hour or more.

Version numbering note, unchanged: Mac and Linux alternate minor versions and share one tag namespace. Mac 0.24 is not "newer than" Linux 0.23, they are different products on different update feeds.

Built and verified on the release Mac: 152 interface tests and 444 Rust tests pass, the bundle reports 0.24.0, the minimum macOS version is pinned at 11.0 so no Mac that runs 0.22.2 is stranded, and the updater signature verifies against the key the app embeds.

Two silent failures, both found on a running rig rather than in a test. If 0.23.0 is working for you, nothing here changes how it mines. It changes what happens when something goes wrong.

• easyBTX can no longer stop a miner that is working. A background auto-start ran once, unprompted, and shut down a healthy MATADOR session. The rig then mined nothing for 22 hours and never said so. The engine it fell back to is retired on Linux since the v4.7 fork, so it could not mine at all: it connected to the pool anyway, failed to understand every job it was sent, and reconnected 112 times while writing a 2.1 GB log onto a disk that was nearly full. The check that should have stopped this was in the interface, which does not own the miner. It now sits with the code that does.
• easyBTX tells you when your pool is on a different chain from everyone else. On 24 August the BTX network halted and the two pools easyBTX offers ended up on opposite sides of the split, neither of them moving. The dashboard stayed green throughout, the episode counter kept climbing, and nothing in the app had ever compared your chain against anything. It now asks a second, independent pool which block it is on, and says so plainly when the two disagree. It stays quiet when that second pool cannot be reached or has nothing to report, so a pool having a bad minute does not get dressed up as a chain split. The older check could not have caught this: it compares against fixed points far back in history that both sides of the split still agree about.

A second mining engine you can actually pick, and three numbers that were lying to you.

• BTX-RC is a real engine now. The solver switch has been on screen for a while with nothing behind it. It works: pick the engine you want, then arm it. BTX-RC is an alternative, not an upgrade. On the one card we have measured, an RTX 3060, it is about 1.5x slower than MATADOR, and we have not tested it on 40-series or 50-series cards. It is offered because it is self-contained, charges no fee of its own, and backs off politely when a pool stops answering. The app says all of that before you switch.
• The engine on screen is the engine that is running. Every label follows the solver you chose, and the fee shown before you arm it is that engine's own fee.
• Your pool's numbers come from your pool. If you mine on BTX Pool the app was quietly reading a different pool's statistics, one that has been offline for weeks, and leaving your own tiles blank. Miner count, network speed, dominance and block height now come from the pool you actually selected.
• "Episodes tried" counts your episodes. It read zero for anyone using a paid engine, which is most people, while the speed above it climbed.
• The app no longer promises a share in "a minute or two." Since the v4.7 fork one episode is the whole unit of work and pools set a floor on your difficulty, so on a slower card a first share can take an hour or more. That is normal. The episode counter is what moves in between, and the app now says so instead of setting a stopwatch you were always going to lose.

A small fix to a corner of yesterday's release. If easyBTX ever stopped itself and showed a warning banner, there was no way back inside the app.

• Switching pool gets you going again. easyBTX stops and explains itself when it cannot mine: on a Mac whose graphics hardware does not support the current proof of work, or if a pool ever rejects this machine's answers. That state was meant to be recoverable by choosing a different pool in Settings, and it was not: the banner stayed, nothing restarted, and quitting the app was the only way out. It recovers properly now.

You can choose BTX Pool on a Mac now, and it is the better fit for one. It charges 1.5% where Byron Bay charges 2.5%, and it credits work differently in a way that matters a lot on Apple silicon.

• BTX Pool is selectable again on a Mac. 0.21.1 removed it because the Mac build could not speak its protocol and picking it left easyBTX sitting on "connecting" forever. easyBTX now speaks it properly. Byron Bay is still the default and is untouched.
• Why it suits a Mac. Your Mac works on one piece of the puzzle at a time and each piece takes about 40 seconds. Byron Bay only pays for work matching the newest job it sent, and it never issues a new job for the same block, so a piece that takes 40 seconds is often finished against a job the pool has moved past. BTX Pool pays for any job on the same block. That turns a large share of finished work from worth nothing into worth something.
• Honest about the trade. BTX Pool pays out on a different schedule and shares arrive less often on a modest Mac. Byron Bay remains a perfectly good choice and stays the default. Nothing changes unless you change it in Settings.
• easyBTX now tells the pool which chip it is running on, and whether that chip passed the mining self-check. We could not answer a simple question, which is which Macs can actually mine BTX, because nothing we sent came back to us in a form we could count. This rides along in the name easyBTX already gives the pool, so there is no new tracking and nothing new is collected: the chip model was already being sent. It means the next release can be aimed at the Macs that really work rather than at a guess.

BTX Pool now works properly on Linux and WSL, and the speed it shows is your own. Until now easyBTX borrowed another pool's figures to fill in that card.

• easyBTX speaks BTX Pool's own language. The app talks to btx-pool.com directly instead of guessing from a neighbour, so the rate on the pool card is the speed that pool actually credits you with, and the block height is the one you are really mining on.
• Pools this build cannot talk to are hidden, not offered. Choosing one used to leave easyBTX sitting on "connecting" with nothing to explain why. If it is in the list, it works.
• The speed readout reads in the right unit. Since the chain changed its proof of work, one attempt is a single large piece of work that takes seconds, not millions of tiny guesses per second. The old arithmetic turned a healthy rig into a 0. It now counts in the unit that matches the work, the same fix Macs received in 0.21.1.
• Carries the 0.21.0 Linux work as well: one engine control instead of three, and the warning that tells you shares have stopped landing.

Your Mac was mining, and the screen said zero. Shares were being accepted the whole time. The number next to them was wrong.

• The speed readout tells the truth again. Since the chain changed its proof of work, a Mac does one large piece of work at a time rather than millions of tiny ones. Each piece takes about half a minute. easyBTX was still counting in the old units, so a healthy Mac showed 0, which looks exactly like a machine that is not mining. It now reads in the unit that matches the work.
• A new "Episodes tried" counter. Shares are rare and get rarer. Measured over 4,283 pieces of work on one Mac: about one accepted share per 40 while the pool is still starting you on its easier beginner setting, then about one per 212 once the pool has measured your speed and adjusted. That is roughly half an hour, then roughly two and a half. Nothing else on screen moved during those gaps. This counter does, so you can see it working instead of guessing.
• BTX Pool is no longer listed on a Mac. It was added in 0.21.0 for Windows and Linux, where it works. The Mac build talks to pools itself and cannot speak this one's protocol, so choosing it would have left easyBTX sitting on "connecting" forever with nothing to explain why. It stays available on Windows and Linux.

• One engine control, not three. The engine area showed a MATADOR power button next to a solver picker that also said MATADOR, so the same word appeared twice and one control read as several. The power button now names whichever solver is selected, and the picker only appears when there is genuinely more than one engine this build can run. Today that means a single control: MATADOR ENGINE.

Older Macs are no longer turned away, and the pool fee is current. 0.20.0 refused any Mac older than an M5. That was wrong, and this corrects it.

• Your Mac is asked, not guessed at. easyBTX now puts the question to your graphics hardware itself, about half a second, instead of judging by which chip you own. If the hardware says it cannot do the work, easyBTX says so in plain language and does not start mining, so no machine burns power producing nothing. It still fails closed: a Mac that cannot answer is treated as unable.
• This opens mining to Macs 0.20.0 refused. BTX's own published measurements include a full-speed production run on an M4, using the same graphics path a newer Mac uses. The code that decides never looks at your chip's name. Older Macs that pass the test can mine, slower, and easyBTX does not pretend otherwise, but they are no longer refused for having the wrong name.
• Byron Bay's fee is 2.5%, changed by the pool on 2026-08-20. Fees are the pool's to set and can change, so easyBTX now points at the pool's own dashboard as the authority rather than a number frozen in the app.
• First share in about eleven minutes, not six hours. The pool now starts new workers on a much easier target and adjusts upward, so a working Mac sees its first accepted share quickly instead of waiting most of a day wondering.

Macs can mine BTX again. Since block 185,000 the chain has run a different proof of work (MatMul v4.7 "ENC-RC"), and the built-in engine could not solve it, so easyBTX refused every job. This release ships a solver that can, and turns mining back on for the Macs that are able to run it.

• Qualifying Macs mine the new proof of work. The bundled solver runs the ENC-RC work on Apple GPU silicon with no CPU fallback. It is checked against the network itself before shipping: it reproduces the seeds and digest of a real block the BTX network accepted (block 192,900), deriving them from the block header alone rather than being handed them.
• Your Mac is asked, not guessed at. Before mining, easyBTX puts the question to the graphics hardware itself and takes about half a second to get an answer. If the answer is no, it says so in plain language and does not start mining, so no machine burns power producing nothing. It fails closed: a Mac that cannot answer is treated as unable, never as able.
• This is not limited to the newest Macs. An earlier version of this release refused anything older than an M5 outright. That was wrong: BTX's own published measurements include a full-speed production run on an M4, and the code that decides never looks at which chip you have, it tests what the hardware can actually do. Older Macs that pass the test can mine. They are slower, and easyBTX does not pretend otherwise, but they are no longer turned away for having the wrong name.
• Expect very few shares, and expect that to be normal. One attempt is a single indivisible ~36 second computation on an M5, so a working Mac produces roughly 4 to 5 shares a day and can legitimately show none for hours. That is the workload, not a fault.
• Honest about the state of it. No share from a Mac has been accepted by a pool yet. The solver's correctness is verified against the chain, but the earning path is not proven, and this release does not pretend otherwise.

• Your hashrate was never zero. easyBTX showed "0.00 ep/s" and "0 N/s" on almost every graphics card while mining perfectly well and having shares accepted. The mining engine rounds its own speed down to a whole number before printing it, and a normal desktop card runs at about a fifth of one unit per second, so the number it printed was zero. An RTX 3060 was reporting nothing while earning. The app now measures the rate from the engine's episode counter, which is exact, and shows the real figure. Two things went wrong beneath that. The large speed figure on the dashboard was only drawn when that zero was above zero, so it did not appear at all. And the warning that tells you shares have stopped landing while the engine is still working was switched off by the same zero, on exactly the cards most likely to need it. Both are fixed.

• Block height showed another pool's number. If you were not mining on Byron Bay, the height came from minebtx, whose node has fallen about eleven thousand blocks behind the chain. The app now uses the height from the pool you are actually mining, which cannot disagree with itself.

• minebtx is no longer used as an automatic backup pool. Its server still accepts connections while serving no work, which is the kind of outage that looks healthy from inside the app: connected, no errors, nothing earned. It reports no active workers and no blocks found in a day. You can still choose it yourself, and it will come back; it is simply not somewhere the app sends you on its own any more. The backups are now Byron Bay and BTX Pool, both live and both charging the same 1.5%, so being moved between them costs you nothing.

• A third mining pool: BTX Pool (btx-pool.com:3334). 1.5% fee, PPLNS over a rolling 30-minute window, paid in the coinbase. It is not btxpool.org, the pool this app deliberately excludes for handshaking and then mining nothing; different operator, different host. It was verified to actually earn before being listed: the dev rig's own worker is credited 0.142 to 0.194 ep/s against 0.19 declared, with a real slice of the payout split, and pool-wide more than a hundred matador workers hold credited hashrate there. Slow cards should expect to wait. Vardiff has a floor tuned for fast rigs, so a card around 0.18 ep/s averages roughly one share an hour here and will show no credited hashrate in about two of every three half-hour windows while mining perfectly well. Earnings are not lost, because a share that lands is credited in full; the swings are just wider. Byron Bay remains the better choice if you want to see quickly that mining works.

• The engine controls moved out of the way of the Start button. The MATADOR power switch used to render on top of the one control that starts mining: Start is positioned over the visualiser and takes no layout space, so the switch below it filled the same spot. Both engine controls now sit together at the bottom right, under the command sheet.

• A solver switch. MATADOR or BTX-RC, with power and choice kept as separate controls, so picking a solver never starts mining by surprise and switching off never silently changes the choice. BTX-RC is an alternative, not an upgrade: it is self-contained, takes no dev fee where MATADOR takes 1%, and reconnects with backoff, but it measured slower than MATADOR on an RTX 3060 (7.96 against 5.3 seconds per episode), and its --lanes option is far worse than useless on a 12 GB card. It is offered for hardware where MATADOR does badly, and the interface says so rather than promising speed.

The node-update machinery catches up with BTX Core 0.33.3, the release that schedules the network's hard fork at block 191,714.

• Node updates can install BTX 0.33.3. BTX published 0.33.3 as a native build without a GPG signature, which our installer, correctly, refused outright. Rather than weakening that rule, the app now carries its own SHA-256 fingerprints of the exact 0.33.3 release files, measured from the release the day it was published and re-verified by downloading and hashing the files themselves. The installer accepts precisely those bytes and nothing else: a file that differs in a single bit is refused before anything is installed. Unsigned releases we have no fingerprints for stay uninstallable, exactly as before.
• The update check can no longer be blinded by a tag-only release. On fork day the v0.33.3 tag existed for 33 minutes before its GitHub release object; for that window the Settings panel still answered "up to date". The check now falls back to the repository's tag list when no release object answers, and accepts only tags shaped like real node releases, so the repo's lineage and experiment tags can never be offered as an installable update.
• "Update node" no longer starts a daemon on installs that never ran one. Applying a node update now restarts the node only if a node was actually running before the update; on current builds (Solo retired) it installs the new version, records it, and leaves it at that.
• The app's baseline node release pin moved from v0.33.1 to v0.33.3.

The app can now tell you whether your pool is mining on the real BTX chain. During the August 11 chain split, the app's default pool spent days mining a losing branch, shares kept landing, dashboards looked normal, and nothing anywhere could say that none of that work would ever pay. This release removes that blind spot.

• New "Pool chain" check on the Pool card. easyBTX now ships with two verified block fingerprints from the BTX chain and asks the pool's own explorer what it has at those heights. If they match, the card shows a calm green "verified ✓". If the pool answers with a different history, the card says so in plain words, mining there may not pay, and the pool picker shows the same warning on that pool's row so the moment you go to switch, the reason is right there. If there is no answer, the row shows ",": unknown is shown as unknown, never as green. (Found while building this: Byron Bay's explorer still lists one leftover row from the August split, below the old fork point, while its node is on the right chain. The check recognizes that leftover for what it is and does not raise a false alarm over it.)
• The minebtx pool entry says what is actually wrong with it. Its stats page came back online, but the pool behind it did not: measured on August 17, its node is stuck about 6,100 blocks behind the network, no miners are active on it, and its mining port accepts a connection and then never answers. The entry's note now says its node is stuck behind the network, replacing the older "not responding" wording that no longer matched what we measured.
• A pointer to Keeper mode. The About screen now mentions that a Mac that isn't mining can still help keep the BTX chain verifiable, via the free BTX Node app's Keeper mode, with a link to easybtx.com/keeper.

Mac catches up with the reliability work Linux got in 0.15.0, stops shipping a node it never starts, and pins the minimum macOS version so an update can never strand a Mac that cannot run it. Mining on Mac is still not available, but we now know exactly what is missing, and it is not your hardware.

• Your Mac's GPU can do the new work. We measured it. BTX's own node ran a full production episode of the new algorithm on an Apple M4 in 90.6 seconds, entirely on the GPU, with no fallback to the processor at any point. The same test on an older M2 Pro takes 218 seconds. So Apple Silicon is not the problem, and the Metal code to drive it already exists. What is missing is a mining program for Mac that speaks the new algorithm. The one easyBTX ships was built before the change and can only do the old work, which is why it stops rather than burning your battery on results the network will reject. That program is what has to be rebuilt, and it is the next thing we are doing.
• The reliability fixes from 0.15.0 now apply on Mac. The error banner clears itself instead of sticking forever, easyBTX stops redialling a pool that accepts a connection and then drops it (which can get your address refused for hours), the block explorer backs off when it is unreachable instead of retrying in a loop, and the status screen says "waiting" when it is waiting rather than claiming to be mining.
• The app no longer carries a copy of the BTX node it never runs. It was 27 MB of the download, it had not been started since the Solo mode it belonged to was retired, and the version bundled was the one that stops at block 185,000 after the algorithm change. Removing it makes the download smaller and removes a way for things to go wrong.
• The minimum macOS version is pinned to macOS 11, which is what 0.14.2 required. Nothing in the build had ever fixed this, so the answer was whatever the machine that did the build happened to default to. A newer build machine would have quietly raised it, and Macs below the new floor would have been offered an update they could not open, with no way back. It is now fixed in the build itself and checked after every build.

The dashboard read zero while the engine mined fine, the default pool went down, and the mining engine was overcharging its own fee. All three are fixed here.

• Your hashrate reads a real number again. The mining engine changed what it counts. It used to report nonces; since the algorithm change it reports episodes, where one episode is a full solve of the new work and takes roughly thirty seconds on a card like a 3060. easyBTX was still looking for the old field names, found nothing, and showed zero. It now reads the new ones and prints the unit the engine actually used, so an episode rate is never dressed up as a nonce rate. The two differ by about a hundred million to one, so this is not a cosmetic distinction.
• The error banner clears itself again. It was wired to clear only when the old hashrate field went above zero. That field stopped existing, so the banner could never clear and any passing hiccup stayed on screen permanently. It now clears on a rate the app can actually read, or simply on the engine's work counter moving.
• easyBTX stops hammering a pool that is not answering, which can get your address blocked. When a pool accepts a connection and then drops it, the engine redials once or twice a second and never slows down. We measured about two hundred connections from one machine in fifteen minutes, and that machine was then refused by the pool for hours while the pool kept serving everyone else. easyBTX now notices the pattern, stops reconnecting, tells you the pool is not answering, and waits before trying again. It resumes on its own the moment the pool responds.
• The default pool is now Byron Bay. minebtx is down: it returns an error on every web address it has, and its mining port accepts connections and then closes them without a word. Byron Bay is running normally, with over two hundred miners on it. If your install was still pointed at minebtx it is moved across once, automatically, so it can mine. minebtx stays in the pool list and you can select it again at any time; that choice will be kept.
• The mining engine was charging more than its stated 1% fee, and easyBTX made it worse. The engine positioned its fee window using how long it had been running, and that clock restarts at zero every launch, so every start landed inside the fee window. easyBTX restarts the engine on a schedule to collect its own fee, so easyBTX rigs restarted more often than most and paid the engine's fee more often than they should have. The engine's v0.9.24 fixes it. easyBTX now requires that version or newer and replaces anything older on its own.
• The "you are earning nothing" warning stops crying wolf. Pools raise your share difficulty as you mine, which legitimately makes shares arrive far less often, and after the algorithm change one share can take hours by design. The warning now allows for that, says what your difficulty is, and stays quiet when the real problem is simply that the pool connection is down.
• MATADOR "Classic" for older graphics cards is finished, and we are saying so plainly. Classic was the build for pre-Ampere cards, meaning GTX 10-series, RTX 20-series and similar. The engine's makers retired those builds when the algorithm changed, and have published none since. There is nothing left for easyBTX to install and nothing that can mine the current algorithm on those cards. If that is your card, easyBTX stops rather than running your GPU on work the network will reject, and tells you why. Nothing you can change in easyBTX alters this.
• Balance lookups stop hammering an explorer that is down. The block explorer runs on minebtx, which is currently returning errors, and easyBTX was retrying it about five times a second. It now pauses for half a minute after a failure and resumes as soon as the explorer answers. Your balance shows a dash while it cannot be read, which is the honest answer, and it was already doing that.
• The pool connection indicator reflects the engine's own connection state instead of assuming it is connected whenever the engine is running. While easyBTX is waiting out a pool that will not answer, the status line says exactly that instead of "connecting to the pool", and the engine badge reads WAITING rather than ENGAGED.
• The engine is re-checked before each mining session rather than only at startup, so a fix published mid-session reaches you without restarting the app.

Nothing about your wallet, payout address, or settings changes.

Says what is actually happening after the algorithm change, instead of sitting on "starting".

• The screen was lying. 0.14.1 stopped correctly at block 185,000, but the status line still read "Pool: starting…" and the button kept pulsing, so it looked like the app was stuck. It had stopped on purpose and simply failed to say so. Now the explanation takes precedence over every routine line, and the button reads Stopped.
• Your Mac is not mining, and that is not a setting you can change. BTX replaced its mining algorithm outright at block 185,000, and no Mac engine for it exists yet.
• Your hardware is capable of it. We ran BTX's own software on an Apple Silicon Mac and it completed the new work on the GPU at full production settings. This is a matter of building the engine, not of your machine being too old. We are working on it, and we would rather say that than show a hashrate that means nothing.
• Payout address, settings and balances are untouched.

BTX changes its proof of work at block 185,000. This is the Mac side of that change.

• The built-in easyBTX engine stops at the fork, and says so. It solves the old algorithm only, and BTX has no replacement build of it. Rather than run your GPU flat out on work the network will reject, easyBTX stops at block 185,000 and tells you what happened. Before the switch it shows a live countdown read from the pool's own jobs, so the timing comes from the chain rather than from a date we guessed.
• There is no Mac mining engine for the new algorithm yet, and we will not pretend otherwise. MATADOR is not the answer on a Mac: we checked its macOS build directly, and its solver for the new algorithm runs on the processor rather than the graphics card. On an M2 Pro a single attempt ran for over five minutes without finishing, where a graphics card takes about thirty seconds. Pointing you at it would heat your Mac up for nothing, so easyBTX does not.
• The good news: your Mac can do this work. We put BTX's own v0.33.2 software on an M2 Pro and it completed a full-size attempt of the new algorithm on the GPU, at the real production settings, with no fall back to the processor, and it qualified against BTX's own reference list. So the hardware is capable. What is missing is an engine that drives it, and that is what we are building next. No date promised until it works.
• Honest reporting when mining stops paying. A live scan rate with no credited shares is now reported as the problem it is. Engine failures stay on screen instead of being erased by the next status line, and stale numbers are cleared when the engine restarts rather than left frozen.
• Automatic pool failover. If your pool stops answering, mining rolls onto the other vetted pool by itself within seconds. Your chosen pool is always tried first.
• Delivered over the self-updating channel, nothing to reinstall.

BTX changes its proof of work at block 185,000. This release keeps you mining through it.

• MatMul v4.7 ready. BTX v0.33.2 replaces the mining algorithm outright at block 185,000, no signalling, no grace period, no fallback to the old one. easyBTX now ships the MATADOR engine build that implements the new work (v0.9.2+), so mining carries on across the switch. The pool decides when the new work starts; easyBTX follows it.
• A live fork countdown, and proof you're on the new algorithm. The MATADOR card shows how many blocks remain before the switch, and afterwards confirms that the engine is genuinely solving the new proof of work, read from the pool's own job, not from anything the app assumes.
• The engine is now downloaded on first use instead of bundled. The new engine build is ~600 MB, which would have quadrupled the app download for everyone. Instead easyBTX fetches it once, when you first switch MATADOR on, shows the progress, and verifies its SHA-256 against the publisher's checksum before it is ever allowed to run. The app download stays small, and you always get the current engine.
• It will now tell you when you're mining for nothing. Previously, if the engine kept running but stopped earning, the dashboard carried on showing a healthy hashrate and a share counter that quietly stopped moving. easyBTX now watches for exactly that, a live scan rate with no credited shares, and says so. Genuine engine failures (a pool refusing the connection, a fall back to CPU) now raise a warning that stays up instead of being erased by the next telemetry line, and stale numbers are cleared when the engine restarts rather than left frozen on screen.
• Automatic pool failover. If your pool stops answering, mining rolls onto the other vetted pool by itself within seconds instead of simply stopping. Your chosen pool is always tried first. This was not hypothetical: while this release was being prepared one pool began refusing our engine while staying perfectly healthy for its own miners, and anyone on it earned nothing until they changed a setting by hand.
• The built-in easyBTX engine stops at the fork, honestly. It solves the old algorithm only, and there is no replacement for it. Rather than burn your GPU on work the network will reject, it now stops at block 185,000 and explains that MATADOR is the way to keep mining.
• Older NVIDIA cards: please read. The MATADOR engine has retired its Pascal, Volta and Turing builds, its notes state the new proof of work needs Ampere-or-newer tensor cores. So cards like the GTX 10-series, GTX 16-series and RTX 2070 can mine right up to block 185,000, and we expect them to stop there. easyBTX now says so plainly and stops, instead of silently restarting an engine that cannot work. If that changes, the engine authors ship a new build, or these cards turn out to work after all, we will update and say so.
• Delivered over the self-updating channel, nothing to reinstall.

Macs can now choose their mining pool, and the default is the cheaper one.

• Mining-pool switcher, now on Mac. In Settings you can choose which pool your Mac mines to, Byron Bay (the new default) or minebtx, or enter a custom host:port. Only pools verified to actually earn are listed; your payout address carries over, and the dashboard shows the pool you're on. Custom pools are advanced, most BTX pools speak a different stratum protocol and will silently mine nothing, so if shares stay at zero, switch back.
• Byron Bay is the default for new installs on Mac. Its pool fee is 1.5% instead of minebtx's 2.5%, so a little more of every share stays with you. If you're already mining on minebtx, an update keeps you there, nothing switches under you, and you can move to Byron Bay, or back, anytime in Settings.
• The block explorer is now btxscan.io, easyBTX's own BTX explorer, everywhere the app opens a transaction or address.
• Solo mode bundles the latest BTX node (v0.33.1). No consensus change; it brings the newest wallet-interop fixes from the BTX team.
• Fresh links. The Links panel now points to the BTX portal (btx.best), exchanges live at btx.best/exchanges, and community chat is the easyBTX Telegram (t.me/easyBTX).
• Stats follow your pool. The dashboard and the Community panel now say which pool you're on and show that pool's own numbers, miners online, pool dominance, and the "Open pool dashboard" button all follow your selection (Byron Bay's dashboard for Byron Bay, minebtx's for minebtx). The old "pool blocks found (24 h)" tile is gone, and quiet stretches read as "quiet now" instead of a scary "~0.0/min".
• Two speeds, side by side. Pool mining now shows the big two-row readout: what your GPU is actually trying (e.g. 15.01 MN/s, HARDWARE) stacked over what the pool credits you (e.g. 218 N/s, POOL · COUNTS). They differ by roughly a thousand times, that's normal, not a bug, and the credited figure is the one your pool's dashboard shows, so the two finally agree. (Those numbers were previously missing from the pool screen entirely.)
• Clearer fees. Now that pools differ, the app says it straight everywhere: easyBTX takes its 4.99% tool fee, and your pool takes its own on top (Byron Bay 1.5%, minebtx 2.5%). Payout terms are no longer described as if every pool paid on minebtx's schedule.
• Quieter in the background. The animated starburst now pauses whenever the window isn't the one you're looking at (minimized, or just behind another app), and resumes when you come back. On a Mac the animation shares the GPU with mining, so leaving it running in the background cost a little speed and a lot of extra fan and battery, starting mining and switching to other work is now the efficient path.
• Honest GPU readout on Mac. A Mac can't accurately measure its own GPU from inside the app while mining, so the old "GPU load / watts" figures were a low, wrong guess. Rather than show a misleading number (to you or on the pool dashboard), the app now shows "," on Mac. Your GPU is still fully at work; we just won't pretend to a precision we don't have.

The dashboard now heals itself, and pool switching says what it means.

• Self-healing dashboard. On some Linux setups, WSL2 especially, the system's WebKit render process can die after minutes or hours of running. Until now the window silently froze on its last frame (or eventually went white), even though mining kept running untouched in its own process the whole time. easyBTX now detects the moment that render process dies and reloads the dashboard automatically, it's back live within a couple of seconds, and the app logs why the render process died. To be clear: mining, shares, and payouts were never affected by this; the window just looked dead.
• Clearer pool switching. After switching pools, the status line used to say "Switched MATADOR to Byron Bay", which read as if the engine changed. MATADOR is the engine, and it mines on whichever pool you pick. It now says: "Pool switched to Byron Bay, MATADOR is mining on it now."
• Delivered over the self-updating channel, nothing to reinstall.

Choose your mining pool, and a new home for the block explorer.

• Mining-pool switcher (MATADOR). In Settings you can now choose which pool MATADOR mines to, minebtx (the default) or Byron Bay, or enter a custom host:port. Only pools verified to actually earn with the MATADOR engine are listed; your payout address and fees carry over, and the dashboard shows the pool you're on. Custom pools are advanced, most BTX pools speak a different stratum protocol and will silently mine nothing, so if shares stay at zero, switch back. The built-in engine stays on minebtx.
• The block explorer is now btxscan.io, easyBTX's own BTX explorer, everywhere the app opens a transaction or address, plus the explorer links on this site.

The MATADOR engine gets faster, and older NVIDIA cards (Turing / RTX 2070) are now supported.

• MATADOR engine updated to v0.8.53 (from v0.8.28), it adds a hybrid CPU+GPU solve path and tracks the latest pool protocol, so a card mines harder in MATADOR mode. Your dashboard readout, wallet, payout address and settings are unchanged.
• "Classic" build for older GPUs. MATADOR now ships a dedicated build for pre-Ampere cards, Turing (RTX 2070, GTX 16-series), Volta and Pascal (GTX 10-series). easyBTX bundles both and picks the right one automatically from your GPU, so those cards can finally run MATADOR mode properly instead of stumbling on a build meant for newer hardware. On a real RTX 2070 this nearly tripled the pool rate (measured ≈2.7×, and the card runs fully saturated instead of stuttering).
• Delivered over the self-updating channel, nothing to reinstall.

The main miner's bundled node moves to the latest BTX core, matching easyBTX Node.

• Bundled node → BTX v0.33.1 for the miner's faststart path (was v0.32.11). The pinned snapshot is now btx_core::snapshot::v0_33_1_spec() (height 155,700, v9 format, verified SHA-256 e0fb6d34…5fc69e), the same asset easyBTX Node already uses. New installs bootstrap on the current node with the corrected external-miner getblocktemplate context and the v0.33.0 mainnet-hardening refresh; existing installs already update the node in-app. Only the (disabled) Mac Solo path uses the bundled node, so this is a maintenance refresh that keeps miner and Node on one pin.

Polish: the "POOL · COUNTS" readout no longer shows a stray , N/s.

• Fixed the "POOL · COUNTS" rate on the main screen showing a blank , N/s. Two things fed it: a CSS rule kept that row visible even when it had no value to show, and in MATADOR mode the app couldn't resolve its pool-side rate from the pool's public API. Now the row hides cleanly when there's genuinely no rate, and in MATADOR mode it shows matador's own credited rate (the same number the pool counts) instead of a dash.
• Pool-worker lookup now also tolerates the pool's (client) name suffix (e.g. 3060-ECHO-1-eBTX (GANGBANG-eBTX)), so the built-in engine resolves its rate too.
• Your mining and share crediting were always correct, this was only a cosmetic secondary readout.

MATADOR is now an unmistakable, one-tap engine right on the dashboard.

• The MATADOR button is now a real engine ON/OFF toggle. Tapping it arms the closed ~2.3× engine (after the one-time fee disclosure) and it lights up to read "MATADOR ENGINE · ON"; tapping again switches back to the free easyBTX engine. It stays in sync with the switcher in Settings and the Lab.
• A bold MATADOR sticker ignites on the left of the dashboard while the engine is running, showing the live scan rate (MN/s), so there is zero doubt the fast engine is engaged.
• Carries forward the live readout: the mode chip reads "MATADOR" and the big speed number leads with MATADOR's scan rate while it runs.
• Adds a startup safety net so a rare bootstrap error surfaces a visible notice instead of a silent, inert screen.

Supersedes v0.10.6 (which was reverted before it shipped to the fleet). The Linux launch white-screen guards, the GL-stripped AppImage and the WebKit software-render env (DMABUF/compositing off, llvmpipe), remain in place.

MATADOR is now unmistakable on the main screen.

• The mode chip now reads "MATADOR" (instead of "POOL") whenever the MATADOR engine is running, so you can tell at a glance which engine is active.
• The big speed number now leads with MATADOR's scan rate in MN/s, its true headline throughput, instead of the smaller credited rate. The share count and credited rate are still shown alongside.

MATADOR now shows its real numbers on the dashboard.

• Fixed the "0" readout in MATADOR mode. The dashboard could show 0 hashrate and 0 shares while MATADOR was actually mining at full speed, so it looked broken when it wasn't. Root cause: the app was reading MATADOR's live stats from the wrong output stream, so the numbers never reached the screen. Fixed, hashrate, shares, and GPU stats now update live everywhere on the dashboard.
• MATADOR's live rate and share count are now also written to the app log, so if anything looks off you can send a log that actually contains the numbers.

MATADOR connection stability.

• Fixed MATADOR dropping shares. A safety check in the app could restart the MATADOR engine during normal pool reconnects and difficulty changes, which interrupted mining and dropped accepted shares. Removed it, MATADOR has its own reconnect handling, so it now holds a steady connection and keeps submitting shares.
• General stability improvements.

Stability and reliability fixes, focused on Linux and MATADOR mode.

• Fixed a Linux launch issue. After updating, some Linux setups could crash on start or open to a blank white window. Fixed, the app now starts reliably across different GPUs, desktops, and WSL. If an older build is stuck and won't open, reinstall from easybtx.com and it's sorted.
• MATADOR shows its status on the dashboard. With MATADOR on, the main screen now shows it actively mining (rate + shares) instead of sitting on "starting", and your balance displays correctly while it runs.
• MATADOR stays on. If the engine ever hits a hiccup it now retries and keeps running, instead of quietly falling back to the built-in engine.
• General bug fixes and stability improvements.

No change to fees or how mining works, same engine, same shares.

A new opt-in high-performance engine. Most people should stay on the built-in easyBTX engine: it's free, open, and mines only to your own wallet. But if you want maximum speed and don't mind a small extra fee, you can now switch the whole mining engine to MATADOR in one tap.

• MATADOR mode, an engine switch. A closed, third-party mining engine measured ~2.3× faster on NVIDIA cards. It's opt-in and clearly disclosed. Fees while it runs: MATADOR's own 1% plus easyBTX's standard 4.99%; everything else mines to your own wallet. MATADOR replaces the easyBTX engine while it's on.
• One-tap MATADOR TURBO. A new button on the dashboard arms MATADOR: it opens the Lab, shows you the engine card and a plain-language disclosure, and switches the moment you confirm, with a live "ULTRA POWER" readout of speed, shares and GPU while it runs.
• Where to find it. Dashboard → MATADOR TURBO, or Settings → Mining, or the top of the Lab. Turn it off any time to return to the free easyBTX engine.
• Honest by design. The switch spells out the trade-off up front: the closed engine, the 1% fee, and that it replaces the easyBTX engine, so it's always your informed choice.

No change to the built-in easyBTX engine: same shares, same speed, same fee as before. MATADOR is purely an extra option.

The Windows/Linux (WSL) interface release. Brings back the small "Mini" window, adds a Codename label so identical rigs are easy to tell apart on the pool, and gives you a clear (and clearly-marked-risky) path to overclocking for a few extra percent. No change to the mining engine, same shares, same speed out of the box.

• Mini mode is back. Toggle between the standard Wide dashboard and the small, compact Mini orb with the layout button or the Space bar. Mini stays out of the way while you work; any menu, info or settings panel automatically opens in Wide so nothing is ever cramped, then drops back to Mini when you close it.
• Worker Codename line. Under "This machine's worker" there is now a "Codename:" label showing your own miner name. Because identical hardware gets the same auto-assigned pool name, this makes your rig easy to spot on the dashboard. Editing the name in Settings updates the line right away.
• Power & Overclock (advanced). A new fire-marked card in the Optimization Lab links straight to MSI Afterburner, the one tool that can actually raise the GPU core clock on Windows/WSL, with an info button warning that overclocking adds heat and needs good cooling. The WSL cheat sheet gains a copy-paste "Power & overclock" section (check clocks, raise the power limit, lock a higher clock, undo), noting that the example values are per-card and that the clock-lock is ignored under WSL/WDDM (use Afterburner there). Optional, the miner already runs at the optimal solver settings without it.
• Same mining engine, same shares, no consensus change. The dev fee is unchanged. macOS is unaffected by this release.

Your Mac now keeps mining at full speed even when you lock the screen or step away.

Two things were quietly costing some Macs their hashrate, with no sign anything was wrong. macOS "App Nap" throttles background apps, so whenever the screen locked or the app sat behind other windows, the miner slowed to a fraction of its speed. A Mac left mining overnight could earn a fraction of what it should. And a Mac left idle would simply go to sleep and stop. This release fixes both, and adds a warning if your charger is too small to run the chip at full speed.

• Keeps mining when the screen is locked or the app is in the background. macOS no longer throttles the miner while you are away, so a Mac left mining overnight earns at full speed the whole time.
• Stays awake while mining. If your Mac is set to sleep when idle, it now stays awake as long as the miner is running, so it does not quietly stop earning. It sleeps normally again the moment you stop mining.
• Warns about an underpowered charger. A small USB-C charger power-caps the chip and can cut mining speed by 3 to 4 times. The app now tells you if your charger is too small. Use the 67W or higher charger that came with your Mac for full speed.
• Exact same mining engine and shares. These are reliability fixes only, no consensus change. Windows and Linux are unchanged.

The Apple Silicon speed + connectivity release. Faster mining, and it now works on locked-down networks without a VPN. Auto-updates, so most Macs pick it up on their own within ~30 minutes, nothing to do.

• Faster Apple Silicon mining. A new optimized Metal solver from the pool (embedded GPU kernel, Opt#1/#3/#5) scans more nonces per second on the very same Mac. Verified bit-for-bit identical results to the previous solver before shipping, so every share the pool credited before it still credits, just more of them.
• Mines through blocked networks, no VPN needed. On hotel, office, or firewalled Wi-Fi where the plain mining port is blocked, easyBTX now automatically falls back to a secure TLS connection on port 443 that looks like ordinary HTTPS. It just keeps mining where it used to stall.
• Still runs on macOS Ventura 13 and up (Sonoma and Sequoia included), same as 0.8.10.
• Windows and Linux are unchanged in this release.

The Linux & WSL release. easyBTX now updates itself, mines through blocked networks, and is far easier to run on a Windows PC through WSL.

On Windows? The fast path is WSL. 🔥 Native Windows still works, but the Linux build, running inside WSL on your Windows machine, uses the modern V3 mining engine and earns substantially more on the very same NVIDIA card. Same one-click feel, far more hashrate, and it keeps itself up to date.

• Auto-update comes to Linux & WSL. Once you're on this build, easyBTX keeps itself current on its own. New versions download, verify, and install automatically, exactly like the Mac. No more re-downloading, no commands. Every update is cryptographically signed and verified end-to-end, so a bad or tampered update can't install. This is the big one: set it up once, and it stays current forever.
• Mines through blocked networks, no VPN needed. On hotel, office, or firewalled Wi-Fi where the plain mining port is blocked, easyBTX now automatically falls back to a secure TLS connection that looks like ordinary HTTPS traffic. It just keeps mining where it used to stall.
• A built-in WSL command cheat sheet. A new in-app page with copy-paste commands for Windows/WSL users (start the miner, check the GPU, restart, update), each with a one-click Copy button and a colored badge telling you exactly which terminal to run it in (PowerShell, Ubuntu/WSL, or CMD). No command-line experience required.
• A wider, more readable window on Windows and Linux that opens in the roomy desktop layout and stays put.
• Experimental updates channel (opt-in). In Settings you can turn on early test builds and receive them in-app, one click, before they go public, for users who want the bleeding edge.
• Mac is unchanged in this release.

Apple Silicon Macs on older macOS can mine again, including Ventura, Sonoma, and Sequoia.

The bundled Metal solver had been built for the newest macOS only, so on macOS Ventura (13), Sonoma (14), and Sequoia (15) the app opened but the miner quit the instant it tried to start, leaving it stuck on "Starting…". This release ships a solver built to run on those older systems, so those Macs mine normally again. If you're already on the latest macOS nothing changes for you, and it updates automatically.

• Runs on macOS 13 (Ventura) and up. The previous build needed the very latest macOS; this one supports Ventura, Sonoma, and Sequoia too. Affected Macs go straight from "Starting…" to finding shares.
• Exact same mining engine, verified bit-for-bit. The consensus seeds and per-share digests are byte-identical to the pool's official build, so every share you find stays valid. This is purely a compatibility rebuild, not an engine change, and the speed is unchanged.
• Windows and Linux are unchanged in this release.

Apple Silicon Macs mine about 4–5× faster.

The Mac build had a bug that quietly held the Metal miner far below what the chip can actually do, so every Apple Silicon Mac was running at a fraction of its real speed. This release fixes it. Nothing to change on your end, it updates automatically.

• About 4–5× more hashrate on Apple Silicon (M1 through M5). On an M2 Pro we measured a jump from roughly 50 to around 190–275 N/s. Just keep the app open and you'll watch it climb.
• Same canonical mining engine as the pool's official build, verified bit-for-bit identical to the reference, so every share you find stays valid.
• Windows and Linux are unchanged in this release.

Apple Silicon Macs mine noticeably faster, same engine, better tuned.

• Macs now use all their GPU cores by default. The old default held the Metal solver back to a fraction of the chip. On an M2 Pro we measured roughly 1.4–1.8× more sustained throughput from this change alone, and in the live pool a tuned M2 Pro now out-earns stock M4 and M5 machines. Every Apple Silicon Mac benefits automatically, there's nothing to change.
• Better Metal GPU buffer sizing. easyBTX now sizes the GPU's work pool to the GPU rather than letting it default low. This especially helps the smaller fanless Macs (Air-class), which were quietly running at about half speed.
• Windows and Linux are unchanged.

Mac switches to the new V3 engine, now the whole fleet is on V3.

• Mac now runs the new V3 engine. We confirmed the Apple Silicon (Metal) build of the new engine runs well on Mac, so easyBTX now mines with it. After the recent BTX network upgrade, V3 is the engine the pool credits, so this keeps your Mac earning valid shares.
• Linux and WSL2, already on the V3 engine since 0.8.3, unchanged.
• Windows, native Windows keeps the proven engine; the in-app banner still points you to the free WSL2 build, which runs the fast V3 engine (there's no native-Windows V3 build yet).
• Quieter updates, behind the scenes. easyBTX now watches the pool's engine channel and can pick up a newer mining engine on its own, but only after it has verified the download and confirmed the engine actually runs, so you never end up on an untested one. A brand-new engine we haven't vetted is just flagged for review, never auto-installed.

Linux and Windows-via-WSL2 get the fast new engine.

• Big speed jump on Linux and WSL2. The BTX team's pool update plus the new v0.32.11 engine unlocked a large throughput gain on NVIDIA cards. easyBTX on Linux, and on Windows through WSL2, now runs that engine and mines much harder than before.
• Windows: switch to WSL2 for the fast engine. Native Windows keeps the proven, stable engine (it still earns), and the in-app banner points you to the free WSL2 build, which runs the faster new engine.
• Mac keeps the proven fast engine for now. The matching Mac (Metal) version of the new engine isn't out yet, so Apple Silicon stays on the engine it already runs (which is faster on Mac today). Your Mac mines at full speed the whole time; we'll switch it over the moment the Mac engine is ready.

New app features, on the engine you already have, so nothing slows down.

• All the new conveniences, none of the speed cost. This update adds the new app features below while keeping the proven, fast mining engine you're already running. The newer engine from the BTX team is still being sped up, so we held it back rather than ship anything slower, your hashrate and earnings are unchanged.
• First-run payout helper, new here? A simple popup asks for your BTX payout address (or helps you grab a wallet) so you never sit on "starting…" without earning.
• Auto-heals a stuck connection, if the pool ever connects but sends no work, easyBTX now notices and reconnects on its own.
• New "Mono" color theme and a clearer Deep-Tune readout when an overnight tune finds no improvement (was an unreadable box).
• Under the hood: the bundled node and tidy-up were refreshed. When the BTX team's faster new engine is ready, a later update will switch to it automatically.

The Linux/WSL2 speed fix, a big first step.

• Linux and WSL2: a big speed recovery. The BTX core team's v0.32.11 solver gets your GPU working properly again after the network upgrade (the previous build left it mostly idle). It's a major jump over that build, and the BTX team is still working on further speed gains for the new engine, so expect more to come.
• Bundled node updated to v0.32.11 and its newer snapshot, ready for BTX's next network step at block 132,000.
• Mac stays on the current engine for now. The matching Mac (Metal) build from the BTX team is still on its way. Your Mac mines valid the whole time.
• Windows (native) continues on the proven engine; the in-app banner points you to the WSL2 build, which runs the new engine.

A required mining upgrade, and Mac joins the newest engine.

• Required upgrade for everyone (BTX block 130,500). BTX is changing how mining works ("MatMul-V3") at block 130,500. From that block on, older versions stop earning until they update. easyBTX 0.8.0 has the new engine built in, so updating now keeps you earning right through the change. Mac and Linux update automatically.
• Mac runs the newest engine. Apple Silicon Macs move to the freshly rebuilt v0.32.10 Metal solver, the first Mac engine update since the last fork.
• Windows: one step to keep earning. The new engine can't run natively on Windows yet, so easyBTX shows you how to switch to the free WSL2 (Linux) build, which runs it fully. Your current Windows version keeps earning right up to the upgrade.
• First-run payout helper. New here? A simple popup now asks for your BTX payout address (or helps you grab a wallet) so you never sit on "starting…" without earning.
• Auto-heals a stuck connection. If the pool ever connects but sends no work, easyBTX now notices within seconds and reconnects on its own.
• Clearer tuning results. When a tuning run finds nothing faster, it now says so plainly in a clearly marked box and invites you to try again, instead of a hard-to-read panel.
• Faster out-of-the-box tuning. Default solver settings now follow the latest pool-wide measurements for NVIDIA cards.

With the built-in wallet, easyBTX no longer starts a local node on Mac, it's pool-only everywhere now, which keeps things simple and light.

easyBTX comes to LINUX, and the whole fleet moves to the v0.32.8 solver.

• Linux is here (pool mining). easyBTX now runs on Linux as a one-click AppImage or .deb, pool-only like Windows, no node, no terminal. It ships the modern CUDA solver (BTX v0.32.8 + the GPU-saturation kernels + continuous feeding) that Windows can't run yet, so a single NVIDIA card on Linux mines far harder than the same card on the older Windows engine. Works on NVIDIA GTX 10-series and newer; runs natively or under WSL2 on Windows 11.
• v0.32.8 solver. Linux ships the fleet-blessed v0.32.8 build (a faster CPU-side pipeline; same shares, same rewards). Mac keeps its proven Metal engine (the BTX developer confirmed it's already the best Mac build). Windows stays on its proven engine for now while the modern stack is hardened for it.
• Tuning. The auto-tuner now follows the BTX developer's latest large-scale pool study: it holds the batch size at the validated sweet spot and tunes the CPU feed instead, where the real gains are.
• Bundled node updated to BTX v0.32.9 (the network's latest, with the reorg-hardening fix) plus a fresher startup snapshot. Used only by optional Mac Solo mode; pool mining is unaffected on every platform.

The MINING TUNING & OPTIMIZATION LAB, and your tuned settings now survive updates.

• The LAB. "Pro tuning" grew up: the flask button on the mining card now opens the MINING TUNING & OPTIMIZATION LAB, with a clearer hardware header and a friendlier face. The flask pulses green while a tuning session is running, and gives a tiny blink now and then if you have never tried tuning, that's your invitation.
• Tuned settings survive updates. Updates used to reset everyone's tuning to Standard as a safety measure. Now easyBTX resets only when the mining engine itself changes between versions, a proven Deep Tune win (the first fleet reports measured +23% to +157%) stays applied across normal app updates.
• Saved results, managed. Every saved Deep Tune result now shows the app version it was found on, can be deleted with its ✕ (after a confirm), and switching settings always shows exactly what would change, threads, slice, extra knobs, the proven win, before anything is applied.
• Find the Lab from Settings. A new "Mining Optimization" section in Settings explains tuning in three lines and takes you straight to the LAB.
• Wallet downloads where you need them. The Post-Quantum BTX Wallet and bonuz wallet buttons moved next to the wallet manager, right above the payout options, exactly where you decide where rewards go.
• Solo node updated to BTX v0.32.7 (the network's latest), with a much fresher startup snapshot, new Solo setups now start almost at the chain tip instead of thousands of blocks behind. Pool mining is unaffected.

The mining engine learns to never stop: continuous feeding on Mac and Windows.

• Fresh shares, full credit. The continuous-feed engine batches its shares per work slice, and the pool pays less for shares that arrive late against its fast job rotation. Batches are now capped at the pool's own cadence (~5s) so every share lands fresh, keeping the engine's full output AND the pool's full credit.
• Continuous-feed mining engine (Mac: ~2.2× measured live). The solver now keeps scanning through its whole work slice and hands back every share it found in one batch, instead of stopping at the first one and waiting to be restarted. At real pool speeds the old engine restarted ~38 times a minute, paying a GPU spin-up each time; the new one keeps the GPU saturated. On an M2 Pro this measured ~2.2× more difficulty-weighted shares in a live 45-minute side-by-side (zero rejected shares). easyBTX submits every share from each batch, credit to shib (dexbtx) for the C4 continuous-feed design.
• Windows: the full GPU-saturation stack, the same continuous-feed engine plus the byte-exact PR#58 kernel optimizations (windowed SHA-256, SHA midstates, factored compression; by vanities, via shib's btx-prebuilds-v0.32.5). Measured 3-5× on NVIDIA cards in the dexbtx fleet; ships after on-device validation.
• Tuning resets to Standard after every update. Each release can change the mining engine itself, so settings tuned on the old engine may not fit the new one. On the first launch after an update the app returns to Standard; your saved Deep Tune finds stay in the dropdown and you can re-apply or re-tune any time.
• Mac Auto threads follow the pool's formula, same speed, much cooler. On the new engine, Auto now splits your CPU (~40% solving, ~80% feeding the GPU) instead of all-cores solving. Live-measured on an M2 Pro: equal or slightly better mining output from far fewer busy cores, a cooler, quieter machine, matching the pool's own recommendation for Apple rigs. Your own thread/knob settings always override it.
• The tuning knobs are real now. Every GPU knob in Pro tuning (and the settings Deep Tune tests) was writing names the mining engine never read, silent no-ops since they shipped. They now use the engine's real setting names, old saved profiles and shared files migrate automatically, and the "Threads per block" knob is gone (no such setting exists in the engine). Deep Tune's GPU-setting test windows measure the real thing from now on.
• Smarter engine defaults per generation. The app pinned a Windows setting that was right for the old engine but starved the new one (a 3060 dropped to a tenth of its speed in field testing, caught before release). The app now detects which engine generation it ships and applies the right profile automatically.
• Pool mode hides node chores. If a leftover Solo node lives on your Mac, pool mining neither needs nor waits for it, the app no longer shows "waiting for the blockchain", the node-update button, or a scary recovery banner in pool mode (a background node now says it doesn't affect your mining speed).
• Upstream panel, simplified. Four plain tiles naming the open-source projects easyBTX builds on, tap one to visit it. No version numbers, no badges, nothing to check: updates install themselves.

The disclosed 4.99% tool fee is unchanged.

A much faster Mac mining engine, and a friendlier Deep Tune.

• ~6× faster Mac mining engine (BTX v0.32.5). The bundled Metal solver is upgraded from BTX v0.32.2 to v0.32.5, which fixes the Apple GPU digest path upstream and keeps the whole mining pipeline on the GPU instead of falling back to the CPU. On an M2 Pro the new engine found shares about 6× faster in side-by-side testing (same machine, same settings, measured on real share-class work). Verified bit-exact against the network's reference vector on both CPU and Metal before shipping, same proofs, just faster. Windows keeps its proven CUDA engine unchanged (the newer upstream CUDA path is still being validated on real cards; it ships only when it passes the same on-device gates).
• Your Deep Tune wins, in a dropdown. The "Active settings" row in Pro tuning is now a dropdown menu of every setting Deep Tune ever proved on your machine, each saved as a sentence like "Deep Tune fastest +30%, found 6/11/2026", plus "Use Standard". Switch any time; share your finds in @easyBTX.
• A little celebration when Deep Tune wins. When a session ends with a proven winner the panel now says "New fastest settings applied, nothing to do" with a small sparkle, instead of asking you to keep something that was already applied automatically. OK just dismisses; Share is the main action; Revert stays available.
• Fixed: the done-screen could caption the wrong settings. After a session, the "Applied:" line could show the last tested window's settings (often the old baseline) instead of the actual winner. The engine always applied the right settings, the label now matches them.
• Big hints are now popups. The "your GPU isn't fully used" hint (and its Deep Tune shortcut) now appears as a centered popup in the same style as the settings and info dialogs, no more one-word-per-line column when the window switches between tall and wide layouts.
• Honest upstream panel. In Settings, the BTX node / MineBTX / Tauri rows no longer show "Update available" and are no longer clickable at all (that's maintainer telemetry, not something you can act on, people thought they had to update something). Only the easyBTX releases row answers the one question that matters: "am I on the latest easyBTX?", and updates install themselves anyway.
• Clearer wallet buttons. "Get the BTX Wallet" is now "Get the Post-Quantum BTX Wallet (Mac & Windows)", and the Payout screen adds a "Get bonuz Wallet for BTX (Android & iOS)" button wearing the bonuz signature gradient ring. The "Get bonuz" button in the About page now carries the full animated bonuz gradient on every color theme. All bonuz buttons open bonuz.xyz, where the official store links live.
• Mac cooling tip (macOS only). A cooler Mac holds its mining speed better. Settings → Links now recommends the free Macs Fan Control app (by CrystalIDEA, not affiliated), with a matching note in Pro tuning.

Deep Tune: easyBTX now tunes itself on your real mining, over hours, proves what actually made it faster, and remembers it.

• Deep Tune, long, honest tuning sessions. Open the new lab button (the little flask next to the ℹ️), pick 3–12 hours and press Start. easyBTX keeps mining the whole time while it changes one setting at a time in ~30-minute windows, measures difficulty-weighted share production (so the pool's automatic difficulty changes can't fake or hide a result), and applies a new setting only when the statistics genuinely separate it from your baseline, shown as a real number, like "+23% vs your baseline". No winner? It says so honestly and changes nothing. When a session ends, a green "Deep Tune results arrived" pill appears right on the mining animation so you can't miss it, even a day later.
• Your fastest settings, remembered and switchable. The panel now always shows which settings your miner is running right now (Standard, Deep Tune fastest, Manual, or Loaded), and a proven winner is kept as a durable "fastest found" profile, Reset to Standard never deletes it, and switching between Standard and your fastest is one click each way.
• A report file you can actually share. When a session ends (finished or stopped), the report saves to your Desktop automatically as a small .txt, hardware, every window's settings and results with confidence intervals, and your public worker + payout address so results can be checked against the pool. Never any keys. One click opens the @easyBTX Telegram channel to drop it in; shared reports are how defaults improve for every miner.
• Save, load and share tuning settings. Your knob setup exports as a readable text file (with your hardware and fastest-found result in the header), loads back with one click, and travels through @easyBTX so miners can swap proven setups.
• Finer manual knobs. Solve slice in 1-second steps (5–60 s), solver threads as a real slider sized to your machine's cores, type-a-number boxes next to every slider, and platform GPU knobs (NVIDIA: threads per block, GPU inputs, batch size · Apple: batch size, prepare workers) with plain-English hints. The panel opens in wide layout and shows your chip, cores, RAM and GPU at the top.
• Quick tune measures the real thing now. The fast sweep benches against your live pool job instead of an easy synthetic one that was ~22× lighter than real mining.
• "How mining works", rewritten. The info page is now a small sectioned guide: pool mining needs no node and starts in seconds (perfect for a MacBook on the go), what your earnings look like and how to verify them on the explorer, when solo + the node make sense, the fees side by side (pool ~7.5% total · solo just the 4.99% tool fee), and an honest note on the built-in wallet.
• Looks and fixes. Section headings in Settings and About are twice the size; hardware stats got gauge bars; color themes and mining animations are now truly independent (picking an animation no longer resets your color); the hardware line no longer clips and shows your RAM the way Apple does; and the bonuz box wears its signature flowing orange→pink neon frame.

The disclosed 4.99% tool fee is unchanged, and Deep Tune never touches it.

Updates now take care of themselves, and your rig always has a name on the pool dashboard. Mac and Windows ship together again.

• Automatic updates that actually update. easyBTX now installs new versions on its own: it checks every 30 minutes and updates automatically, so fixes like 0.6.8's Mac speed-up reach every machine without anyone clicking. You can turn this off in Settings, the app then still checks hourly and shows the familiar update cue so you can install yourself. A failed download now retries on the next check instead of silently giving up on that version.
• Your machine can no longer be nameless in the pool. If a hardware probe failed at launch, a rig could register with an empty GPU name and become a hidden "-ALPHA-1" entry on the pool dashboard, mining and earning, but invisible in the charts. easyBTX now always reports a proper GPU name, on every platform, even when the probe fails.
• Windows rejoins the Mac version. The Windows build catches up to the same release as the Mac, carrying the proven CUDA mining engine plus the 0.6.8 correctness guards (share timing pinned to its job, older NVIDIA GTX 10/16 and RTX 20-series cards enabled on every mining path).

The disclosed 4.99% tool fee is unchanged.

Apple Silicon Macs mine pool shares at full speed again.

• Macs land shares again. Apple Silicon Macs now run the GPU solver as a single warm, always-on engine using every core, instead of restarting it each mining cycle. Restarting kept the Metal pipeline cold, so the Mac was scanning but finding almost nothing; with the warm engine it finds and submits shares like the rest of the fleet. If you mine on a Mac, this is the update that makes it actually earn.
• Every found share is timed to match its job. Locked the mining engine so it can never re-stamp a share with a time the pool didn't expect (which the pool would reject). easyBTX already behaved this way after the block-125,000 upgrade; this pins it so future engine updates keep it that way.
• Consistent older-NVIDIA support across Windows mining paths. GTX 10/16 and RTX 20-series (Pascal/Turing) cards are now opted in on every Windows mining path, so they keep mining on the GPU instead of being refused on future builds.

Makes shares actually land by letting the pool settle on the right difficulty.

• Steady connection so the pool can tune your difficulty. easyBTX was reconnecting roughly once a minute (to rotate the disclosed dev-fee window), which never gave the pool the few minutes it needs to set your mining difficulty correctly, so it ran away to an impossible level and your shares stopped landing. easyBTX now holds one connection for hours at a time, so difficulty settles and shares land steadily. The disclosed 4.99% fee is unchanged (just applied in longer, less frequent slices).

Gets easyBTX miners landing shares again after the block-125,000 upgrade.

• Reverted to the proven mining engine. A newer solver build regressed GPU mining after the upgrade: some NVIDIA cards would connect but sit near 0% GPU and find nothing. easyBTX uses the proven engine, which mines normally across GTX 10/16 and RTX 20/30/40/50 cards.
• The work your GPU finds now gets submitted. Post-upgrade each attempt is heavier, so a long search could be cut off before it finished and reported. Mining now runs in short slices that always complete, so found shares get sent and counted instead of being thrown away.
• Live mining speed is reported to the pool (continued from 0.6.4), scaled by your power slider so it reflects what you're actually contributing.

Faster mining after the block-125,000 upgrade, plus fixes so the pool sees your real hashrate again.

• Faster mining after the upgrade. The block-125,000 change made each mining attempt more work, which briefly slowed the whole network. easyBTX now runs the BTX v0.32.3 mining engine (and the v0.32.3 node for solo mining on Mac), so your GPU works at full speed again while the network's difficulty settles back down.
• Your hashrate shows up at the pool again. After the upgrade the miner could report zero speed to the pool even while the GPU was busy. Mining now runs in short slices that always finish and get counted, so your live speed is reported.
• Reported speed follows your power slider. The speed sent to the pool now reflects how high you've set mining power, so it matches what you're actually contributing instead of your peak.
• Windows: smoother start on more NVIDIA cards. Some cards could stall right after the upgrade while the GPU warmed up for the first job. easyBTX now gives that first step more time, so those cards start mining instead of retrying.

A required BTX network upgrade that keeps your miner producing valid work through block 125,000, plus wider NVIDIA GPU support on Windows.

• Required update for block 125,000. BTX changes how mining work is generated at block 125,000. easyBTX updates its mining engine to match, so your miner keeps producing valid work through the change on both pool and solo mining, on Mac and Windows. Existing installs update themselves; keeping easyBTX current means no interruption at the upgrade.
• easyBTX now runs the BTX v0.32.2 node, so solo mining on Mac keeps following the network through the required upgrade. Pool mining doesn't use the node (the pool runs it for you), so pool miners are covered by the mining-engine update above.
• Wider NVIDIA GPU support on Windows. GeForce GTX 10-series (Pascal) and GTX 16 / RTX 20-series (Turing) cards now mine on the GPU directly instead of falling back to slow CPU mining. If you have a 10-, 16-, or 20-series card, your GPU now does the work.

A required BTX network upgrade for solo mining, lighter animations, and quicker access to live stats and the community.

• easyBTX now runs the BTX v0.32.1 node, so solo mining keeps following the network through the required upgrade at block 125,000. Pool mining is unaffected (the pool runs the node for you), and existing Mac installs update themselves.
• Mining animations are lighter on your machine, they render more efficiently, so more of your GPU and CPU go to mining (a real help on smaller Macs).
• The mining animation is one picker, Power Core, Surfer, or None, independent of your color theme, so any animation pairs with any color.
• New Stats dashboard link opens the live easyBTX + BTX network page (uptime, hashrate, blocks), and a BTX Community link makes it easy to share your diagnostics file and get help.
• The big mining view now shows two speeds side by side: your hardware speed (what your GPU is doing) and the pool-counted speed (what the pool credits), with your share of the network alongside.

New blue theme + mining optimizations.

• New Blue color theme (Appearance → Theme).
• New Silver Surf mining-animation skin, a chrome surfer that reacts to your live share pace, mining intensity, and every accepted share. Pick it in Appearance → Animation skin; it works with any color theme.
• Dev-fee capture fix: the ledger is now persisted, so it survives restarts and reconnect churn; the first capture window lands in ~16 minutes (was ~1 hour) and targets ~5.05%.
• DNS-resilient pool connect: caches the last-good IP, fixing the ~30s Windows reconnect churn.
• Live share-rate: per-minute and per-hour rows in the big view.

A required BTX network upgrade, a richer info page, and a few wallet niceties.

• easyBTX now runs the BTX v0.31.0 node, so solo mining keeps following the network through the required upgrade at block 123,000. Pool mining is unaffected, and existing Mac installs update themselves.
• A reworked info page: a section nav that jumps you straight to each part, your live block height and the pool's network dominance, your last and longest mining sessions, a single Safety section, and a Builder section that credits bonuz (the maker's self-custodial wallet, BTC, SOL and ETH today, with BTX coming soon).
• You can turn the mining-core animation off (Settings → Appearance) for a calm, still background. It is purely visual and every number still shows.
• Transactions now show the selected wallet's balance and have a Refresh button, since pool payouts can take a minute or two to appear.
• There is now a third-party OTC market at btx.trade. We are not affiliated with it, it is use-at-your-own-risk, and nothing here is financial advice.

Wallet balances and activity, fixed everywhere.

The built-in wallet is node-less: it reads your balance and history straight from the BTX explorer. BTX wallets spread funds across many derived addresses, so an earlier build could show 0 on a wallet that actually held coins. Now every screen reads the right addresses:

• Your balance shows correctly on the wallet card, the Send screen, and the dashboard. While a number is still loading it shows ",", never a bare 0.
• Balances refresh on their own from the explorer, so they stay current.
• A "View in Explorer" button opens your address on the BTX explorer in your browser.
• Transactions now reads your history from the explorer (no more "node not ready"), with a switcher to pick which wallet to view and export.
• The wallet window has a cleaner header.
• The BTX node version shown in Settings reads 0.30.2.

When a new easyBTX version is out, a clear "UPDATE AVAILABLE" signal now blinks over the miner, and the app re-checks every few hours (not just at launch) so a long-running install notices it. On Mac, updates still install automatically if you have that turned on; on Windows, click the signal to go to Settings and update.

Mining is unchanged on both Mac and Windows.

Windows mining works, and the built-in wallet comes to Windows.

The big one for Windows: pool mining now uses a persistent daemon-mode solver, which ends the GPU-context hang that left earlier Windows builds finding zero shares. Your NVIDIA card now mines and credits shares the way the Mac already did. And the full node-less built-in wallet (create, receive, send, and restore from a node wallet.txt or wallet.dat) is now available on Windows too, matching the Mac build.

Also fixed: pausing no longer resets your lifetime accepted-share count, and a restored HD wallet now shows its balance. Those funds live across many derived addresses, so the card couldn't total them without your passphrase. Enter it once via the new "Load balance" prompt (or review any send) and the balance loads and stays current.

The macOS Metal mining path is byte-for-byte unchanged.

A built-in wallet, with real Send and node-wallet Restore.

A self-custodial wallet now lives inside the miner. You can create a new wallet or import an existing one, check your balance, and receive your mined BTX directly, without a separate app. A WALLET button sits in the top bar next to the settings gear.

Pool mining di Mac kini langsung jalan, tanpa node yang perlu diunduh dan tanpa sinkronisasi.

Sorotannya adalah kecepatan. Dalam mode pool, easyBTX tidak lagi mengunduh atau menjalankan node BTX lengkap. Pool mining tidak pernah membutuhkannya, dan itu menambah unduhan bergiga-giga, sinkronisasi "menyusul" yang lama, dan sesekali crash. Kini kamu buka app, alamat pembayaran kamu sudah terisi, dan Mac kamu langsung mulai mining. Jika kamu sudah punya easyBTX sebelumnya, alamat pembayaran kamu yang ada terbawa otomatis, jadi tidak ada yang perlu diatur lagi.

Pool mining di Mac berfungsi lagi, plus panel statistik GPU langsung.

Sorotannya adalah sebuah perbaikan. Pool mining di Mac, yang rusak di 0.4.5, berfungsi lagi. Sebuah perubahan yang dibuat saat membawa easyBTX ke Windows mengarahkan Mac ke helper mining yang salah, sehingga mining tidak mau mulai. Ini memulihkannya. Jika kamu memperbarui ke 0.4.5 dan tidak bisa memulai mining, ini memperbaikinya, dan Mac berperilaku persis seperti di 0.4.4.

easyBTX hadir di Windows.

Ini adalah rilis Windows pertama. easyBTX kini menambang BTX di Windows PC dengan GPU NVIDIA RTX seri 30 atau yang lebih baru, memakai pendekatan satu app, satu klik, kustodi mandiri yang sama seperti versi Mac. Kamu cukup membawa kartu NVIDIA, pilih alamat pembayaran, dan GPU kamu bergabung ke pool. Versi Mac (Apple Silicon, Metal, solo atau pool) tidak berubah.

Pengiriman berfungsi lagi, statistik mining pribadi kamu sendiri, dan jendela yang lebih besar dan tenang.

Tindak lanjut yang terfokus dari 0.4.3. Sorotannya adalah sebuah perbaikan: mengirim BTX dari app berfungsi lagi setelah build belakangan ini bisa membuat pengiriman gagal dengan pesan yang menyesatkan. Selain itu, layar Tentang kini menampilkan statistik mining kamu sendiri, jendela-jendela popup semuanya terbuka dalam bentuk lapang yang sama, dan menyalin tautan explorer sebuah transaksi cukup satu ketukan.

Jeda dan lanjutkan, restart yang lebih tenang, lebih banyak privasi, dan Mac kamu di dashboard pool.

Rilis ini melanjutkan desain ulang 0.4.0 dengan sekumpulan pekerjaan yang membuat hidup lebih nyaman. Berhenti kini menjaga node kamu tetap hangat dan menawarkan tombol Lanjutkan hijau, penantian "bersiap-siap" yang lama setelah restart menjelaskan dirinya sendiri alih-alih terlihat macet, dan kamu bisa menyembunyikan saldo dengan satu ketukan. Miner pool kini bisa menampilkan angka GPU langsung Mac mereka dan nama yang mereka pilih di dashboard minebtx.

Tampilan baru, dan pool mining kini membayar ke dompet eksternal kamu.

easyBTX punya desain baru. Tampilan default kini berupa jendela "ruang kontrol" yang lebih lebar, menyebarkan semua elemen ke tiga kolom yang tenang, sehingga layar tidak penuh sesak begitu node kamu terisi informasi langsung. Ada juga tombol ganti tema baru: Gelap tetap jadi default, Terang tersedia jika kamu lebih suka, dan Sistem yang mengikuti Mac kamu dan berganti sendiri. Pool mining kini menghormati alamat pembayaran eksternal kamu, sama seperti solo mining yang sudah melakukan itu sejak dulu, sehingga kamu bisa mining di laptop yang tidak pernah menyimpan kunci koin kamu.

Node kamu tidak pernah terlihat rusak selagi menyusul. Setelah easyBTX ditutup cukup lama, atau dihentikan paksa (crash, force quit, atau mengganti app saat masih berjalan), node kamu kadang butuh beberapa menit untuk menyusul saat kamu membuka app berikutnya. Sebelumnya, easyBTX bisa salah mengira waktu menyusul itu sebagai masalah nyata dan menampilkan galat. Kini ia menunggu dengan tenang, memberi tahu apa yang terjadi, dan membiarkan dompet serta koin kamu tidak tersentuh. Ia tidak akan pernah menawarkan perbaikan selagi node hanya sedang menyusul. Tidak ada yang perlu kamu lakukan.

Rilis "kepatuhan pool dan transparansi". Pool dexbtx milik shib berpindah ke v5 pada 2026-05-27 dengan gerbang kapabilitas wajib pre_hash_block_tier_v18 dan dict ekstensi mining.subscribe baru yang membawa session_id beserta sidik jari hardware per rig. easyBTX v0.2.0 hanya mengirim dua dari tiga bidang yang diperlukan, yang berarti Mac worker terhubung ke pool tetapi tidak pernah muncul di dashboard worker. v0.3.0 mengirimkan handshake v0.3.x lengkap, menambahkan heartbeat worker.report_metrics yang membuka baris dashboard langsung per rig, dan menampilkan nama kanonik yang ditetapkan pool ke setiap rig agar pengguna bisa mencocokkan Mac mereka dengan baris di /stats. Selain itu, fitur self-custody opt-in pertama: hadiah yang ditambang secara solo kini bisa dibayarkan ke alamat BTX eksternal yang tidak menyimpan kunci di Mac ini. Serta banyak pekerjaan UX yang diminta pengguna v0.2.0 di Telegram. cargo test: 195/195. tsc --noEmit: bersih. cargo build --release + npm run build: keduanya hijau.

Rilis polish "mega audit". Audit keamanan /cso ditambah audit bug fungsional 3 agen menemukan 4 masalah KRITIS, 10 TINGGI, 13 SEDANG, dan beberapa RENDAH di v0.1.13. Rilis ini menutup semuanya sekaligus. cargo test: 149/149. tsc --noEmit: bersih. Tidak ada IPC publik yang dihapus, tetapi send_btx mendapatkan parameter subtract_fee: bool yang eksplisit (tombol Max frontend meneruskannya). EasyBtxState mendapatkan tiga field #[serde(default)] (file state lama tetap dimuat).

Ditambahkan

• Baris saldo masuk. Pembayaran yang diterima tetapi belum dikonfirmasi (untrusted_pending) kini muncul sebagai baris "Masuk ... sedang dikonfirmasi" yang jelas, bukan terlihat hilang sampai dikonfirmasi. Saldo yang bisa dibelanjakan tetap hanya yang terpercaya, sehingga Kirim tidak pernah bisa overdraft.
• Tautan block explorer. ID transaksi dan alamat di Kirim, Terima, dan Audit/Ikhtisar dibuka di explorer.minebtx.com (dipotong, bisa disalin, bisa dibuka). Layar konfirmasi Kirim menampilkan alamat penerima lengkap agar kamu bisa memverifikasinya.
• Kirim: tombol "Max" dan pengiriman penuh yang aman. Tombol Max mengisi saldo yang bisa dibelanjakan penuh, dan pengiriman saldo penuh kini mengurangi biaya jaringan dari jumlahnya alih-alih gagal dengan "dana tidak cukup". Alamat penerima juga diperiksa sebelum langkah konfirmasi.
• Klaim ruang. Tombol Pengaturan, Penyimpanan (dan proses otomatis saat launch) membebaskan disk dengan menghapus blockfilterindex/coinstatsindex yang tidak digunakan, snapshot assumeutxo pasca-load, dan debug.log yang terlalu besar. Blockchain dan dompet kamu tidak pernah disentuh.