Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 304. (Read 1514786 times)

legendary
Activity: 1736
Merit: 1006
I thought a RpI2 could ru it with easy. No?

I was thinking of setting up a few at various locations .

It will, but the block chain size is getting to be the problem with running it on a Pi (it takes a 64GB SD card to run it now or it did).

Sooner or later, it's going to take a 128 GB SD to run, or a USB HD on the Pi. And I don't know how much lag time USB HD would have on a node.

same.

I even tried storing the blockchain on a USB HDD and it still wouldn't stay running.

People out thetre have a way to turn one into just a transaction verifying node (no --generate command I believe);

But that doesnt solve my problem of needing a fallback if CK goes/shuts down =)

nicehash has a solo pool that runs almost the same code..
https://solo.nicehash.com/

if you want a backup its something to consider.
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
I thought a RpI2 could ru it with easy. No?

I was thinking of setting up a few at various locations .

It will, but the block chain size is getting to be the problem with running it on a Pi (it takes a 64GB SD card to run it now or it did).

Sooner or later, it's going to take a 128 GB SD to run, or a USB HD on the Pi. And I don't know how much lag time USB HD would have on a node.

same.

I even tried storing the blockchain on a USB HDD and it still wouldn't stay running.

People out thetre have a way to turn one into just a transaction verifying node (no --generate command I believe);

But that doesnt solve my problem of needing a fallback if CK goes/shuts down =)
sr. member
Activity: 331
Merit: 250
I thought a RpI2 could ru it with easy. No?

I was thinking of setting up a few at various locations .

It will, but the block chain size is getting to be the problem with running it on a Pi (it takes a 64GB SD card to run it now or it did).

Sooner or later, it's going to take a 128 GB SD to run, or a USB HD on the Pi. And I don't know how much lag time USB HD would have on a node.
legendary
Activity: 1694
Merit: 1002
Go Big or Go Home.....
I thought a RpI2 could ru it with easy. No?

I was thinking of setting up a few at various locations .
legendary
Activity: 1274
Merit: 1000
If a RasPi could reliably run as a full node...   I would have been doing that at a remote site.

Before 21co took over bitnodes, bitnodes offered a stand-alone node with a SSD drive for storing the block chain.  When 21co took over, this became their "bitcoin computer", I think the SSD drive (and therefore full node capability) went away at that time.



(old address for device: http://getaddr.bitnodes.io/hardware/  now redirects to 21co bitcoin computer)
legendary
Activity: 1638
Merit: 1005
Someone out there has a best share that will make them wince. Current diff is 62253982449.76081848

Holy fudge, i'm gonna have to drink a beer for whoever came that close to solve a block ....
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
[2015-11-10 04:59:45] Pool 0 message: Block 382903 solved by 122ki3sRnLQVmVYQqNTuPxjudb4tMQUpcf @ solo.ckpool.org!
 [2015-11-10 04:59:46] Stratum from pool 0 detected new block
 

just saw it

Code:
[2015-11-10 12:59:40.552] Possible block solve diff 91744837102.841385 !
[2015-11-10 12:59:42.971] BLOCK ACCEPTED!
[2015-11-10 12:59:42.979] Solved and confirmed block 382903 by 122ki3sRnLQVmVYQqNTuPxjudb4tMQUpcf

https://www.blocktrail.com/BTC/block/00000000000000000bfbf9158b41c0a4a5153cdaa4e44a04810cd09ba4401111

There was also a near-miss by someone. Ckpool submits all possible block solves within 1% of the current diff in case of rounding errors:

Code:
[2015-11-10 16:03:28.794] Possible block solve diff 62238693717.853767 !
[2015-11-10 16:03:28.877] SUBMIT BLOCK RETURNED: high-hash
[2015-11-10 16:03:28.879] Submitted, but rejected block 382916

Someone out there has a best share that will make them wince. Current diff is 62253982449.76081848
sr. member
Activity: 359
Merit: 251
zOU
hero member
Activity: 728
Merit: 500
★ these are stars ★
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Grin Back from travel.

So many block's solved in the last 3 day's... 

Congrats to all the lucky solver.
legendary
Activity: 1722
Merit: 1000
Come on S3 solve me a block!
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
 [2015-11-10 04:59:45] Pool 0 message: Block 382903 solved by 122ki3sRnLQVmVYQqNTuPxjudb4tMQUpcf @ solo.ckpool.org!
 [2015-11-10 04:59:46] Stratum from pool 0 detected new block
 

just saw it
sr. member
Activity: 331
Merit: 250
Another block found.

Congrats!
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
Everyone is working on unique work on all pools - even changing just 1 bit in the work template gives completely different results to every miner. The difference on other pools is they are all trying to generate a block to the same generation address(es). With this pool, every unique bitcoin address has its own generation address as part of the block it's trying to solve. This "pool" is in a sense only pooled miners on one node, but each unique miner is mining their own unique coinbase generation transaction. The result is the same as true solo mining to your own bitcoind locally - however you are now trusting your hashrate to my node to handle your workload which means you have the element of trust involved in the pool operator (i.e. me) that you are truly working on what you think you are working on (though that happens with every pool) so it's not in the strictest sense true solo distributed mining. But you get the bonus of the ultra low latency high performance node at an extremely low fee for the service.
Exactly the answer I seek =)


I thought it would work this way.   I think it would be very convoluted if it worked the other way.

I am very happy to not have to run a bitcoinD service on my cellular connection.   The miners are fine.  barely much traffic.   But;  just running a node... man.  GB of data. =)  Yeah;  I mine from T-mobile!

You do provide a great service for that.  If a RasPi could reliably run as a full node...   I would have been doing that at a remote site.  but; so far;  I am happy with what I found here! (and over trying to get other stuff to work right 24/7)
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
CK;  am I correct in assuming that each user (bitcoin address mined to) is solving for a hash for a block with a transaction to themselves?

In another way of asking, if another guy is mining, does the block seed hash change because of his bitcoin address compared to mine?  or is the winning hash just the "stamp" or "seal"" and the pool server writes the transaction based on who the winning hash came from?

Are we truly "Solo" mining, or is it more "pooled"....

I have always been curious on this "mechanic" of solo pools.
Everyone is working on unique work on all pools - even changing just 1 bit in the work template gives completely different results to every miner. The difference on other pools is they are all trying to generate a block to the same generation address(es). With this pool, every unique bitcoin address has its own generation address as part of the block it's trying to solve. This "pool" is in a sense only pooled miners on one node, but each unique miner is mining their own unique coinbase generation transaction. The result is the same as true solo mining to your own bitcoind locally - however you are now trusting your hashrate to my node to handle your workload which means you have the element of trust involved in the pool operator (i.e. me) that you are truly working on what you think you are working on (though that happens with every pool) so it's not in the strictest sense true solo distributed mining. But you get the bonus of the ultra low latency high performance node at an extremely low fee for the service.
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
CK;  am I correct in assuming that each user (bitcoin address mined to) is solving for a hash for a block with a transaction to themselves?

In another way of asking, if another guy is mining, does the block seed hash change because of his bitcoin address compared to mine?  or is the winning hash just the "stamp" or "seal"" and the pool server writes the transaction based on who the winning hash came from?

Are we truly "Solo" mining, or is it more "pooled"....

I have always been curious on this "mechanic" of solo pools.
sr. member
Activity: 413
Merit: 250

You're welcome and good luck Smiley. Today I fired up a lone S5 (1.1TH) with a Corsair AX860 platinum psu to solo mine for the winter here in the UK to keep the chill off my office. No real chance of finding a block but the way I look at it is that its a £2 a day heater / lottery ticket Cheesy.

P.S. I changed the fan so its reasonably quiet, wouldn't get any work done with the stock fan all that would do is give me a headache.

good luck to you.
legendary
Activity: 1414
Merit: 1077
I rent miners sometimes form nicehash Web site. Which diff setting i must use good performance ckpool site solo mining?

none it auto adjusts.

I hit 2 blocks in 2 hours on nicehash pointed to solo here no diff needed.

Thanks.

So i only wrote x in Password area. I do not write d=1024 etc.

Just x is good for the password, the pool will automatically adjust the diff Smiley.

@philipma1957 @hedgy73

thank you very much for information. i will try solo mining 1 month about 100 TH/s.  

You're welcome and good luck Smiley. Today I fired up a lone S5 (1.1TH) with a Corsair AX860 platinum psu to solo mine for the winter here in the UK to keep the chill off my office. No real chance of finding a block but the way I look at it is that its a £2 a day heater / lottery ticket Cheesy.

P.S. I changed the fan so its reasonably quiet, wouldn't get any work done with the stock fan all that would do is give me a headache.
sr. member
Activity: 413
Merit: 250
I rent miners sometimes form nicehash Web site. Which diff setting i must use good performance ckpool site solo mining?

none it auto adjusts.

I hit 2 blocks in 2 hours on nicehash pointed to solo here no diff needed.

Thanks.

So i only wrote x in Password area. I do not write d=1024 etc.

Just x is good for the password, the pool will automatically adjust the diff Smiley.

@philipma1957 @hedgy73

thank you very much for information. i will try solo mining 1 month about 100 TH/s. 
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
While I agree that the mathematical probability of each event is independent, I also believe there is more going on than just pure random numbers.  If you are consistently getting low best share numbers over a period of time, it is logical to predict that it is unlikely to have a sudden best share of over 64 billion.

My best share climbed to about 30 billion just before solving the block.   I'm not saying its always like this, I just look for patterns, anything to help know when it is more likely to happen.

Just my opinion, and what works for me.   I'm interested to know what "system" if any, others use...
There is no system, it's a common flaw most people make with statistics - ignoring something called sample vs population.
Statistics has a whole analysis of exactly that - what sample size is required to give an expected accuracy of predicting the population.

If someone sees a small sample that has their desired result, most will incorrectly assume that effect to be more apparent than it is.

The simplest and most obvious example of the expected result is to look at the pools that have mined hundreds or thousands of blocks.
Look at their long term block finding 'luck' (ignore Eligius - their pool management and code suck)
If there was some magic way to get more blocks, no doubt some pools would be finding more blocks than expected.
Instead, of course, pools that have mined many blocks are averaging close to the expected 100% luck.
Jump to: