Payout 384195 sent (2hrs ago)
a434ef83f110fe936221168a0e26c76e9697189544d285d9c8bc59482ca8d0ba
and confirmed (just now)
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1986. (Read 5352429 times)
November 19, 2015, 08:23:12 AM
November 18, 2015, 04:10:21 PM
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 ?
Yes.But I guess it will still come through ?
Also, blocks have been full most of the time since I did the payout so they haven't been confirmed by anyone else yet.
They will confirm
Worst case scenario is that we have to wait until our next block ... I use the bitcoin priority command to help ensure they're in our mining work.
That rarely happens that we confirm them though, coz we don't find many block each day and someone else usually confirms it a lot faster
(most payouts confirm within only a few blocks, often the next block after I send them)
Yep this one is a slow (2 payouts) to confirm.
November 18, 2015, 04:01:42 PM
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
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. Shame to know that blockchain is implementing such a harsh policy though..
November 18, 2015, 04:00:26 PM
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
Shame to know that blockchain is implementing such a harsh policy though..
Shame to know that blockchain is implementing such a harsh policy though..
November 18, 2015, 03:50:55 PM
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). But I guess it will still come through ?
November 18, 2015, 03:48:59 PM
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 ?
But I guess it will still come through ?
November 18, 2015, 02:33:45 PM
Payouts 384072 and 384086 sent
5285bad7abc63989cf2fb8549f6bee5af6a516f64311d8fe8b32193034a59268
87e070db824685ae5a9e0a01a489277ffc270935bfcba9df6e317254595d7e66
(but not confirmed yet)
and a block when I was processing them
5285bad7abc63989cf2fb8549f6bee5af6a516f64311d8fe8b32193034a59268
87e070db824685ae5a9e0a01a489277ffc270935bfcba9df6e317254595d7e66
(but not confirmed yet)
and a block when I was processing them
November 18, 2015, 01:12:28 AM
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.
November 17, 2015, 11:14:33 PM
Finished all the eggs I had, yesterday.
I better go buy some more
I better go buy some more
buy more eggs!
everybody buy eggs!!!
November 17, 2015, 09:50:57 PM
Back to back blocks! Cool!
November 17, 2015, 09:11:43 PM
Finished all the eggs I had, yesterday.
I better go buy some more
I better go buy some more
November 17, 2015, 09:04:39 PM
Block!
Guess who had chicken, hmmm?
Will we get more blocks if I eat duck?
November 17, 2015, 08:52:00 PM
November 17, 2015, 08:48:29 PM
thank you sir may I have another
November 17, 2015, 06:32:24 PM
Block!
November 16, 2015, 10:48:00 PM
Payout 383851 sent
94ba355695531a53056dfdf5dd85d59bc02c0d11df9eb295f495a2241e126efd
and confirmed
94ba355695531a53056dfdf5dd85d59bc02c0d11df9eb295f495a2241e126efd
and confirmed
November 16, 2015, 10:18:28 PM
time to sleep when I awake there will be two more blocks
November 16, 2015, 07:43:33 AM
a little over 10 minutes to confirmations with network hash rate at 592+ Ph/s
November 16, 2015, 07:28:56 AM
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.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.
November 13, 2015, 07:23:30 PM
Last payout was sent and confirmed about 2 hrs ago (but I couldn't get on to the forum 
)
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
)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
Jump to: