I jumped from BTC.com pool to here just to try. I see that my configuration is corrrect as I am seeing that my hashing rate is consistent to what my miner is capable.
But how do you know how much bitcoin are you getting? I mean, yes there is a mark where it will payout, but is there any other way to see whether you are near to payout or not.
Thank you.
If you click on the pool work link http://ckpool.org/pool/pool.work you will see who's scheduled to receive a reward on the next block find under "payouts". If you're in the "postponed" list that means you haven't contributed enough hashrate yet to receive a payout and will be postponed. As you contribute hashrate you can move up into the payout list if a block hasn't yet been found if your hashrate is significant enough. That work page is created dynamically every minute and changes continuously and is an estimate of payout should a block be found this instant. |
|
|
|
http://ckpool.org/pool/pool.status#gives me json error in chrome (probably because I installed JSONView chrome app): Error: Parse error on line 1:
..."Disconnected": 12}{"hashrate1m": "1.33
----------------------^
Expecting 'EOF', '}', ',', ']'a missing comma? The user stats are valid json. The pool status page is there for your perusal and are dumps of multiple lines of json so don't try to parse them directly unless you feed it in as multiple lines. The pool work page can be parsed though. |
|
|
|
FWIW early termination has been used by miners since at least 2010.
Ha not surprised. Any sources I can look at? Minerd and the earlier versions of cgminer had CPU mining which had this optimisation pretty much from the beginning. You can also see the same optimisation in the openCL code used in GPU versions of cgminer. The current version of cgminer doesn't contain any CPU or GPU code any more to prevent people doing futile attempts at mining bitcoin with it. |
|
|
|
Seems like your AUC3 is broke. Alternatively it could be the dodgy usb ports on the pi. Try attaching a decent USB hub to run it off instead.
I agree it does seem that way. I tried a couple of different AUC3's but same result. I'd like to try your suggestion with the USB hub. Would you set it up this way?: Avalon controller (pi 3) -> USB hub -> AUC3 converter -> miner Yes that's the only way you can plug it in anyway. |
|
|
|
I have the same question open in a Mining help thread here but thought I'd ask you guys who are most knowledgable with cgminer. Running cgminer 4.10.0 on a Raspberry Pi 3, which is connected to an Avalon AUC3, which is connected to an Avalon 741 ASIC miner. When I start cgminer, I get the following response: root@OpenWrt:/lib/modules/4.4.14# cgminer -o us-east.stratum.slushpool.com:3333 -O userid.shop100:x -D --verbose
[2016-12-14 02:10:04.665] Started cgminer 4.10.0
[2016-12-14 02:10:04.665] RES: thread starting
[2016-12-14 02:10:04.665] USB scan devices: checking for AV7 devices
[2016-12-14 02:10:04.832] AV7 looking for AV7 29f1:33f2 but found 0424:ec00 instead
[2016-12-14 02:10:04.832] AV7 looking for AV7 29f1:33f2 but found 0424:9514 instead
[2016-12-14 02:10:04.832] AV7 looking for AV7 29f1:33f2 but found 1d6b:0002 instead
[2016-12-14 02:10:04.832] No devices detected!
[2016-12-14 02:10:04.832] Waiting for USB hotplug devices or press q to quit
[2016-12-14 02:10:04.832] Probing for an alive pool
[2016-12-14 02:10:04.832] Testing pool stratum+tcp://us-east.stratum.slushpool.com:3333
[2016-12-14 02:10:04.921] Succeeded delayed connect
[2016-12-14 02:10:05.219] Pool 0 stratum session id: 1
[2016-12-14 02:10:05.220] Pool 0 difficulty changed to 2048
[2016-12-14 02:10:05.221] Pool 0 coinbase 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4503f27307fabe6d6d14260e5f1745bbbfd4edaa7f0a102fcfb8ac5ece9a3399e6c37e8f6586741cb80100000000000000036501004fb5f2000000003245072f736c7573682f00000000022b8c185
[2016-12-14 02:10:05.326] Stratum authorisation success for pool 0
[2016-12-14 02:10:05.326] Pool 0 stratum+tcp://us-east.stratum.slushpool.com:3333 alive
[2016-12-14 02:10:05.832] Unable to set thread to low priority
[2016-12-14 02:10:05.832] Unable to set thread to high priority
[2016-12-14 02:10:05.832] Testing pool stratum+tcp://us-east.stratum.slushpool.com:3333
[2016-12-14 02:10:05.833] Unable to set thread to low priority
[2016-12-14 02:10:05.833] Work update message received
[2016-12-14 02:10:05.833] Unable to set thread to low priority Assuming the plugged in hardware is functioning correctly, what could be causing these messages: [2016-12-14 02:10:04.832] No devices detected!
[2016-12-14 02:10:04.832] Waiting for USB hotplug devices or press q to quit Are there downloadable USB drivers for the Raspberry Pi 3? Anyone else ever have this issue and successfully resolve it? Thanks Direct USB needs no drivers. Seems like your AUC3 is broke. Alternatively it could be the dodgy usb ports on the pi. Try attaching a decent USB hub to run it off instead. |
|
|
|
|
The blockchain doesn't compress very well so I'd advise against trying to compress the directory. The easiest thing to do is prune your blockchain which gives you a fixed size blockchain of only the latest blocks that fit into the size you specify. The smallest you can set it to is 550MB. You won't be contributing to the network as much since you will no longer be able to seed new nodes, but it depends on what you want to run your own node for. If it's only for your own security and wallet then you won't lose anything by pruning it. Set prune= in your bitcoin.conf to the size you want.
|
|
|
|
Couple ways to do it:
1) Use the cgminer API on the S9. You can build something that calls the API and retrieves the stats. If this fails, its down.
2) Use the pool stats for your worker. Again, build something to occasionally poll the pool stats, and if your worker is down, take some action.
OK, yes I think 2) is probably pretty easy to implement. However I noticed I can't check individual works like: ckpool.org/users/*user*.0 ckpool.org/users/*user*.1 etc So am I right in thinking I won't be able to monitor individual workers this way? Or I would have to put each worker as a separate username / address? All the individual workers are listed within the user stats. The stats are all in valid JSON format so you need to use a JSON parser to get what you want and extract per worker information. |
|
|
|
When a block is found by this pool, instead of you waiting for me to process the payouts and you get a payment, you will get the reward immediately with the block solve as a "mined" entry in your wallet. Your wallet will say it's immature and you won't be able to use the reward for 100 confirmations but basically you get newly generated coins. |
|
|
|
HEY -ck,
Why wont my s-9 connect through ckproxy? i set up same as my s-7's and s-4+, but i put s-9's and they will never connect>?
what am i missing?
I'm not aware of anything stopping the S9s connecting. I know people with thousands of S9s connected via ckproxy. |
|
|
|
|
There's no such thing.
Locking thread since it's nonsense. Do some reading before posting.
|
|
|
|
Just got through the full thread, WOW! Tons of work into this.
I just got a USB stick running to play with mining, and while pointed at the ckpool the CG miner has popped up with "2017-09-27 18:04:01] Stratum from pool 0 detected new block"
As that obviously was not a solve, what does the new block detected refer to? Apologies if this is the wrong forum to ask in.
New bitcoin network block. They happen every 10 minutes on average. We want one for ourselves. |
|
|
|
|
DOWNTIME NOTIFICATION FOR DE.CKPOOL.ORG
My hosting provider for the de pool has notified me they have urgent repairs for the network switch at the datacentre which may affect the DE pool and they expect up to 20 minutes of downtime.
The works will run during the following times:
Start: September 28, 2017 5:00:00 AM CEST
End: September 28, 2017 7:00:00 AM CEST (expected)
The main pool will be unaffected during this time so please use it as your primary backup and as always make sure you have a further backup.
|
|
|
|
|
Due to fluctuations in reported hashrate, I would be basing it on the total shares submitted by each miner to the pooled effort which will be the most accurate measure of overall hashrate as it may be difficult to extract the exact hashrate of each worker at exactly the time a block is found.
|
|
|
|
|
You may link to this thread in the solo pool thread if you like as well.
|
|
|
|
|
To be clear, everyone would use the same username bitcoin address that I provide them and use a different workername for me associate them with your account, and the btc addresses associated with each workername I would have to know before the round began. Should a block be found, I would distribute the funds based on the relative hashrate of each worker at the time a block was found. Please coordinate amongst yourselves and finalise how many miners you are before considering beginning. If your hashrate is small (<100TH) despite there being many people, I will not be offering this service for the inconvenience and low likelihood of finding a block makes it not worthwhile.
|
|
|
|
It is a lottery the only thing that matters is your total hashrate so the more hashrate you have the more chance you have.
I don't have much hashrate here but was thinking we could make some kind of "syndicate" sort of we know that the only thing that matters is total hashrate so if a few people were to throw power at the pool in a collective that would add higher chance?
Is that theroy correct ck?
Yes that's correct and this has been done successfully (and unsuccessfully) in the past. It is entirely up to you to coordinate people and payouts between you though since the reward only goes to one address. If you wish to use me as escrow to send out payments to multiple people I would do so for a 1% extra fee if I get all the addresses and proportions to give out in advance. |
|
|
|
|
Show Posts
