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

The argument could be made quite easily that it is a waste of time regardless mining at that hash rate.

You can verify you are hashing at http://solo.ckpool.org/users/14cC6urXAXLMNaeCpQY5B8TFsgu2GkXUPM.

The argument could be made quite easily that it is a waste of time regardless mining at that hash rate.

You can verify you are hashing at http://solo.ckpool.org/users/14cC6urXAXLMNaeCpQY5B8TFsgu2GkXUPM.

I'm currently mining solo.ckpool.org:3333 with user 14cC6urXAXLMNaeCpQY5B8TFsgu2GkXUPM @166GH/s / 1d  But is it only waste of time if i can't confirm that i'm mining to my own address?

You can't do it with your hardware, you need software that can do it for you. If you build the latest cgminer from git you can use the --decode option (which needs bitcoind running as well as the first pool). Otherwise you have to extract the coinbase from stratum through some other means and feed it into bitcoind to decode the hex.

@-ck I have an s7 running;   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Thu Dec 3 16:07:54 CST 2015
Cgminer Version   4.8.0

is this possible to crack a block or do I need to update? Thank you much...

I'm beginner with solo mining and using blackarrow prospere x1 for this..
How i should config my device for "All you need to confirm you are mining to your own address is to examine the coinbase and template sent to you over stratum."  

Came home saw this on the miners screen FoundBlocks 1 - Got very excited!

Can't seem to see any payout though?

Also this is a old S3 which was even more of a surprise!

Start cgminer in debug mode and dump the output to a log. Adding the options: -D -P -T 2>log.txt
Cgminer gives a hex dump of all the stratum fields, you can examine the coinbase fields. The part of the coinbase that determines which wallet you are mining to doesn't change for the life of a stratum connection.

That shows a best share of less than 6.2 million; if you found a block, it wasn't a Bitcoin block (which has a diff of 711,697,198,173). An error in the Antminer firmware, maybe?

Came home saw this on the miners screen FoundBlocks 1 - Got very excited!

Can't seem to see any payout though?

Also this is a old S3 which was even more of a surprise!

I feel that if SegWit is activated, no matter the method, UASF BIP148 is success.

What I see happening is BIP148 user activated soft fork will be a miserable failure but it won't matter.

What I see happening is BIP148 user activated soft fork will be a miserable failure but it won't matter. By that stage most pools will be signalling segwit thanks to segwit2x. Segwit will get activated and then fees will remain low, blockstream will not commandeer the blockchain, lightning network will not centralise transactions, nothing bad will happen and everyone will wonder what the fuck all the fuss was about. There will be no need for antpool with Jihan at the helm to create an aggressive hard fork against UASF; that was always a bullshit powerplay "I want my lollipop back" from Jihan as a counterthreat to UASF which hasn't got anywhere near enough traction to be relevant anyway. So nothing will happen to diff, there will be no fork, there will be no change of PoW. Forget the talk of diff drop to 2014 levels; that's off the cards entirely. The confidence that consensus will instil in the market will be reflected by yet more BTC value increases... till the next phase. The fun part is now that most of the pools are agreeing on what to signal next, transaction fees have suddenly plummeted due to total transactions plummeting - which means it's almost certain that someone amongst the pool groups was the architect behind the transaction flood which made it look like there was a transaction block space crisis. There's no economic reason for the total number of transactions to crash the way they have over the last week with BTC value being so strong right now.

After that people will be left scratching their heads wondering if we even need a 2MB block size increase at this time, but because all the pools made such a fuss about it, we'll have our next debate, but the pools have already insisted they want a block size increase and signed the NYA. I'm not sure how core will respond at that stage because that will be the true test of whether the miners can effect a change in consensus - but despite all the anti-core rhetoric, core dev has always overwhelmingly said they would do a block size increase but with a much slower time frame than that proposed by segwit2x simply because the regression testing required to confirm a hard fork is safe is substantial. I predict we'll get a 2MB base blocksize increase as well, though how and when I can't tell at this stage.

By the way, the current segwit2x "signalling" is just a show of support in their coinbase signature and doesn't change the way anything operates. However what it is saying is that they will be actively signalling from mid-July for segwit.

What does this mean for current ASIC miners?