Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1830. (Read 5352140 times)

full member
Activity: 196
Merit: 100
ckpoolmonitor.zachmonroe.com update:

Several people requested it and I think I have it all working now, if not, things will go bad and the internet might melt.  Wink

Go into your Account Settings and at the bottom there should be options for each of your Workers.

Let me know if you have any problems.


Does it matter what browser to use?  I'm using Chrome and in setting under individual workers, I only see save button but nothing to edit them.  I also can't see my rewards or hashrate.

username =  nhando1977


P.S Love this summary Chart in the home page!  It clearly showed that on January 10-12, whoever rented hash rate made good money and whoever rented on the 13/14 probably loss a tiny bit of money but if it's over a 3 or 5 days average then it's still profitable.    I did pretty well from the the 11-12.  

Date   Total Payout   Average Hashrate TH/s   Average BTC/TH/s/Day   3 Day Average   5 Day Average   7 Day Average   30 Day Average
2016-01-14   49.55000000   10,912   0.00488621   0.00593600   0.00785489   0.00885854   0.00600156
2016-01-13   50.15728638   9,811   0.00505941   0.00777307   0.00687765   0.00894420   0.00617562
2016-01-12   74.92146475   9,735   0.00786240   0.00977628   0.01041283   0.00822143   0.00600698
2016-01-11   99.51151015   9,739   0.01039742   0.00715548   0.00993752   0.00790855   0.00594311
2016-01-10   99.75424394   9,233   0.01106901   0.01126810   0.00785803   0.00726476   0.00620662
2016-01-09   -   8,705   0   0.00940705   0.00677868   0.00612100   0.00583765
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
If a rig owner wants to use these sites they have to use that sites version of your software. That's what I meant by being "available for scrutiny"

I have very limited software/programming experience, but I am currently enrolled in courses. I look forward to breaking down and understanding the workings of cgminer. Thanks for making it so easy to use.
There are 2 pieces of software.

1) The one running on the miner
2) The proxy site that the miner connects through

1
You don't have to run their hacked security risk software that hides where your shares are going and allows them to redirect your miner to anything, any where, any time without even a log of it happening.
You could run master cgminer, or even your own cgminer hacked to not submit.

2
Their site software is not public
... and they don't even care if anyone withholds blocks coz they get paid no matter what happens.
It's the exact same risk concept as running a PPS pool - that really no one in their right mind should do.
The difference is that the risk is passed to the person paying to rent the miners and the pool they are mining at
Not-so-nice-hash and the person with the miner lose nothing if the miner withholds blocks.

A whole thread on the subject:
https://bitcointalksearch.org/topic/pps-block-withholding-and-rentals-1002086

And my recent comment to not-so-nice-hash about it - completely ignored coz they get paid no matter what - why would they care if anyone block withholds?
https://bitcointalksearch.org/topic/m.13533668
legendary
Activity: 3654
Merit: 8909
https://bpip.org
If a rig owner wants to use these sites they have to use that sites version of your software. That's what I meant by being "available for scrutiny"

That's not true.
hero member
Activity: 777
Merit: 1003
ckpoolmonitor.zachmonroe.com update:

Several people requested it and I think I have it all working now, if not, things will go bad and the internet might melt.  Wink

Go into your Account Settings and at the bottom there should be options for each of your Workers.

Let me know if you have any problems.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
And about your rigs - just upgrade this to factory firmware.

Will do. I'll make sure to download a fresh copy thanks.

Edit- Regarding the software at the rental sites- If there was a way for individual miners to withhold blocks I'm sure it would have come to light by now. The software is readily available for scrutiny, is it not?

You can't see the software running at the miner, nor do the rental sites show you their software. Where did you get the idea they put themselves up for scrutiny?

Do you not believe me when I say there is a way to do it? Given they're all using my software in various forms, I think it's fair to say I'm qualified to say it's possible. I didn't say it was likely, just that it's possible.
full member
Activity: 157
Merit: 103

Now I have to study the software to make sure it's not set up to send the previous owner my shares. Frick.
You will not learn anything as at least you don't have software running at rental site and will never get it.
And about your rigs - just upgrade this to factory firmware.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Right on.. Sorry i bothered

Edit .. im sure i know why you dont like the rentals. and its not block withholding..  Wink  People are gaining the system with all this good luck.. pay ..0045 and get back double in return.. But that just takes from us loyal miners. Let me know if im wrong
You can't tell if and when a rental decides to block withhold and the rentals themselves still get the same profit regardless of whether they hold or submit blocks. That they haven't so far is a good sign, so I'd run with rentals that have a reputation, but there's nothing stopping them doing it at any time in the future. If it weren't for rentals, solo wouldn't be anywhere near as successful as it is - I'm just saying there is a huge element of trust involved and renters should be aware of that.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools.  If pools don't have a way of detecting such behavior, then what you would see is some longer-established pools starting to see consistent lower luck.  New small pools such as kano would see relatively higher luck until the dishonest miners start infiltrating them as well.  In other words, the anecdotal data on "luck" of different pools is consistent with there being dishonest miners out there.

So what is or can be done to detect and/or block such miners?  Certainly over time you can run statistical tests that would identify miners with below-average luck.  At some point that becomes statistically significant, but a smart dishonest player could keep changing accounts to make this hard to detect.

Or more realtime tricks could be done by the pool to detect and kill bad players up front.

now where's the script for that ?  Tongue  I'd have to go mine over at antpool or f2pool with that though huehuehue

I thought i read somewhere that there was a proposal and it went something like this.. The pool operator is able to send your miner a "fake" share that would result in the miner returning a valid block to that fake share. then you could tell if the miners are witholding blocks.. Let me do some digging and ill come up with the article..

Best regards
d57heinz
Not possible to do reliably. Don't bother digging it up again. There's no safe way to trust rentals is the final conclusion.

Right on.. Sorry i bothered

Edit .. im sure i know why you dont like the rentals. and its not block withholding..  Wink  People are gaining the system with all this good luck.. pay ..0045 and get back double in return.. But that just takes from us loyal miners. Let me know if im wrong
hero member
Activity: 770
Merit: 523
140th from me, real bitmain hardware in a tier 4 datacenter. 24/7 , no pool hopping. No rentals.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools.  If pools don't have a way of detecting such behavior, then what you would see is some longer-established pools starting to see consistent lower luck.  New small pools such as kano would see relatively higher luck until the dishonest miners start infiltrating them as well.  In other words, the anecdotal data on "luck" of different pools is consistent with there being dishonest miners out there.

So what is or can be done to detect and/or block such miners?  Certainly over time you can run statistical tests that would identify miners with below-average luck.  At some point that becomes statistically significant, but a smart dishonest player could keep changing accounts to make this hard to detect.

Or more realtime tricks could be done by the pool to detect and kill bad players up front.

now where's the script for that ?  Tongue  I'd have to go mine over at antpool or f2pool with that though huehuehue

I thought i read somewhere that there was a proposal and it went something like this.. The pool operator is able to send your miner a "fake" share that would result in the miner returning a valid block to that fake share. then you could tell if the miners are witholding blocks.. Let me do some digging and ill come up with the article..

Best regards
d57heinz
Not possible to do reliably. Don't bother digging it up again. There's no safe way to trust rentals is the final conclusion.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools.  If pools don't have a way of detecting such behavior, then what you would see is some longer-established pools starting to see consistent lower luck.  New small pools such as kano would see relatively higher luck until the dishonest miners start infiltrating them as well.  In other words, the anecdotal data on "luck" of different pools is consistent with there being dishonest miners out there.

So what is or can be done to detect and/or block such miners?  Certainly over time you can run statistical tests that would identify miners with below-average luck.  At some point that becomes statistically significant, but a smart dishonest player could keep changing accounts to make this hard to detect.

Or more realtime tricks could be done by the pool to detect and kill bad players up front.

now where's the script for that ?  Tongue  I'd have to go mine over at antpool or f2pool with that though huehuehue

I thought i read somewhere that there was a proposal and it went something like this.. The pool operator is able to send your miner a "fake" share that would result in the miner returning a valid block to that fake share. then you could tell if the miners are witholding blocks.. Let me do some digging and ill come up with the article..

Best regards
d57heinz

Edit found one article about it..

http://bitcoin.stackexchange.com/questions/1338/how-is-block-solution-withholding-a-threat-to-mining-pools    read down thru the comments


5
down vote
A "check block" and "block found reward" combined are an effective counter measure.

Once a "good" miner reports a valid block the pool operator could resend it to other members of the pool (maybe random % of pool, maybe pool members who are "unlucky" , etc). As others have indicated if you sent it to entire pool that would be detectable by bad miners so pool would need to experiment with what fraction of pool is the best countermeasure.

The pool operator knows this header (with this specific extra nonce) is valid. If a miner reports it as invalid he is suspicious. If he keeps doing it then he is an attacker and the pool bans him and seizes his funds. Most pools hold 120 blocks worth of rewards as unconfirmed meaning the attacker risks losing more than one block worth of compensation everytime he cheats. To avoid bad morale the pool operator could split the siezed funds among "good miners" to compensate them for the times when bad "miners" are not caught.

Another method which can be combined with the check block is to provide a "block found reward". Collect an x% fee from all miners and award the miner who finds the block this fee. In the long run this fee has no cost to miners (they will receive as much as they payout). That puts a financial gain on finding a block. This increases the revenue loss an attacker will incur by witholding blocks. That combined with risk of getting caught and losing all unconfirmed rewards should be sufficient to make block witholding punitively expensive for the attacker.

shareimprove this answer
edited Oct 28 '11 at 13:28
answered Oct 6 '11 at 21:11

DeathAndTaxes
5,8601653
add a comment
donator
Activity: 2058
Merit: 1007
Poor impulse control.
Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools. 

...


Miners can't steal blocks from pools, and this problem was addressed by the very first pooled mining groups.

If you mine at a pool, then you accept the pool's generation address and the block reward can only be paid to that address (or addresses). If a miner attempts to include a different address then the work will not be accepted by the pool.

hero member
Activity: 575
Merit: 500
Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools.  If pools don't have a way of detecting such behavior, then what you would see is some longer-established pools starting to see consistent lower luck.  New small pools such as kano would see relatively higher luck until the dishonest miners start infiltrating them as well.  In other words, the anecdotal data on "luck" of different pools is consistent with there being dishonest miners out there.

So what is or can be done to detect and/or block such miners?  Certainly over time you can run statistical tests that would identify miners with below-average luck.  At some point that becomes statistically significant, but a smart dishonest player could keep changing accounts to make this hard to detect.

Or more realtime tricks could be done by the pool to detect and kill bad players up front.

Don't know much about this but I can say that before I came to Kano, I used Slush and Bitminter. I rented from nice hash many times to supplement my own hardware and my rented hash has found a block for Bitminter and Slush. With Bitminter, my rented hash connected to them and within 30 minutes found a block. Funny thing was that my rental ended and the next block was over 300% so I got zero payment for that rented hash. Since my hash found a block so soon after connecting I did not have many shares on the 10 shifts they pay. On slush case it was about 18 hours after I rented the hash. In both cases it was 25th.

I also think we had several blocks found here with rented hash, just by looking at the worker names, don't know for sure but I'd say so with worker name like R1 or rent.
legendary
Activity: 2294
Merit: 1182
Now the money is free, and so the people will be
Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Specifically, the hypothesis is that dishonest miners are contributing hashes but stealing blocks from various pools.  If pools don't have a way of detecting such behavior, then what you would see is some longer-established pools starting to see consistent lower luck.  New small pools such as kano would see relatively higher luck until the dishonest miners start infiltrating them as well.  In other words, the anecdotal data on "luck" of different pools is consistent with there being dishonest miners out there.

So what is or can be done to detect and/or block such miners?  Certainly over time you can run statistical tests that would identify miners with below-average luck.  At some point that becomes statistically significant, but a smart dishonest player could keep changing accounts to make this hard to detect.

Or more realtime tricks could be done by the pool to detect and kill bad players up front.

now where's the script for that ?  Tongue  I'd have to go mine over at antpool or f2pool with that though huehuehue
full member
Activity: 206
Merit: 100
Anyone notice the little over 40PH that Ant lost today? I think it's helping keep the 10m block times and MAYBE diff in check this cycle. Where did it go? Maybe the s3 hashnest that just went negative maintenance? I always thought they were running all s7 and just charging people different rates for s3,4,5. Maybe they really had a legit s3 farm that they shut down?

Either way it good for keeping diff in check. Hope it lasts.

LLK

Kinda hard not to see a 40PH drop.
I was wondering what happen also.
hero member
Activity: 575
Merit: 500
Anyone notice the little over 40PH that Ant lost today? I think it's helping keep the 10m block times and MAYBE diff in check this cycle. Where did it go? Maybe the s3 hashnest that just went negative maintenance? I always thought they were running all s7 and just charging people different rates for s3,4,5. Maybe they really had a legit s3 farm that they shut down?

Either way it good for keeping diff in check. Hope it lasts.

LLK

BTW, my new signature is LLK (long live KANO) Wink
hero member
Activity: 723
Merit: 519
It has also been posted many times about if you can  trust the miners you rent to report a block if found. Also you have no idea how far away from the pools servers they are located.

I've been wondering about this.  Does anyone have any references on this, or perhaps kano/ck can comment on what safeguards exist against bad miners?  Do you test miners periodically to see if they faithfully report winning hashes?



Well...your question itself is the reason I don't rent hash. There's no BTCPD gonna look out for us. Our security is our own responsibility. That said, I'm sure the renters are, on the whole, honest...but I don't see much of a way to independently (as a user) verify that, and so my basically paranoid personality tends to rely on my own gear, and on a pool that essentially has the Bernie Sanders outlook...keep it honest, keep it efficient, and keep on truckin'...  Grin

Bernie Sanders?!? Looks like we have a socialist mining here  Grin
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I guess in case anyone was wanting an update Smiley

Yep it's all done (over 35 minutes ago) and the only one minor hitch was that the nonce proxy failed-over one user unexpectedly due to having to kill the nonce proxy and restart it.

All's good.
hero member
Activity: 770
Merit: 523
One of my s7's has been at .02 HWE for two weeks, running at the bottom of my worker list on the worker page.
I rebooted it and now it is running at .002 HWE. I guess sometimes a power cycle will kick the HWE up until a reboot occurs.

Yup. Interesting that it's S7s (I don't have one yet). My old S2 is like that, but occasionally an S3 will do the same. I've found that doing a reboot via the html interface only reboots the OS, and the controller can get confused all on its own, so a cold boot will reset everything once you've done your config. How are your S7s for temp? I live in the tropics and would like to move up.
 
Unless your ambient temp is low it is a flame thrower.
I have two in my 400sqft garage and it it 32 degrees outside. Garage temp is tropical and it is  not sealed well.
Think 2400 watt space heater.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
... and on the subject of changes ...

There's been some important changes on the ckpool local <->remote node code by -ck so there'll be a set of updates with those in about 18 hours.
I'll post again tomorrow morning (it's early afternoon here now) an hour before I do that with ckpool on all the nodes.

...
Here's that 1 hour warning to let everyone know.

In just over 1 hour I'll be doing ckpool updates on the "5" nodes.
When the minute hand hits zero in 65 minutes at 23:00 UTC

Each update is immediate, no delays or anything like that.

Firstly the main node which will be the usual case of most miners should just see a reconnect in cgminer, though a small % will failover.
People on the remote nodes have a higher chance of failover when the main node restarts.

Then will be the Tube nonce connection (1) and each of the remote nodes (3)
These updates should only see reconnects and no failovers.

There will also be a reduction in stales on the remote nodes due to this update.
In 3 minutes.
Jump to: