Topic: Will I know if one of my miners ever finds a block? (Read 397 times)

But at least you are willing to LEARN! Thass the most important part

Thank you both for the replies - unfortunately this is too advanced for me to understand at this stage. My brain is spinning!

if you rented bad hash and point it at solo pool. you the renter gets fucked.

the solo pool does not get fucked.


if you rented bad hash and point it at a small pool
 the pool owner  and all
 the pool miners including you get fucked.

Bad rental is very high number of Invalids (stales, dupes) caused by high latency, excessive number of very low diff returned shares (what happened to Kano.is) which is ntentional block witholding. Maybe not a problem for solo miners or pointing at a very large pool but it can be the Kiss of Death when pointed at small pools.

As Mikey gracefully pointed out he (Kano) runs the most stable and arguably best constructed pool on the planet and things like his KDB  backend which stores/verifies every single share sent out/received since the pool opened allowing for in-depth analytics are why.

nicehash is a rental of hash company.

I can go to nice hash right now and rent about 100 to 200 ph. and point it to any pool.

more to come.


Here comes the next part

Pretend I am an evil doer I can write a custom firmware that discards any share over

20t

so your share of 22 t would vanish and not hit a block

but shares from 17.5 to 21.9 t. would hit a Block


Why would I do this?

more to come.

I don't like {any smaller pool you want}

So how can I fuck them?
But not lose money?

Program 50ph with shit firmware designed to discard block wins

Point it at nicehash as a seller of hash.

So 1/4 to 1/2 of the hash at nicehash could be 'bad'

meanwhile I get paid as a hash seller no loss.
nicehash gets paid as a broker of it.

the guy that rents it gets fucked if he pointed it at a solo pool. as it will miss blocks.
the other smaller pools get fucked if 25 or 30% of the hash is bad hash.

they get bad luck.

there is a good chance this did happen to

 kano.is pool
BTC Guild pool ------- out of business
Bitminter pool -------- out of business

What exactly is 'bad rental hash'?

The only folks he 'treats like shit' are those who are either: a) those who insist their erroneous concept of what a miner does and how mining works is correct and then refuse to learn when he corrects them, b) the 3rd party firmware folks (aside from the Braiins team) and C) the hash rental folks who don't get why he banned them in early 2019. Oh, and D) -ck but he started it

I've mined at Kanopool since late 2014 and have found him to be a fountain of knowledge, the Discord channel a great meeting place. In short, if you are technically savvy you'll be happy interacting with him/us as long as you can budget for Variance. Then again, I've been a power electronics systems design engineer for well over 40 years so I'm rather used to dealing with other folks that know what they are talking about (can you say often arrogant?) and having to educate those who are perhaps not clueless but nonetheless very wrong.

Oh, why we dropped from over 250PH to where we are now was in part due to the rental hash kerfuffle - bad rental hash pushed us to a couple VERY long blocks - like a series of over 300% ones i a row - and those pushed Management of a couple very large miners to move to PPS. It was Kano's KDB back end that stores every single share sent which allowed him to find what the problem was (bad rentals) but in the 2 months it took to become suspicious and then rerun the data the damage was done and the decline was on a roll.

     I am trialling Asic.to on 2 x old T17+ but from the results so far, I'll likely revert them back to Bitmain standard firmware. They are reporting around 67 TH/s in the miner GUI, but according to F2Pool, over a 24h period the worker hashrates are actually lower than when the units were running standard Bitmain firmware. These are T17+ 58 TH/s units, on standard firmware they get around 59-60 TH/s according to my pool app, but now they are reporting 57-58. So either the firmware lies about the hashrate, or the dev fee is massive.

I'm aware custom firmware isn't allowed on Kano.is, so if I do switch to this pool I won't point any custom firmware units there (or will have reverted back to standard firmware).

He will also carry the most risk among other miners, just with like everything else in life, the greater the risk the greater the rewards, with merely 20PH a bit of bad luck can be tragic, of course a bit of good luck will be over overwhelming, the downside for PPS is that you never get paid for more than 100% of luck, you can't be lucky, it's less fun to mine on PPS but if you treat mining as a business and you have other financial obligations mining on PPS or extremely large PPLNS is the only way to go.

Also if I am not mistaken danieleither has some gears running custom firmware, so he won't be able to mine on Kano regadless of his hashrate. No?



One reason is Kano's attitude, a few members around the forum (including myself) can easily make his pool 2-3 times larger in no time, but he treats people like shit and most people don't want to support his pool, this of course doesn't negate the fact that his pool is probably one of the most stable and perfectly constructed mining pools, so if you have no problem with his attitude you should certainly consider his pool.

If I had 25ph I would do differently then I do with 1.7ph

Also my 1.7 ph is not all my hash I manage it for 4 people.

 Myself
buysolar
warehouse owner
his son.

I simply can not point it all to solockpool or kano.is. as

pointed at solo I would hit 1 block in about 684 days with standard luck
pointed at kano.is about 30 days to hit for 10% of a block

I can not afford to wait 684 days for a solo block
I could last 30 days for a kano.is block but if there is a 300% block and 90 days it is 3 power bills due.


Most of the gear points to viabtc. they have promotions and some shit coins so the take out is about 2% not 4%
I can live with the certainty.

Also I earn more then 0.01 coins a day. about 0.012325 btc a day. and I get paid out every day my risk of pool theft is a known. 0.012325 would be my loss as I would move my gear if viabtc failed to pay me.

A small pool say kano.is I would earn about .6 btc in a block and take about a month.

So it is possible to lose .6 btc if the pool fails at the wrong point.

ie

do I risk 0.012325 btc with a pool failure
do I risk 0.600000 btc with a pool failure

My power deal is good enough that pool failure or gear failure is the only way I can lose out.

 Thus I try to reduce both of those risks.

Because if you take a look here: https://bitcointalksearch.org/topic/m.54538744

At least in my opinion it's more then just simple variance now. In a perfect world you will make more with Kano then you will with VIA.

But it's not a perfect world, and some people can't wait for a block. Others don't want to risk loosing BTC because the last 2 blocks mined on a PPLNS pool were low fee but the FPPS were better paid (and more frequent) blocks.

My small farm is pointed at a PPS, if I had more hash and did not need the BTC I would be at a PPLNS.

As always YMMV based on what you need.

-Dave

Hmm, I do like a gamble to be fair - and by the end of July I will be at 7.1PH (if my S19 Pro's arrive on time), so I could add significant power to the pool. It's clear though, from the stats, that support for the pool is significantly diminishing, there must be a reason for this?

 

Actually, the current sustained average hash rate is just over 11PH and every week or so can almost hit 20 for a few days when Canaan is burning in miners (Kanopool is one of 2 pools Canaan uses for batch testing) but yes, we are finding a block about every month or so.
I'm #5 or 6 in the pool stats running 480TH and our last block in June earned me 0.22032233 BTC. Keep in mind that if your contribution can increase the pools hash rate by 50% then you would also be getting a MUCH larger % of each block reward...

The plus side to putting 5ph on kano's pool is if kano rips 3 blocks fast.
The down side to putting 5ph on kenos pool is if kano rips 3 blocks slow.

Variance is the term.

If you are going to be king of a pool it can be very good to you if the pool has a hot streak.

I was looking into Kano Pool, I like the idea of the 0.9% fee but as I understand it, payout is only when the pool finds a block - and since the pool is operating at under 10PH total, payouts could be very sporadic. If I joined this pool I'd be increasing the pool hashrate by 50%! Unless I've totally misunderstood the figures on their website...?

OR, just use a pool with multiple nodes spread around the world such as kano.is has and use the different addresses for the 3 pools.
Kanopool nodes:
stratum+tcp://stratum.kano.is:3333
stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
stratum+tcp://nl.kano.is:3333 (Netherlands)
stratum+tcp://sg.kano.is:3333 (Singapore)

Each node also supports different ports if needed. If 1 node goes down it does not affect the others and your mining seamlessly continues. AFAIK, Kanopool has never had an outage on Kano's master server that the nodes link up to and that would be the only thing that could adversely affect its users.

     Yes, I agree - Even with my limited knowledge this advice didn't make sense to me and I never followed it.
     If you refer to the 'instructions' or settings examples on most pool websites, they recommend to set pool 1 and pool 2 as I have (same pool but different port settings) so I was simply following those instructions.

     My thinking here was that if my primary pool went down, ALL my miners would switch over to viaBTC. At the current difficulty it would take around 38 minutes of mining to reach the 0.001 payout threshold, however when I first setup the miners this would have been much lower.

 

You could set your miners up this way.

1.6 ph on favorite pool. f2pool in your case

0.4 ph on second favorite pool viabtc in your case.


pretend you have 20 100th miners.


16 set like this

1)f2pool
2)viabtc
3)solockpool

4 set like this

1)viabtc
2)f2pool
3)solockpool


you are offered protection if either pool crashes
you are offered less loss if either pool runs away or has its coins stolen
you have a small outside shot at a block on ckpool if first 2 pools crash
since you have enough gear running at viabtc pool it will collect every day

I used 1.6 ph and .4 ph as the example

but even
0.8ph-- f2pool
0.2ph-- viabtc

works.

I won't claim that I know better than whoever told you so, but use your common sense, when F2pool goes down for maintenance or DDOS attack or whatever reason, how will a different worker name make any difference when the whole pool is down? using the same pool on a different port as a back-up pool hardly makes sense, let alone using only a different user name.


The minimum payout on Viabtc is 0.001, S17+ makes 0.000554 BTC a day as of today's difficulty, which means you need to mine for a total of 1.8 days or 43 hours on Viabtc in order to get to the minimum payout, based on your connectivity and F2pool stability it's almost impossible to get a total of 43 hours of mining on the back-up pool, it would take you years of mining, things will be better if you have more miners, but with difficulty rising you might not be able to withdrawal from Viabtc ever, so if you don't have another gear that uses viabtc as a primary pool, a solo pool as back up will be your best shot, it also helps with mining decentralization oneway or the other.


Well done, I doubt there is an easier way to find the block, and for privacy reasons, one shouldn't be sharing the block number/share because that may expose some details about them, I now know the F2pool username for member danieleither  , so if he wants to keep that private, he should change it.

You miner found this block:

https://explorer.viawallet.com/btc/block/638655?page=1

If you look at the difficulty of the block it matches the number you are showing as the best share.

I'm sure there is an easier way to find it, I went though 2 block explorers. Started with btc.com and filtered by f2pool. The just show the 1st 4 digits of the difficulity xx.yy. Then the via explorer to confirm because on the detail page it gives the exact value.

-Dave