KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[philipma1957]

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.

[1715255601]

1715255601

[1715255601]

1715255601

[1715255601]

1715255601

[E]

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.

I know you understand all of the following, and your comment is about daily vs. blockly payouts, but even in this case (55 inputs) the fee is really reasonable:

Your transaction was over 11KB -- suggested fee for inclusion in next 0-1 blocks is sat50/byte, or  0.0057 for your transaction. That's about 0.07% of the transaction amount.

Your included fee of 0.0013 is sat11/byte, which 21.co currently estimates means a delay of around 14 blocks.

It's a change from the past, I agree -- and I am a 2MB HF now supporter, running a Classic node since 3 Feb, but I think your original fee was too low for the market conditions.

[cavaliersrus]

hey kano some reason my s2 on your firmware is running better and cooler temps on my boards same temperature in the room

my boards was between 50-55C and now there between 46-50c

[firetreeactual]

hey kano some reason my s2 on your firmware is running better and cooler temps on my boards same temperature in the room

my boards was between 50-55C and now there between 46-50c

My old S2 runs hot, and I've had to mod it to keep it running at 60 or so. Can I get a link for the firmware? Should try that.

[kano]

For those waiting on them and wondering where they were:

Payouts 399612 and 399633 sent (about 30 minutes ago)
c1c848938edf937a940d10ea0328f467defed7d20a2370e01185ee373c2f837c
5a18606bacc80bcc24713995b58540d73771727a24ee283cccf055eeb6b144fa

awaiting confirm e.g. a block by us

I had to build a new bitcoind from scratch at home.
Not the wallet, but my main one at home, with no wallet, that talks to the internet.

The first 300k blocks were quick, then it slowed down ...

First 100k took 8 minutes
100k - 200k took 13 minutes
200k - 250k took 17 minutes
250k - 298k took 51 minutes
At this point I shut down my desktop and added 2 more fans to the case coz the CPU hit 100C a couple of times
298k - 353k took 4 hours
353k - 363k took 2 hours
363k - 399.7k took 5.5 hours

Though the overall total of about 13 hours wasn't too bad - since it also has -txindex

[kano]

hey kano some reason my s2 on your firmware is running better and cooler temps on my boards same temperature in the room

my boards was between 50-55C and now there between 46-50c

My old S2 runs hot, and I've had to mod it to keep it running at 60 or so. Can I get a link for the firmware? Should try that.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS2

[kano]

... 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.

[philipma1957]

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.

I know you understand all of the following, and your comment is about daily vs. blockly payouts, but even in this case (55 inputs) the fee is really reasonable:

Your transaction was over 11KB -- suggested fee for inclusion in next 0-1 blocks is sat50/byte, or  0.0057 for your transaction. That's about 0.07% of the transaction amount.

Your included fee of 0.0013 is sat11/byte, which 21.co currently estimates means a delay of around 14 blocks.

It's a change from the past, I agree -- and I am a 2MB HF now supporter, running a Classic node since 3 Feb, but I think your original fee was too low for the market conditions.

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.

[firetreeactual]

hey kano some reason my s2 on your firmware is running better and cooler temps on my boards same temperature in the room

my boards was between 50-55C and now there between 46-50c

My old S2 runs hot, and I've had to mod it to keep it running at 60 or so. Can I get a link for the firmware? Should try that.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS2

Way cool. Thank you.

[rkinnin]

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?

[bctmke]

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://bitcointalk.org/index.php?topic=789369.msg13987159#msg13987159

[cavaliersrus]

im seeing it also

[Real-Duke]

Restart? I can smell a block *sniff* *sniff* 

[bbOOmm]

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.

[kano]

... 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.

[generalt]

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!

[kano]

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" ?

[philipma1957]

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%

[Biodom]

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.

[edonkey]

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.