I just bought a 25lb case of chicken fritters..... hopefully that'll inject some good juju into the pool .....
OR ....
Kano could reboot the whole system. That has ALWAYS worked in the past ....
:-)
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1482. (Read 5352420 times)
May 06, 2016, 01:20:19 PM
May 06, 2016, 01:01:47 PM
Problem is no information was ever given out about that or what was done to resolve it. So ya that miner could have moved but no one knows who it is or what software was used.
so did someone stop eating chicken and go vegetarian? all this red is starting to creep into the the 100 block stats. if this is from an attack it seems pretty childish, if its just a run of bad luck wow. time to sacrifice something chicken related.
Maybe a bad luck maybe a attack , but in the past 3 days we got 1 block each day , and in the past 3 days we got 2 oprhan ... i would say that is very unusal for a pool with 35-40PH/s ... Just in case , the Pool operator should look after a possible attack , and maybe contact another pool operators where the same thing happened in the past ...for some advice .
You are right , Slash did not give out any information what happened exactly , but there is a reason behind that . Maybe they did not want to give any idea for ppl how to attack any pools ... so they just said to the public , they find a attacker and fixed the problem .
May 06, 2016, 12:05:22 PM
My apologies for the OT, but there's a lot of experts here.
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
251 inputs? every couple of weeks you should sweep your payout address to a clean one. this will keep the inputs low and make transactions faster.
May 06, 2016, 11:46:00 AM
Wowzers...been off the boards for a couple of days with the power issues, etc. Looks like it may have been a propitious time for a power fail, as a slack time for the pool as well. I happened to get the S7s up and running just before each of the last two blocks, though.
Re BTC and the Chinese...I'm a retired profiler (among other things...that was just the Renaissance Gal's last career). I ain't gonna go there.
One thing I've found over the decades, though...when a person or group is exceptionally good at what they do, and produces success in that action, there will always be those who are (1) jealous, (2) threatened by what they perceive as a danger to their self-interest, and/or (3) greedy to the degree that they believe damaging the successful one will increase their own worth.
Kano & CK are the best I've seen at what they do...and I've seen just about everything from Turing machines to steel chassis' and vacuum tubes to now. IMHO, we here should do what we reasonably can to support that effort. It is to all our benefit, of course, but at least in my personal view it is essential to preserving the integrity of the network.
Rant over. We rock. Mine on.
Re BTC and the Chinese...I'm a retired profiler (among other things...that was just the Renaissance Gal's last career). I ain't gonna go there.
One thing I've found over the decades, though...when a person or group is exceptionally good at what they do, and produces success in that action, there will always be those who are (1) jealous, (2) threatened by what they perceive as a danger to their self-interest, and/or (3) greedy to the degree that they believe damaging the successful one will increase their own worth.
Kano & CK are the best I've seen at what they do...and I've seen just about everything from Turing machines to steel chassis' and vacuum tubes to now. IMHO, we here should do what we reasonably can to support that effort. It is to all our benefit, of course, but at least in my personal view it is essential to preserving the integrity of the network.
Rant over. We rock. Mine on.
May 06, 2016, 11:39:31 AM
To Me looks like a Block withholding attack is happening with kano ..its a a well-known weakness of the whole pool mining principle and no public pool is immune against it. Slush pool had a same situation in February .
"Published: 2016-02-06 17:02:27
Dear miners, we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved."
Problem is no information was ever given out about that or what was done to resolve it. So ya that miner could have moved but no one knows who it is or what software was used."Published: 2016-02-06 17:02:27
Dear miners, we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved."
so did someone stop eating chicken and go vegetarian? all this red is starting to creep into the the 100 block stats. if this is from an attack it seems pretty childish, if its just a run of bad luck wow. time to sacrifice something chicken related.
May 06, 2016, 11:32:53 AM
To Me looks like a Block withholding attack is happening with kano ..its a a well-known weakness of the whole pool mining principle and no public pool is immune against it. Slush pool had a same situation in February .
"Published: 2016-02-06 17:02:27
Dear miners, we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved."
"Published: 2016-02-06 17:02:27
Dear miners, we would like to inform you that we have detected and resolved an unintentional block withholding attack.
The issue has been discovered a week ago and we have immediately taken an action by contacting the particular miner. The cause turned out to be a bug in a custom mining firmware, which has been promptly fixed by the miner. We have no indication that there was any bad intention. The fixed firmware solved two blocks since then so we can consider this issue as resolved."
May 06, 2016, 11:07:18 AM
My apologies for the OT, but there's a lot of experts here.
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
it will stay stuck fee is too low.
kano does .002 for around 42000 bytes and no one ever confirms it (kano and ck solo confirm it 90% of the time)
so you 37000 bytes and .0007 is far worse payment then kano's so my guess is it stays stuck.
May 06, 2016, 10:36:39 AM
I think the thing that bothers me the most about the replies by macbook-air is not the accusation of racism, or the statements about probability. What bothers me the most is the misdirection away from kano's original query:
Is f2pool taking a deliberate measure to work on their own old blocks for some amount of time hoping to win their own orphan races? In other words, are they abusing their large hash rate percentage and trying to game the system?
Here are kano's original theories on why block 410419 was orphaned at all:
I bolded the one to help make it clearer.
Is f2pool taking a deliberate measure to work on their own old blocks for some amount of time hoping to win their own orphan races? In other words, are they abusing their large hash rate percentage and trying to game the system?
Here are kano's original theories on why block 410419 was orphaned at all:
Quote
So basically the cause was one or more of the following:
FUPool is REAL slow getting their blocks to the CN relay.
FUPool works on their own blocks after they see other pool blocks if they are found soon after.
FUPool had most of their 410419 block transactions not in the relay so was really slow getting their block into the relay (compression was almost zero as you can see) Edit: but I don't think this is it coz it was prolly the relay did that coz it already had our block using the transactions.
FUPool is REAL slow getting their blocks to the CN relay.
FUPool works on their own blocks after they see other pool blocks if they are found soon after.
FUPool had most of their 410419 block transactions not in the relay so was really slow getting their block into the relay (compression was almost zero as you can see) Edit: but I don't think this is it coz it was prolly the relay did that coz it already had our block using the transactions.
I bolded the one to help make it clearer.
Agreed. That's the key point. How and why is F2Pool able to do that? Quite simply, it defeats the egalitarian intent of BTC mining as it does seem that they are somehow able to game the system.
The other bothersome thing is it seems that the larger pools may have found a way to block a smaller, more successful, pool from finding blocks without using DDOS. For the past 10 days or so, it seems that they have targeted this pool. The Stats show this. In other words, a pool can have a few days of bad luck and kano has had some of those before...but the longer than usual bad luck streak here seems like something else is afoot. I don't have the technical skills to investigate how this is being done- but it's simply my observation.
It should be traceable somehow with all of the wisdom of the members in this pool to show that there is a decrease during a period of time in CKPool and and an exact inversion in F2Pool. Is this possible to determine?
May 06, 2016, 10:31:53 AM
Really nice to see a block found. Been an odd week or so here on the pool...
May 06, 2016, 10:12:27 AM
stupid question...
Kano's hash rate not even showing on any hash rate distribution charts anywhere???
edit it is showing but why so low
Kano's hash rate not even showing on any hash rate distribution charts anywhere???
edit it is showing but why so low
Those calculations are based on the number of blocks found, which has been quite abysmal lately. The opposite is true as well - during a period of "good luck" it will show much higher on a chart than it should.
May 06, 2016, 10:10:51 AM
Of course. Lol. Hopefully that is the start to the pull out of this slump
May 06, 2016, 10:09:28 AM
Kano I would have to agree more than a couple days this deep in the red is unusual. Any thoughts?
May 06, 2016, 10:06:32 AM
Block Friday by 12TMhCpL! That is his 23rd kano block!
May 06, 2016, 09:44:52 AM
stupid question...
Kano's hash rate not even showing on any hash rate distribution charts anywhere???
edit it is showing but why so low
Kano's hash rate not even showing on any hash rate distribution charts anywhere???
edit it is showing but why so low
May 06, 2016, 09:10:13 AM
My apologies for the OT, but there's a lot of experts here.
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
I just sent a 37181 (bytes) transaction and the fee was 0.000018846453833947445 BTC per kB (0.00070073 BTC)
251 inputs/2 outputs
I've some problem calculating the fee and the transaction size, but that's what was sent....
Does it seem ok ? or will it take literally forever to be confirmed and my BTC is stuck in space ?
May 06, 2016, 09:08:49 AM
I think the thing that bothers me the most about the replies by macbook-air is not the accusation of racism, or the statements about probability. What bothers me the most is the misdirection away from kano's original query:
Is f2pool taking a deliberate measure to work on their own old blocks for some amount of time hoping to win their own orphan races? In other words, are they abusing their large hash rate percentage and trying to game the system?
Here are kano's original theories on why block 410419 was orphaned at all:
I bolded the one to help make it clearer.
Is f2pool taking a deliberate measure to work on their own old blocks for some amount of time hoping to win their own orphan races? In other words, are they abusing their large hash rate percentage and trying to game the system?
Here are kano's original theories on why block 410419 was orphaned at all:
Quote
So basically the cause was one or more of the following:
FUPool is REAL slow getting their blocks to the CN relay.
FUPool works on their own blocks after they see other pool blocks if they are found soon after.
FUPool had most of their 410419 block transactions not in the relay so was really slow getting their block into the relay (compression was almost zero as you can see) Edit: but I don't think this is it coz it was prolly the relay did that coz it already had our block using the transactions.
FUPool is REAL slow getting their blocks to the CN relay.
FUPool works on their own blocks after they see other pool blocks if they are found soon after.
FUPool had most of their 410419 block transactions not in the relay so was really slow getting their block into the relay (compression was almost zero as you can see) Edit: but I don't think this is it coz it was prolly the relay did that coz it already had our block using the transactions.
I bolded the one to help make it clearer.
Agreed. That's the key point. How and why is F2Pool able to do that? Quite simply, it defeats the egalitarian intent of BTC mining as it does seem that they are somehow able to game the system.
The other bothersome thing is it seems that the larger pools may have found a way to block a smaller, more successful, pool from finding blocks without using DDOS. For the past 10 days or so, it seems that they have targeted this pool. The Stats show this. In other words, a pool can have a few days of bad luck and kano has had some of those before...but the longer than usual bad luck streak here seems like something else is afoot. I don't have the technical skills to investigate how this is being done- but it's simply my observation.
May 06, 2016, 09:03:26 AM
Another reason rentals aren't good. I'm guilty of using them from time to time, but this may be the icing on the cake.
May 06, 2016, 08:38:46 AM
I know of a few ways they can do it.
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
Can you explain what you mean by "send[ing] dead hashers?"
*Hash don't care either coz they get paid BEFORE you mine and they wont lose anything.
The people who own the miners will get paid no matter what also.
Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ...
Basically, as a renter you can absolutely never make an informed decision about whether the hashing power you're renting is behaving badly.
May 06, 2016, 08:34:01 AM
I know of a few ways they can do it.
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
Can you explain what you mean by "send[ing] dead hashers?"
*Hash don't care either coz they get paid BEFORE you mine and they wont lose anything.
The people who own the miners will get paid no matter what also.
Thus someone could provide "bad hash power" on *Hash and no one would know unless they mined a VERY large amount and kept track of the statistics ... ... ...
May 06, 2016, 08:22:02 AM
I know of a few ways they can do it.
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
so to everyone here that is renting from NH / WH consider that
f2pool can send dead hashers to WH/NH with ease
Can you explain what you mean by "send[ing] dead hashers?"
Jump to: