We just sent our weekly Digibyte mining loyalty rewards, so please check your wallets.
Paid 2,499.99999702 DGB to 382 miners (6.54450261 DGB each)
Paid in 3 separate transaction id's. 8d23968a4bccd177a8765052aae3e507f720f7cc7c6286380d0399ed6d277d0b
b3fc0fd61e535c76ba76aff3e9ba58127d752f1a959b132fefbcdb7dc60ced36
e36a58b4f95a45278106d3bfd4ae63489bf22324e7e48d271cbf70afa206ed6e
Thank you for your loyalty!
We wanted to share a big thank you to Jared and the DigiByte team for working with us directly to get to the bottom of the SHA256 pool issue we hit after the recent DigiByte node upgrade.
After recently updating our DigiByte node to version 9.26.2, we started seeing a major drop in credited hashrate from certain SHA256 miners, especially NerdAxe and NerdQAxe units. Device hashrate stayed normal, but poolside credited hashrate fell off hard, which told us something in the share flow had changed.
Over the last few days we worked closely with the DigiByte side by feeding them real miner websocket logs, pool behavior, live testing results, and side by side comparisons from our environment. We were able to show exactly what miners were receiving, what they were submitting back, and how the behavior changed between the old and new node/job versions. That back and forth made a huge difference because it moved the conversation from theory to actual field data.
Jared stayed engaged through all of it, reviewed the evidence, acknowledged where the problem came from, and helped narrow it down to the version rolling and bit 23 interaction affecting some SHA256 firmware. Once that was understood, we tested the fix in our sandbox, confirmed it restored expected behavior, and then rolled it out live.
We really appreciate the fact that the DigiByte team listened, took the reports seriously, and worked with us to solve it properly. That kind of response matters a lot.
So sincerely, thank you to Jared and the DigiByte team for the time, the communicatio and the help getting this resolved. We are very happy to see this fixed and moving in the right direction.
So far our initial beta for our "next project" is going well. We are now looking for a few more testers as we enter into phase 2, closer to launch. If you have already signed up and are participating, there is no need to signup again.
We’re especially interested in people who currently have or manage different types of mining hardware and are familiar with pointing miners to different pools/stratum URLs.
Ideal beta testers:
This is not a token launch, not an investment thing, and not a trading bot. It is a mining utility/platform we’ve been building for some time to solve a real problem we’ve seen in the mining space.
We’re not opening it publicly yet, but we’d like a second group of miners to test this second version, give feedback, and help us shape the platform before launch.
There is no pay or compensation for testing. Your duty will be to test the platform, report problems, recommend changes, updates and more. You will be given direct access to a new platform that we have been working on but confidentiality at this point is a must.
We are looking for serious feedback, not hype.
If you are interested, please fill out the form here:
Miners, the DigiByte Core team has released v9.26.2 today as an emergency fix for an active network attack.
What happened: Starting June 28, an attacker exploited a dormant bug in the v8 codebase that left DigiByte's retired Groestl mining algorithm (retired in 2019) unenforced. The attacker has been mining Groestl blocks at floor difficulty, causing brief chain splits and network instability.
What v9.26.2 does. Permanently blocks retired-algorithm blocks. Once the majority of nodes upgrade, the attack ends and the network fully heals.
The deadline. Block 23,808,000 (on or about July 6–7). At that point v9.26.2 nodes hard-reject all Groestl blocks. Nodes still on v8 will be on the wrong chain and will basically be inoperable.
For our miners:, we are upgrading our DGB pool node to v9.26.2 right now. There will be a brief maintenance window of approximately 5–10 minutes. Mining will resume automatically, no changes needed on your end.
No coins were stolen and no transactions were reversed. This is a stability and security fix. Keep your miners pointed at the digi pool as this should only be a brief max 10 minute downtime.
The HashedMax Team
We added a dedicated EU stratum endpoint for miners in Europe who want a shorter path to the pool.
eu.xec.hmpool.io is a regional relay for the same HashedMax eCash pool you already use at xec.hmpool.io. Same pool, same accounting, same payouts, same dashboard. The only change is where your miner connects.
EU port range: 3350 to 3356
Port assignment
3350 Best for Ultra-low hashrate (NerdMiner, ESP32, under 100 MH/s)
3351 GPU / small miners (100 MH/s to 300 GH/s)
3352 Bitaxe and similar (300 GH/s to 2 TH/s)
3353 Mid ASIC (2 TH/s to 20 TH/s)
3354 High / farm (20 TH/s to 100 TH/s)
3355 Large rigs (100 TH/s to 500 TH/s)
3356 Ultra-high / PH-class (500 TH/s and up)
Not sure which port to use? The setup wizard on the home page can recommend one from your hashrate or your miners suggested difficulty.
EU endpoint: https://eu.xec.hmpool.io
Please try to connect and if you have any issues, please don't hesitate to reply to this post.
The payout for the first 2 XEC blocks we hit have been successfully processed. Please check your XEC wallets (for those that mined with us).
Introducing our newest pool, ecash!
Hello miners,
We are happy to announce that the new dedicated HashedMax XEC pool is now live and open to all miners. It's already above 2ph, so hop on now and lets get that first block!
This pool includes the standard HashedMax features our miners are used to, including loyalty point integrations, reward structures, miner tracking, and the same low-hashrate friendly approach we use across our pools.
We appreciate everyone who voted and gave input during the transition. The poll made it clear that XEC was the direction the community wanted, so that is where we put our focus.
For those that are not familiar with what we are talking about, we had a multi node switching pool that did not meet our expectations, and we put up a poll asking the community which token they wanted. XEC won, hands down.
Since this is a new pool launch, we are opening it up and asking miners to help us put it through its paces. If you connect, mine, check your stats, or notice anything that does not look right, please let us know. That includes display issues, worker stats, estimated rewards, difficulty behavior, payout questions, dashboard bugs, or anything else that feels off.
Our goal is to make this a stable, fair, and reliable XEC pool for SHA-256 miners, and the fastest way to get there is with real miner feedback.
You can connect and start mining now at:
Thank you again to everyone who voted, supported the move, and stuck with us through the transition.
The HashedMax Team
*Right now we have only the USA endpoint setup. EU will be added very soon.
Hey everyone, we’re working on a new mining related platform and are looking for a select group of beta testers.
We’re especially interested in people who currently have or manage different types of mining hardware and are familiar with pointing miners to different pools/stratum URLs.
Ideal beta testers:
This is not a token launch, not an investment thing, and not a trading bot. It is a mining utility/platform we’ve been building for some time to solve a real problem we’ve seen in the mining space.
We’re not opening it publicly yet, but we’d like a select group of miners to test the first version, give feedback, and help us shape the platform before launch.
There is no pay or compensation for testing. Your duty will be to test the platform, report problems, recommend changes, updates and more. You will be given direct access to a new platform that we have been working on but confidentiality at this point is a must.
We are looking for serious feedback, not hype.
We expect the test to run only 3 days max once we hit our minimum threshold of testers.
If you are interested, please fill out the form here:
https://pools.hmpool.io/beta.html
We expect to start inviting participants very soon. If you are invited you will receive an email from us, so please be sure to check your spam folder as well as your inbox.
Hey everyone, we’re working on a new mining related platform and are looking for a select group of beta testers.
We’re especially interested in people who currently have or manage different types of mining hardware and are familiar with pointing miners to different pools/stratum URLs.
Ideal beta testers:
This is not a token launch, not an investment thing, and not a trading bot. It is a mining utility/platform we’ve been building for some time to solve a real problem we’ve seen in the mining space.
We’re not opening it publicly yet, but we’d like a select group of miners to test the first version, give feedback, and help us shape the platform before launch.
There is no pay or compensation for testing. Your duty will be to test the platform, report problems, recommend changes, updates and more. You will be given direct access to a new platform that we have been working on but confidentiality at this point is a must.
We are looking for serious feedback, not hype.
If you are interested, please fill out the form here:
https://pools.hmpool.io/beta.html
We expect to start inviting participants very soon. If you are invited you will receive an email from us, so please be sure to check your spam folder as well as your inbox.
We just sent all loyalty rewards to our DGB miners.
Paid 1,246.41833772 DGB to 348 miners (3.58166189 DGB each)
TXID: 24b27d7c2feb09746eebd68b79dff7182baebbca1e9b0ffc2a147f0c1ba9a2cd, b8cf7b6bd1852cec6bcfe4b7f1765b6e2c708ff4affcf3cfc1d86396c9db5696
This was sent in 2 transactions.
We still have one miner with a bad DGB address that was not paid.
DGb1ntPQ.....yhdeJhzvg
The b in DGB should be an uppercase. We cannot change this or I would. So miners, please check your addresses
The BC2 block we hit over a week ago finally confirmed and all payments were made to 19 miners. See the chart below for the complete payment information. While it's not a BTC block, it is something...great job to the block finder! Lets try to get more miners on board at multi.hmpool.io
We just made payment to the loyalty rewards for Digibyte.
Loyalty payment sent to 309 miners.
1250.00 DGB.
TXID: e582e3e3be782908c22e5b218509330e71b262e622ac01a2382660c608841de7
Also, the DGB weekly rewards winner verified his wallet and he was sent 1250 DGB as well.
One of the biggest pieces of feedback we've received since launching the HashedMax Multi Pool was that getting wallet addresses, especially for Namecoin, which was more difficult than it should be.
To make onboarding easier, we've added browser-based wallet generators for all three Multi Pool payout coins:
🔹 BC2 (Bitcoin 2)
🔹 XEC (eCash)
🔹 NMC (Namecoin)
The generators create a new wallet, recovery phrase, and payout address directly in your browser, making it much easier to get started mining.
Security First
Your recovery phrase and private keys are generated locally on your device and are never uploaded to or stored on our servers. We cannot see them, so please do not ask us to help you recover your wallet. It simply CANNOT BE DONE!!!
HashedMax cannot see, recover, or access your wallet.
Because these wallets are non-custodial, it is critical that you write down your recovery phrase and store it somewhere safe. If you lose it, nobody, including us can recover your funds.
Each generator also includes a "Destroy Session" option that clears the wallet information from the page when you're finished.
We've also added direct wallet generator links throughout the Multi Pool site and miner dashboard to simplify setup for new miners.
If you've been waiting to try the Multi Pool because wallet setup was confusing, now is a great time to jump in.
**IMPORTANT** - There are instructions on each of the wallet generation pages. Please read through them thoroughly. It explains wallet recovery, checking balances and more.
As always, we'd love your feedback and suggestions as we continue improving the platform.
https://multi.hmpool.io/generate-nmc-wallet.html
https://multi.hmpool.io/generate-xec-wallet.html
https://multi.hmpool.io/generate-bc2-wallet.html
Happy mining!
So far our new multi pool (multi.hmpool.io) is doing well. No issues reported and a 1.1ph hash rate. So lets get some more miners pointed at this and solve that first BC2 block!
Good Sunday Everyone!!! We are performing a little house cleaning this morning so if stats are a bit slow to load or you get no stats, not to worry. We are pruning our database as with the increase in miners, this means more stored shares. In fact at last glance we had over 100m shares stored, which isnt necessary as we will now keep a log of all shares stored to minimize table size. This will not effect mining, payouts or block finds and will only take roughly an hour.
Remember, this is for DGB only at this time. It's currently 9:05am.
Thanks
There is a miner on our DGB pool (digi.hmpool.io) that is using an ESP32 / Nerdminer device that has an invalid address and is potentially missing out on payments.
DGBUxq1VWMcg........mfphrEGLGRF9gH
This is the address in question. It is truncated for privacy but please check your addresses.
Thank you
Hello fellow Digi miners, we have sent this weeks loyalty payment.
281 miners paid 1245.57 DGB.
TXID: 9bedd268172540893fcce0eea7128668095a27858980765157b7c5a6a940d2cc
Please note, one miner did NOT get paid due to an invalid DGB address. Please be sure to check your addresses on the digi pool.
The invalid address is here:
DGBUxq1VWM........wBmfphrEGLGRF9gH
Truncated for privacy. DM us if this is you and you must send the correct address. It also must be this exact address, but in the correct format.
Thank you again for another successful week!
A short explanation on what we think caused these orphaned blocks.
We rely heavily on what they call peers. Peers are just other nodes that we share info with. We found that one of our top low latency peers that had been working well went down. Since mining pools depend on fast peer communication, this may have reduced our node’s ability to see and share blocks quickly. We have updated the peer setup so the pool can maintain healthier outbound and inbound network connections. This will help reduce orphan risk.
Outbound peers keep our node connected to the current network, while inbound peers help spread our blocks to other nodes. If a peer goes offline or becomes stale, this causes our node to have fewer healthy paths to the network, which can slow block propagation or cause us to see blocks late.
But, with that said, the amount of workers that have joined our Digibyte pool climbed by 81 overnight and we've seen a positive growth in miners and workers now for the last couple of weeks. Even though many of these workers are low hashrate miners, they take up resources. We are planning another server upgrade that will involve moving our database server to it's own dedicated server across all 3 pools, which will eliminate a huge load on the straturm servers. We will of course keep you updated on when we plan to do this and if it will involve any downtime (but we should be able to do it without taking anything offline).
Thanks
Hey everyone,
We wanted to get some honest feedback from the community about the future of our HashedMax BTC pool.
As most of you know, we currently run dedicated pools for BTC, BCH, and DigiByte. Our DGB pool is absolutely crushing it, finding blocks regularly, and BCH is sitting at a very realistic difficulty for a smaller independent pool.
BTC, however, is a different animal right now.
The Bitcoin network is sitting around 136.6T difficulty, with a global network hashrate close to 980 EH/s. At smaller independent pool hashrates, the statistical odds of finding a raw BTC block are incredibly low.
To put the math in perspective, an estimated average BTC block time looks like this:
Mining is variance-based, so a block could happen tomorrow, or it could happen a decade from now. But statistically, standard BTC mining has become very difficult for a smaller independent pool to make exciting and consistent for home miners.
HashedMax is entirely self-funded, and our goal is to build pools that are actually useful and rewarding for the independent miner, not just a place to park hashrate and wait years for a lottery ticket.
We are considering a few options for the SHA-256 stratum, and we want your vote:
If we build the Multi-Pool, how do you want your payouts?
We are not making a final decision until we hear from the community. Would a multi-pool with more frequent blocks be more useful to your rigs? Drop your votes and opinions (Options A/B/C and Payout 1/2) in the comments below.
Thanks for the continued support.
The HashedMax Team
We’ve added a new FairShare Loyalty status indicator to the Miner Dashboard on all 3 HashedMax pools.
When you look up your address on miner.html, you will now see a “FairShare Loyalty” card that shows:
Important notes:
This update is live on DGB, BCH and BTC, and the indicator is designed to make it much clearer where you currently stand and what you need to do to maintain eligibility for our loyalty program.
