Author

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

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Thanks for the explanation, had no idea they were using "more stricter policy" compared to "usual/other nodes" if such a concept as usual node even exists Cheesy

Shame to know that blockchain is implementing such a harsh policy though..
Once a transaction is mined into the blockchain, provided it's still a valid transaction, then there's no valid reason for bitcoin nodes to reject the transaction since it's part of a block.
newbie
Activity: 41
Merit: 0
Thanks for the explanation, had no idea they were using "more stricter policy" compared to "usual/other nodes" if such a concept as usual node even exists Cheesy

Shame to know that blockchain is implementing such a harsh policy though..
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hmm when trying to view the transactions via blockchain.info it gives this error on both transactions: "Transaction rejected by our node. Reason: The Maximum number of outputs in a single transaction is 250"

But I guess it will still come through ?
They always say that, but then they're only one bitcoin node and fortunately most other nodes and mining pools don't impose such restrictions, and that's what will determine whether the transaction gets propagated. That's the advantage of a peer to peer network rather than blockchain.info being the central authority for bitcoin (which it isn't).
newbie
Activity: 41
Merit: 0
Hmm when trying to view the transactions via blockchain.info it gives this error on both transactions: "Transaction rejected by our node. Reason: The Maximum number of outputs in a single transaction is 250"

But I guess it will still come through ?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payouts 384072 and 384086 sent
5285bad7abc63989cf2fb8549f6bee5af6a516f64311d8fe8b32193034a59268
87e070db824685ae5a9e0a01a489277ffc270935bfcba9df6e317254595d7e66
(but not confirmed yet)

and a block when I was processing them Wink
legendary
Activity: 1274
Merit: 1000
time to sleep when I awake there will be two more blocks

Did you wake up yet?  Or did you happen to sleep for two days?  Because you came pretty close to calling these last two blocks.  Whatever you did, do it again please.  Cool
hero member
Activity: 742
Merit: 500
Finished all the eggs I had, yesterday.
I better go buy some more Smiley

buy more eggs!

everybody buy eggs!!! Shocked

 Grin
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Back to back blocks!  Cool!
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Finished all the eggs I had, yesterday.
I better go buy some more Smiley
legendary
Activity: 2338
Merit: 1124
Block!

Guess who had chicken, hmmm?

Will we get more blocks if I eat duck?
hero member
Activity: 777
Merit: 1003
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
thank you sir may I have another
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Payout 383851 sent
94ba355695531a53056dfdf5dd85d59bc02c0d11df9eb295f495a2241e126efd
and confirmed
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
time to sleep when I awake there will be two more blocks
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
a little over 10 minutes to confirmations with network hash rate at 592+ Ph/s
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Connections went down all over the net 20 minutes ago and started to recover but then dropped again.
I restarted ckpool 10 minutes ago and all has been OK since.

Edit: there was a 2nd lot of disconnects/dropouts about 20 minutes later, but all has been OK since.
Cause was the data centre but no details about exactly why yet - but it's been OK ever since.
Switched all bitcoinds over to v4 blocks (0.11.2) last night.
v4 block Smiley
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Last payout was sent and confirmed about 2 hrs ago (but I couldn't get on to the forum Tongue)

Payout 383318 sent
171b62672b83dd71a8115c8b05e1485ce1319d42d2115e34d1fddbd9b1cca0c1

The changes last night and some more bitcoind code changes from -ck seem to have reduced the block change times a little more again Smiley
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
I had a short blackout at home due to thunder/lightning just to add a little excitement to it.

 Undecided

I saw the block, then my computer blip out and reboot....

Some times in the past that happend during work, so I desided to check the PSU.

This 500W China thing is 3 years old and no supprise one of the cap's was brocken.
A quick repair and a routine "dust" maintanace was carried out and I hope it runs now for a while.

Usaly that happen's on Saturday/Sunday or Bank Hollydays but: it is friday the 13 (I forgot to point that out as well).

 Grin
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Will do a ckpool restart in the next 5 minutes.
As usual for a ckpool restart there should be minimal failover - only miners that can't reconnect within the 30 seconds of the restart will failover
For most is should just show as a reconnect message in cgminer

A few minor ckpool updates since the last time (15 days) - including the worker stats change -ck did for solo.
Also a change in the backend bitcoin startup configuration which I hope will (yet again) be another gain in block change performance.

Edit: all done.
Jump to: