If 1 MB blocks are already to big for mining farms to validate properly won't 8mb blocks just slow down the network even more?
It wasn't the size that was the issue here. The pool wasn't keeping updated with all the BIPs.
Topic: Blockchain split of 4 July 2015 - page 24. (Read 45630 times)
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
It wasn't the size that was the issue here. The pool wasn't keeping updated with all the BIPs.
If 1 MB blocks are already to big for mining farms to validate properly won't 8mb blocks just slow down the network even more?
...
And WHAT has happened to all the transactions that occurred during that time frame? Do they all get recorded in new blocks? Block 363737 only has some 166 trx listed.
Maybe other tools are better than blockchain.info?
Is there a way to see recently orphaned blocks?
And WHAT has happened to all the transactions that occurred during that time frame? Do they all get recorded in new blocks? Block 363737 only has some 166 trx listed.
Maybe other tools are better than blockchain.info?
Is there a way to see recently orphaned blocks?
Is there something us users can do to help this issue? If I launched my full node and started validating transactions would this help, not help this issue? This seems serious.
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
The correct fork now gets to block 363737 and the problem is solved for now. But if another v2 block is created while Antpool and F2Pool failing to reject it, we could have another fork then.
so it was a 6 block orphan chain
F2Pool blocks are now all Orphaned.
The correct fork now gets to block 363737 and the problem is solved for now. But if another v2 block is created while Antpool and F2Pool failing to reject it, we could have another fork then.
We are so fucked
Edit: someone tell me its all going to be ok.
Edit: someone tell me its all going to be ok.
It's all goin' be...
blockchain.info and blocktrail.com are on different chains, this may be proof we really do have a fork.
BIP66 is enforced in block 363275, and since then v2 block should be considered invalid.
BTC Nuggets created a v2 block 363731, but Antpool, F2Pool, and bc.i doesn't not reject it and hence they are now on the wrong fork.
We are so fucked
Edit: someone tell me its all going to be ok.
Edit: someone tell me its all going to be ok.
...
Been over 30 minutes since the 5 suspicious blocks...
Um, an interesting way to spend a Friday night?
* * *
turtlehurricane, a PM for you. That phone number of yours seems to place you near me.
EDIT: Has anyone checked the other blockchain tools? blockexplorer appears to be down / not working.
Been over 30 minutes since the 5 suspicious blocks...
Um, an interesting way to spend a Friday night?
* * *
turtlehurricane, a PM for you. That phone number of yours seems to place you near me.
EDIT: Has anyone checked the other blockchain tools? blockexplorer appears to be down / not working.
So many people are going to get scammed tonight with fake transactions.
So the Chines miners are creating invalid blocks but smart phone wallets and even website wallets can't tell they are invalid?
Yes
Interesting test case for alert being sent out to older version of Bitcoin Core to warn users.(Prior to 0.10). I have various cores installed on different computers and do not see the alert on any of them.
As far as I am aware 3 people have alert keys - Gavin, Satoshi, and Theymos. Why isn't an alert being sent out?
As far as I am aware 3 people have alert keys - Gavin, Satoshi, and Theymos. Why isn't an alert being sent out?
So the Chines miners are creating invalid blocks but smart phone wallets and even website wallets can't tell they are invalid?
...
Just saw that myself at blockchain.info and came over here for an explanation, right place!
Chinese miners ought to take care not to screw the pooch through selfishness or whatever.
Very unusual things happening are often a bad sign. I will not do ANY transactions until we get some clarity.
Just saw that myself at blockchain.info and came over here for an explanation, right place!
Chinese miners ought to take care not to screw the pooch through selfishness or whatever.
Very unusual things happening are often a bad sign. I will not do ANY transactions until we get some clarity.
I am using Bitcoin Core (old version, yes I am lazy and paranoid). So basically you are saying if I start my wallet now and it update blockchain it will be corrupted and I will lose access to my coins?
You run a risk of losing your coins if you perform a transaction at the moment on anything but Bitcoin Core 0.10.0 or newer. Starting up your wallet is fine though.
If you are using Bitcoin Core 0.10.0 or newer you will be safe for performing txs at the momment
More info plz
Check http://www.reddit.com/r/Bitcoin/comments/3c2cfd/psa_f2pool_is_mining_invalid_blocks/ to get a rough idea of what happened.
BTW, did something like this happen when the BIP 34 soft fork was done?
F2Pool is building on a wrong side and there is fake confirmation since block 363731.
If you use light weight wallet or with old version of Bitcoin Core, you should stop accept bitcoin for a moment
I am using Bitcoin Core (old version, yes I am lazy and paranoid). So basically you are saying if I start my wallet now and it update blockchain it will be corrupted and I will lose access to my coins?If you use light weight wallet or with old version of Bitcoin Core, you should stop accept bitcoin for a moment
No. All the transaction confirmed before the fork happened (in block 363731) is safe.
legendary
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
Is this for real? A fork would be a big deal.
why is it a big deal? don't orphan chains happen regularly and get resolved ?
No direct evidence of that yet though, could be something else.
where are you getting your data that it's not common? blockchain.info charts show thousands of orphan blocks each day. sure most of them are probably single blocks, but show me your data please.
Jump to: