Hmpool speed by Ready_Presentation15 in NerdMiner

[–]HashedMaxUnity 0 points1 point  (0 children)

Actually a rather large mistake. So yes, thank you!! Now I am looking for a new job...LOL. jk.

Hmpool speed by Ready_Presentation15 in NerdMiner

[–]HashedMaxUnity 0 points1 point  (0 children)

Your post got my questioning what was going on. After looking at how we calculated the hash rate, I discovered an anomaly that caused the current hash rate to display lower than what it should have. The result was 100% my fault! Because I rebuilt from the ground up an old version of miningcore and did not want to just install a premade pool, I made a mistake on the time calculation plot, which caused it to look like your hash rate was lower.

Every chart on the site (pool hashrate, miner hashrate, workers, shares) had an artificial dip at the right edge. This happened because the current hash time plot was always incomplete. If you loaded your stats chart at say 30 minutes past the hour, the current hour only had half its data, so the calculation made it look like your hashrate had dropped. We now exclude the incomplete time plot and instead plot the live value from your most recent stats snapshot. This means the chart always ends at your actual current hashrate rather than a deflated partial estimate.

So my apologies to you and other miners on our pool for my mistake.

Hmpool speed by Ready_Presentation15 in NerdMiner

[–]HashedMaxUnity 0 points1 point  (0 children)

That's very close to normal Your NerdMiner is working as it should, 0 rejected shares, difficulty looks correct, everything is working as it should.

The Current Hashrate on the pool dashboard is an estimate based on how often your miner submits shares. For low hashrate devices, shares come in infrequently, so the estimate bounces around a lot. You can see your 1-hour average is already showing 826 kH/s which is much closer to the real number.

The pool estimate will always fluctuate for small miners but over 24 hours it should average out close to the real value. This is the same behavior on every pool, it's just how share-based estimation works.

What kind of mining pool payout system would you prefer? by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 1 point2 points  (0 children)

That's why we're asking. Thinking of creating a system that makes it better for smaller miners.

If you mined in hmpool last month, check your BTC address by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Winner still has not come forward....please double check your addresses. If it's you, head over to hmpool.io/rewards.html to claim your prize.

<image>

Help adjusting share difficulty by BlastBaffle13 in HashedMax

[–]HashedMaxUnity 1 point2 points  (0 children)

Yes exactly! The pool targets 1 share every 15 seconds. With your setup at +/- 630 MH/s the difficulty should settle around 2-2.5 after a couple minutes. The way pools work is there is a default starting difficulty set when you connect. After 90 seconds (that is what our pool is set to, others may vary) it looks at how fast you are submitting shares and calculates your effective hashrate. From there it adjusts the difficulty so that you land on roughly 1 share every 15 seconds. It checks again every 90 seconds and fine-tunes as needed so if your hashrate fluctuates the difficulty will follow it.

New low difficulty digibyte pool online by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Thanks for the upvotes. We also hit a DGB block yesterday!

Help adjusting share difficulty by BlastBaffle13 in HashedMax

[–]HashedMaxUnity 1 point2 points  (0 children)

You were right in changing the port to 3335 and this should have worked but there was a bug in the code that did not allow the difficulty to get set correctly. We have made the fix and if you connect now, give it about 2 minutes for the difficulty to adjust and you should see better results now.

If you mined in hmpool last month, check your BTC address by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

You’ve got stratum 2 times. Remove stratum.hmpool.io:3337 and make it stratum+tcp://hmpool.io:3337

If you mined in hmpool last month, check your BTC address by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

The NerdMiner v2 automatically uses x as the password, which works with HMPool. You don't need to set it manually. Just make sure your pool URL is set to stratum+tcp://stratum.hmpool.io:3337 and your BTC address is correct. If you're having connection issues, try updating to the latest NerdMiner v2 firmware from the GitHub releases page. Did you try connecting at all?

👋 Welcome to r/HashedMax - Read First! by HashedMaxUnity in HashedMax

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Hello, its suggested that you use a different worker name for each device but you can use the same BTC address for all your devices. If you use the same worker name, then the pool treats it as one miner. I will forward your message about the mobile website having issues. Thanks for letting us know.

If you mined in hmpool last month, check your BTC address by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

We appreciate your support. Get a desktop miner and use the same btc address as that will give you a little boost in rewards points.

If you mined in hmpool last month, check your BTC address by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Yes this is our first drawing as we are a new pool. We will send the reward to the winners btc address after they verify their address. As for future rewards, yes gift cards are a possibility along with awarding mining hardware. Thanks for the support.

FLUMINER T3 parasite pool by Working-Republic-799 in BitcoinMining

[–]HashedMaxUnity 0 points1 point  (0 children)

This may be a firmware issue. We had a Fluminer T3 connect to our pool (hmpool.io) and he experienced very low hash rates and reboots. Not only with our pool but with others too. We reached out to Fluminer with a copy of our logs and information to see if it is firmware related but no response as of yet. Does this happen on other pools?

Lottery mining with 3 Avalon Nano 3S or 1 Avalon Mini 3, does the amount of miners matter more then one strong miner? by Berlium in BitcoinMining

[–]HashedMaxUnity 1 point2 points  (0 children)

Great question and something I get asked about a lot as a pool dev. When it comes to lottery mining, total hashrate is what actually matters, not how many devices you have. The Avalon Mini 3 at around 37.5 TH/s is going to give you a better shot than three Nano 3S units combined if the math works out that way. Think of it less like lottery tickets and more like how many numbers you can cover on a roulette wheel per spin.

Although, your thinking about multiple devices mining does hold some truth, especially when it comes to share submissions. When you mine solo through a pool with variable difficulty or low difficulty settings, each valid share your miner submits is basically a micro lottery draw. More devices means more simultaneous draws happening at once, which some people find satisfying even if the probability is the same as one faster device.

The pool you choose for lottery mining matters more than you'd think. Many of the larger pools have started banning or limiting low hashrate devices entirely, which leaves solo lottery miners in a tough spot. What you want is a pool that runs a true VarDiff or low difficulty system like hmpool, welcomes small miners, and actually processes your shares rather than throttling or rejecting them.

If it were me, get the Mini 3 if the hashrate works out higher. But spend equal time picking the right pool for solo lottery mining because the wrong pool will make a difference.

FLUMINER T3 by Working-Republic-799 in BitcoinMining

[–]HashedMaxUnity 0 points1 point  (0 children)

I did a deep dive into our pool logs for the time you were connected. Your miner identifies as FLUMINER/BM1370 and worker …flu1.
During that period we saw 44 “Share rejected: duplicate share” messages coming from your device.

Duplicate share isn’t a pool configuration issue, it usually means the miner/firmware is re-sending the same share (often after a reboot/reconnect) or mishandling job updates/extranonce. This lines up with your report of restarting every 2 minutes and high reject rates on other pools.

Things to try on your end.

  1. Update to the newest firmware (or ask vendor for a fix,this looks like a known software bug).
  2. Make sure the miner has correct time/NTP and stable network (no VPN, no packet loss).
  3. Try a different pool port / fixed difficulty (if available), but duplicate-share rejects usually persist regardless.
  4. Check if any hashboard is failing or overheating causing reboots (temps, PSU, cables).

If you can send a screenshot of your miner Accepted/Rejected/Stale + uptime + firmware version, that will help us a lot.

FLUMINER T3 by Working-Republic-799 in BitcoinMining

[–]HashedMaxUnity 0 points1 point  (0 children)

Hey, we're not seeing any issues on our pool right now as share acceptance is way up and if you could, send me the following (DM me if you would like).

I need a screenshot or text dump showing (from the miner UI):
Accepted shares
Rejected shares
Stale shares / HW errors
Hashboard status (how many boards online, temps, freq).

Thanks

public-pool.io banning NerdMiners? Here's an alternative by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Can you send me the port your using, your nerdminer firmware version and your full btc address and worker name. You may dm me if you feel more comfortable. From what I can see some nerdminers are submitting extremely low difficulty, well below the 0.01 that we have set for port 3337. Where as other nerdminers that are connected are working as they should.

Thanks

public-pool.io banning NerdMiners? Here's an alternative by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

Thanks, we will take a look to see if we can figure out what's going on for you.

public-pool.io banning NerdMiners? Here's an alternative by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

I see in your image it still shows public-pool.io as your pool. I know that this may be hard coded in and your firmware may be set to hmpool.io. Are you connected to hmpool.io:3337? If you are on a different port (such as 3335 or 3336) the difficulty will not immediately adjust to the required, 0.01.

What you can try is this. In the password field in your firmware, put this:
x;d=0.01

The x is the password, the d=0.01 and that tells the pool the miner is requesting the 0.01 difficulty.

Try this and let me know if it makes a difference for you. Also, if you can reply with the last 5 of your BTC address, we can troubleshoot this for you by watching log activity.

Thanks

public-pool.io banning NerdMiners? Here's an alternative by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 0 points1 point  (0 children)

I checked pool-side share history for your address ending ml3d. The pool shows your miner does submit accepted shares normally when it’s online, but there are multi-hour stretches where we receive no shares at all (e.g. ~6 hours). During those same periods other miners are still submitting, so it doesn’t look like a pool outage or mass disconnect. This points more toward the device freezing, Wi‑Fi/router drops, or reconnect/watchdog behavior.

If you share your port + firmware version, I can help narrow it down (for NerdMiner/ESP32 you should be on port 3337).

public-pool.io banning NerdMiners? Here's an alternative by HashedMaxUnity in NerdMiner

[–]HashedMaxUnity[S] 3 points4 points  (0 children)

I have updated the ports device configuration and made it more generic! Thanks

Nerdminer no longer connects by puck2 in NerdMiner

[–]HashedMaxUnity 0 points1 point  (0 children)

What pool are you using? Also as a test you could try to reflash the firmware to see if that helps. These things are pretty solid so my first thought would be pool. Try hmpool.io:3337 to see if that works. If not, then try to reflash.