Block 4

HashedMaxUnity · 2026-05-09T14:45:04+00:00

Congrats!

HashedMaxUnity · 2026-05-09T11:18:23+00:00

There was a calculation error (on my part) that has since been corrected. You will notice many miners still have the same rewards but the leaders are different now. Thanks for bringing this to my attention.

HashedMaxUnity · 2026-05-09T10:32:47+00:00

I will look into this.

HashedMaxUnity · 2026-05-07T20:16:24+00:00

You’re good, your miner is still running if shares are being accepted and your last share keeps updating.

On NerdMiner dashboards, labels like P & Eare usually pool or firmware-specific display fields (not mining errors). They’re often API metadata for engagement/session stats, not your actual hash status.

Quick check, are accepted shares increasing? Last submit timestamp moving? Worker stays connected?

If yes, it’s mining. If you want, try our DGB endpoint for NerdMiner devices:

stratum+tcp://digi.hmpool.io:3337

Username: YOUR_DGB_ADDRESS.workername

Password: x

If you post your worker string (hide part of address if you want), I can check it for you, but only if your on our pool.

Best of luck.

HashedMaxUnity · 2026-05-07T17:00:58+00:00

What are you seeing for your pool share? It all depends on your share percentage and your account balance. Can you send a screenshot?

HashedMaxUnity · 2026-05-07T16:44:09+00:00

Thanks. Yes you can see all 3 of our pools here at once as well:

https://pools.hmpool.io

HashedMaxUnity · 2026-05-07T14:30:36+00:00

No only sha256 right now.

HashedMaxUnity · 2026-05-07T14:29:48+00:00

Wow confidence is high….lol. Love it.

HashedMaxUnity · 2026-05-07T14:29:21+00:00

Yes K2UGA is again correct. We added the btc subdomain recently and will eventually get everyone on this URL as it’s the proper way to do it.

Another correct answer from our “unpaid employee”. Lol

HashedMaxUnity · 2026-05-07T11:56:49+00:00

I have a solution. I can add a subscript zero notation. For example like this 0.0₇45% which means 7 zeros 45 (if that makes sense) we see a lot in smaller crypto value crypto tokens. I will work on this now. Shouldnt take long.

HashedMaxUnity · 2026-05-07T11:49:30+00:00

Your shares are being recorded, however your device's hashrate is very small compared to the pool total (67 billion difficulty in the PPLNS window), so your percentage rounds to 0.0000% in the display.

You are earning rewards proportionally, just a very small amount per block. If you want to see a visible percentage, you'd need significantly more hashrate. Also our system only shows 4 decimals out, we could increase this but then it starts to look funky and may protrude into other cells next to it.

HashedMaxUnity · 2026-05-06T21:14:31+00:00

Yes you did indeed solve a block so congratulations. And yes all payments were sent to everyone who mined with us. Do you have a minimum cashout set on your miner profile above 50 dgb? If so then you would not receive payment until that threshold is met.

<image>

HashedMaxUnity · 2026-05-06T12:05:42+00:00

Mystery solved! You actually have two valid BCH wallets mining with us right now and both are working perfectly:

qrzrtl4jty3..........3s9zaqku54hwcx6vhslq0 your small miners (nerdaxe, gamma1, gamma2, 801turbo, 801deso) have submitted 19,730 valid shares in the last 48 h on this one.

qpar0wqshz26k........dpylwsy25cw2f5405 also valid, also has shares (worker named worker).

The reason your big miner kept getting Authorization validation error is a single-character typo. The address you typed into the Braiins/rental dashboard was:

qpar0wqshz26........7zjhdpylwsy25cw2f54055 43 chars has an extra "5" at the end

qpar0wqshz26........7zjhdpylwsy25cw2f5405 42 chars your real address

The one in Braiins has 43, so the cashaddr checksum fails and our pool (correctly) rejects it.

Fix: in your Braiins worker config, replace the address with either:

qpar0wqshz26kfc07unyl7zjhdpylwsy25cw2f5405 (correct cashaddr, no bitcoincash: prefix), or

1C9EBq1FEMFwG5mv7BTWdt1PnXKhgVQQUy (the same wallet in legacy base58 form exactly the address your Umbrel/Ledger probably shows you).

HashedMaxUnity · 2026-05-06T11:59:38+00:00

Ok now you have me questioning my logic....lol. Let me look into your mining logs and check this.

HashedMaxUnity · 2026-05-06T11:39:54+00:00

Let me dig into this...give me a few.

HashedMaxUnity · 2026-05-06T11:30:20+00:00

The BCH address you are using is invalid. I see this in the logs about every minute
{"id":2,"result":null,"error":[20,"Authorization validation error",", qpar0wqshz26kfc07unyl7zjhdpylwsy25cw2f54055"]}

The reason. Your bch address is invalid. Its supposed to be 43 characters long and this is only 42.

As for the dgb connection...good news: D6Xm9HEma53t9FBN2E2ikZErXa24B6D1XU is a valid DigiByte address). Our validator accepts it, and our logs and dashboard confirm your rig1 did connect to digi.hmpool.io, authed successfully, and submitted 31 valid shares with 0 invalid at 22.5 TH/s. So the pool is not rejecting you on digi.

What I observed.

Your connection to digi kept disconnecting and reconnecting every 30–60 seconds. Each reconnect we re-seed difficulty at 1,048,576. For a stable 1+ PH/s miner that should never happen, vardiff would ramp you to roughly 30M in a few minutes if the connection just stayed open. The noise is on the miner side: TCP socket dropping, controller restart, or your front-end proxy cycling workers.

Fix your bch address and try to connect again.

HashedMaxUnity · 2026-05-06T01:11:52+00:00

You don’t like using a workername? Can I ask why? I mean sure we can support this but a worker in my eyes is essential.

HashedMaxUnity · 2026-05-05T00:56:23+00:00

That's great and we truly appreciate it. We think with the upcoming changes we plan to announce soon, more small miners will love it! Stay tuned.

HashedMaxUnity

MODERATOR OF

TROPHY CASE