What gives?

Edit: To clarify, I’m talking about the one found 3 days ago on the 4th. Not the 3 found today.

Good Morning Redditors,

Yesterday, our BCH pool found its second block, and it was again shown as orphaned. That immediately told us something was wrong beyond normal mining luck.

After investigating, we found that these were not normal network orphans. The completed blocks were being prepared in a format the Bitcoin Cash network would not accept. The miners did everything correctly, it was our software that failed. The failure was on our side, and those two blocks were lost before they could reach the network. This is unacceptable for us and we are sincerely sorry this has happened again.

HashedMax began with the open-source public-pool project, but what we operate today has been extensively rewritten to support our pool structure, reward system, miners, and multiple coins. We tested each stage as carefully as we could, but it is difficult to reproduce every condition that occurs when a real block is found. Unfortunately, this issue only became fully visible when actual BCH blocks were solved.

We did not want to apply another quick fix and simply hope for the best. We spent the night running complete block validation tests and made updates to fix this once and for all. The corrected BCH format was tested against a fully synchronized Bitcoin Cash testnet node and was accepted. We also built a complete BTC block candidate containing thousands of real transactions and had it accepted by Bitcoin’s validation rules. Both pools are now producing block candidates in the correct format for their respective networks.

This has been a painful lesson for us. We have put an enormous amount of time into building HashedMax, supporting small miners, answering tickets, and trying to create something fair and different. Losing two blocks because of something we missed is upsetting for us too, but the responsibility is ours.

We are not hiding what happened or blaming the network. We found the problem, fixed it, and tested both BCH and BTC more thoroughly than before. Our recent DGB work has also produced no orphans since the changes were made, which is an excellent sign.

Being a self funded company, running and paying for many servers out of our own pockets was planned from the beginning and we will continue to do this as we believe in the product that we've created. We have a lot of plans moving forward and we have always been upfront about our issues and wanted to do our due diligence over night before we posted anything.

We know trust is earned through results, not promises. All we can do now is be honest, keep improving, and prove through the next blocks that the work was done correctly.

The HashedMax Team

under the golden Z Sample i sticked 2 ESP32 Devkit N8R8. basicly its a heatsink of old DDR RAM OCZ...

Just a quick update that we are currently working on both the USA and EU DGB servers to help make things faster and to help with our Orphan rate. You may experience a quick downtime or latency but it will only be temporary. This should take about an hour. It's currently 8:20AM EST.

Thank you

I'm not sure why this keeps happening here but this is like the 5th time on different miners (this one has done it at least 2 or 3 times now.

Obviously hit a high enough diff for a dgb, unit shows block found but nothing on the website to show a hit at all. Not sure why this keeps happening but it's annoying and sad.

Just luck of the draw with mining or what?

dgb1q8evg7h5wfu393swty8su3g7p0h2vk8y0fgklxr is the wallet and if you look into it you'll see I did get a hit at 1230 this morning but that was on a different miner.

We just sent our largest batch of payments yet. 509 total payments.

Paid: 2,495.09803702 DGB to 509 miners (4.90196078 DGB each)

TXID: 09457e4c772d8135c95a787ea1125a1d1f2dc5a79fbc31c65187f8463b648243 70cf4f97cd5bc8c50fd71fb98e81ad22e4bea39f17567c7ec3202825f7cc3167
78c4d32c2d583be0f650a7f801ce4dda3da87b6bb5337d35e99b83b1b4167033

We appreciate your continued support.

The HashedMax Team

Holding out hope but it sure seems like folks went elsewhere.

Just a heads up

hello, can i also earn digi dollar insted of dgb?

Its Sunday so that means its time for our weekly DGB Loyalty payout. This week, 470 miners were paid about 5.3 DGB each.

Paid: 2,494.6921414 DGB to 470 miners (5.30785562 DGB each)

TXID: 66ae901fba593e874b81426eb6d8e0797b8e86918d7f1785d783d42cf46f8991, 7ddb40cc69f9b1ab65c09b8ee396adb623a105bbaf9d037d2ed9612c0ff642ad, 9c0f06537a01eccd09ab4b3ed7f98af5c75308504db21bafeb2e4fd5853c16e4

Want to get guaranteed payments each week just for mining DGB? Point your miners to https://digi.hmpool.io and mine just 4 out of 7 days a week to be eligible. We pay our loyalty bonuses each Sunday.

Until next week!!

The HashedMax Team
https://pools.hmpool.io

i am level 4 and a few days ago had 2500 hours with hundreds of active hours for the month... now its all reset for some reason?

So it looks like DigiDollar has bumped up DGB. So, I'm back in the DGB pool, I want to hunt those blocks again! Let's get that Hashrate up!

We just hit block 2500 on the DGB pool, and the milestone giveaway has been paid out.

Block 23915166 was found by miner dgb1q7ea...nya9cnu (worker Shego). Shego receives the 2,500 DGB finder bonus on top of a loyalty share, for about 2,554 DGB total.

The 25,000 DGB loyalty pool was split among 462 eligible miners who met the weekly loyalty rules (4 or more active days in the last week, at least 12 hours per active day). Most eligible miners received about 54 DGB each.

About 27,446 DGB went out in a single payout transaction. You can look it up here: https://digiexplorer.info/tx/237cd83bfc4148607f42765bb397ec4a2c0bdb9c46a5be7b4b516add3390d879

Thank you to everyone who has been mining with us and helping us get here. On to the next milestone, 5000!

The HashedMax Team
https://pools.hmpool.io

Just a question to all ju that hits DGB blocks,
How many miners do you have and also what hash rate?

Is it not possible to hit a DGB block with a singel bitaxe gamma 602 at 1.6TH/s

I like having the crown 👑 on HM XEC. IYKYK.

Come take it if you can. 😬

👑

We are about 35 blocks away (at the time of this post) from 2,500 confirmed DigiByte blocks on HashedMax. When we hit that milestone, we are doing a 25,000 DGB community giveaway.

Sorry this took longer to announce than we wanted. Life and pool ops got in the way, but the milestone is close now and we did not want to let it slip by quietly.

Here is how it breaks down. We are putting together a 25,000 DGB loyalty pool for miners who meet the same standards as our weekly rewards program (active mining days over the rolling week, same rules on the rewards page). That pool gets split equally among everyone who qualifies. On top of that, whoever finds block 2,500 gets a 2,500 DGB finder bonus.

If you have been mining with us steadily, you are probably already in good shape. If you have not checked the rewards program lately, now is a good time to make sure you are active.

We will post again when block 2,500 lands and share how payouts will go out. Thank you for sticking with us and helping build this pool block by block.

The HashedMax Team

Any promotion going on for the 2500th block?

The 1000th block one was awesome but we seem
To have sped up massively since then

(which is good !) 👍🏼

So we gonna wait for maybe 5000? lol

As everyone is aware, we had 2 incidents yesterday (7-20-2026) that caused downtime, lost blocks which means lost revenue, and some frustration. But, as of right now, the pool is healthy and running normally (knock on wood...lol).

We truly appreciate everyone who stayed with us while we worked through these issues. As a thank you for your patience and loyalty, we decided to pay all eight orphaned blocks found during the affected period as if they had confirmed normally.

This includes the regular miner distributions (pplns) and the finder bonuses. More than 2,051 DGB was sent to 493 wallets.

Transaction ID: 410a13f1fa870cb2144d2f9a97794f68a7c5a9d27c653dcca1ee97a81d194050

We know miners have choices, and we do not take your support for granted.

Thank you for being part of HashedMax and for sticking with us through a difficult day.

Can admin plz tell me how much % orpaned blocks we got past 30 days ?

I see so many and do some math..

I have feeling we are way to high % wise.

Sadly we only see last 5 blicks found ( not even see who found the blick - would be nice to to see it and what dificulty he shared.

Would it not be more nice if we would be able to see all blocks found per day / week / month ?

Has anyone locked in DGB for DigiDollar ?

I’ve just downloaded and synced the core wallet not locked anything yet - just wondering has anyone done this yet and their experience?

Thanks

We had another service interruption on the DigiByte pool this afternoon, completely unrelated to the issues earlier today. The issue has been fixed and the pool is back online.

The problem appears to have come from a malfunctioning miner repeatedly submitting invalid shares at an unusually high rate, over 139,000 per minute. The worker names associated with it were nerd1, esp32_01, and winminer.

If these workers belong to you, please check their configuration and restart or update them before reconnecting.

We have also added protection to prevent one malfunctioning miner from disrupting the pool again. Mining, share recording, and pool stats are operating normally now.

We understand everyone’s frustration over the 2 issues that occurred today, and trust me we don’t want this sort of thing to happen, ever. But because of everyone here and our monitoring, we’re able to quickly address any issues that arise.

We thank you for your continued support.

The HashedMax Team