← ./blog

2026-09-05

Why I stopped Easy Mining

I built wenblockniceha.sh to automate EasyMining solo waves on NiceHash. For a while that was useful. Then I stopped using EasyMining. This is why, and what that means for the tool.

I still use NiceHash as a hashrate marketplace. The marketplace is fine. EasyMining is the part I walked away from.

The short version

EasyMining does not give you a way to check that your hash is doing what you paid for. You place an order, wait for a wave, and take the outcome on faith. After enough of that, and after Team Gold XXL BTC Asia on 28 August 2026, I decided the product was not for me anymore.

I am not alleging fraud. I am saying I want receipts. EasyMining does not give me those.

January context

In January 2026 a run of Bitcoin blocks showed up as "Unknown". NiceHash later said they were internal tests for a new product. They posted this on X:

Over the past 48 hours, “Unknown” Bitcoin blocks have sparked significant excitement and speculation.

BTC blocks: 932395, 932373, 932353, 932167, 932129 were all mined by NiceHash.

This was part of internal testing for a new product that will significantly expand what you can do with NiceHash. The launch date is not yet known, but it’s going to be worth the wait.

X post by @NiceHashMining, 16 Jan 2026

Fair enough as a teaser. It did not answer the EasyMining questions people already had in Discord: thin updates, unclear Team Gold expectations, and no customer-side audit trail.

Team Gold XXL BTC Asia (28 Aug 2026)

That weekend was the practical cutoff for me. Roughly 1 in 3.6 odds. About 1.25 BTC pledged to the team. Zero blocks for the team. In the same window, several NiceHash internal blocks did land.

People in #easymining (CDK, Worldhash, and others) had been asking for clearer verification for months. The XXL just made the gap obvious. When you cannot check the work, a bad stretch feels worse than variance alone.

How to tell the coinbases apart

On an explorer, NiceHash-related blocks can look similar. The coinbase tag and the outputs are the tell.

  • Internal: tag /NiceHashMining/. One payout address. No separate ~1% fee output. Example: block 964474 (28 Aug 2026).

  • EasyMining: tag /NiceHash/. Miner payout plus NiceHash's ~1% fee. Example: block 964462 (same day).

Internal: block 964474

BTC block 964474 coinbase tagged NiceHashMining with a single reward recipient and no 1% fee output

/NiceHashMining/

EasyMining: block 964462

BTC block 964462 coinbase tagged NiceHash with miner reward plus separate 1% fee output

/NiceHash/

During the XXL, that distinction mattered because people were watching both live.

What I took from it

NiceHash is a licensed company with a long track record. That is not the issue. The issue is that EasyMining still has no clear path to customer-verifiable mining. Concerns got a late reply. The transparency roadmap never showed up in a form I could use.

So I stopped buying EasyMining. Marketplace orders stay. Different product, different trust model.

wenblockniceha.sh

The automation I built was EasyMining-shaped. Without that, there is nothing useful left to maintain against their APIs. The site is deprecated. Old block data and the explorer may stay up for reference, see wenblockniceha.sh/deprecation.

Where I mine for blocks instead

Rigly Block Party runs on ckpool. You can check the log. I already wrote up block #955,703 from Party #28.

They have also talked about Private Teams, which is closer to what a lot of EasyMining users wanted from team mining, with a pool you can actually verify.