Author

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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
kano this pool tends to do that though doesent it ?
Random, but becoming more common as the number of miners increases so the size of the payout increases.
hero member
Activity: 735
Merit: 500
★YoBit.Net★ 350+ Coins Exchange & Dice
kano this pool tends to do that though doesent it ?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Our last block (15 min ago) confirmed the last payout Smiley
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
nhando kicking on the afterburners and the pool's up over 28PHs atm!  Far out! Grin
hero member
Activity: 770
Merit: 523
52 minutes on the last network block

full member
Activity: 162
Merit: 100
guys off topic question. Is it possible that pool operator, takes part of the hash and point to nicehash to again mine on the same pool? If its possible that will show double or that part hash and the pool owner takes the split?

yes its very possible.. there was a pool called bitcoinaffiliatnetwork.. he was accused of selling hash to rent..
the pool became very shady and nobody got paid for weeks.. i think it went offline with him owing 100s of bitcoin to people.
i think that happens at slush, maybe not but i cant say for sure
legendary
Activity: 1736
Merit: 1006
guys off topic question. Is it possible that pool operator, takes part of the hash and point to nicehash to again mine on the same pool? If its possible that will show double or that part hash and the pool owner takes the split?

yes its very possible.. there was a pool called bitcoinaffiliatnetwork.. he was accused of selling hash to rent..
the pool became very shady and nobody got paid for weeks.. i think it went offline with him owing 100s of bitcoin to people.
full member
Activity: 162
Merit: 100
guys off topic question. Is it possible that pool operator, takes part of the hash and point to nicehash to again mine on the same pool? If its possible that will show double or that part hash and the pool owner takes the split?
legendary
Activity: 1274
Merit: 1000
That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.

Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.

Any comments?
I think the once per day payout it a good balance between payment frequency and having to pay tx fees for sending out the payments.  I like your outline, it sounds like it only adds one more step to what you are currently doing, but that one step could end up saving you coin in the long run on the tx fees that you save.  So a bit more work but you are compensated for it.

Also, if this change would handle sweeping up dust payments and sending those out it would be cool for all the people who have asked about how to get their dust, and it would keep the pool from having to store that coin.
legendary
Activity: 1150
Merit: 1004

https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.


even though the fee is .0013 I got skipped here  for this block.

These funds were sent to me and there are 3 big parts in the send  about  7.5  and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.


55 pennies is large fee to send $4,400 ?
Last week I spent $46.00 to wire $1,700 at the bank.
Sticking to .0001 per kb should still assure relatively fast acceptance.


 

First off I understand the fee mechanism, but many don't..  

  Many people think 0.0001 or 0.0002 just works.

 From your post I am inclined to think you realize BTC size means nothing kb size means everything.

So a          1 btc send consisting of 75 x 0.02  is expensive to send.                 0.0013 is too small
While a 25.2 btc send consisting of a confirmed virgin block is cheap to send.   0.0004 will do the trick almost everytime

The problem is a lot of people don't understand this.
Most people do not understand that btc amount means nothing.
Here is one of my kano.is payment addresses:

it has .20453225 in it

https://blockchain.info/address/16yLHLoeyuCLPMXkVpC3gyrRYvwRGwjKJr

that is from 1 avalon6 and is the last 20 rewards from kano.is pool

to empty this and send to someone  will cost 0.0004 to 0.0006  due to the fact it is 20 payments or so.

.204 is under 90 bucks  and this is why I would like 1 payment a day since it would be 6 payments not 20 plus  and sending the coins out would be

0.0002 or 0.0003 tops.

I think the rec I have seen was to check how many bits are in your transaction, then multiply by 20 sat.
So, for 700bits, 700X20=14000 sat or 0.00014 btc
So far it worked for me. If need comes, i will bump it to 30sat/bit, but I haven't done any transactions in a week or two.

At this risk of continuing this off topic discussion, doesn't your wallet software automatically compute a reasonable fee for size of the transaction? I remember the first time I bought something with mined coins and was shocked by the fee. Then I realized how huge the transaction was due to tons of tiny inputs, after which it made sense.

I've only used Bitcoin-Qt and a Trezor for receiving mined income. Both of them seem to do a decent job of computing reasonable fees when spending. Never seen a stuck transaction. Maybe other wallets don't automatically do as good a job, or maybe people think they know what they're doing and they override the wallet and low ball the fee?

Note that in the Trezor's case I periodically transfer from my mining account to my main one so that I can consolidate my bazillion tiny inputs. One drawback of the Trezor is that its signing is slow, so big transactions can take a long time to sign (many minutes sometimes). By consolidating I can pick when I want to spend that time.
legendary
Activity: 3990
Merit: 4597

https://blockchain.info/tx/df60741e004f63c13d07eb422f89b3fbc1a2b270cccd35c05d0daeb35af5f20f

now 10 blocks have skipped the .0013 fee transaction due to it having 52 small parts of coin and 3 big parts.
thus 55 parts of coin which takes up space so it gets skipped.


even though the fee is .0013 I got skipped here  for this block.

These funds were sent to me and there are 3 big parts in the send  about  7.5  and 52 small parts around 0.05

This is tough as small payments take up space and the large fee of .0013 is not big enough.


55 pennies is large fee to send $4,400 ?
Last week I spent $46.00 to wire $1,700 at the bank.
Sticking to .0001 per kb should still assure relatively fast acceptance.


 

First off I understand the fee mechanism, but many don't..  

  Many people think 0.0001 or 0.0002 just works.

 From your post I am inclined to think you realize BTC size means nothing kb size means everything.

So a          1 btc send consisting of 75 x 0.02  is expensive to send.                 0.0013 is too small
While a 25.2 btc send consisting of a confirmed virgin block is cheap to send.   0.0004 will do the trick almost everytime

The problem is a lot of people don't understand this.
Most people do not understand that btc amount means nothing.
Here is one of my kano.is payment addresses:

it has .20453225 in it

https://blockchain.info/address/16yLHLoeyuCLPMXkVpC3gyrRYvwRGwjKJr

that is from 1 avalon6 and is the last 20 rewards from kano.is pool

to empty this and send to someone  will cost 0.0004 to 0.0006  due to the fact it is 20 payments or so.

.204 is under 90 bucks  and this is why I would like 1 payment a day since it would be 6 payments not 20 plus  and sending the coins out would be

0.0002 or 0.0003 tops.

I think the rec I have seen was to check how many bits are in your transaction, then multiply by 20 sat.
So, for 700bits, 700X20=14000 sat or 0.00014 btc
So far it worked for me. If need comes, i will bump it to 30sat/bit, but I haven't done any transactions in a week or two.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
My miners have been frequently dropping off of the pool. It seems to be happening more and more since the pool went over 20PH.... along with the blocks being very slow .... I'm kinda wondering if the mining servers cannot handle the load of over 20PH

Playing with pool management with a private test pool to learn how things work, I get the same effects when I overload the hardware.

just my thoughts, we will have to wait for the official cause.
Well, considering the pool has only dropped to 20PH today, but been running 25PH avg, and often up to 30PH for quite a while now ...

... how did you determine "blocks being very slow" ?

well very slow is 90 to 99%  not your usual 106% Roll Eyes
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
My miners have been frequently dropping off of the pool. It seems to be happening more and more since the pool went over 20PH.... along with the blocks being very slow .... I'm kinda wondering if the mining servers cannot handle the load of over 20PH

Playing with pool management with a private test pool to learn how things work, I get the same effects when I overload the hardware.

just my thoughts, we will have to wait for the official cause.
Well, considering the pool has only dropped to 20PH today, but been running 25PH avg, and often up to 30PH for quite a while now ...

... how did you determine "blocks being very slow" ?
legendary
Activity: 1096
Merit: 1021
So I got caught on sends due to this more then once. So I know to send high fees when the coin in my wallet is 35 or 50 x .01 from mining here.

A lot of of  people sending to me  don't  know this issue so  they send decent coin and think it is enough. Then everything bogs down for hours or worse sends just fail.

This actually answers some questions that I've had that I never asked.  Thanks!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
... and a ckpool (and ckdb) restart about to happen in the next minute.

The ckpool restart is the fixes for the last restart that are rather urgent.
Sorry for the short warning, but it's early morning here now and having done the payouts, I need to get this update in there now also.

Restart all done.
Seems it will need more work still, but all is running ok.
Both payouts confirmed just before the restarts.
sr. member
Activity: 277
Merit: 250
My miners have been frequently dropping off of the pool. It seems to be happening more and more since the pool went over 20PH.... along with the blocks being very slow .... I'm kinda wondering if the mining servers cannot handle the load of over 20PH

Playing with pool management with a private test pool to learn how things work, I get the same effects when I overload the hardware.

just my thoughts, we will have to wait for the official cause.
legendary
Activity: 3486
Merit: 2287
Wheel of Whales 🐳
Restart? I can smell a block *sniff* *sniff*  Grin
hero member
Activity: 735
Merit: 500
★YoBit.Net★ 350+ Coins Exchange & Dice
sr. member
Activity: 294
Merit: 250
I am seeing ? next to all the stats on your pool web site when I log in.  Did I miss an announcement that the site going down?

Yes just a few posts up

https://bitcointalksearch.org/topic/m.13987159
sr. member
Activity: 316
Merit: 250
I am seeing ? next to all the stats on your pool web site when I log in.  Did I miss an announcement that the site going down?
Jump to: