July 2015 chain forks - Revision history

Harding: There won't be any more forks in July 2015

2015-08-02T12:14:54Z

There won't be any more forks in July 2015

← Older revision		Revision as of 12:14, 2 August 2015
Line 1:		Line 1:
	The July 2015 forks were two ~~(so far)~~ block chain forks with two or more invalid blocks. They were caused by miners who didn't properly validate blocks before mining on top of them.<ref>[http://bitcoin.org/spv-mining Some miners creating invalid blocks], Bitcoin.org, 4 July 2015</ref>		The July 2015 forks were two block chain forks with two or more invalid blocks. They were caused by miners who didn't properly validate blocks before mining on top of them.<ref>[http://bitcoin.org/spv-mining Some miners creating invalid blocks], Bitcoin.org, 4 July 2015</ref>

	== Wallet Advice ==		== Wallet Advice ==
Line 36:		Line 36:
	* ecdsa.net (version 0.10.99, changeset 3c60937ce6a251e565e169715ebb2f3dd76825c4)		* ecdsa.net (version 0.10.99, changeset 3c60937ce6a251e565e169715ebb2f3dd76825c4)

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to ~~authoratatively~~ determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoritatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.
	Note that this, too, relies on trusting the server you are using.		Note that this, too, relies on trusting the server you are using.

Taras: Taras moved page July 2015 forks to July 2015 chain forks: Clarifying

2015-07-23T03:46:34Z

Taras moved page July 2015 forks to July 2015 chain forks: Clarifying

← Older revision		Revision as of 03:46, 23 July 2015
(No difference)

Taras: Taras moved page July 2015 Forks to July 2015 forks

2015-07-08T23:59:26Z

Taras moved page July 2015 Forks to July 2015 forks

← Older revision		Revision as of 23:59, 8 July 2015
(No difference)

Luke-jr: /* Wallet Advice */

2015-07-08T21:15:22Z

Wallet Advice

← Older revision		Revision as of 21:15, 8 July 2015
Line 5:		Line 5:
	* If you use Bitcoin Core, [https://bitcoin.org/en/download upgrade to 0.10.2] to ensure you don't see invalid confirmations.		* If you use Bitcoin Core, [https://bitcoin.org/en/download upgrade to 0.10.2] to ensure you don't see invalid confirmations.

	* If you use a peer-to-peer lightweight wallet (also called a P2P SPV wallet), you must wait for additional confirmations. See the [https://bitcoin.org/spv-mining Bitcoin.org alert] for the currently recommended number of additional confirmations.		* If you use a peer-to-peer lightweight wallet (also called a P2P SPV wallet), you must wait for additional confirmations unless you can tie it to a single trusted and up-to-date node (as is the case with Electrum - see below). See the [https://bitcoin.org/spv-mining Bitcoin.org alert] for the currently recommended number of additional confirmations.

	* If you use Electrum, see the Electrum section below.		* If you use web wallet or an exchange, you should wait for additional confirmations unless you know they are running an up-to-date node. See the [https://bitcoin.org/spv-mining Bitcoin.org alert] for the currently recommended number of additional confirmations.

	* If you use web wallet or an exchange, you should wait for additional confirmations. See the [https://bitcoin.org/spv-mining Bitcoin.org alert] for the currently recommended number of additional confirmations.

	=== Electrum ===		=== Electrum ===

Luke-jr: /* Electrum */ Still requires trust

2015-07-08T21:14:10Z

Electrum: Still requires trust

← Older revision		Revision as of 21:14, 8 July 2015
Line 13:		Line 13:
	=== Electrum ===		=== Electrum ===

	Electrum ~~gets data from~~ a ~~Bitcoin Core~~-~~backed~~ server. If ~~the~~ server is running a recent version of Bitcoin Core, it ~~may be safe---but~~ you ~~must~~ take action to ~~be sure~~.<ref>[https://www.reddit.com/r/Bitcoin/comments/3c305f/if_you_are_using_any_wallet_other_than_bitcoin/cssqykx Electrum servers run Bitcoin Core], /u/etmetm, 5 July 2015</ref>		Electrum is a SPV client that uses a non-standard protocol to communicate with a single node. As with all SPV clients, if that node is trustworthy, you can rely on it to perform the proper validation for you.

			Electrum allows you to specify a specific server that your client uses.
			If a server is running a recent version of Bitcoin Core, and you are okay trusting it with your security, you can take action to use it exclusively.<ref>[https://www.reddit.com/r/Bitcoin/comments/3c305f/if_you_are_using_any_wallet_other_than_bitcoin/cssqykx Electrum servers run Bitcoin Core], /u/etmetm, 5 July 2015</ref>

	# Go to Tools → Network and unclick ''Auto-connect''. This prevents Electrum from automatically changing to servers that have the longest block chain (which, during these invalid chain forks, may be the wrong chain). Note that Electrum will warn you when you're not on the longest chain—you must ignore these warnings until this fork event is over or use the plugin mentioned at the bottom of this section to determine whether you're on the valid chain.		# Go to Tools → Network and unclick ''Auto-connect''. This prevents Electrum from automatically changing to servers that have the longest block chain (which, during these invalid chain forks, may be the wrong chain). Note that Electrum will warn you when you're not on the longest chain—you must ignore these warnings until this fork event is over or use the plugin mentioned at the bottom of this section to determine whether you're on the valid chain.
Line 20:		Line 23:
	# If the message includes a line that says "Bitcoin Core 0.10.2" or "bitcoind 0.10.2", then confirmations reported by the server are likely to be accurate. The only other safe versions are 0.9.5, 0.10.0, and 0.10.1.		# If the message includes a line that says "Bitcoin Core 0.10.2" or "bitcoind 0.10.2", then confirmations reported by the server are likely to be accurate. The only other safe versions are 0.9.5, 0.10.0, and 0.10.1.
	# If the message does not indicate that the server is running Bitcoin Core 0.10.2, you can change servers by going to Tools → Network, unclicking ''Auto-connect'', and choosing a server from the list. After connecting, a new message will be displayed; use the instructions in step #3 again.		# If the message does not indicate that the server is running Bitcoin Core 0.10.2, you can change servers by going to Tools → Network, unclicking ''Auto-connect'', and choosing a server from the list. After connecting, a new message will be displayed; use the instructions in step #3 again.
			# You should also ensure you are using TLS encryption, and with a known certificate of your trusted server.

	Please note that this information is provided voluntarily by the server administrators. It is not validated.		Please note that this information is provided voluntarily by the server administrators. It is not validated.
Line 35:		Line 39:

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.
			Note that this, too, relies on trusting the server you are using.

	== Invalid Block Hashes ==		== Invalid Block Hashes ==

Darthandroid: /* Electrum */ Re-added ecdsa.net (using a safe changeset), added us.electrum.be

2015-07-07T17:09:04Z

Electrum: Re-added ecdsa.net (using a safe changeset), added us.electrum.be

← Older revision		Revision as of 17:09, 7 July 2015
Line 31:		Line 31:
	* electrum.dragonzone.net (version 0.10.0)		* electrum.dragonzone.net (version 0.10.0)
	* electrum.be (version 0.10.2)		* electrum.be (version 0.10.2)
			* us.electrum.be (version 0.10.2)
			* ecdsa.net (version 0.10.99, changeset 3c60937ce6a251e565e169715ebb2f3dd76825c4)

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.

Darthandroid: /* Electrum */ version was updated last night

2015-07-07T17:01:59Z

Electrum: version was updated last night

← Older revision		Revision as of 17:01, 7 July 2015
Line 25:		Line 25:
	The following Electrum servers have a safe Bitcoin Core version in their banner:		The following Electrum servers have a safe Bitcoin Core version in their banner:

	* electrum.no-ip.org (version 0.10.0)		* electrum.no-ip.org (version 0.10.2)
	* electrum.jdubya.info (version 0.10.2)		* electrum.jdubya.info (version 0.10.2)
	* vps.hsmiths.com (version 0.10.2)		* vps.hsmiths.com (version 0.10.2)

Darthandroid: /* Electrum */

2015-07-07T16:55:51Z

Electrum

← Older revision		Revision as of 16:55, 7 July 2015
Line 30:		Line 30:
	* erbium1.sytes.net (version 0.10.0)		* erbium1.sytes.net (version 0.10.0)
	* electrum.dragonzone.net (version 0.10.0)		* electrum.dragonzone.net (version 0.10.0)
			* electrum.be (version 0.10.2)

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.

Harding: Undo revision 57202 by Darthandroid (talk) --- only 0.10.99 after commit 41e6e4ca are safe; revert this if you know ecdsa.net is safe

2015-07-07T12:33:59Z

Undo revision 57202 by Darthandroid (talk) --- only 0.10.99 after commit 41e6e4ca are safe; revert this if you know ecdsa.net is safe

← Older revision		Revision as of 12:33, 7 July 2015
Line 30:		Line 30:
	* erbium1.sytes.net (version 0.10.0)		* erbium1.sytes.net (version 0.10.0)
	* electrum.dragonzone.net (version 0.10.0)		* electrum.dragonzone.net (version 0.10.0)
	* ecdsa.net (version 0.10.99, a pre-release test build)

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.

Darthandroid: /* Electrum */

2015-07-07T06:12:23Z

Electrum

← Older revision		Revision as of 06:12, 7 July 2015
Line 30:		Line 30:
	* erbium1.sytes.net (version 0.10.0)		* erbium1.sytes.net (version 0.10.0)
	* electrum.dragonzone.net (version 0.10.0)		* electrum.dragonzone.net (version 0.10.0)
			* ecdsa.net (version 0.10.99, a pre-release test build)

	During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.		During a fork, it is possible to use the Get Block Header custom plugin<ref>[https://bitcointalk.org/index.php?topic=1110912.msg11800126 Get block header electrum plugin], Belcher, 6 July 2015</ref> to authoratatively determine which side of the fork an Electrum server is on. Bitcoin Core 0.10.x servers should always be on the valid side of the fork.