Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PMP / Mining4people profitability comparison problems #2657

Open
realsetvin opened this issue Jan 31, 2024 · 12 comments
Open

PMP / Mining4people profitability comparison problems #2657

realsetvin opened this issue Jan 31, 2024 · 12 comments
Assignees

Comments

@realsetvin
Copy link

Something is off with the way profitability is calculated on these two pools (maybe more). Please take the coin "YERBAS" (YERB) for example. If you configure your machine to include both mining4people and pmpmining with mining directed to a yerbas address - you will notice that the profitability levels are way off.

PMPmining seems to over reported by a factor exceeding 90%. That is to say, PMP is being seen as much more profitable than any other pool by a margin of several times.

Even when PMP is adjusted to a 90% penalty, rainbowminer will not switch to mining4people at all. It seems that mining4people is being under reported (I do not see a way to give it a "negative" penalty)

Looking at miningpoolstaats at the time of this writing I see that mining4people and pmpmining have relatively equal hashrates for coin yerbas. The expected behavior is that rainbowminer should gently switched between both pools. What is happening is that rainbowminer is just staying directly on pmpmining without ever hitting the other yerbas pools I add. I even have pool switch hyst to 1 the lowest level.

Please investigate this when you have a moment

SIDE NOTE: Some pools will wipe your balance if you have not mined on their pool for several months. It would be nice if rainbowminer could mine to each pool for at least one short cycle every 24 - 48 hours.

@RainbowMiner RainbowMiner self-assigned this Jan 31, 2024
@whitindllc
Copy link

i setup this coin for shits and giggles and i think i see the issue..... the ttf and last found are off and thats why it always defaults to that one... plus it has a higher pool hashrate

image

@realsetvin
Copy link
Author

That was a great catch, thank you!

Do you know why pmpmining is reporting 10x profits compared to all other pools?

@whitindllc
Copy link

i dont know... i need to add the coin to see....

M4P is claiming that they are finding a new block every negative 471 mins.... and its TTF is infinite... However MPS reports each is finding a block every 5 mins or so with them both reporting finding 31.... one has 10 miners the other 7... but the one with 7 has the higher hash rate...

image

@realsetvin
Copy link
Author

I have tagged someone from mining4people maybe its an error in their reporting.

@totom9000
Copy link

Will take a look on this. Im bawls from Mining4People

@furcalor
Copy link

furcalor commented Feb 2, 2024

i dont know... i need to add the coin to see....

M4P is claiming that they are finding a new block every negative 471 mins.... and its TTF is infinite... However MPS reports each is finding a block every 5 mins or so with them both reporting finding 31.... one has 10 miners the other 7... but the one with 7 has the higher hash rate...

Could you show where we report as finding block every negative 471 mins.... and its TTF is infinite. Seems to me there is some issue with rainbow miner logic over an issue on our end.

here's and example of the api report on yerb:
{"coin":"YERB","id":"yerbas-pplns","algorithm":"Ghostrider","name":"Yerbas","hashrate":103231,"poolHashrate":103231,"networkHashrate":159085,"networkBlocktime":118,"miners":9,"workers":31,"fee":1,"feeType":"PPLNSBF","minPay":1,"blockHeight":445782,"blockReward":100,"lastNetworkBlockTime":null}

RainbowMiner added a commit that referenced this issue Feb 2, 2024
- fix typo (issue #2657)
- just to be sure, convert datetimes to universal time before calculation
@RainbowMiner
Copy link
Owner

@whitindllc is your rig's time setting correct? I have now added an automatic compensation in case your rig's datetime is off.

RainbowMiner referenced this issue Feb 2, 2024
- compensate for time difference of rig vs. pool (issue #2658)
@RainbowMiner
Copy link
Owner

Regarding that PMPmining - YERB got it's quote from minerstat:
image

.. and that is off by a lot. Looking at Xeggex, we have 0.000501 USD for 1 YERB.

I have lowered the requirements for rbminer.net's xeggex API, so that we get the quotes for YERB (and a hand full other low volume coins) from that exchange. The problem should now resolve pretty soon.

@whitindllc
Copy link

@whitindllc is your rig's time setting correct? I have now added an automatic compensation in case your rig's datetime is off.

its the same time as my smart watch and smart phone and my other smart phone to the second.. its not part of a windoze domain so its not relying on a domain controller to tell it what time it thinks it is

@whitindllc
Copy link

@whitindllc is your rig's time setting correct? I have now added an automatic compensation in case your rig's datetime is off.

however i pulled this out of a pc thats on a domain

WARNING: This rig's system time is off by 230 seconds. Please adjust and restart RainbowMiner!

@realsetvin
Copy link
Author

Regarding that PMPmining - YERB got it's quote from minerstat: image

.. and that is off by a lot. Looking at Xeggex, we have 0.000501 USD for 1 YERB.

I have lowered the requirements for rbminer.net's xeggex API, so that we get the quotes for YERB (and a hand full other low volume coins) from that exchange. The problem should now resolve pretty soon.

That's great! Did you ever get a chance to look at yerbas on mining4people? Still showing negative TTF

@totom9000
Copy link

totom9000 commented Feb 12, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants