KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 876.

oawan

member

Activity: 67

Merit: 10

Quote from: bronder on August 08, 2017, 10:59:19 AM

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

It looks like not very much went over to bitcoin cash and even more than that amount has been brought online in the last 2 weeks as there is still an expected diff increase of 8.12% in 17 hours.

bronder

newbie

Activity: 48

Merit: 0

So with the hashing power lost that went over to bitcoin cash, it means that in average for the network it should be taking a bit more time to mine those 12.5 bitcoins until a network difficulty update comes over. So the flow of new bitcoin will be slowed down until network diff adjustment, right?

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

The mining code is ckpool.
For this update I've just done a few changes as mentioned above (and rolled forward to the current ckpool git ... that failed)

Seems the node code can't handle a pool version update Tongue

It may need a complete restart of everything.
I'll do some node<->pool testing and work out what's up with that - I was more concerned about block code, and I tested that thoroughly - didn't expect a network protocol problem.
Weird, coz some of the nodes are current code also. As I said ... more work to do

Everything else is my KanoDB
That's the name for the updated closed source version - so no one has any wrong ideas about who wrote almost all of it Tongue

The CKDB in the public ckpool git (that I got thrown out of) works fine for a single pool and can handle a few hundred PH - but has no support at all.

A few pools use it: Ver's bitcoin.com did (no idea if they still do) BitClub does, so does LinuxJounal
There's 1 other I know of but I wont mention their names since:
they removed my copyright off the web site and replaced it with their own copyright ... scumbags

Mine on

voodooman

newbie

Activity: 41

Merit: 0

Updating suckz Grin

Hope you'll find the faulty codesnipped soon!

Is there a posting somewhere out here where you explain how the pool is build up?
Which programming language, which hardware you use etc...?
No details about the code or hardware but maybe some infos about.

I don't wanna build up a pool but i'm coding every now and than some stuff.
So I'm a bit curious bout all this pool stuff. Cheesy

You're doing a great job kano! I like the pool you build!
Your avarage working time seems to be nearly 24/7/356 ...RESPECT! Grin

Don't waste your time with morons trying to annoy you. Wink

I think you have to do much more important stuff.

Mine ON guys.

MEARK

newbie

Activity: 19

Merit: 0

Quote from: kano on August 08, 2017, 07:10:33 AM

Quote from: ?? on ??

There'll be a pool restart at 12:00 UTC in half an hour.

It will mean a failover and an immediate failback for ALL miners.

This is an update of the mining pool code to include segwit transactions in our work (since they clearly have been working on the network for a while now) and a fix for the deadlock long ago back in Feb Tongue

I've also added a log dump of the block information so I can find out what these valid 'inconclusive' blocks we are getting are.

Unfortunately the update failed dismally Sad

I switched back to the old code again and all is OK again.

Total outage was 2 minutes.
I terminated the pool at 21:59:56, but then had to switch back to the old code, all nodes had reconnected by 22:01:51 so miners would have failed back from then.

More work to do.

Good luck Kano and thanks for all that you do!

clgrissom3

legendary

Activity: 1736

Merit: 1032

Carl, aka Sonny :)

Quote from: kano on August 08, 2017, 05:44:09 AM

Block!

by jotun

Nice Job! This is our 3rd of BLOCK TUESDAY! Cheesy

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ?? on ??

There'll be a pool restart at 12:00 UTC in half an hour.

It will mean a failover and an immediate failback for ALL miners.

This is an update of the mining pool code to include segwit transactions in our work (since they clearly have been working on the network for a while now) and a fix for the deadlock long ago back in Feb Tongue

I've also added a log dump of the block information so I can find out what these valid 'inconclusive' blocks we are getting are.

Unfortunately the update failed dismally Sad

I switched back to the old code again and all is OK again.

Total outage was 2 minutes.
I terminated the pool at 21:59:56, but then had to switch back to the old code, all nodes had reconnected by 22:01:51 so miners would have failed back from then.

More work to do.

philipma1957

legendary

Activity: 4382

Merit: 9330

'The right to privacy matters'

Quote from: kano on August 08, 2017, 05:44:09 AM

Block!

by jotun

nice we need to keep them coming

Monthly Statistics

UTC Month.........Pool Avg,,,,,,,Blocks.........Expected.......Mean Diff%,,,,,,,,MeanTx%.......Luck%.....PPS%
2017 Aug........…79.80PHs,,,,,,14..............16.26,,,,,,,,,,,,116.12%...........105.42%........86.12%....89.97%

we have to get three by the end of the day to be ahead for the month Grin

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Block!

by jotun

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: usernamehere on August 08, 2017, 01:39:38 AM

Quote from: kano on August 08, 2017, 01:17:02 AM

Quote from: usernamehere on August 08, 2017, 12:48:43 AM

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in Tongue

BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool

(it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also

Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

I reached out to him on twitter to change it.

Thanks!

usernamehere

member

Activity: 85

Merit: 10

Quote from: kano on August 08, 2017, 01:17:02 AM

Quote from: usernamehere on August 08, 2017, 12:48:43 AM

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in Tongue

BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool

(it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also

Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

I reached out to him on twitter to change it.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: usernamehere on August 08, 2017, 12:48:43 AM

100 blocks left until SegWit locks in! https://xbt.eu

Hmm ... well ... segwit is already locked in Tongue

BIP91 did that.

If you happen to have twitter (no I don't and never will) get them to fix the pool name if you can.
It's KanoPool

(it says it there in the coinbase so they shouldn't require any verification ...)
At least you see the cat there also

Blocktrail doesn't show the UTF-8 symbols, btc.com does though.

NomadGroup

sr. member

Activity: 508

Merit: 250

Quote from: kano on August 07, 2017, 10:15:44 AM

Well ... this way you get them faster ... ...
I mentioned before that I'll continue it while it keeps working ... i.e. the payouts contine to be confirmed faster

Cool! Thanks Kano! Sure works for me!

usernamehere

member

Activity: 85

Merit: 10

100 blocks left until SegWit locks in! https://xbt.eu

oawan

member

Activity: 67

Merit: 10

Quote from: kano on August 07, 2017, 11:24:19 PM

Quote from: oawan on August 07, 2017, 11:08:39 PM

Quote from: kano on August 07, 2017, 04:18:14 PM

Quote from: oawan on August 07, 2017, 11:06:32 AM

Quote from: kano on August 07, 2017, 10:15:44 AM

Well ... this way you get them faster ... ...
I mentioned before that I'll continue it while it keeps working ... i.e. the payouts contine to be confirmed faster

It's also more efficient. Because if we get even a moderately decent time block like 10 min since previous, we probably end up earning an extra $~30 in TX fees for the space that would have been taken up by one payout.

Well that might have been the case for a while before when fees were high, and blocks were full, (and the price was lower) but blocks are now filling up with zero or almost zero fee transactions, so our payouts don't push much out off the end

BLOCK! by pangborn

And by my calculations the lowest fee in that block was ~93 sat/byte. 4 payouts would have displaced 0.10416 BTC or $357. So that was ~$6 well spent!

It was a 21minute network block, so it had twice as long to throw out cheap transactions and replace them with more expensive ones as they came out on the network.

That's also why the tx fees are high 13.98 BTC block (yes that's now considered high)

However ... 93 sat/byte wasn't the lowest ... e.g. the last transaction in the block was 6.57 sat/byte and I'm not 100% sure of the ordering i.e. is it lowest last? I've never checked

Edit: no it's not ordered highest to lowest fee/byte, the 2nd last one was 268 sat/byte

Interesting. I wonder if there is a tool to determine the lowest fee transactions in blocks. It would seem the 6.57 sat/ byte transaction was some kind of anomaly or something since it looks like according to this https://jochen-hoenicke.de/queue/#2h the block at 20:52 didn't quite break into the blue 80-100 layer.

oawan

member

Activity: 67

Merit: 10

been waiting for a back to back for awhile. Nice time to have some fatties!

tbonetony

sr. member

Activity: 441

Merit: 250

No zuo no die why you try, u zuo u die dont be shy

back to back blockieeeeeeeeeeeeeeeeeeeeeeeeees Tongue

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Wooo double! Cheesy

2nd block by jimmy Cheesy

Awesome - 40 minute block - 14.209116 BTC

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: oawan on August 07, 2017, 11:08:39 PM

Quote from: kano on August 07, 2017, 04:18:14 PM

Quote from: oawan on August 07, 2017, 11:06:32 AM

Quote from: kano on August 07, 2017, 10:15:44 AM

Well ... this way you get them faster ... ...
I mentioned before that I'll continue it while it keeps working ... i.e. the payouts contine to be confirmed faster

It's also more efficient. Because if we get even a moderately decent time block like 10 min since previous, we probably end up earning an extra $~30 in TX fees for the space that would have been taken up by one payout.

Well that might have been the case for a while before when fees were high, and blocks were full, (and the price was lower) but blocks are now filling up with zero or almost zero fee transactions, so our payouts don't push much out off the end

BLOCK! by pangborn

And by my calculations the lowest fee in that block was ~93 sat/byte. 4 payouts would have displaced 0.10416 BTC or $357. So that was ~$6 well spent!

It was a 21minute network block, so it had twice as long to throw out cheap transactions and replace them with more expensive ones as they came out on the network.

That's also why the tx fees are high 13.98 BTC block (yes that's now considered high)

However ... 93 sat/byte wasn't the lowest ... e.g. the last transaction in the block was 6.57 sat/byte and I'm not 100% sure of the ordering i.e. is it lowest last? I've never checked

Edit: no it's not ordered highest to lowest fee/byte, the 2nd last one was 268 sat/byte

oawan

member

Activity: 67

Merit: 10

Quote from: kano on August 07, 2017, 04:18:14 PM

Quote from: oawan on August 07, 2017, 11:06:32 AM

Quote from: kano on August 07, 2017, 10:15:44 AM

Well ... this way you get them faster ... ...
I mentioned before that I'll continue it while it keeps working ... i.e. the payouts contine to be confirmed faster

It's also more efficient. Because if we get even a moderately decent time block like 10 min since previous, we probably end up earning an extra $~30 in TX fees for the space that would have been taken up by one payout.

Well that might have been the case for a while before when fees were high, and blocks were full, (and the price was lower) but blocks are now filling up with zero or almost zero fee transactions, so our payouts don't push much out off the end

BLOCK! by pangborn

And by my calculations the lowest fee in that block was ~93 sat/byte. 4 payouts would have displaced 0.10416 BTC or $357. So that was ~$6 well spent!

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