Author

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

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Well, blockchain.info does more than provide information about blocks... it's also an online wallet service.  So, I can understand the logic behind throwing a DDoS at them for that reason.

AntPool has been under attack for a while now.
full member
Activity: 182
Merit: 100
Ok thanks for clarifying. I have no idea what is/isn't possible. But I always take the assumption anything is possible, you just need to know how.

Looks like some DOS attacks going on specifically blockchain.info (and probably antpool). I could understand why some might DOS a pool (for greed, extortion, rivalry etc...) but why attack blockchain?

EDIT: taken off my hat now, head is cold...  Grin
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
I'm unaware of any settings you can configure to allow you to block transactions from specific BTC addresses.  Even *if* one pool decided it wanted nothing to do with kano and figured out a way to block transactions from him, there are plenty of other pools out there mining blocks who would be happy to include it.

Put away the tin foil hats, kids Smiley.
full member
Activity: 182
Merit: 100
Kano would a test payment to/from the pool address and a private address confirm any suspicions? I am sure you know how to prove this on your own, I am just curious to know if this would be a way to prove some pools are playing dirty.
Who cares of this proof? Yes, they ignoring Kano's transaction and so what?  You will post it on forum and they fix this immediately? Wink I do not think so.  Just we need to be patient and it will be confirmed anyway.

I wasn't looking for proof, I was just more curious to know if that would identify that address is being blocked. I guess I should of asked, are the pools specifically blocking transactions from 1N6LrEDiHuFwS....? or is there something else being done?

If it is just as simple as blocking that address, can pools have a new address for each newly found coins? or is there more to it like pool/relay IP's?

Thanks.
full member
Activity: 157
Merit: 103
Kano would a test payment to/from the pool address and a private address confirm any suspicions? I am sure you know how to prove this on your own, I am just curious to know if this would be a way to prove some pools are playing dirty.
Who cares of this proof? Yes, they ignoring Kano's transaction and so what?  You will post it on forum and they fix this immediately? Wink I do not think so.  Just we need to be patient and it will be confirmed anyway.
sr. member
Activity: 294
Merit: 250
It's still out there waiting.  Wheeeee.  We'll see it someday Smiley  Maybe before we hit the next block!!
full member
Activity: 182
Merit: 100
So every pool so far is either ignoring this transaction or is mining empty blocks? (not that they would include this transaction anyway). So looks like we need to confirm our own transaction.... come on pool Smiley

Or could other things be influencing this that are either normal or occasionally happen (i.e. backlog)?

Kano would a test payment to/from the pool address and a private address confirm any suspicions? I am sure you know how to prove this on your own, I am just curious to know if this would be a way to prove some pools are playing dirty.
full member
Activity: 182
Merit: 100
Does that mean some other pool has to do it first and only then will f2pool accept it? seems a bit wrong or a lot wrong actually.

If I understand correctly this transaction is going to take a while due to several things..

F2Pool doesn't want to process Kano transactions/blocks and mines empty blocks.
Antpool mines empty blocks
BW.com mines empty blocks.

I did see some new blocks with transactions from Antpool and BW so should that transaction have been included in one of those? (e.g. 387867  or  387865 )
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
blacklisted Kano pools payouts as well as the "not building on your blocks"

I missed that part. I thought they were just no longer to SPV mine here (even though Kano blocked their IP's) or was that the part when they said they would only build on it once its part of the block?


EDIT: looked back at Kanos coloured post and can see where it was mentioned. Does that mean some other pool has to do it first and only then will f2pool accept it? seems a bit wrong or a lot wrong actually.

Exactly!  F2pool and Antpool are just giant children throwing temper tantrums, hurting Bitcoin, and hurting pools that follow the rules.
full member
Activity: 182
Merit: 100
blacklisted Kano pools payouts as well as the "not building on your blocks"

I missed that part. I thought they were just no longer to SPV mine here (even though Kano blocked their IP's) or was that the part when they said they would only build on it once its part of the block?


EDIT: looked back at Kanos coloured post and can see where it was mentioned. Does that mean some other pool has to do it first and only then will f2pool accept it? seems a bit wrong or a lot wrong actually.
newbie
Activity: 41
Merit: 0
Maybe the chinese pool operators have acted upon their threats and have blacklisted Kano pools payouts as well as the "not building on your blocks" threat they made earlier:D

Seems like a conspiracy to me Cheesy
full member
Activity: 157
Merit: 103
No any probs with confirmation delay, just wondering why it was not included with 0.001 fee in those 10+ blocks
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
It usually confirms quickly.
'usually'
But sometimes takes a while due to lotsa txns on the network
(and I pretty much always set the txn fee to 0.001, subtracted from my mining payout)

Edit: oh, it's also in our block work, so if we find a block that will usually confirm it also, if it hasn't already been confirmed.
full member
Activity: 157
Merit: 103
I wonder what is the reason some nodes reject this?  There were about 10 block for last 1.5 hours but nobody included this.. Some nodes like blockchain.info rejects this  because of >250 outputs. What is the problem with 250 qty? Or just a wish..?

http://blockr.io/zerotx/info/5819e053783aa9ef768a9fa3d76da7cc6a1e86104fd485838101c8d47b5765c9
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payout 387752 sent about 1.5 hours ago
5819e053783aa9ef768a9fa3d76da7cc6a1e86104fd485838101c8d47b5765c9
But still not confirmed yet
member
Activity: 109
Merit: 10
I Got 2 controllers, so can point them at 2 different places where ever you want them. They Are just turned OFF atm..
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Edit: and if you or anyone Else find A solution to point my asictubes at this pool it would be great Grin ck hasnt answered my post yet so got no clue if its possible some other way.
I'd need someone to come onto irc and help me debug it live by aiming one at a testserver where I'd play with some settings till we got it right to figure out what they need.
member
Activity: 109
Merit: 10
Gotta say the Best thing i did was to switch over to this pool.!

Only been here 5 days or so, and its already better Then all the other pools i tried.

Now we just Need evryone Else to do the same thing  Cheesy



Edit: and if you or anyone Else find A solution to point my asictubes at this pool it would be great Grin ck hasnt answered my post yet so got no clue if its possible some other way.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Well you can't exactly disallow empty blocks on the network anyway.
There's a number of rare circumstances that can produce work that will produce an empty block.

Heh, even here the other day when I had a problem with CKDB for a few hours, that was caused by the fact that my CKDB code didn't actually allow an empty block (I didn't code it that way on purpose, it was just a side effect of how I handled the merkle tree array)

I created empty block work for ckpool by restarting bitcoind and at the time it was first available, ckpool asked for work and it had no transactions.
The rest after that was me dealing with finding the exact cause in my ckdb code and fixing it once I realised it was indeed an empty block that caused it. Yeah that hasn't ever happened before on the pool Cheesy
newbie
Activity: 41
Merit: 0
Good to hear on this issue, if only empty blocks were considered invalid by the rest of the network it would do a great service to bitcoin, it seems SPV and empty blocks can only harm it, and only do good short term for the greedy pool operators (and miners) wallet while hurting the whole ecosystem big time..

Empty and invalidly based blocks should be discarded by rest of network, anyway to get such a proposal to the protocol or does it not matter since the chinese control such a large portion of the hashrate and network ?
Jump to: