has nothing to do with core.  Its antpool alone.. If they would just stop mining empty blocks.. 25 in the last week alone.. then you wouldnt have this problem.   Get the miners to do whats its required to do to participate or find a way in the next release of bitcoin core to block miners that submit empty blocks. Once everyone gets with the program then and only then if the blocks are still full you may have a leg to stand on..

Best Regards
d57heinz


Now whats going to happen when the block size goes to 2 mb? .. I only imagine block propagation getting much much worse.  not that it isnt already.  I cant imagine doubling the bandwidth required is the fix.>  Seems to me its the opposite.. More of a crippling effect if the large pools are the only ones able to process the blocks.. And ive seen some pools take a minute to even see the blocks once they are found. (Hell look at slush right now.  https://poolbench.antminer.link/  if you look at the bottom you see that slush stratum (with the most hash no less https://slushpool.com/stats/) takes over 30 seconds(us-east) for a block notification.. So that means on every block for 30 seconds over 22 ph is mining into the wind.  Jeez wonder whats wrong???)> So does that mean now that will take 1 min?? or more?.  Thats great we will all be mining into the wind for 10 % of every block while the bitcoind waiting for nodes to pass along the info of new block finds.  2 mb blocks wont work if decentralization is one of bitcoin key attributes.> But i can imagine if people start losing money over this .. Soon it will be "ok" to centralize.. Just stop the bleeding right?.. 


Those of you mining on the us-east stratum .. do you have an abnormally high amount of rejects?.. Also what effect does the 30 seconds of half the pool mining on old blocks do to the luck?.. 

Best regards
d57heinz

Rejected from blockchain.info doesn't mean anything.  Look at that same transaction here: https://www.blocktrail.com/BTC/tx/f4af45f69d6ab6bbf8943e8e242e466c6b351f4521ced77fda22e302c3dd78c1

As for the unconfirmed status of the two... well, that's because there weren't enough fees to entice miners to include the transactions in blocks.  In "normal" situations, the fee he supplied is fine at 0.0001 per kb.  However, the mempool is currently flooded with over 30k transactions, so the ones getting confirmed are the ones with higher fees.

If only pools would stop mining empty blocks... looks at AntPool.

The transaction itself is still unconfirmed and has been broadcast.  Take a look at it.  Do you see your wallet address in it?  If yes, then when it confirms, the balance will appear in your wallet.  The question is whether or not slush continues to broadcast that transaction, or if he stopped.  If he stopped, then it is typically 72 hours before the network forgets about it.  If that happens, slush will have to resend the transaction (hopefully with higher fees).

i am still at 18+ hours and waiting on my deposit to show up at nicehash showing 0/2 conformations..

Icon

The new stats page:
https://beta-mining.bitcoin.cz/stats/

Vote for BIP109, for increasing the blocksize to two megabytes, for scaling Bitcoin directly as was always intended.

i have saved all my tx not confirmed on a txt doc

Problem with the confirmation left



- 400 802 %    

Ya mine finally posted after 24+ hours late, good thing i didn't really need my own BTC back or anything...

Icon