Author

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

legendary
Activity: 3990
Merit: 4597
I doubt that.  A single input transaction is costing between 1 and 2 dollars recently.  

The transaction I referenced had fees of 4 satoshi per byte.  Any lower and it won't even get into the mempool.

see kano's post.
you are doing something funky.
if you apply his math and go for 5sat/byte, you'll get $2.69 for 50tx consolidation, exactly what i posted (BTW, we have 34 tx at the moment, so it is $1.88, albeit RIGHT NOW fees are higher, so don't do it).
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
again excuse my ignorance but can anyone explain how the transaction fees work?

Well a transaction with say 50 inputs - roughly a month worth - would be about 9K bytes

btc.com says at the moment https://btc.com/
Current best transaction fees 0.00134 BTC/KB = 130 sat/byte

So 9K would be 0.00134 * 9 = 0.01206 BTC or about $70

If instead you paid 13 sat/byte it would be 0.001206 BTC or about $7 and most likely get through in the next day or so.

If fees were low (transaction less often, so blocks not always full) then the 13 sat/byte would often get through in the next hour or so.
In that case you could even put it lower and be pretty sure it would get confirmed in a day or so.

It's all about planning ahead Smiley

FYI when I change the payout structure, the longest you will be allowed to go without being paid is probably monthly payouts.
full member
Activity: 228
Merit: 100
Mine ON!!!
again excuse my ignorance but can anyone explain how the transaction fees work?
hero member
Activity: 756
Merit: 501
..you need to have hundreds of Th online to make your payments from the pool worthwhile.  

sorry to call you on this, but this is simply NOT so.
I typically pay $2-3 to consolidate monthly 'kano' inputs.
You might be doing it the wrong way. Don't go for the next block tx, for one.


I doubt that.  A single input transaction is costing between 1 and 2 dollars recently. 

The transaction I referenced had fees of 4 satoshi per byte.  Any lower and it won't even get into the mempool.
legendary
Activity: 3990
Merit: 4597
..you need to have hundreds of Th online to make your payments from the pool worthwhile.  

sorry to call you on this, but this is simply NOT so.
I typically pay $2-3 to consolidate monthly 'kano' inputs.
You might be doing it the wrong way. Don't go for the next block tx, for one.
hero member
Activity: 756
Merit: 501
Now that the panic has subsided; Kano can you get your payments system working?

Since the Core fanatics seem determined to abort the 2x block size increase into another stupid fork, we will continue to not have a scaling solution.  These tiny inputs are killing me, and we are a pretty huge miner on your pool.  I can't see how most folks can even spend what they are getting from your per block payments.

I sent a transaction from a mining address last week and even manually setting the fee to a bare minimum, it cost $170 to process the transaction.  If I had used the recommended fee it would have cost over 1 BTC! 

can you elaborate on the issue bothering you for us new people?
sorry to bother Huh

Kano summarized it quite nicely.  The size of your transaction depends on the number of inputs (and outputs), and fees are charged by size.  When you have an address with a lot of mining input, a transaction to consolidate them is very large, and very expensive.

As Kano's example suggests, you need to have hundreds of Th online to make your payments from the pool worthwhile.  Otherwise you lose too much in friction to transaction fees.
full member
Activity: 228
Merit: 100
Mine ON!!!
full member
Activity: 228
Merit: 100
Mine ON!!!
Now that the panic has subsided; Kano can you get your payments system working?

Since the Core fanatics seem determined to abort the 2x block size increase into another stupid fork, we will continue to not have a scaling solution.  These tiny inputs are killing me, and we are a pretty huge miner on your pool.  I can't see how most folks can even spend what they are getting from your per block payments.

I sent a transaction from a mining address last week and even manually setting the fee to a bare minimum, it cost $170 to process the transaction.  If I had used the recommended fee it would have cost over 1 BTC! 

can you elaborate on the issue bothering you for us new people?
sorry to bother Huh
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Now that the panic has subsided; Kano can you get your payments system working?

Since the Core fanatics seem determined to abort the 2x block size increase into another stupid fork, we will continue to not have a scaling solution.  These tiny inputs are killing me, and we are a pretty huge miner on your pool.  I can't see how most folks can even spend what they are getting from your per block payments.

I sent a transaction from a mining address last week and even manually setting the fee to a bare minimum, it cost $170 to process the transaction.  If I had used the recommended fee it would have cost over 1 BTC! 
Well as I (and many others) have pointed out in the past, you need to consolidate your payouts somehow.
Spending a large number of inputs will cost depending on how busy the network is.
If you consolidate them every so often when the network isn't busy, the consolidation fee can be very low.

I'm not sure how you ended up with $170 in fees though, unless you had to use a very large number of payouts and did it at the worst time to do it.

100THs now should get about 0.01 BTC per block.

$170 is 0.03 BTC and at BTC.COM says 0.00137 BTC/KB so a pretty large 22KB transaction ...
The pool payouts are a 28KB transaction for about 800 people so you must be using a lot of payouts in that transaction or the wallet is over charging you (yes core gets it wrong also)

Anyway, no I've not finished going through all this yet and I'll be back working on the payout changes after I complete this share checking work.
full member
Activity: 228
Merit: 100
Mine ON!!!
one more S9 online
LETS GO!!!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
... and a possibly useful tool that I posted elsewhere on the forum long ago but use myself for this and have updated in the past also.

It's the PHP code to convert a share difficulty to an approximate of the block hash:

difftoblock.php
Code:
#
function basecvt($str$frombase=10$tobase=16)
{
 
$str trim($str);
 if (
intval($frombase) != 10)
 {
  
$len strlen($str);
  
$q 0;
  for (
$i=0$i<$len$i++)
  {
   
$r base_convert($str[$i], $frombase10);
   
$q bcadd(bcmul($q$frombase), $r);
  }
 }
 else
  
$q $str;

 if (
intval($tobase) != 10)
 {
  
$s '';
  while (
bccomp($q'0'0) > 0)
  {
   
$r intval(bcmod($q$tobase));
   
$s base_convert($r10$tobase) . $s;
   
$q bcdiv($q$tobase0);
  }
 }
 else
  
$s $q;

 return 
$s;
}
#
function bctrim($num0)
{
 if (
strpos($num0'.') === false)
  return 
$num0;
 else
 return 
rtrim(rtrim($num0'0'), '.');
}
#
$diff str_replace(','''$argv[1]);
#
bcscale(1000);
#
$d1_sp '00000000 FFFF0000 00000000 00000000 00000000 00000000 00000000 00000000';
$d1_16 str_replace(' '''$d1_sp);
$d1_0 basecvt($d1_161610);
$d1_10 bctrim($d1_0);
#
$blk0 bcdiv($d1_10$diff);
$blk10 bctrim($blk0);
$blk16 basecvt($blk101016);
#
echo "diff=$diff\n";
echo 
"d1_16=$d1_16\n";
echo 
"blk10=$blk10\n";
echo 
"blk16=$blk16\n";
#
?>


It works like this:
Code:
php difftoblock.php 13,515,318,406,575.7

diff=13515318406575.7
d1_16=00000000FFFF0000000000000000000000000000000000000000000000000000
blk10=1994739190006393264211328987798730314111045124329010603.4118662030266775963456011609545381073605519916888689998048069750235059778050017483678112979756202597418432893164811479721865017459961002819477374188976756222446490354830161705531355123156955600591459765919442787026276796065071739050920751191689306882241755009962835324766554057278633589982821943902554137642807938368820659058105948301714646674725398837885180334465403321512266213331074098927544026464234001707213680957296203848893959638481620204022452776577543099321955289028826624308987405471068407670210379333941374893084405700389927434927907741052149912144384095509889985511226758984370371988163870776246813018969189185447847286620387026721495590395226016002561381504112927420444983609219293071249930342105875437563823497137260623462227520906901497102168738067263663510220693569146087249958245458016702391689090364528152624948312485492563873977733867807702954704854580469764421917353429927189806407208134290652114518068541438397536536285324879830325653866928329107454796350791816760757796910377261
blk16=14d377f075e75428ad14f23640ebd7ba03217a409375ab
The blk16 value is sorta the block hash so you search any source of block hashes you have for the first 6 or so characters with eight zeros on the front like so:
0000000014d377

For the linux gurus among, searching the bitcoind debug.log file would be:
grep 0000000014d377 debug.log

And my result of that on one of the node bitcoinds is:
Code:
2017-10-15 16:46:33.487916 UpdateTip: new best=00000000000000000014d377f075e7632439a087256b4dea039235fa2d90769c height=489987 version=0x20000000 log2_work=87.285942 tx=262350214 date='2017-10-15 16:46:07' progress=1.000000 cache=66.3MiB(37539tx)

So that shows block height=489987 for that diff value

and checking on blocktrail shows that is our block:
https://www.blocktrail.com/BTC/block/489987
hero member
Activity: 756
Merit: 501
Now that the panic has subsided; Kano can you get your payments system working?

Since the Core fanatics seem determined to abort the 2x block size increase into another stupid fork, we will continue to not have a scaling solution.  These tiny inputs are killing me, and we are a pretty huge miner on your pool.  I can't see how most folks can even spend what they are getting from your per block payments.

I sent a transaction from a mining address last week and even manually setting the fee to a bare minimum, it cost $170 to process the transaction.  If I had used the recommended fee it would have cost over 1 BTC! 
member
Activity: 68
Merit: 10
I'm pushing ~60 TH of ~ 60 PH now Smiley
newbie
Activity: 23
Merit: 0
Another noob question..
Do we get any benefit from the shares we're making now? I mean without a block being found
Your shares are what you get rewarded for - nothing else Smiley

When the pool finds a block, your reward from that block is the value of the shares you submitted in the last 5Nd vs the total submitted by everyone in the 5Nd.
(as it says on the Help->Payouts web page)
Awesome!
Thanks for making such a great pool
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Another noob question..
Do we get any benefit from the shares we're making now? I mean without a block being found
Your shares are what you get rewarded for - nothing else Smiley

When the pool finds a block, your reward from that block is the value of the shares you submitted in the last 5Nd vs the total submitted by everyone in the 5Nd.
(as it says on the Help->Payouts web page)
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
sorry for being negative  
but here comes the block from hell again
please let me be wrong

Cheer up my man!  We are only at 29.83% and every block is expected to be at 100% Cheesy


This is true
29.83 x 30 = 895. So you are way too early to call falling skys

Please explain that math. For us noobs

+1
The "Shares:" % on the web page is the number that matters when deciding if it is below or above expected.

At the moment we are at 44% with the current block, so that's still below expected average, but of course we haven't found the next block yet.

Then of course there's the CDF table to consider - we should expect to average about 2/3 of blocks below average 100% and about 1/3 of blocks above 100%
That's also why looking back at history for e.g. the last 500 blocks, we are still ahead of the average expected 100% even including these 2 nightmare blocks.
That 2/3 below makes up the average for the bad high % blocks that appear every so often.
It's just unfortunate that the 2 worst blocks of all time came in so close together
(though as I've said I'm checking lots of data to ensure everything is still ok)

Time is only a factor when the pool isn't expected to find quite a few blocks every diff change - about every 2 weeks -
otherwise, you don't look at the time, you look at the "Shares:" %

If we expect, on average, to find a block every 1.2 days (at the moment) then a 200% block would be 2.4 days, but from the CDF table, we expect, on average, one in every 7.4 blocks to be over 200%

Edit: and for anyone wondering ... the CDF values for those two blocks, to a few more decimal places are:
875.193% 0.99984
928.788% 0.99991
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
BLOCk!
Quiet here Smiley
Block by schmokeandapancake Smiley
... and the anime shift was Ichiko ... hmmm is there a pattern here Cheesy
https://vignette2.wikia.nocookie.net/binbougamiga/images/a/a8/Episode_02.jpg/revision/latest?cb=20121118024752

Pattern = my miners like busty anime characters?

and as far as: "...Anyone else here of course if you have time to do it and can, please check your miners.
What I'm looking for is a miner with a "Best Share" above Network Difficulty 1,196,792,694,098..."

I have some but may be older than this streak (miners have > 250 days of uptime) so i'll send by PM
Well in your case you certainly will have some blocks in there Smiley
If they have a long up time, then even 11 or 12 digit "Best Share" would be good for the checking I'm doing.
It's of course shares that "should" be blocks, and the network difficulty at the time the "block" was found.
newbie
Activity: 5
Merit: 0
BLOCk!
Quiet here Smiley
Block by schmokeandapancake Smiley
... and the anime shift was Ichiko ... hmmm is there a pattern here Cheesy
https://vignette2.wikia.nocookie.net/binbougamiga/images/a/a8/Episode_02.jpg/revision/latest?cb=20121118024752

Pattern = my miners like busty anime characters?

and as far as: "...Anyone else here of course if you have time to do it and can, please check your miners.
What I'm looking for is a miner with a "Best Share" above Network Difficulty 1,196,792,694,098..."

I have some but may be older than this streak (miners have > 250 days of uptime) so i'll send by PM
full member
Activity: 658
Merit: 118



I think Bitmain's contact database was compromised.  

M

Yep - happened a couple months back. Bitmain sent out emails and urged everyone to change their password.
legendary
Activity: 1540
Merit: 1001
I deleted it rather quickly after I received it this morning...  Tongue
I suspect it's a repercussion of the BiteMe hack some time ago when they lost a lot of customer info.  I had to reset my password for them after it happened, as did many others.  Oh well... Mine on!!  Wink
Ah, yeah...I'd forgotten about that one. This is from a Chinese origin, FWIW. I'm deleting it also...just wanted to ask. It affirms the assertion in the mail that they actually have it.

What I want to know is why we are all getting the same junk e-mail.  Who sold our e-mail addresses from this Bitcoin Forum?  I have never been part of any forum, group or anything onlone before where suddenly the members were all getting the same junk mail.  This forum is what we all have in common, so I fear that it is compromised.

I think Bitmain's contact database was compromised. 

M
Jump to: