Pages:
Author

Topic: Blockchain split of 4 July 2015 - page 22. (Read 45630 times)

administrator
Activity: 5222
Merit: 13032
July 04, 2015, 03:03:13 AM
#68
I am curious about this as well.  I know the electrum servers are connected directly to bitcoin core nodes, so I imagine it would depend on whether the core version on the individual electrum server is properly updated.

Right, with Electrum it depends on which version of Bitcoin Core your Stratum server is using. AFAIK by default Electrum chooses a random untrusted Stratum server from IRC, so you probably can't (ever) trust that you're getting accurate info.
full member
Activity: 223
Merit: 132
July 04, 2015, 02:59:34 AM
#67
If I use electrum will be any problem?

Thanks

I am curious about this as well.  I know the electrum servers are connected directly to bitcoin core nodes, so I imagine it would depend on whether the core version on the individual electrum server is properly updated.
legendary
Activity: 1134
Merit: 1000
July 04, 2015, 02:57:22 AM
#66
I use a coinbase wallet. is this wallet affected by this problem? Thanks.

you can try to send one transaction with a very small amount, to see if it is affected, but if they have the last version it should be not

Thank you!

And if I will receive btc it is the same problem? Depends everything from the version of they who send btc? If they have not the last version what happen? I must wait to have 30 confirmations? And if these 30 confirmations don't arrive what happen to btc sent?

To many questions but I wait btc from a cloud mining site and must know how to act.

Thanks.
hero member
Activity: 527
Merit: 501
July 04, 2015, 02:57:15 AM
#65
If I use electrum will be any problem?

Thanks
hero member
Activity: 714
Merit: 500
July 04, 2015, 02:56:34 AM
#64
What about bitcoinj. I am using version 0.11-SNAPSHOT.
As far as I know, bitcoinj is just a java library. The problem described here is, if the blockchain you have downloaded is valid. So, which blockchain are you using? On your PC or an external node?

Using the above version in spv mode.
So, that means you are using an external node. You now have to find out, which version the node you are connecting to uses.
If you somehow get the ip-address, you could look it up here:
https://blockchain.info/connected-nodes
legendary
Activity: 3248
Merit: 1070
July 04, 2015, 02:52:46 AM
#63
I use a coinbase wallet. is this wallet affected by this problem? Thanks.

you can try to send one transaction with a very small amount, to see if it is affected, but if they have the last version it should be not
legendary
Activity: 1001
Merit: 1005
July 04, 2015, 02:49:31 AM
#62
What about bitcoinj. I am using version 0.11-SNAPSHOT.
As far as I know, bitcoinj is just a java library. The problem described here is, if the blockchain you have downloaded is valid. So, which blockchain are you using? On your PC or an external node?

Using the above version in spv mode.
legendary
Activity: 1134
Merit: 1000
July 04, 2015, 02:47:44 AM
#61
I use a coinbase wallet. is this wallet affected by this problem? Thanks.
sr. member
Activity: 336
Merit: 251
July 04, 2015, 02:42:56 AM
#60
Thanks for the early warning on this.

Making use of a 'light' client and was going to send off a couple of transactions (+-14) today.

All on hold for now.
legendary
Activity: 1268
Merit: 1006
July 04, 2015, 02:42:12 AM
#59
I love how the problem was essentially fixed by the time I found this thread. The tech community is so efficient
hero member
Activity: 756
Merit: 500
July 04, 2015, 02:37:26 AM
#58
Whats going to happen with coins merge mining with Bitcoin the likes of Unobtanium ?
full member
Activity: 217
Merit: 259
July 04, 2015, 02:36:54 AM
#57
Can someone explain me like i am five. Thanks.

ELI5 is difficult Smiley.  I try for a higher age...

The developers designed a soft fork BIP66 that does not allow some malformed bitcoin transaction (that have a strange signature that may not be accepted by newer versions of openssl).  To make sure that there is only minimal forking, they had some rules accompanied with the fork.

  • Miners vote for the fork by setting version 3 in the block header.
  • Only when 75 % of the miners vote, the change has any effect at all
  • When 95 % of the miners vote, the new client ignores all miners voting 2 and orphans them off.

The latter should have produced a few orphans for the 5 % that didn't update.  However, it looks like f2pool and antpool just voted by setting version 3 but did not implement the rules of the fork, at least not the last one.   They built a fork on top of a block from a miner that didn't update.  Since they have a lot of hashing power they managed to produce a longer fork that was alive for some time before being overtaken by the miners implementing the soft fork correctly.  The effect is that we may see transactions with 6 confirmations that are later double spend.  Also f2pool will loose a lot of blocks since they are orphaned later.

If you have a full node that is updated, you have nothing to worry.  It will just ignore the invalid forks.   If you have a SPV client, it will trust the miners to not do something stupid like this and thus it may be on the wrong side of a fork.  There is a small chance that you see a transaction with a few confirmations that doesn't make it to the 0.10.x chain.
hero member
Activity: 714
Merit: 500
July 04, 2015, 02:33:10 AM
#56
What about bitcoinj. I am using version 0.11-SNAPSHOT.
As far as I know, bitcoinj is just a java library. The problem described here is, if the blockchain you have downloaded is valid. So, which blockchain are you using? On your PC or an external node?
hero member
Activity: 686
Merit: 500
July 04, 2015, 02:32:25 AM
#55
What the hell does that means ? Shocked
How it's possible to make fake transaction , isn't that only possible when you do 51% attack or whatever it's name is  . I guess I'am safe since I'am using the latest version of Bitcoin core however knowing more about this would be nice .
legendary
Activity: 1148
Merit: 1014
In Satoshi I Trust
July 04, 2015, 02:29:50 AM
#54
we are doomed.  Shocked
---


If you're using Bitcoin Core 0.10.0 or newer you are fine!

The majority of hashing power is mining an invalid chain - it's not going to "win" - they're just wasting their effort.

by the way, the problem is already solved



legendary
Activity: 1001
Merit: 1005
July 04, 2015, 02:29:41 AM
#53
What about Bitcoinj. I am using version 0.11-SNAPSHOT. Which fork will this follow? Any help appreciated.
hero member
Activity: 714
Merit: 500
July 04, 2015, 02:24:54 AM
#52
Can someone explain me like i am five. Thanks.
How I understand it:
There is a fork, because some Chinese miners are using an old version. If you use a newer version of Bitcoin Core, it just ignores the invalid fork: No problem there.
But there doesn't seem to be any info about SPV(e.g. Smartphone) wallets.
A fork means, that when you see a transaction confirmed on the invalid chain, it doesn't mean it is confirmed on the valid chain.
But: Nobody can steal your Bitcoin, it is just about, if you can trust, if a transaction is really confirmed.
legendary
Activity: 3248
Merit: 1070
July 04, 2015, 02:15:16 AM
#51
this one of the reason why bitcoin is not accepted everywhere, people feel unsecure with all that shitty fork that can happen..randomly

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 Huh

Latest version is 0.10.2. I don't know if that has anything to do with it or not.

well i'm not getting any warning with the last version

also rc1 is not even a final a complete version
hero member
Activity: 675
Merit: 502
#SuperBowl50 #NFCchamps
July 04, 2015, 01:53:45 AM
#50
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
I did notice that I was waiting for over an hour for a 2 BTC transaction to get confirmed from TC that took ~5 blocks to get confirmed then all of a sudden I saw that it had 8 confirmations (this may have been 3 confirmations later, so it got confirmed on the first block of the longest chain but not the other).

I also noticed that f2pool was mining an unusually large number of 1 tx blocks (only the coinbase tx).....this is obviously speculation, but maybe they were trying to do something malicious.

IMO this is very interesting. I don't think I have been around since we have seen a reorg of this magnitude. 
staff
Activity: 4242
Merit: 8672
July 04, 2015, 01:43:34 AM
#49
I'm using 0.10.2 and still got the message, it's not a version specific announcement.
The message was briefly up for 0.10.2 because 0.10 had failed to increment the protocol version and I failed to account for that. The there are two alerts which are active right now covering everything prior to 0.9 plus the specific subversion strings for 0.9.0-0.9.5.
Pages:
Jump to: