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

Kryptex Mining Pool #2574

Open
sfalas01 opened this issue Dec 14, 2023 · 14 comments
Open

Kryptex Mining Pool #2574

sfalas01 opened this issue Dec 14, 2023 · 14 comments
Assignees
Labels
implemented an enhancement has been implemented pool issue

Comments

@sfalas01
Copy link
Contributor

Hello,

Could you please consider adding Kryptex mining pools? It even has a referral link you can incorporate into this.

Thanks!

@RainbowMiner RainbowMiner self-assigned this Dec 14, 2023
RainbowMiner added a commit that referenced this issue Dec 15, 2023
RainbowMiner added a commit that referenced this issue Dec 15, 2023
- important fix, I forgot the duration (issue #2574)
@RainbowMiner RainbowMiner added the implemented an enhancement has been implemented label Dec 15, 2023
RainbowMiner added a commit that referenced this issue Dec 17, 2023
- add parameter "Email" to pools.config.txt (issue #2574)
@RainbowMiner
Copy link
Owner

Parameter Email has been added to pools.config.txt for Kryptex. Put your Krypted registered eMail into that field to activate all coins.

@coolbreeze21
Copy link

coolbreeze21 commented Dec 18, 2023

Kryptex looked like an interesting autoexchange pool with no KYC to supplement zergpool, so I signed up for an account. After entering the email address I used in pools.config.txt and checking the Kryptex box in Setup, RBM started benchmarking with ERG using TREX.

However, the console showed it wasn’t mining anything. The error messages were: “failed to stratum-authorize on erg.kryptex.network:7777” and “Invalid login”. It looks to me like the RBM command string for Trex wasn’t passing the email address to Kryptex. Kryptex says that the wallet format for using it in this manner should be [your@email.com/WORKER_NAME], but no email address appeared in the RBM command string. The next miner RBM tried, Teamblack for ETHW had the same issue – the wallet parameter had “/WORKER_Name” but no email address.

There seems to be an issue with RBM passing the Kryptex email address to the miners.

Kryptex's instructions for mining to an account email address are here: https://pool.kryptex.com/en/articles/account-mining-en

@sfalas01
Copy link
Contributor Author

Kryptex looked like an interesting autoexchange pool with no KYC to supplement zergpool, so I signed up for an account. After entering the email address I used in pools.config.txt and checking the Kryptex box in Setup, RBM started benchmarking with ERG using TREX.

However, the console showed it wasn’t mining anything. The error messages were: “failed to stratum-authorize on erg.kryptex.network:7777” and “Invalid login”. It looks to me like the RBM command string for Trex wasn’t passing the email address to Kryptex. Kryptex says that the wallet format for using it in this manner should be [your@email.com/WORKER_NAME], but no email address appeared in the RBM command string. The next miner RBM tried, Teamblack for ETHW had the same issue – the wallet parameter had “/WORKER_Name” but no email address.

There seems to be an issue with RBM passing the Kryptex email address to the miners.

Kryptex's instructions for mining to an account email address are here: https://pool.kryptex.com/en/articles/account-mining-en

Is this fixed yet? Have you found any workaround?

@coolbreeze21
Copy link

It is not yet fixed as far as I know. I would think it requires an update and there has been none since 4.9.1.0, which has the issue. I don't want to attempt a workaround, only to have to reverse it when this gets fixed in RBM.

It is possible that RainbowMiner missed the issue report in a thread he had marked "implemented". I have found him very responsive in the past. If there is no response after a week, or the next release, I will repost the issue in a separate thread. Or you can do so now, if you want to nudge him sooner.

@sfalas01
Copy link
Contributor Author

sfalas01 commented Dec 22, 2023

It is not yet fixed as far as I know. I would think it requires an update and there has been none since 4.9.1.0, which has the issue. I don't want to attempt a workaround, only to have to reverse it when this gets fixed in RBM.

It is possible that RainbowMiner missed the issue report in a thread he had marked "implemented". I have found him very responsive in the past. If there is no response after a week, or the next release, I will repost the issue in a separate thread. Or you can do so now, if you want to nudge him sooner.

I am working on a fix myself but the pull requests usually don't get implemented fast enough. I get it, it's different to review code rather than do it yourself. If found and fixed some bugs in the pool.config but there's a problem with how miners interpret the username. Since some of them include the username with the pool address, the @ symbol in the email get's interpreted as the pool address and tries to connect to your email domain instead of the pool address. I will test some more miners on the pool and see. Xmrig works fine as of now.

Edit (will update fully later on)

What doesn't work:

  • MiniZ (GPU)
  • Nanominer (CPU & GPU)
  • Phoenix (GPU)
  • lolminer (kHeavyHash, HeavyHashPyron)
  • Rigel (Dual-Mining)
  • BzMiner (Ethash-based algos)

@Robbylikes
Copy link

disable nanominer reboot re-run tests for other algos.

@sfalas01
Copy link
Contributor Author

sfalas01 commented Dec 28, 2023

@RainbowMiner @coolbreeze21
I have submitted #2591 which contains a workaround for the Kryptex email issue if you want to test it out. As I stated in my earlier comment:

What doesn't work:

  • MiniZ (GPU)
  • Nanominer (CPU & GPU)
  • Phoenix (GPU)
  • lolminer (kHeavyHash)
  • Rigel (Dual-Mining)
  • BzMiner (Ethash-based algos)

It seems that the reason for this is that the @ symbol is interpreted as an end of line or another separator symbol, which breaks a lot of miners and how they treat the syntax of their parameter strings so there's not much you can do about it.

@RainbowMiner
Copy link
Owner

Thank you very much! I will look into it.

@RainbowMiner
Copy link
Owner

We might try to convert @ to %40 in the miner command line.

@sfalas01
Copy link
Contributor Author

We might try to convert @ to %40 in the miner command line.

Yes, that might work!

RainbowMiner added a commit that referenced this issue Dec 31, 2023
- try to fix "@" in user/wallet breaking commandline (issue #2574)
@RainbowMiner
Copy link
Owner

Not all algorithms are valid for account-mining on Kryptex. I have added commit 6ec65cb to filter out account-mining for non-valid algorithms.

@sfalas01
Copy link
Contributor Author

sfalas01 commented Feb 3, 2024

Not all algorithms are valid for account-mining on Kryptex. I have added commit 6ec65cb to filter out account-mining for non-valid algorithms.

Kryptex added pyrin and karlsen to the autoexchange feature.

RainbowMiner added a commit that referenced this issue Feb 4, 2024
- add KLS and PYI as mineable top account (issue #2574)
@RainbowMiner
Copy link
Owner

Thank you! I have updated the pool.

@Boulder08
Copy link

There's something going wrong at least with MiniZ, noticed this while benchmarking after changing OC profiles.

[ERROR  ]  (kaspa)
[ERROR  ] Pool:kas.kryptex.network - worker not authorized: xxxx%40gmail.com/xxxxx
[ 0d 0h 4m30s] S:  0/0/0 0.0( 0.0)H/s  18( 18.7)W [kas.kryptex.network]- 24ms
 0>RTX 3070       100% [40 C/ 0%]    0.00(  0.00)H/s  18( 18.7)W clk=1050MHz mclk=810MHz H/W=0.000

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
implemented an enhancement has been implemented pool issue
Projects
None yet
Development

No branches or pull requests

5 participants