Gleb Gamow
In memoriam
VIP
Legendary
 Offline
Activity: 1428
Merit: 1145
|
 |
July 04, 2015, 03:47:59 AM |
|
We are so fucked
Edit: someone tell me its all going to be ok.
It's all goin' be...  |
|
|
|
|
Shogen
Legendary
Offline
Activity: 966
Merit: 1001
|
|
July 04, 2015, 03:52:23 AM |
|
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.
|
|
|
|
HerbPean
Legendary
Offline
Activity: 1638
Merit: 1005
|
|
July 04, 2015, 03:53:19 AM |
|
F2Pool blocks are now all Orphaned.
|
|
|
|
|
jonald_fyookball
Legendary
Offline
Activity: 1302
Merit: 1004
Core dev leaves me neg feedback #abuse #political
|
|
July 04, 2015, 03:53:53 AM |
|
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 |
|
|
|
coinableS
Legendary
Offline
Activity: 1442
Merit: 1179
|
|
July 04, 2015, 03:55:38 AM |
|
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.
|
|
|
|
OROBTC
Legendary
Offline
Activity: 2912
Merit: 1852
|
|
July 04, 2015, 03:56:06 AM |
|
...
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?
|
|
|
|
|
Quantus
Legendary
Offline
Activity: 883
Merit: 1005
|
|
July 04, 2015, 03:58:11 AM |
|
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?
|
(I am a 1MB block supporter who thinks all users should be using Full-Node clients) Avoid the XT shills, they only want to destroy bitcoin, their hubris and greed will destroy us. Know your adversary https://www.youtube.com/watch?v=BKorP55Aqvg |
|
|
jonald_fyookball
Legendary
Offline
Activity: 1302
Merit: 1004
Core dev leaves me neg feedback #abuse #political
|
|
July 04, 2015, 03:59:07 AM |
|
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. |
|
|
|
Shogen
Legendary
Offline
Activity: 966
Merit: 1001
|
|
July 04, 2015, 04:02:01 AM |
|
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.
If you are using bitcoin core older than 0.9 or older, you should upgrade to 0.10 or newer. If you have contacts with miners still mining v2 blocks or not rejecting v2 blocks, you could ask them to upgrade as well. ...
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?
You could use blocktrail.com or btc.blockr.io. They are correctly rejecting v2 blocks AFAIK. |
|
|
|
ajareselde
Legendary
Offline
Activity: 1722
Merit: 1000
Satoshi is rolling in his grave. #bitcoin
|
|
July 04, 2015, 04:02:23 AM |
|
Both blockchain and blocktrail are now reporting identical blocks from block 363737, and transactions seam to be passing through.
I'm interested to know what will happen to the transactions from few block before that?
cheers
|
|
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 04:11:01 AM |
|
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. You are both right. One Mining pool which mined an invalid block was picked up by other pools who do not verify as they are "SPV mining" . The reason f2Pool and Antpool among others SPV mine instead of fully validate is for a slight~1% edge in latency which does indicate that larger blocks do have an impact upon the economics of mining. |
|
|
|
|
OROBTC
Legendary
Offline
Activity: 2912
Merit: 1852
|
|
July 04, 2015, 04:11:36 AM |
|
... AntPool just put up another "bad one", selfish bastids... Block 363741. Whee... (?) Penalty box for miners who do that? But with everything so de-centralized, how would THAT work? EDIT: Thanks, BitUsher, that explains something for me.  |
|
|
|
|
jonald_fyookball
Legendary
Offline
Activity: 1302
Merit: 1004
Core dev leaves me neg feedback #abuse #political
|
|
July 04, 2015, 04:13:22 AM |
|
...
AntPool just put up another "bad one", selfish bastids... Block 363741. Whee... (?)
Penalty box for miners who do that? But with everything so de-centralized, how would THAT work?
people will start leaving the pool if they keep up those shenanigans. |
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 04:24:28 AM |
|
Current status: F2Pool still broken; Antpool fixed (but no promise they won't intentionally re-break in the future).
|
|
|
|
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 04:31:04 AM |
|
That is actually on the correct chain... Take a look. Antpool appear to have a safeguard to not include transactions under certain conditions as well. |
|
|
|
|
OROBTC
Legendary
Offline
Activity: 2912
Merit: 1852
|
|
July 04, 2015, 04:35:37 AM |
|
... BitAmigos Well, this has been perhaps my most exciting Friday night looking at BTC transactions. But, maybe the excitement is over, for now. I have seen unflattering references to AntPool landing a lot of blocks with just their win as the only transaction. This kind of thing why I (as a non-tekkie) have no interest in trying to mine BTC, too complicated. * * * OK, back to my Lee Child book... |
|
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 04:38:21 AM |
|
Nice... I just got the warning in core from the Alert Key. May have been Theymos responding to my IM, or Gavin noticing.
"Your node software is out of date and may accept an invalid blockchain fork. Do not trust confirmations. "
The odd thing is that I received this message on 0.10.0rc1 which is supposed to be safe In this instance. I'm going to update and see if the alert is removed.
edit **** warning was just changed to --
" Warning: This version is obsolete, upgrade required!"
|
|
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 04:44:00 AM |
|
Someone just used the alert key. "Your node software is out of date and may accept an invalid blockchain fork. Do not trust confirmations" I have 0.10.1, how can that be right  Latest version is 0.10.2. I don't know if that has anything to do with it or not. I'm guessing its a blanket statement for all old versions, even though 0.10.0 is technically safe |
|
|
|
|
BitUsher
Legendary
Offline
Activity: 994
Merit: 1034
|
|
July 04, 2015, 05:05:31 AM |
|
Another update from Peter Todd:
"The majority of hashing power is now mining only valid blocks. However, SPV wallets are still vulnerable as they do no validation, and ~4% or so of hashing power is still mining invalid blocks. Don't trust txs in SPV wallets w/o >= 2 confirmations right now."
FYI-- no alert message with 0.10.2 now that I upgraded to test this node.
|
|
|
|
|
|
