https://bitcointalksearch.org/topic/bitcoin-group-mining-let-us-burn-a-block-10-phs-reloaded-14-5246506
Make sure to join b4 its too late
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 246. (Read 102489 times)
Only 0,03 btc missing for our last solorun with 10 PH/s for 24h before the big halving :~)
https://bitcointalksearch.org/topic/bitcoin-group-mining-let-us-burn-a-block-10-phs-reloaded-14-5246506
Make sure to join b4 its too late
https://bitcointalksearch.org/topic/bitcoin-group-mining-let-us-burn-a-block-10-phs-reloaded-14-5246506
Make sure to join b4 its too late
Quote
Hi Snowy,
I have similar hasrates to you. Are you using the standard difficulty port (3333) or using the higher difficulty port? I seem to be smashing in a heap of shares at around 13.4k difficulty. Not that it's a huge problem, just looking at the impact on bandwidth.
I have similar hasrates to you. Are you using the standard difficulty port (3333) or using the higher difficulty port? I seem to be smashing in a heap of shares at around 13.4k difficulty. Not that it's a huge problem, just looking at the impact on bandwidth.
Hi, yes i'm using the regular 3333 port, which quite stable for my machine.
Going to spare another shot for 24 hours before headed back to regular mining
Wish you all good luck.
ITs getting ridiculously hard to find blocks on our low power
"hashrate1m": "535T",
"hashrate5m": "471T",
"hashrate1hr": "391T",
"hashrate1d": "381T",
"hashrate7d": "388T",
"lastshare": 1588910429,
"workers": 2,
"shares": 811787948908,
"bestshare": 1828478123299.129,
"bestever": 1828478123299,
"worker": [
i saw that and though hell yeah 18 Trillion- THATS A BLOCK
but noooooooooo its only 1.8 Trillion
"hashrate1m": "535T",
"hashrate5m": "471T",
"hashrate1hr": "391T",
"hashrate1d": "381T",
"hashrate7d": "388T",
"lastshare": 1588910429,
"workers": 2,
"shares": 811787948908,
"bestshare": 1828478123299.129,
"bestever": 1828478123299,
"worker": [
i saw that and though hell yeah 18 Trillion- THATS A BLOCK
but noooooooooo its only 1.8 Trillion
Seems getting really hard to solve one, but who knows
"hashrate1m": "17.4T",
"hashrate5m": "14.2T",
"hashrate1hr": "14.2T",
"hashrate1d": "11.7T",
"hashrate7d": "3.09T",
"lastshare": 1588900119,
"workers": 1,
"shares": 490163101,
"bestshare": 1680719429.274467,
"bestever": 1680719429
Good luck to all.
"hashrate1m": "17.4T",
"hashrate5m": "14.2T",
"hashrate1hr": "14.2T",
"hashrate1d": "11.7T",
"hashrate7d": "3.09T",
"lastshare": 1588900119,
"workers": 1,
"shares": 490163101,
"bestshare": 1680719429.274467,
"bestever": 1680719429
Good luck to all.
Hi Snowy,
I have similar hasrates to you. Are you using the standard difficulty port (3333) or using the higher difficulty port? I seem to be smashing in a heap of shares at around 13.4k difficulty. Not that it's a huge problem, just looking at the impact on bandwidth.
Seems getting really hard to solve one, but who knows
"hashrate1m": "17.4T",
"hashrate5m": "14.2T",
"hashrate1hr": "14.2T",
"hashrate1d": "11.7T",
"hashrate7d": "3.09T",
"lastshare": 1588900119,
"workers": 1,
"shares": 490163101,
"bestshare": 1680719429.274467,
"bestever": 1680719429
Good luck to all.
"hashrate1m": "17.4T",
"hashrate5m": "14.2T",
"hashrate1hr": "14.2T",
"hashrate1d": "11.7T",
"hashrate7d": "3.09T",
"lastshare": 1588900119,
"workers": 1,
"shares": 490163101,
"bestshare": 1680719429.274467,
"bestever": 1680719429
Good luck to all.
{"diff": 101.0, "accepted": 16323311050006,} over expected now
Come on Bitcoin give me a break lol
"shares": 51398044379,
"bestshare": 309430998061.3869,
"bestever": 309430998061,
Come on Bitcoin give me a break lol
"shares": 51398044379,
"bestshare": 309430998061.3869,
"bestever": 309430998061,
we start our last Mining Rental before the halving --> https://bitcointalksearch.org/topic/bitcoin-group-mining-let-us-burn-a-block-10-phs-reloaded-14-5246506
You can join the last train to hit a block with 12.5 BTC
You can join the last train to hit a block with 12.5 BTC
http://solo.ckpool.org/users/13SmFktu83HwAvgWMeuhuVv6PdJRqADXNv
hashrate5m": "9.09T",
"hashrate1hr": "1.1T",
"hashrate1d": "47.6G",
"hashrate7d": "6.82G",
"lastshare": 1588837962,
"workers": 1,
"shares": 970000,
"bestshare": 1840249.429837954,
"bestever": 1840249,
"worker": [
you submitted shares
hashrate5m": "9.09T",
"hashrate1hr": "1.1T",
"hashrate1d": "47.6G",
"hashrate7d": "6.82G",
"lastshare": 1588837962,
"workers": 1,
"shares": 970000,
"bestshare": 1840249.429837954,
"bestever": 1840249,
"worker": [
you submitted shares
I have literally the exact same URL sitting in my browser now and coming up as 404 Not found. Click on the link in your post and it works fine. -ck checked and saw no shares from my device either. Must have taken a while to filter through or something?
In any case, thanks for proving that I was indeed doing productive work!
http://solo.ckpool.org/users/13SmFktu83HwAvgWMeuhuVv6PdJRqADXNv
hashrate5m": "9.09T",
"hashrate1hr": "1.1T",
"hashrate1d": "47.6G",
"hashrate7d": "6.82G",
"lastshare": 1588837962,
"workers": 1,
"shares": 970000,
"bestshare": 1840249.429837954,
"bestever": 1840249,
"worker": [
you submitted shares
hashrate5m": "9.09T",
"hashrate1hr": "1.1T",
"hashrate1d": "47.6G",
"hashrate7d": "6.82G",
"lastshare": 1588837962,
"workers": 1,
"shares": 970000,
"bestshare": 1840249.429837954,
"bestever": 1840249,
"worker": [
you submitted shares
Ok. Here's the screenshot of the miner status page:
https://ibb.co/BG6Dzf8
Here's the screenshot of the solo.ckpool URL I entered to check my connection that gave me the 404 Not Found result.
https://ibb.co/txLpsWJ
If there's nothing helpful here, I'll point the miner back to solo.ckpool tonight and see if I have a result. If not, I'll grab the kernel log and upload it.
Hope these help.
https://ibb.co/BG6Dzf8
Here's the screenshot of the solo.ckpool URL I entered to check my connection that gave me the 404 Not Found result.
https://ibb.co/txLpsWJ
If there's nothing helpful here, I'll point the miner back to solo.ckpool tonight and see if I have a result. If not, I'll grab the kernel log and upload it.
Hope these help.
You should have put a screenshot since the beginning and we can prob troubleshoot it for you there. until then not much else can
be done here
be done here
FWIW, I entered the nicehash configurations in exactly the same way and haven't had any issues.
[EDIT] just clarifying the point about the BTC address and the entry to the URL. Think I misunderstood what you meant about typing the address in.
[EDIT] just clarifying the point about the BTC address and the entry to the URL. Think I misunderstood what you meant about typing the address in.
did you type in the address as
Code:
stratum+tcp://solo.ckpool.org:3333
or did you leave out the first bit? maybe that could be causing a problemAlso with the name you gave your miner did you include a . and no space in the naming? like mine, see i have the address then a . and its named S9 worker 1 (and yeah i pulled a few digits out of the address)
Code:
1PBchjo22ED1kyi5vRaiEcpCKn.S9w1
and the address to check your miner
Code:
http://solo.ckpool.org/users/Your Wallet Address
Hi,
I copied and pasted it straight from the site, the miner added the stratum+tcp:// prefix itself. If this wasn't there, I believe there would have been no connection to the pool and hence no shares accepted.
I didn't give the miner a name as it wasn't necessary. I only have one so didn't need to track individual stats/serviceability. I have a name for it on nicehash as I have other miners there and want that definition in the data.
Yep, that's the address I used. Still have the tab open on the laptop (as well as a miner status page for those interested) so can screenshot if you'd like. Don't have a kernel log though and won't until I can get access to the miner later this evening.
Thanks for the suggestions though!
FWIW, I entered the nicehash configurations in exactly the same way and haven't had any issues.
[EDIT] just clarifying the point about the BTC address and the entry to the URL. Think I misunderstood what you meant about typing the address in.
[EDIT] just clarifying the point about the BTC address and the entry to the URL. Think I misunderstood what you meant about typing the address in.
did you type in the address as
Code:
stratum+tcp://solo.ckpool.org:3333
or did you leave out the first bit? maybe that could be causing a problemAlso with the name you gave your miner did you include a . and no space in the naming? like mine, see i have the address then a . and its named S9 worker 1 (and yeah i pulled a few digits out of the address)
Code:
1PBchjo22ED1kyi5vRaiEcpCKn.S9w1
and the address to check your miner
Code:
http://solo.ckpool.org/users/Your Wallet Address
I'm going to be moving old user entries for clean up reasons as there are currently over 27,000 users there. Any from last year or before will be moved to solo.ckpool.org/users/old/ and still available manually but won't be accessible via the web interface.
The one he posted was definitely a vaild bitcoin address. If he input it wrong into his miner, then solo would have just rejected him entirely.
We don't know if he is actually typing that address without any spaces, or a space in the url itself, or maybe using a wrong password, anyone who seeks support must at least provide
1- A screenshot of the miner status page.
2- A screenshot of the pool settings (you can hide a few digits in the middle).
3- Kernel log.
Without these 3 and without a magic ball, I don't think it's possible to help anyone troubleshoot their miners, some people are too lazy to post these things and all they say is that "my miner isn't showing on the pool" well, good luck.
Ease up turbo, I'm new to this and haven't had to ask for help on here before. Apologies for the lack of information.
I did have a random space in the URL itself which reported the pool Dead on the mining status page. Once I found it, the pool reported alive and the hashing started. After that, I checked for spaces in the address field and found none. The pool site says no password is required. If any of these were wrong, surely the pool would have rejected me straight away. Other people on here have tried to check my BTC address to see if any hashes had been reported by the pool and they haven't seen any either. I don't believe there is an issue with typing the address in to the URL or the box on the pool site.
I understand what you're saying about the kernel log but having verified the pool address and a valid connection on the mining status page, I don't understand why the pool wasn't seeing the miner. I'll try tonight and get those pieces of information if I still have no luck.
FWIW, I entered the nicehash configurations in exactly the same way and haven't had any issues.
[EDIT] just clarifying the point about the BTC address and the entry to the URL. Think I misunderstood what you meant about typing the address in.
The one he posted was definitely a vaild bitcoin address. If he input it wrong into his miner, then solo would have just rejected him entirely.
We don't know if he is actually typing that address without any spaces, or a space in the url itself, or maybe using a wrong password, anyone who seeks support must at least provide
1- A screenshot of the miner status page.
2- A screenshot of the pool settings (you can hide a few digits in the middle).
3- Kernel log.
Without these 3 and without a magic ball, I don't think it's possible to help anyone troubleshoot their miners, some people are too lazy to post these things and all they say is that "my miner isn't showing on the pool" well, good luck.
The one he posted was definitely a vaild bitcoin address. If he input it wrong into his miner, then solo would have just rejected him entirely.
I verified the address creation and validity with a block explorer. It's definitely there and all good. I'm just not sure why it wasn't reporting on the stats page. I tried for 5 hours and got nowhere, hence reverting back to nicehash.
The status page showed everything looked good for solo.ckpool and so did the configuration page so I don't believe it was hacked.
Make sure your btc address is correct as well.
The one he posted was definitely a vaild bitcoin address. If he input it wrong into his miner, then solo would have just rejected him entirely. you can post the url that you were using?
I have seen people mine to the ckpool instead of the cksolo pool.
Hi JimJam,
I'm just using the URL and port off the website: solo.ckpool.org:3333
Punched my BTC address in to the little search box and got a 404 Not Found result. copied and pasted it straight from the miners status page.
Antminer S9 SE is the miner I'm using. It was reporting huge numbers of shares accepted so I'm guessing I had a good conneciton, but I was hoping to see it on the solo.ckpool site for confirmation.
There's no hashrate recorded to his username there either as far as I can see.
Thanks for checking in there -ck. Any ideas why that might be the case?
That's entirely possible. I'll have to look in to checking those permissions.
It had only been online for 48 hours (in total - to any pool) so someone must have been pretty quick off the mark to hack it. When pointed to Nicehash, it reports just fine and is earning what I'd expect it to. This is where it's pointed now to verify what I configured was accurate. I should add, it's Dec 19 batch.
I'll try to have another go tonight and see if I can't get it working on the solo.ckpool site.
Make sure your btc address is correct as well.
you can post the url that you were using?
I have seen people mine to the ckpool instead of the cksolo pool.
Hi JimJam,
I'm just using the URL and port off the website: solo.ckpool.org:3333
Punched my BTC address in to the little search box and got a 404 Not Found result. copied and pasted it straight from the miners status page.
Antminer S9 SE is the miner I'm using. It was reporting huge numbers of shares accepted so I'm guessing I had a good conneciton, but I was hoping to see it on the solo.ckpool site for confirmation.
There's no hashrate recorded to his username there either as far as I can see.
Thanks for checking in there -ck. Any ideas why that might be the case?
That's entirely possible. I'll have to look in to checking those permissions.
It had only been online for 48 hours (in total - to any pool) so someone must have been pretty quick off the mark to hack it. When pointed to Nicehash, it reports just fine and is earning what I'd expect it to. This is where it's pointed now to verify what I configured was accurate. I should add, it's Dec 19 batch but running Nov 2018 firmware at the moment.
I'll try to have another go tonight and see if I can't get it working on the solo.ckpool site.
[EDITs] - add batch date and FW version.
Jump to: