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

chore: always use p2p difficulty to mine even if we mine solo #215

Closed

Conversation

SWvheerden
Copy link
Contributor

Description

Currently when we mine solo, the miner gets the full tari difficulty. Although this is correct, it can cause the miner to check in less with p2pool. If we are synced with p2pool we should start mining on the p2pool blocks as soon as possible again. Not wait till we mine a tari block or the template changes. This should make very little difference on the mining power, but will cause the miner to check in with p2pool more frequently

@stringhandler
Copy link
Contributor

I don't know if this is necessary, xmrig is configured to check for a new template every second and xtrgpuminer every 10 seconds. I am not sure about the merge mining proxy though

@SWvheerden
Copy link
Contributor Author

Maybe, this is based on the miner, most miners will check frequently for template changes, but I know some of our miners use some complicated caching system. This is more preventative then reactive thou

@SWvheerden SWvheerden closed this Dec 11, 2024
@SWvheerden SWvheerden deleted the sw_alwayschangedifficultytoloweramount branch December 11, 2024 08:35
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

Successfully merging this pull request may close these issues.

2 participants