wenblockniceha.sh logo wenblockniceha.sh Block block
Home Block explorer Deprecated Legal
Admin login

Block block

This product is deprecated. We are no longer building on NiceHash.

NiceHash in 2026, and why we're done

We spent a long time automating EasyMining solo waves on NiceHash. Over 2026, trust in that setup fell apart. It really boiled over after Team Gold XXL BTC Asia on 28 August 2026. Here's the short version of what happened, what people were saying, and where we'd look next.

What NiceHash said publicly

Back in January 2026 a bunch of Bitcoin blocks showed up as "Unknown" and people lost their minds trying to figure out who mined them. NiceHash eventually said those were theirs: internal testing for some new product. No launch date. And nothing that really spoke to the EasyMining / Team Mining frustrations that were already loud in Discord.

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.

@NiceHashMining, 16 Jan 2026

A vague teaser with no timeline doesn't fix trust. If you pay for hashpower, "worth the wait" is not a useful answer.

When it peaked: Team Gold XXL BTC Asia (28 Aug 2026)

People in NiceHash Discord #easymining, including folks like CDK and Worldhash, had been annoyed for months. Team Gold was a mess of unclear expectations, updates were thin, and there was basically no way for a customer to check that EasyMining was doing what it claimed.

That all got a lot worse after Team Gold XXL BTC Asia on 28 August 2026. Roughly 1 in 3.6 odds, 1.25 BTC pledged to the team, and zero blocks for the team. In the same window, several NiceHash internal blocks did land.

Nobody here is claiming courtroom fraud. The problem was transparency. You couldn't audit EasyMining. You couldn't confirm it was honestly mining for you. You just had to take their word for opaque outcomes.

EasyMining blocks vs NiceHash internal blocks

On a block explorer they can look similar at first. Both are NiceHash-related coinbases. The tag and the outputs are how you tell them apart.

  • Internal blocks use the coinbase tag /NiceHashMining/. The whole reward goes to one address. There is no separate 1% fee output. Example: BTC block 964474 (28 Aug 2026).
  • EasyMining blocks use /NiceHash/ (not NiceHashMining). You get two payouts: the miner's wallet and NiceHash's ~1% fee. Example: BTC block 964462 (same day).

During the XXL, people were watching explorers live. Seeing internal-style blocks land while the team's EasyMining / Team Gold money got nothing is a big part of why this distinction suddenly mattered so much.

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

Internal: block 964474

Tag NiceHashMining. One payout. No separate 1% fee.

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

EasyMining: block 964462

Tag NiceHash. Miner payout plus ~1% NiceHash fee.

/NiceHash/

What we think happened (and what still sucked)

We assume no illegal activity here. NiceHash is licensed and has been around a long time. That still doesn't make the response okay.

  • Community concerns got brushed off while an XXL was planned for that period.
  • Damage control mostly showed up after the fact.
  • Still no clear roadmap to improving transparency, which is the bit users actually wanted.

Being licensed doesn't help much if you run a big XXL, then only talk once people are pissed, and still don't give a real plan for letting customers verify anything. Reputation is not a substitute for being able to check the work.

Then a Gold L made it weirder

After users vented in Discord, Kevin (you don't see him in #easymining that often) said he'd pass the concerns to the team. Not long after that, a Gold L landed on a wallet that looked suspicious to a lot of people.

Cue the jokes that NiceHash themselves (or, as people put it, "the NiceHash CEO") had landed it to prove they were still honest. Coincidence or not, it lands the same way: if you can't audit outcomes, every awkward block looks like a setup.

What this means for wenblockniceha.sh

We're done using NiceHash. No more building against their APIs. Old block data and the public explorer might stick around for reference, but treat this product as deprecated.

Where to go instead

Have a look at Rigly Block Party if you still want Bitcoin mining block participation.

They've hinted that Private Teams are coming soon, which is closer to the team-mining setup a lot of EasyMining users kept asking NiceHash for.

Transparency is built in: Rigly runs on Ckpool, so you can actually verify what's going on instead of taking someone's word for it.

Visit blockparty.rigly.io

wenblockniceha.sh Block block

Block block — solo mining automation for your own NiceHash account. Non-custodial software: your keys, your orders, your rewards.

Non-custodial · API keys to your NiceHash account only

Product

  • Home
  • Block explorer
  • Deprecation notice
  • Admin login

Legal

  • Privacy Policy
  • Terms of Use
  • Cookie Policy
  • Disclaimer
  • Legal Notice
  • Contact
© 2026 wenblockniceha.sh · The Saban Company B.V. · Netherlands KVK 91125030 · No custodial wallets · Service scope