u/HashedMaxUnity

Some of you noticed connection issues last night, especially on EU endpoints.

Over the past 36 hours we've been dealing with a number of IPs hammering our public API and stratum reconnect loops, abusive traffic that was pushing load way higher than it needed to be. As part of the response we've:

• Added per-IP rate limiting on the public API endpoints
• Added short-lived server-side caching to the highest-traffic endpoints so the DB isn't asked the same question 200x/second
• Firewalled the worst offenders at the OS level
• Hardened reconnect handling on the stratum side

This caused connection issues, high ping and latency issues which many of you reported.

All EU and USA pools are back to normal now.

If your worker is still misbehaving, drop your worker name in a comment and we'll check.

After many hours of watching logs and debugging our BCH pool, I believe we have narrowed down one of the main issues affecting high-hashrate miners and rentals.

When a miner connects, it can request a difficulty in a few different ways. Some miners/rentals include it in the password field, such as d=8000000. Some miners automatically send mining.suggest_difficulty, which is the suggested difficulty of the miner. If neither is provided, the pool starts the miner at the configured starting difficulty for the port they connected to.

The purpose of these difficulty settings is to prevent a high hashrate miner from starting too low and flooding the pool with shares, while also keeping share submission smooth enough that the miner does not appear dead or unstable.

What we found was that our pool could correctly read a requested d= difficulty, but then another startup/reconnect difficulty helper could override that value based on recent share history. In some cases, miner supplied suggested difficulty could also affect the session in ways that were not ideal for high hashrate miners.

We made changes so that password requested d= difficulty is respected more strongly, and miner supplied mining.suggest_difficulty is treated as a hint instead of something that can pull the pool’s chosen difficulty downward. Reconnect difficulty seeding can still help normal reconnecting miners, but it should no longer override miners that have requested d=.

I did restart the BCH pool node so the changes could take effect. Sorry for the disconnects, but the restart was needed to move the live pool onto the corrected code.

So far things look better from the logs, but we are continuing to monitor. If you are still seeing connection issues, rejected shares, or unstable hashrate after reconnecting, please let us know with your worker name, port, and approximate time.

Remember, this issue was currently only on our BCH server. We are monitoring BTC and DGB as well.

The data is in: HashedMax's new HMP FairShare is working.

We just audited 68 blocks of Digibyte data since launching our new payout model on May 10th. The results for the community are massive:

*Pool Growth: Participation per block is up 132%.

Small Miner Wins: Average earnings per block are up 20.2%.

Maximum Impact: Our most consistent small miners saw boosts as high as 132%.

Before FairShare (Old PPLNS System):

5% of block reward went to participation pool
Roughly 12.97 DGB split among participating miners per block

After FairShare (New System):

5% base participation
+8% small miner boost (for miners < 10 TH/s)
+5% loyalty bonus (for miners with 96+ hours)
Roughly 30.11 DGB split among qualifying miners per block

The participation pool is split equally among all qualifying miners regardless of hashrate. This is why it benefits small miners across the board, a small miner gets the same participation share as a large miner, making it a larger percentage of their total earnings.

*Participation per block refers to the total DGB distributed through the participation bonus pool each time a block is found.

We built this to protect the independent miner, and the numbers show that loyalty and consistency are finally being rewarded. No more guessing. The math is on your side.

https://preview.redd.it/aljxrc0o5z0h1.jpg?width=1396&format=pjpg&auto=webp&s=0615b1224a72a9183e26910d459cae98cb962a4e

We have just updated our hashrate wizard to include an optional difficulty setting.

Many mining rigs display an Optimal Difficulty range directly in their interface. This number is often more accurate than estimating based on hashrate alone, especially for larger miners running multiple ASICs or rented hashrate.

If your miner shows something like "Optimal Difficulty 186k - 1,118k", you can now enter that value directly into our wizard and get the correct port recommendation instantly.

The wizard is available on all HashedMax pools at hmpool.io, bch.hmpool.io, and digi.hmpool.io, as well as our EU endpoints.

We have just updated our hashrate wizard to include an optional difficulty setting.

Many mining rigs display an Optimal Difficulty range directly in their interface. This number is often more accurate than estimating based on hashrate alone, especially for larger miners running multiple ASICs or rented hashrate.

If your miner shows something like "Optimal Difficulty 186k - 1,118k", you can now enter that value directly into our wizard and get the correct port recommendation instantly.

The wizard is available on all HashedMax pools at hmpool.io, bch.hmpool.io, and digi.hmpool.io, as well as our EU endpoints.

We have updated all 3 of our pools to the new HMP FairShare payout system that we posted about the other day.

So far we've hit a few Digibyte blocks since the change and small miners are already benefiting from the increased payout.

We ask that if any of you are on Social Media that you share this update, crosspost and get the word out. We think with this change we can capture a large portion of miners (at least that's the hope).

Stay tuned for further updates soon, as there is a lot more to come.

FEEDBACK WANTED FROM OUR COMMUNITY ON THE FOLLOWING THAT WE ARE DEBATING IMPLEMENTING.

Most pools are built for the "whales" industrial farms that jump in, dilute the reward pool, and jump out. At HashedMax, we’ve finalized a payout system that rewards Loyalty and protects Small Miners. We call it HMP FairShare (TLDR Video Attached).

The Block Split:

When HMPool finds a block, the reward is distributed with surgical precision:

1% Pool Fee (Keeping the fortress running)

20% Max Weighted Finder Reward (Reward for the hunter)

66% Base PPLNS Share Reward (The community backbone)

5% Loyalty Reward (For the long-haulers)

8% Small Miner Boost (Protective subsidy for hobbyists)

_______________________________

The Weighted Finder Reward: A Ladder to 20%

We don’t believe in "luck-based" flat bounties. We reward consistency. Your Finder Reward scales based on your active mining time over a 7-day rolling window:

 < 8 hours: 4.0% Finder / 70% PPLNS

 8–24 hours: 5.6% Finder / 70% PPLNS

 1–2 days: 8.0% Finder / 70% PPLNS

 2–4 days: 12.0% Finder / 70% PPLNS

 4–7 days: 16.0% Finder / 70% PPLNS

 7+ days: 20.0% Finder / 66% PPLNS

If a miner hits a block and is only in the 8 - 24 hour range (for example), the finder gets 5.6% for the block reward. The remaining 14.4% of the finders fee goes back to the PPLNS payout and NOT to the pool owners. Ensuring fairness as our fee will only ALWAYS be 1%.

 ________________________________

The Small Miner Boost: Anti-Gaming Mechanics

The 8% Small Miner Boost is specifically engineered to prevent "gaming" by larger operations.

Wallet-Level Tracking: Boosts are calculated by payout address, not worker name. Splitting your farm into 100 small workers won't work here.

The "Gaming-Proof" Formula: We use a rolling average to ensure stability.

$$boost\_tier\_hashrate = max(24h\ rolling\ hashrate,\ 7d\ rolling\ hashrate)$$

This specific formula prevents miners from dropping hashrate temporarily to "look small" for the boost. By using rolling submitted share difficulty over time, we ensure the 8% goes exactly where it’s intended: to the independent, home-based miners.

Why this matters:

Whether you're running a Bitaxe, a NerdMiner, or a small home-office rig, HMP FairShare ensures your contribution isn't swallowed by the noise of the global hashrate.

Please give us your opinions on this possible change.

https://reddit.com/link/1t7mhuz/video/1ihpd9uenzzg1/player

I wanted to give a quick update on some things we've updated across all 3 of our pools. First, we added a new workers stat card to your miner stats page. While we show the workers separately below the stat cards, it now shows how many workers you have any its clickable to bring you right to your individual worker stats.

https://preview.redd.it/hj99lo2yupzg1.png?width=1210&format=png&auto=webp&s=8521cb4ebec9bff50958b31edbe81017b877d1c8

We figured this was helpful so you immediately know if you have a worker offline with just a glance.

The next thing we changed was something called subscript zero notation. Some miner stats show 0.0000% for their pool share percentage. This is not totally accurate because these small hashrate miners are submitting shares and participating but because of our decimal limitation (which skews the display) it shows as 0.0000. Now it will show your actual pool share percentage with subscript. For example.

Actual Percentage	Display
0.0500%	0.0500%
0.00005%	0.0₄5%
0.00000045%	0.0₆45%
0.0000000012%	0.0₉12%

Thank you again for all of your support. The HashedMax community has grown to more than what we've ever imagined. We have some great things coming your way very soon....stay tuned.

Not mining on our pools? Check them out now at:

https://btc.hmpool.io - BTC Pool (Bitcoin)
https://digi.hmpool.io - DGB Pool (Digibyte)
https://bch.hmpool.io - BCH Pool (Bitcoin Cash)

I wanted to give a quick update on some things we've updated across all 3 of our pools. First, we added a new workers stat card to your miner stats page. While we show the workers separately below the stat cards, it now shows how many workers you have any its clickable to bring you right to your individual worker stats.

https://preview.redd.it/35vtfguorpzg1.png?width=1206&format=png&auto=webp&s=43b601ee7fb7cc8c16fadc56ca0211cc27499da8

We figured this was helpful so you immediately know if you have a worker offline with just a glance.

The next thing we changed was something called subscript zero notation. Some miner stats show 0.0000% for their pool share percentage. This is not totally accurate because these small hashrate miners are submitting shares and participating but because of our decimal limitation (which skews the display) it shows as 0.0000. Now it will show your actual pool share percentage with subscript. For example.

Actual Percentage	Display
0.0500%	0.0500%
0.00005%	0.0₄5%
0.00000045%	0.0₆45%
0.0000000012%	0.0₉12%

Thank you again for all of your support. The HashedMax community has grown to more than what we've ever imagined. We have some great things coming your way very soon....stay tuned.

Not mining on our pools? Check them out now at:

https://btc.hmpool.io - BTC Pool (Bitcoin)
https://digi.hmpool.io - DGB Pool (Digibyte)
https://bch.hmpool.io - BCH Pool (Bitcoin Cash)

I wanted to give a quick update on some things we've updated across all 3 of our pools. First, we added a new workers stat card to your miner stats page. While we show the workers separately below the stat cards, it now shows how many workers you have any its clickable to bring you right to your individual worker stats.

https://preview.redd.it/35vtfguorpzg1.png?width=1206&format=png&auto=webp&s=43b601ee7fb7cc8c16fadc56ca0211cc27499da8

We figured this was helpful so you immediately know if you have a worker offline with just a glance.

The next thing we changed was something called subscript zero notation. Some miner stats show 0.0000% for their pool share percentage. This is not totally accurate because these small hashrate miners are submitting shares and participating but because of our decimal limitation (which skews the display) it shows as 0.0000. Now it will show your actual pool share percentage with subscript. For example.

Actual Percentage	Display
0.0500%	0.0500%
0.00005%	0.0₄5%
0.00000045%	0.0₆45%
0.0000000012%	0.0₉12%

Thank you again for all of your support. The HashedMax community has grown to more than what we've ever imagined. We have some great things coming your way very soon....stay tuned.

Not mining on our pools? Check them out now at:

https://btc.hmpool.io - BTC Pool (Bitcoin)
https://digi.hmpool.io - DGB Pool (Digibyte)
https://bch.hmpool.io - BCH Pool (Bitcoin Cash)

We wanted to take a moment to genuinely thank everyone mining with us over at digi.hmpool.io. We're still growing and gaining momentum, but crossing 24 blocks in a single 24-hour period is a milestone we're really proud of and it wouldn't have happened without the support of this community.

If you haven't checked us out yet, we run a multi-coin mining pool at https://pools.hmpool.io covering Bitcoin, Bitcoin Cash, and DigiByte, with a unique FairShare payout system that rewards finders, loyal miners, and small miners alike.

Why we chose DigiByte:

Beyond just the mining gains, the DigiByte ecosystem is in an exciting place. The team is actively developing DigiDollar ($DD) a fully decentralized, USD pegged stablecoin built natively on the DigiByte blockchain. Unlike USDT or USDC, no company controls it, anyone with DGB can mint it as collateral. It's currently in active testnet with mainnet targeted for later this month, and integration guides for wallets and exchanges have already gone live.

With 15-second block times, sub-cent fees, and 5 algorithm PoW security, DGB is quietly one of the most solid chains to be mining and holding right now.

Come mine with us: https://digi.hmpool.io

Thanks again to everyone who's been part of this journey. We're just getting started.

It was brought to our attention that our rewards program did not properly credit higher hashrate miners. A miner running multiple smaller devices was earning more draw entries than someone running fewer, more powerful rigs, even if their total hashrate was a fraction of the other miner's contribution.

Old System — Points calculated per worker device.

Each worker (device) earned its own points separately, capped at a flat 1.30x multiplier regardless of how much hashrate you actually contributed.

Miner | Total Hashrate | Workers | Points/hr

1 Bitaxe | 1.2 TH | 1 | 13

6 Bitaxes | 7.2 TH | 6 | 78

18 Bitaxes | 21.6 TH | 18 | 234 - gets more

6 × 6TH rigs | 36 TH | 6 | 78 - loses

1 × 100TH ASIC | 100 TH | 1 | 13

The 36 TH miner contributes 67% more hashrate than 18 Bitaxes but earned 3× fewer draw points simply because they used fewer devices. The 100 TH ASIC earned the same as a single Bitaxe. That's not fair, and we fixed it.

Points are now calculated once per wallet address, using the sum of all yourworkers' hashrates. Running more devices no longer inflates your entries, only your total hashrate contribution matters. We also significantly expanded the multiplier tiers to properly reward higher hashrate miners.

New tiers:

Tier | Multiplier

< 10 MH | 1.00x

10–100 MH | 1.05x

100 MH – 1 GH | 1.10x

1–10 GH | 1.15x

10–100 GH | 1.20x

100 GH – 1 TH | 1.30x

1–10 TH | 1.50x

10–25 TH | 1.80x

25–50 TH | 2.20x

50–200 TH | 2.75x

≥ 200 TH | 4.00x

Updated points comparison:

Miner | Total Hashrate | Tier | Points/hr

1 Bitaxe | 1.2 TH | 1–10 TH · 1.5x | 15

6 Bitaxes | 7.2 TH | 1–10 TH · 1.5x | 15

18 Bitaxes | 21.6 TH | 10–25 TH · 1.8x | 18

6 × 6TH rigs | 36 TH | 25–50 TH · 2.2x | 22 now correctly rewarded

1 × 100TH ASIC | 100 TH | 50–200 TH · 2.75x | 27.5 properly credited

When does this take effect?

Immediately, and retroactively. We have already re-processed the entirecurrent draw period (back to April 26th) using the corrected formula. No one loses points they legitimately earned, the recalculation simply removes the worker count inflation and replaces it with accurate per wallet totals.

All rewards pages across all 3 pools have been updated and your points have been recalculated going back to last Sunday, April 26th.

Thanks to the community member who flagged this, feedback like this makes the pool better for everyone.

I created a post for our community and it's just not listed. If I go to our profile, posts its listed. I tried looking from a different browser and its not there. Now, oddly enough I do have one comment on it, but I am at a loss right now...LOL.

Here is the post in question
https://www.reddit.com/user/HashedMaxUnity/comments/1szydmp/hashedmax_has_officially_gone_global_with_all_of/

But if you go to my Reddit, its not there.
https://www.reddit.com/r/HashedMax/

What am I doing wrong?

We're really excited to announce that we've just brought two new regional endpoints online for our European mining family:

eu.btc.hmpool.io  → Bitcoin stratum (ports 3334-3338)

eu.bch.hmpool.io  → Bitcoin Cash stratum (ports 3335-3339)

This rounds out the regional rollout. DGB has had eu.digi.hmpool.io for a while, and now BTC and BCH have joined the family.

You get a dedicated European-side connection point for your miners.

HTTPS landing pages with built-in port-selection wizards: https://eu.btc.hmpool.io and https://eu.bch.hmpool.io

Same pool, same wallet, same dashboard, same PPLNS balance, same finder bonus, same participation bonus, same reward points, same affiliate link, same payouts. Nothing about your account changes.

How to switch:

Change one thing, the hostname and you're done:

Before:  stratum+tcp://btc.hmpool.io:port

After:   stratum+tcp://eu.btc.hmpool.io:port

Before:  stratum+tcp://bch.hmpool.io:port

After:   stratum+tcp://eu.bch.hmpool.io:port

Wallet, worker name, password, difficulty hint, all stay exactly the same. If you have multiple workers, you can move some now and others later. Every share lands on the same wallet on the same dashboard.

If you're closer to our US endpoints, no need to change anything, they're not going anywhere.

Got questions? Drop them in the channel or use the contact form on any of our pools.

Welcome aboard!

We’re looking at ways to improve payouts for smaller miners on HashedMax while still keeping our pools fair for everyone, including the larger miners who provide a lot of steady hashrate.

One idea we’re considering is a payout adjustment that would give active smaller miners a stronger share when the pool finds a block. In some cases, a very small but consistent miner could see their per-block payout increase by up to around 100% compared to our current system.

This would not mean taking away the normal share-based payout. Larger miners would still earn based on the valid work they submit, and miners who find blocks would still receive a finder reward. The goal is not to punish large miners. The goal is to make sure smaller miners who consistently support the pool feel like their contribution actually matters.

We’re not ready to release the full details yet, but we want community feedback before making any major payout changes.

A few questions:

What should classify someone as a “small miner”? 1th, 5th, 20th or more?

Should it be based on submitted share difficulty, estimated hashrate, time connected, or a mix of those?

Where would you draw the line between tiny, small, medium, and large miners?

Should a miner need to be active for a minimum amount of time before qualifying for any small miner boost? For example, 24 hours active. More time or less?

Would you support a system where active smaller miners can earn more per block, while larger miners still earn the majority of rewards through the work they submit?

Our goal is to make HashedMax more attractive to real long-term miners, reduce short-term pool hopping, and keep the system fair for both small and large miners.

We’d appreciate honest feedback from the community before we move further. We are building this community for you, so your opinion really matters.

We ran a poll on X about changes to our pplns system and after reviewing the poll results and the direct feedback from miners who feel "priced out" of PPLNS rewards, we’ve realized that the 4 standard capping models we offered might just be band-aids on an old system.

We have officially begun development on a new payout architecture. Our goal, create a system that makes it mathematically viable and exciting, to point a few TH/s or even GH/s at a pool again. We're moving beyond the standard industry templates to build something "Hardened" from the ground up.

Details dropping soon. The "pleb" crowd is about to have a new home. Stay tuned while we iron out details.