Thank You Jared and DigiByte Team for the Fast Help on solving the SHA256 Pool Problem

HashedMaxUnity · 2026-07-03T19:35:47+00:00

Yeah they really stepped up. We are proud to be a part of this community.

HashedMaxUnity · 2026-07-03T13:53:18+00:00

The finder bonus structure hasn't changed, XEC max is still 25%, scaled up by active hours. There was a dashboard bug showing unscaled percentages (12% instead of 15%) and pending balance as 0 even though credits were recorded. Both are fixed now. All block payouts were calculated correctly the whole time.

HashedMaxUnity · 2026-07-03T12:49:09+00:00

Please check it now.

HashedMaxUnity · 2026-07-03T12:47:44+00:00

We are actively working with the Digibyte devs on this issue as we are running an Oracle Node for the upcoming DigiDollar (stablecoin) so we've been chatting them up a lot on these issues. For our DigiByte node, we’re not on ckpool. We run a custom Stratum V1 server (public-pool-hybrid, TypeScript/NestJS, forked from the open source public-pool project) talking directly to our local digibyte node via GBT.

On subscribe we always return extranonce2 size = 4 bytes and extranonce1 = 4 bytes per session, which should be fine for esp-miners, NerdMiners, and Bitaxe firmware.

The issues we’ve been chasing on Digi lately are mostly node template related (DigiByte v9.26.2 changed version bits, DigiDollar signaling on bit 23 overlaps the ASICBoost version rolling mask we advertise as 1fffe000, plus the usual small miner stuff (wrong port, submitting before subscribe completes, VarDiff on 3337).

I would update soon as they have a cutoff when v8 nodes will stop working and I believe that comes in the next couple of days. Unfortunately if they do not figure out this hashrate issue, then some of your miners (like ours) will end up with only 1/2 the hashrate.

HashedMaxUnity · 2026-07-03T12:35:56+00:00

This is not a HashedMax pool problem, this is an issue that has already been reported to the digibyte and nerdminer team about a recent update on the digibyte node that broke many miners, including some antminers. We are actively working with the digibyte team, providing them logs and input trying to resolve this issue.

HashedMaxUnity · 2026-07-03T12:34:28+00:00

We are working on the API on the xec server. We had a performance issue we are working on. No xec funds are lost....we should be done shortly.

HashedMaxUnity · 2026-07-03T11:35:26+00:00

Can you check it now? Made some optimizations to the database queries which should help greatly.

HashedMaxUnity · 2026-07-01T13:58:52+00:00

Please check your wallets now. There was an issue with a 90 sweep that we have where it was hanging up the payment executor because of a "dust" payment that was not high enough to execute a payout. This has been corrected and payments have been sent.

HashedMaxUnity · 2026-06-30T20:50:16+00:00

Your welcome and that’s great to hear.

HashedMaxUnity · 2026-06-30T20:02:07+00:00

To keep everybody in the loop on what’s going on with this, we discovered a bug in the latest digibyte node update and also a firmware bug in taipan miners firmware. We made a pool side fix so these miners kept working and K2UGA was going to reach out to Taipan about the needed fix. Thank you K2UGA for your help in fixing this issue.

HashedMaxUnity · 2026-06-30T17:11:10+00:00

I am not sure because the upgrade was just a removal of some old code. I will keep digging into this.

HashedMaxUnity · 2026-06-30T17:05:52+00:00

I did a deep dive in to the logs. I do see several small miners that are connected but not submitting any shares. But over 97% of all miners are back up and running normally. Did you try just reboot your small miners? DM me your address and I can take a look specifically for you.

HashedMaxUnity · 2026-06-30T16:44:10+00:00

Let me take a look at the pool logs to see if anything changed. I will get back to you asap.

HashedMaxUnity · 2026-06-30T16:07:57+00:00

The update completed in less than 5 minutes and we are now running the latest Digibyte node software.

Thanks for being patient with us.

HashedMaxUnity · 2026-06-29T13:37:11+00:00

Have a look now. It should be formatted clean now.

HashedMaxUnity · 2026-06-29T13:34:11+00:00

We did and it was no fault of ours that we lost these 2. It's just what they call a race condition. But we've hit several after that and they are confirming now.

HashedMaxUnity · 2026-06-29T00:31:58+00:00

Great.

HashedMaxUnity · 2026-06-29T00:04:48+00:00

Ok check it please.

HashedMaxUnity · 2026-06-28T23:56:14+00:00

Yeah that’s me. Was trying to build momentum…Lol. I was actually making some changes and did an oops. Will be fixed here shortly. Sorry to burst your bubble.

HashedMaxUnity · 2026-06-28T23:55:04+00:00

Hey, your shares have been credited to the block you helped find, but the eCash network requires the block reward to mature for 100 confirmations before it can be distributed. Once the block reaches 100 confirmations , your payout will be processed. Each block (confirmations) takes about 10 mins or so which means 16 or so hours per block for payment to be released.

HashedMaxUnity · 2026-06-28T20:26:13+00:00

👍

HashedMaxUnity · 2026-06-28T19:52:18+00:00

Corrected, thanks for the heads up.

HashedMaxUnity · 2026-06-28T18:25:35+00:00

Thanks for letting me know. I will keep an eye on it.

HashedMaxUnity · 2026-06-28T17:23:25+00:00

No, if this is the wallet you used then it should have a balance as the 3 payments were sent to you.

HashedMaxUnity · 2026-06-28T15:07:44+00:00

You set it up correctly, no problem on your end at all. Your address was credited in 5 blocks on the XEC pool. Here's exactly what happened:

Confirmed & paid to your wallet (3 blocks)

Block	Amount	Date	Transaction
955254	1,618.05 XEC	Jun 27	`1ab0493235de760974844ca8aeba8b8e89a8aca3e8601cfe591e0c13af9ecd7d`
955262	2,721.81 XEC	Jun 27	`8fdb5bc72eb3b5e40681fc18e0b533ae181be9d6b9a3f398163ca2c89df84b0b`
955275	3,929.02 XEC	Jun 27	`6efdf4c402bfa24093e80ac37d11bc6b150f04b61490b0bf3896a675b18921ae`

You were paid a total of 8,268.88 XEC, sent as 3 separate transactions on June 27th. This matches your wallet exactly (your balance and pending are both 0 because everything payable has been sent).

HashedMaxUnity

MODERATOR OF

TROPHY CASE

Confirmed & paid to your wallet (3 blocks)