0% Dev Fee Firmware: What “No Dev Fee” Actually Means

“0% dev fee” is the most quoted line in mining firmware marketing — and one of the least examined. Almost every aftermarket firmware claims a zero-fee path somewhere on its pricing page. Read the asterisk and the picture changes: the zero usually only applies if you point your hashrate at their pool. This is an honest look at how dev fees actually work, what the numbers really are (in ranges, not the tidy single figures you see repeated everywhere), and how to tell a genuine donation model from a quiet skim — by reading the source code instead of trusting the badge.

What a dev fee actually is (and how it gets skimmed)

When you flash custom firmware onto an Antminer, you’re trusting someone else’s code to talk to your hashboards, manage your pool connection, and submit your shares. A dev fee is how most aftermarket firmware authors get paid for that work: for a small percentage of the time, your miner mines for them instead of for you.

Mechanically, it’s usually one of two methods. The most common is pool redirection: for roughly 2–3% of the time, the firmware silently swaps your configured pool for the developer’s pool address, mines a few shares there, then switches back. You never see it in your own pool dashboard because those shares were never submitted under your account. The second method is fee mining as a background job — a low-priority work queue that pulls a percentage off the top before your shares ever leave the box. Either way, the math is the same: a 2.5% dev fee on a miner earning the equivalent of $5/day in Bitcoin is about $0.12/day, or roughly $45/year, per machine. Run a rack of them and it adds up.

None of this is inherently shady. Firmware is hard, thankless, 24/7 work, and the dev fee is the engine that funds it. We want to be clear up front: the firmwares that charge a fee earned the right to. Braiins, VNish, and Luxor each spent years building tooling that millions of miners now depend on. The problem isn’t that a fee exists — it’s that the fee is often obfuscated, and the marketing “0%” is frequently pool-locked in ways nobody reads. Let’s put the real numbers on the table.

The honest dev-fee table (in ranges, not flat numbers)

You’ll see flat figures repeated all over the internet — “BraiinsOS is 2%,” “VNish is 3%.” Those are simplifications. The real fees are ranges that move depending on miner model, firmware version, and which pool you run. Here’s the grounded version, cross-checked against our firmware feature matrix:

Two things worth saying plainly. First, stock Bitmain firmware is “0%” too — but it’s closed, telemetry-laden, and locks you out of tuning your own hardware, which is exactly why an aftermarket industry exists. A 0% fee on firmware you can’t control isn’t much of a deal. Second, those 2–2.8% fees are the price of some genuinely excellent engineering. We cover the full feature-by-feature breakdown in our firmware comparison — that’s the matrix to read if you want to weigh fees against features (autotuning quality, Stratum support, model coverage) rather than chasing the lowest number in isolation.

Two different fees, and how the “0%” gets misread

Here is where the most widely repeated claim in this whole subject goes wrong. You will read everywhere that Braiins OS is “0% if you mine on Braiins Pool.” It is not — but there is a real zero nearby, and it belongs to a different fee. Firmware vendors charge a dev fee, collected by redirecting a slice of your hashing power. Pools charge a pool fee on what you earn. Those are two separate line items, and the rebate everyone repeats applies only to the second:

• Braiins OS → the zero is the pool fee, not the dev fee. The vendor page states both plainly. The dev fee: “When you use Braiins OS, we collect a 2-2.5% dev fee (depending on the hardware model) by directing that percentage of your hashing power to our pool.” That applies wherever you point the miner. The pool fee is the other line: “When you mine with Braiins Pool using Braiins OS, you qualify for a 0% effective pool fee rate instead of the standard 2.5%. The fee is initially collected, but a rebate is applied… If your entire fleet operates on Braiins OS, you’ll receive a full 100% refund of the pool fee.” Two fees; the rebate zeroes the second and leaves the first untouched. That 100% pool-fee refund is a genuine, documented benefit with no DCENT_OS equivalent — it is simply not a 0% dev fee. (Verified — braiins.com/os-firmware, 2026-08-20.)
• LuxOS → the same two-fee shape. luxor.tech/mining/firmware advertises “0% Pool Fees”; the 2.8% dev fee is published separately, in docs.luxor.tech. Mining on Luxor Pool addresses the pool fee. No dev-fee waiver is documented, so the safe reading is 2.8% published with no operator-side zero. (Verified — docs.luxor.tech, 2026-08-20.)
• VNish → 1.8–2.8%, with no pool-linked zero. VNish publishes one range and applies it regardless of pool, so there is no second fee to disentangle. (Verified — vnish.io FAQ, 2026-08-20.)
• Awesome Miner → 2.8% on everything current. A 1.8% tier exists, but only for three legacy families (S9/S9i/S9j, T9+, L3+/L3++). On any S17, S19, S21, T17, T19 or T21 the figure is 2.8%, and it is set by the model, not chosen by you. (Verified — vendor model table, 2026-08-20.)
• Hiveon → no published figure. A 3% number circulates widely; we could not source it to Hiveon. Treat it as Unknown rather than repeat it. (Unknown — no figure on hiveon.com or its knowledge base, 2026-08-20.)

Both companies state their terms on their own pages; the conflation happens downstream, in how the two fees get repeated as one. What the distinction changes is the arithmetic. On Braiins Pool with Braiins OS you pay the 2–2.5% dev fee and effectively no pool fee. On any other pool you pay that same dev fee plus that pool’s fee. The rebate is worth real money — it is just not the dev fee going to zero, and any comparison that treats it as such will hand you the wrong number.

Two honest caveats before anyone reads this as a sales pitch. ePIC UMC OS charges 1.5%, cut from a higher rate on 2026-01-26, and that is lower than the 2% DCENT_OS ships its optional donation at. For an operator who never opens the setting, ePIC costs less. We are only ahead once you use the control — DCENT_OS has a one-click 0% preset and an off toggle in the firmware’s own settings; ePIC does not. And both Braiins and ePIC will invoice a flat licence instead of taking hashrate, which DCENT_OS does not offer and which institutional operators often prefer for accounting. Where a competitor is genuinely better on a given axis, that is what the table should say.

There is still a cost no fee table shows: where your shares go. Choosing your own pool is one of the few levers an individual miner has over Bitcoin’s decentralization, and a fee structure that nudges an entire fleet onto one pool is worth weighing against the percentage it saves. That is a trade-off, not an accusation — and it is the whole reason we care about this.

Why “NoDevFee” hack tools are a bad idea

Search “remove dev fee” and you’ll find a cottage industry of “NoDevFee” tools — loaders, patched binaries, and DNS-redirect tricks that promise to strip the fee out of closed-source firmware. Skip them. Here’s the honest engineering reality:

• You’re running an unknown binary as root on a money-printing machine. To “remove” a fee from closed firmware, these tools patch or replace the very component that controls your hashboards and your pool credentials. You have no way to audit what else they changed. The most common outcome reported in the wild is the fee getting redirected to the tool author instead of removed — you didn’t kill the skim, you just changed who skims you.
• It can brick your miner. Patching firmware you can’t read is exactly the kind of operation that ends in a dead control board and an SD-card recovery session — if you’re lucky enough that recovery is even possible.
• It’s a trust dead-end. The entire point of worrying about a 2.5% fee is that you don’t want a stranger taking a cut of your hashrate. Solving that by running a different stranger’s unaudited patch is not a solution. It’s the same problem wearing a different hat.

The clean answer to “I don’t want to pay a dev fee” was never a hack tool. It’s firmware that’s honest by design — where the fee logic is open, the default is printed in the source, and you can verify it yourself instead of trusting anyone’s word, including ours.

Donation, not diversion: the DCENT_OS model

This is the part we build differently, and we are going to be exact about it, because the whole point of shipping the source is that you can check. DCENT_OS — D-Central’s open-source firmware for industrial Antminers — has no mandatory dev fee: no pool condition, no standalone-vs-on-pool split, no licence server. What it does ship is a 2% donation that is ON BY DEFAULT. It is a plain value in the config file, it is visible on the dashboard the whole time it runs, and you turn it off by setting [donation] enabled = false. Anyone can confirm both halves of that in ninety seconds: default_donation_enabled() returns true and default_donation_percent() returns 2.0 in dcentrald/dcentrald/src/config.rs. That is the difference between a fee you can read and a fee you have to trust — and it is why we would rather tell you the number than round it down.

What there is is an optional, transparent donation field in the dashboard — a configurable percentage you can set yourself if you want to support the project. It ships at 2%, on by default — and you can set it to zero. The number is a plain config value, it shows on the dashboard while it runs, and the line that sets it is in the public GPL-3.0 source. If you decide the firmware earned a few sats, you can dial in a contribution and watch exactly where it goes. That’s the distinction that matters: this is a donation, not a diversion. The amount is yours to set, and nothing is hidden — the dev-fee mechanism is open and auditable in the source, where most firmware obfuscates it.

If what you actually want is firmware where the levy is yours to set — and where you can read the line that sets it — that is the gap DCENT_OS is built to fill. It is not ready to run your data center: what exists today is signed experimental artifacts for the Antminer S9 and S19j Pro Zynq/XIL lanes, guarded, with no published witnessed install route for any model. But if a fee-free, fully auditable firmware with a one-click 0% donation is the future you want for your hardware, you can meet the project and follow the evidence lane by lane. Backups need building before you need them; open firmware is one of them.

How to verify a dev fee in open source

Here’s the practical skill that makes all of the above moot: when firmware is open source, you don’t have to trust the fee claim — you can check it. This is the real argument for open firmware, and it’s bigger than any single percentage. A skim you can read is a skim that can’t hide.

If you can read the source (or watch someone who can), here’s roughly what auditing a fee looks like:

1. Find the pool-connection code. Every dev fee that works by redirection has to, at some point, swap your configured pool URL for another one. Grep the source for the pool/stratum connection logic and look for any address that isn’t the one you set. In honest firmware, there’s exactly one place your pool gets configured.
2. Look for time-slicing or work-queue logic. Fee mining works by allocating a percentage of work cycles elsewhere. Search for percentage constants, timers, or a secondary work source feeding the share submitter. A hardcoded “0.025” near the mining loop tells its own story.
3. Check the donation field’s default and its wiring. In firmware with a configurable contribution, read the default out of the source rather than off the marketing page, and trace where a non-zero value sends shares. Do it to us first: DCENT_OS ships that default at 2%, enabled, routed to a pool URL printed in the same file, and GET /api/donation/info is unauthenticated on purpose so you can check the payout address on-chain. The value you set should be the only value in play — and you should be able to prove that, not be told it.
4. Prefer reproducible builds. The gold standard is being able to build the firmware yourself from source and get a binary that matches what’s distributed — so you know the running code is the code you read. Reproducible Buildroot builds are the design intent for DCENT_OS; treat “you can verify it yourself” as the bar to hold every open firmware to.

With closed firmware (stock, VNish, LuxOS, or the closed parts of BraiinsOS+) you simply can’t do this — you trust the badge and the brand. That’s not always wrong; trust is a reasonable thing to extend to a developer with a long track record. But “more options that are fully auditable” is, in our view, the same thing as “more decentralization.” The more miners who can verify their own stack, the harder it is for anyone — including us — to skim them quietly. That’s the principle worth optimizing for, and it sits one layer up from any dev-fee number: it’s about owning the box you run, which is the same backup-your-sovereignty instinct that underpins everything from running your own node to keeping your own resilient infrastructure.

So which firmware should you actually run?

Honestly? For a production fleet today, the mature, battle-tested options are the ones charging a fee — and that fee is buying you years of autotuning refinement and broad model support. Don’t pick firmware on dev fee alone; pick it on the whole picture. If you want to weigh fees against features side by side, the full firmware comparison matrix lays out every column — dev fee, open-source status, Stratum support, and supported models — so you can decide with the asterisks visible.

DCENT_OS is D-Central Technologies’ GPL-3.0 open-source Bitcoin mining firmware for Bitmain Antminer ASIC miners — the only Antminer firmware that is open source end to end: daemon, dashboard and image. There is no mandatory fee; a 2% donation ships on by default and is disableable in config. Guarded artifacts exist only for the exact S9 XIL and S19j Pro XIL lanes; install evidence is incomplete and neither is production-ready. Check the exact evidence ledger.

Frequently asked questions

Bitmain Antminer S19 $600.00 CAD

Shop Antminer S19 →