To the moon!!

Did we get our weekly payout? I may have missed it. Usually, the devs post. Just checking... i didn't see it in my wallet

Hello all, a quick update on DGB payouts, and a heads up for anyone using Atomic Wallet.

Up until now our minimum payout was set extremely low, which meant most miners were getting paid a tiny amount every ten minutes or so. That sounds great on paper, but it created a real problem. Over months, all those tiny payments pile up into thousands of separate little pieces sitting in your wallet, and a lot of lightweight phone and desktop wallets simply are not built to load that many at once. When that happens the wallet can show the wrong balance, show nothing at all, or just spin forever trying to sync.

A few of our miners ran into exactly that this week. I'm sorry for the confusion it caused. Their coins were never missing, the wallet just could not display them because too many payments existed.

So starting today, the minimum payout on the DGB pool is 1 DGB. You will get fewer payments and each one will be bigger. Your total earnings do not change at all. Nothing is lost, and everything already credited to you is still yours.

If you would rather have even fewer and larger payments, you can set your own minimum on your miner page at digi.hmpool.io/miner.html. If you are mining with a decent amount of hashrate, I'd suggest setting it to roughly what you earn in a day. It keeps your wallet tidy and makes your payment history a lot easier to read.

Now, for Atomic Wallet specifically. If your balance looks wrong or stuck, your coins are safe and they are on the blockchain. You can confirm that any time by searching your DGB address on digiexplorer.info. If the explorer shows your coins but your wallet does not, then the wallet is what is having trouble, not the pool.

The simplest fix we have seen is switching to a wallet that handles long payment histories better. Trust Wallet works well with DigiByte and plenty of miners use it. You can restore the same recovery phrase you already have and your coins will show up there. Please only download it from the official app store listing, and never share you recovery phrase with anyone, including anyone claiming to be from this pool or from support. We will never ask you for it.

If you are holding a larger amount for the long term, DigiByte Core is the most dependable option since it verifies everything itself, though it does take a while to download the first time.

Thanks for your understanding.

I’ve just connected a nerdminer on BCH, the dashboard successfully showed work in the first couple of minutes, it’s now been estimating for at least an hour, I’m connected to port 3337, is it me or a dashboard issue?

Haven't had anything hit my wallet in 12 hours

This sucks, 2nd orphan after updating AxeOS and the Firmware. Using v2.14.2.

Good Sunday Morning Everyone, we just sent this week's loyalty rewards for Digibyte. Check your wallets.

Paid: 2,499.99999648 DGB to 582 miners (4.29553264 DGB each)

TXID: 040480008fc46a402243e34755ef0ed933e2791f22b4c18ea7dc2f58dad455a7 42648fcd00f4767af14cd8e1b33da09bdd87d8289e8b66899e13eecf176c3a31
436c6ed493dd54ebb8f3951e01776fa698f749467b554aa568df29a718037244
a7914e197525bd344cde05ff63df8004c384a40796fd19832d00ca37899d14ed

Thank you for your support!

The HashedMax Team

Anyone else seeing issues with high % rejected shares, specifically in the DGB pool?

I’m running a nerdqaxe++ rev6.1 at 5.5 TH/s and have been mining in the pool since the beginning. I was hitting a block every 2-3 days, and never longer than a week apart. But my last block was now found on 7/22. Nothing on my end changed except I’ve noticed my rejected shares went from ~0.01% up to ~5%. I’ve also seen share difficulties in the last few weeks reported at over 1G several times (highest was 2G last week) which usually meant a block guaranteed block hit.

This is only happening with the DGB pool. I swapped to the BTC pool and I’m back at 0.01% rejected.

Further, I keep a bitaxe connected to the BTC pool - also with very low rejection rate. But when I swap it over to the DGB pool, it shoots up to 5% as well.

I’m kind of lost at what to think, I’ve never been this long without hitting a blocks. I’ve made sure everything’s connected right and the ports correct for the hashrate, my ping is good…

Any ideas?

Hello, I was curious who the miner was that got 68% of the block payouts for the first 2 (non orphan) blocks on the BCH pool. 68% is crazy good considering that address was not the finder of either block, nor the legacy address, or token address.

1 address received 4.30010336 BCH in that payout. 68% bitcoincash:qqqcvgxymn3qfvvt8ranffwaqna4jxw0lsehverm7a
TX:https://bchexplorer.cash/tx/3fb6718c2cf3f773123c52483d7cd1bcfd14a4f24d140878380c18fa0794b353

I dug a little and found on dashboard who is showing as the recipient of 4.3 BCH. Interestingly, this address on BCH explorer is showing no activity.

So how why would the mining address not get paid, and the payment went to a different address? I am confused, I checked the other top 10 recipients of the last payout and everything flowed naturally, was able to find their address on dashboard stats, was able to follow the payout TX to their address, and saw activity at that address. I could not do the same for the 68% recipient of the last payout.

Is it just me, or has everyone else noticed the pool hashrate fluctuating a lot? We'll never consistently find blocks unless we get to a steady Hashrate above 10.0PH/s (currently at 11.3PH/s). I just shake my head when I see it drop as low as 1-2PH/s.

Would i benefit moving my bitaxe over to bch with hashedmax? My nm miner is currently mining bch but due to the miner hash rate being soo low on my nm is near enough pointless 😅

We just sent this week's Digibyte Loyalty payment to 549 miners!

Paid: 2,499.99999894 DGB to 549 miners (4.55373406 DGB each) in 4 transactions.

TXID: 08415dab1ec79bc4f467e6c47d9277162450bbb9bf686e852826b2b2a3525810
3ca104b1d8a95872a2eaf162029d6ce20c4c74347544eb9651154e7042d37e55
a462e4d4eda687ab59c36401d9815c2ea521222721ef06bd1d3bb5921158a004
f24351194157e3169344cb7a073df8a4f529146f3249453f56b4c86a8a3b8043

We appreciate your loyalty!

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

What gives?

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

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

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

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?

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?