@macbook-air
Do you mean that you'll intentionally not build on blocks from Kano.is? I think you need to clarify what you mean by blacklist.
Do you mean that you'll intentionally not build on blocks from Kano.is? I think you need to clarify what you mean by blacklist.
We will not build on his blocks until our local bitcoind got received and verified them in full. This guy leaked our IP addresses to the public, I pm him kindly and begged him to remove them but he refused. If we ever got DDoSed due to his post, we have no choices but point our domains to his pool.
I have reasonable DDoS protection.
Funny you consider that your only option - clearly you have no idea how to deal with network problems
As stated above, they were the IP addresses of miners mining on my pool but withholding doing any work and using my pool to help SPV mine.
I obviously do not want miners doing that on my pool.
No one asked, (I would have denied it), thus the results.
Interesting that you consider them important, you use these IPs to SPV "dead pool mine" on competitors pools with important IP address?!? ...
You also said to me in PM, after I worked out what was going on, that it is to "reduce my orphan rates" and thus to my advantage to let you SPV dead pool mine on my pool ... ... ... ...
Edit: and said that I don't care about my customers who mine on my pool getting more orphans because it wont cost me since my pool isn't PPS ... ... ...
Clearly we have a different idea about the term "advantage" and what is good for Bitcoin.
While we are at it, I will also point out fake excuses spread by SPV mining pools:
One of the excuses given was because it is often slow to distribute blocks through the GFW, so they are at a disadvantage.
In a peer 2 peer network, if you divide the network with a line, the side of the line with clearly less power is at a disadvantage.
With the GFW, the side of the line inside the GFW has the higher network hash rate ... ... ...