[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[-ck]

There is absolutely no way to extract a block from hashrate going to a pool and send it to another address.

Any block found can easily be redirected to another pool or instance of btc core with another address by altering the code in the miner itself. It's not poolside or pool dependent.

Now you're trolling. It's impossible as the author of both mining and pool software has attested to. The burden is on you to prove otherwise. If the hashrate is showing up at the pool, it is going to the pool. If you redirect it, it will no longer show up at the pool.

[hodedowe]

Now you're trolling. It's impossible as the author of both mining and pool software has attested to. The burden is on you to prove otherwise. If the hashrate is showing up at the pool, it is going to the pool. If you redirect it, it will no longer show up at the pool.

Not at all. The hashrate will still show at the pool since you're not pulling the entire hash from the pool, you're pulling one solved block. More like turning on a small tap in the ocean than diverting the entire ocean.

[Snowykingdom]

I want to believe.
But i can't, too hard to understand for me.

The easiest one according to my understanding is:
When a block solved and (if it really being) "redirected" to another address, I'm sure our address will be at the first place and we can find the trails from blockchain. And if it really happen, that's the time we can make a judge to the machine owner.

I still believe in ck's statement and i hope he's right.

If the hashrate is directed at one address it is impossible to redirect a found block to another address.

Cheers.

ps.
we have a growing hash rate
"hashrate1m": "5.39P"

[philipma1957]

Now you're trolling. It's impossible as the author of both mining and pool software has attested to. The burden is on you to prove otherwise. If the hashrate is showing up at the pool, it is going to the pool. If you redirect it, it will no longer show up at the pool.

Not at all. The hashrate will still show at the pool since you're not pulling the entire hash from the pool, you're pulling one solved block. More like turning on a small tap in the ocean than diverting the entire ocean.

if you can clearly demo this is possible  you will be able to really kill off all mining  other then solo mining.

and of course f2pool.

If you can do this just partner up with any large pool and siphon off a block or 2  a week.

If you say you can and never prove it oh well.  I have a bridge or two for sale myself.

[Mikestang]

Now you're trolling. It's impossible as the author of both mining and pool software has attested to. The burden is on you to prove otherwise. If the hashrate is showing up at the pool, it is going to the pool. If you redirect it, it will no longer show up at the pool.

Not at all. The hashrate will still show at the pool since you're not pulling the entire hash from the pool, you're pulling one solved block. More like turning on a small tap in the ocean than diverting the entire ocean.

You don't understand how pools work apparently.

[bitsolutions]

Not at all. The hashrate will still show at the pool since you're not pulling the entire hash from the pool, you're pulling one solved block. More like turning on a small tap in the ocean than diverting the entire ocean.

Shares are only valid if they are hashing for the pool, the stratum server validates this and it is not possible to fake. Since you can't predict ahead of time which hash will result in a block find the most you can do is withhold a block by not uploading that hash/share to the pool. It can't be redirected because it was generated off of the pools template, shares not generated from the pools template are invalid shares and will be rejected by the stratum server.

[kano]

Sigh, no idea why some people are confused about all this.
Must be bitcoin n00bs who didn't learn what a block header is.

When you hash work, the work ALREADY has the address to which it will be sent.
When you find a block with that work, it is set in stone already.
You CANNOT change the coinbase transaction of a block to go to another address, since if you did, it will NO LONGER hash to being a block.

The pool accepts all shares that match the work sent to the miner, so it knows all the hash rate the miner sent to the pool.
What a miner could do is under represent his hash rate by not sending back 'some' shares, maybe only send blocks, but that would just make the pool look better

When you find a block, you have to send it here to make it able to be sent out to the bitcoin network, since the pool knows the full transaction details of the block, required to submit the block to the bitcoin network.
It is possible to calculate the merkle tree, but you'd be stupid to not send a block to the pool, since the pool is extremely more likely to transmit that block around the bitcoin network faster than you would.
Withholding a solo block is pretty much insane, since no one but the miner and the fee to -ck would lose.
No one else on a solo pools would lose anything due to someone else withholding a block.

[anamichii]

Sigh, no idea why some people are confused about all this.
Must be bitcoin n00bs who didn't learn what a block header is.

When you hash work, the work ALREADY has the address to which it will be sent.
When you find a block with that work, it is set in stone already.
You CANNOT change the coinbase transaction of a block to go to another address, since if you did, it will NO LONGER hash to being a block.

The pool accepts all shares that match the work sent to the miner, so it knows all the hash rate the miner sent to the pool.
What a miner could do is under represent his hash rate by not sending back 'some' shares, maybe only blocks, but that would just make the pool look better

When you find a block, you have to send it here to make it able to be sent out to the bitcoin network, since the pool knows the full transaction details of the block, required to submit the block to the bitcoin network.
It is possible to calculate the merkle tree, but you'd be stupid to not send a block to the pool, since the pool is extremely more likely to transmit that block around the bitcoin network faster than you would.
Withholding a solo block is pretty much insane, since no one but the miner and the fee to -ck would lose.
No one else on a solo pools would lose anything due to someone else withholding a block.

iam purely agree with kano.

Any block found can easily be redirected to another pool or instance of btc core with another address by altering the code in the miner itself. It's not poolside or pool dependent.

yea so i can see that you can easily learn about satoshi's proposal again.

[hodedowe]

Sigh, no idea why some people are confused about all this.
Must be bitcoin n00bs who didn't learn what a block header is.

When you hash work, the work ALREADY has the address to which it will be sent.
When you find a block with that work, it is set in stone already.
You CANNOT change the coinbase transaction of a block to go to another address, since if you did, it will NO LONGER hash to being a block.

The pool accepts all shares that match the work sent to the miner, so it knows all the hash rate the miner sent to the pool.
What a miner could do is under represent his hash rate by not sending back 'some' shares, maybe only blocks, but that would just make the pool look better

When you find a block, you have to send it here to make it able to be sent out to the bitcoin network, since the pool knows the full transaction details of the block, required to submit the block to the bitcoin network.
It is possible to calculate the merkle tree, but you'd be stupid to not send a block to the pool, since the pool is extremely more likely to transmit that block around the bitcoin network faster than you would.
Withholding a solo block is pretty much insane, since no one but the miner and the fee to -ck would lose.
No one else on a solo pools would lose anything due to someone else withholding a block.

Right, however we're talking about rented hash pointed to a solo pool. Withholding or redirecting a block means the customer stays a customer, buying more and receiving nothing. Thus you're continually feeding yourself by renting out hash and providing hope but very seldom or never paying out with altered machines.

[kano]

No that's not all of what you said further above.
... and you can't redirect a block.

Anyway, I've already posted a thread about withholding ...
https://bitcointalk.org/index.php?topic=1002086.0

[hodedowe]

No that's not all of what you said further above.
... and you can't redirect a block.

Anyway, I've already posted a thread about withholding ...
https://bitcointalk.org/index.php?topic=1002086.0

I'll concede to the redirection argument as the identifying bits would destroy the hash, but the withholding stands. If I'm selling lottery tickets (rented hash) I want you to keep buying them, I don't want you to win and stop until I've more than paid for my expenses and shiatsu massage.

[-ck]

I've made it so that solo.ckpool.org is now IPV6 as well as IPV4 so if you have IPV6 compatible networking it will (usually) choose to route you through IPV6 in preference. The solo6.ckpool.org address still works but is not really necessary, however it forces IVP6 networking.

If you don't know what any of this means, don't worry, it won't affect you in any noticeable way.

[bmoscato]

Is there any way to set the minimum or maximum difficulty on the client side? Every time I start my U2, U3 or Compaq's, it takes almost 10 minutes before the diff comes down from 1000 to where I can start getting blocks?  This happens with both CG Miner and BFG Miner for me.

[os2sam]

Is there any way to set the minimum or maximum difficulty on the client side? Every time I start my U2, U3 or Compaq's, it takes almost 10 minutes before the diff comes down from 1000 to where I can start getting blocks?  This happens with both CG Miner and BFG Miner for me.

That isn't going to have any bearing on your finding a block.  The current difficulty is 59,335,351,234, which is way more than 1000.

But, if your using CGMiner you can use the suggest difficulty command line argument.  Again that will have no bearing on your finding a block.

[notoriot]

Lets see what 100TH for 12 hours will bring...wish me luck guys and dolls!

[philipma1957]

Lets see what 100TH for 12 hours will bring...wish me luck guys and dolls!

May the luck be with you!

[notoriot]

Lets see what 100TH for 12 hours will bring...wish me luck guys and dolls!

May the luck be with you!

Thanks 

[thedreamer]

I've been stuck at 4.6B for like a week now. LOL

[727miner]

I've been stuck at 4.6B for like a week now. LOL

About the same for my rentals - "bestshare": 4427928080.1550922. I think this pool is due for a few blocks soon! Good luck guys 

[kano]

Solo block.
https://blockchain.info/block/00000000000000000c31e4e5f86a07da26033cea7f6f1e3920fc8b6a70f7838e

17PWkQgtX4iqEGUCw5KPNhouPz8oTKNWhQ
Looks like about 1PH