Good day! To put all my cards on the table so that ya’ll know I am visually disabloed and have to work at a much slower pase than those with good eyes. input data, check, recheck, recheck , then next step. rinse and repat.
I am having what i think is an issue – I have followed the manual, acouple of You tubers on how to setup the KS0 PRO, multiple time each. I have entered the pool indo from 3 different pools (kaspa.org, humpool, and unmineable. I have entered the only wallet i have from KASPA. password “x”
I have mined for a total of 36+ hours, at least 12 on each pool. I the KS0 Pro dasboard it shows all normal, hashrate (200gh/s), connected, and positive number for received/acepted, no rejections. When cross refferencing info with the pool - no worker is found in any of the 3. Bothing nor any transaction in the wallet.
I am sure that there might be a small error somewhere. I am just having a brain lock atm. any ideas for me to check that i may not be thinking of?
Also anyone know how often payouts to wallets may be for the 3 different pools are? Anyone US side that may be willing to assist quickly with a phone call? Thanks for any imput that is provided.
In your address to your mining pool . Did you put your acct name with the associated pool? Many pools use format like the following example: accountname.minername@stratum+tcp://Poolinfo:
If you didn’t put your account name with the pool info. The pool will show connected but the pool wont pay out because they don’t know who (where) to payout to. (EDIT) In other words they don’t know which account owns the miner attached to their pool. You won’t be showing workers either in this case
Figured here is a good starting point, easily overlooked when setting up.
I dont think that unmineable requires before the pool address. I didnt see ( no pun intended) an account sifn up for the kaspa pool nor the humpool. I’ll check
Sent you a direct message
(EDIT-ADD) I’m stumped, If anyone else has Ideas. @Blind3y3 is looking to connect with unminable as a pool service. We verified proper set up on his KSO for his for the pool addressing (a second opinion would be nice). He is using the 4445 TCP address. Hasn’t set up the 14445 SSL backup. I myself am not sure if that is required for unminable, I would think its not. His Iceriver interface is showing that his pool is connected. When he is looking at the unminable pool he is seeing 0 hashrate and 0 workers. He’s been on that pool for 10+ hours. Unminable has a threshhold of 50 KAS for payout he won’t hit that for a few days of mining.
If you are connecting to unminable, you would normally do that because you want to mine KAS on the device but get paid in something else.
You can get the info you need through their config maker.
Lets say you want to use the KS0 to mine KAS but get paid in BTC. You would need:
Pool addr: kheavyhash.unmineable.com:4445
Wallet/Worker: BTC:YourBTCaddress.WorkerName
Password - x. doesn’t matter.
You need to have the BTC: in front of your addresss and you need to have a worker name.
If you are wanting to paid in something else, you would need a different prefix on the wallett address.
So if you want to mine KAS and get paid in KAS, you need the same KAS pool kheavyhash.unmineable.com:4445
And you need to add KAS: in front of the KAS wallet address, and you have to have a worker name.
You can also put in a referral code to get a fees discount. I use #SEB, but Hobbyist has one also. I don’t know if Vosk does or not. Just find one and add it to the end of the Wallet/Worker line