Electrum - Revision history

Qwerty0: Revert edit by User:Lindsey_Graham that changed the link to non-official (likely malicious) site

2024-12-10T05:46:53Z

Revert edit by User:Lindsey_Graham that changed the link to non-official (likely malicious) site

← Older revision		Revision as of 05:46, 10 December 2024
Line 1:		Line 1:
	[[~~File~~:~~Electrum-4~~.~~5.4~~-~~portable~~.~~png~~\|thumb\|500px\|Electrum 4.5.4 on Windows 10 with showing zero balance and a connected state]]		[[Image:Electrum_logo.png\|400px]][[Image:Capture-Electrum404.jpg\|thumb\|500px\|Electrum 4.0.4 on Windows 7 with showing zero balance and a connected state]]
	~~[[Image:Electrum-walet-logo.png\|400px]]~~
			[https://electrum.org Electrum] is a lightweight Bitcoin client, based on a client-server protocol.
	[https://electrum.is Electrum] is a lightweight Bitcoin client, based on a client-server protocol.		It was released on 5 November 2011.
	It was released on 5 November 2011.
	~~__TOC__~~

	== Main features ==		== Main features ==
Line 20:		Line 18:
	* Written in Python. The code is short, and easy to review.		* Written in Python. The code is short, and easy to review.
	* Add-ons: third-party plugins are supported.		* Add-ons: third-party plugins are supported.
	* Support for Bitcoin URIs, signed URIs and Bitcoin aliases.		* Support for Bitcoin URIs, signed URIs and Bitcoin aliases
	* Two-factor authentication (2FA): Adds an extra layer of security to protect against unauthorized access.
	* Customizable transaction fees: Allows users to adjust transaction fees based on network congestion and desired confirmation speed.		__TOC__
	* Support for [[Segwit]] and [[Lightning Network]]: Offers access to advanced Bitcoin features for faster and cheaper transactions.
	* [[Replace by fee\|Replace-by-fee (RBF)]]: Enables users to replace a pending transaction with a higher fee to expedite confirmation.

	== Verifying Electrum Binaries ==		== Verifying Electrum Binaries ==
Line 110:		Line 106:
	==Documentation==		==Documentation==

	Documentation is hosted on ~~https~~://electrum.~~readthedocs.io~~/.		Documentation is hosted on http://docs.electrum.org/.

	It includes tutorials for the multi-signature, cold storage and hardware wallet features.		It includes tutorials for the multi-signature, cold storage and hardware wallet features.
Line 132:		Line 128:
	Version 3.0 introduced a new server protocol and support for generating [[Segwit]] wallets.		Version 3.0 introduced a new server protocol and support for generating [[Segwit]] wallets.

	On December 27, 2018, an advisory was published<ref>[https://bitcointalk.org/index.php?topic=5090097.0 Electrum vulnerability allows arbitrary messages, phishing]</ref> about a phishing vulnerability where the server returns a fake update message after a transaction is broadcasted~~<ref>[https://dailyreposter.com/2019/05/07/electrum-under-attack-hackers-phish-4m-in-bitcoin/ Electrum Under Attack: Hackers Phish $4M in Bitcoin]</ref>~~, with a link to a phishing domain with a malicious Electrum binary. Users who ran the malicious binary reported theft of all bitcoin funds. A mitigation was applied in version 3.2.1 which renders the rich-text message in plain-text, making it less convincing.		On December 27, 2018, an advisory was published<ref>[https://bitcointalk.org/index.php?topic=5090097.0 Electrum vulnerability allows arbitrary messages, phishing]</ref> about a phishing vulnerability where the server returns a a fake update message after a transaction is broadcasted, with a link to a phishing domain with a malicious Electrum binary. Users who ran the malicious binary reported theft of all bitcoin funds. A mitigation was applied in version 3.2.1 which renders the rich-text message in plain-text, making it less convincing.

	Version 4.0.0 introduced support for [[Lightning Network]] wallets.		Version 4.0.0 introduced support for [[Lightning Network]] wallets.
Line 154:		Line 150:
	<!-- seems less relevant now... not sure		<!-- seems less relevant now... not sure
	Interview with author: https://btcmanager.com/nobody-has-setup-an-electrum-server-for-over-a-year/ archive: https://archive.is/lUnfa -->		Interview with author: https://btcmanager.com/nobody-has-setup-an-electrum-server-for-over-a-year/ archive: https://archive.is/lUnfa -->

	=== Electrum Personal Server ===		=== Electrum Personal Server ===

Line 180:		Line 177:
	[[Category:Clients]]		[[Category:Clients]]
	[[Category:Open Source]]		[[Category:Open Source]]
	~~[[Category:Free Software]]~~
	~~[[Category:License/MIT]]~~
	~~[[Category:Android]]~~

Lindsey Graham: 05/08/24 Updated: Main features, screenshot, docs link, categories, logo, removed typos

2024-05-08T00:02:04Z

05/08/24 Updated: Main features, screenshot, docs link, categories, logo, removed typos

← Older revision		Revision as of 00:02, 8 May 2024
Line 1:		Line 1:
	[[~~Image~~:~~Electrum_logo~~.~~png\|400px]][[Image:Capture~~-~~Electrum404~~.~~jpg~~\|thumb\|500px\|Electrum 4.0.4 on Windows 7 with showing zero balance and a connected state]]		[[File:Electrum-4.5.4-portable.png\|thumb\|500px\|Electrum 4.5.4 on Windows 10 with showing zero balance and a connected state]]
			[[Image:Electrum-walet-logo.png\|400px]]
	[https://electrum.~~org~~ Electrum] is a lightweight Bitcoin client, based on a client-server protocol.
	It was released on 5 November 2011.		[https://electrum.is Electrum] is a lightweight Bitcoin client, based on a client-server protocol.
			It was released on 5 November 2011.
			__TOC__

	== Main features ==		== Main features ==
Line 18:		Line 20:
	* Written in Python. The code is short, and easy to review.		* Written in Python. The code is short, and easy to review.
	* Add-ons: third-party plugins are supported.		* Add-ons: third-party plugins are supported.
	* Support for Bitcoin URIs, signed URIs and Bitcoin aliases		* Support for Bitcoin URIs, signed URIs and Bitcoin aliases.
			* Two-factor authentication (2FA): Adds an extra layer of security to protect against unauthorized access.
	~~__TOC__~~		* Customizable transaction fees: Allows users to adjust transaction fees based on network congestion and desired confirmation speed.
			* Support for [[Segwit]] and [[Lightning Network]]: Offers access to advanced Bitcoin features for faster and cheaper transactions.
			* [[Replace by fee\|Replace-by-fee (RBF)]]: Enables users to replace a pending transaction with a higher fee to expedite confirmation.

	== Verifying Electrum Binaries ==		== Verifying Electrum Binaries ==
Line 106:		Line 110:
	==Documentation==		==Documentation==

	Documentation is hosted on ~~http~~://~~docs~~.~~electrum~~.~~org~~/.		Documentation is hosted on https://electrum.readthedocs.io/.

	It includes tutorials for the multi-signature, cold storage and hardware wallet features.		It includes tutorials for the multi-signature, cold storage and hardware wallet features.
Line 128:		Line 132:
	Version 3.0 introduced a new server protocol and support for generating [[Segwit]] wallets.		Version 3.0 introduced a new server protocol and support for generating [[Segwit]] wallets.

	On December 27, 2018, an advisory was published<ref>[https://bitcointalk.org/index.php?topic=5090097.0 Electrum vulnerability allows arbitrary messages, phishing]</ref> about a phishing vulnerability where the server returns a a fake update message after a transaction is broadcasted, with a link to a phishing domain with a malicious Electrum binary. Users who ran the malicious binary reported theft of all bitcoin funds. A mitigation was applied in version 3.2.1 which renders the rich-text message in plain-text, making it less convincing.		On December 27, 2018, an advisory was published<ref>[https://bitcointalk.org/index.php?topic=5090097.0 Electrum vulnerability allows arbitrary messages, phishing]</ref> about a phishing vulnerability where the server returns a fake update message after a transaction is broadcasted<ref>[https://dailyreposter.com/2019/05/07/electrum-under-attack-hackers-phish-4m-in-bitcoin/ Electrum Under Attack: Hackers Phish $4M in Bitcoin]</ref>, with a link to a phishing domain with a malicious Electrum binary. Users who ran the malicious binary reported theft of all bitcoin funds. A mitigation was applied in version 3.2.1 which renders the rich-text message in plain-text, making it less convincing.

	Version 4.0.0 introduced support for [[Lightning Network]] wallets.		Version 4.0.0 introduced support for [[Lightning Network]] wallets.
Line 150:		Line 154:
	<!-- seems less relevant now... not sure		<!-- seems less relevant now... not sure
	Interview with author: https://btcmanager.com/nobody-has-setup-an-electrum-server-for-over-a-year/ archive: https://archive.is/lUnfa -->		Interview with author: https://btcmanager.com/nobody-has-setup-an-electrum-server-for-over-a-year/ archive: https://archive.is/lUnfa -->

	=== Electrum Personal Server ===		=== Electrum Personal Server ===

Line 177:		Line 180:
	[[Category:Clients]]		[[Category:Clients]]
	[[Category:Open Source]]		[[Category:Open Source]]
			[[Category:Free Software]]
			[[Category:License/MIT]]
			[[Category:Android]]

Ysangkok: Fix screenshot of GPG failure

2024-02-28T03:06:07Z

Fix screenshot of GPG failure

← Older revision		Revision as of 03:06, 28 February 2024
Line 102:		Line 102:
	[[File:GPG-Verify.png\|none\|frame\|The GPG message when signature verification succeeds.]]		[[File:GPG-Verify.png\|none\|frame\|The GPG message when signature verification succeeds.]]

	[[File:GPG-~~Verify~~.png\|none\|frame\|The GPG message when signature verification fails.]]		[[File:GPG-VerifyFail.png\|none\|frame\|The GPG message when signature verification fails.]]

	==Documentation==		==Documentation==

Manu: /* Windows */

2022-06-19T21:28:11Z

Windows

← Older revision		Revision as of 21:28, 19 June 2022
Line 29:		Line 29:

	=== Windows ===		=== Windows ===

			Windows 10 has "Ubuntu on Windows" and allows you ton follow the Linux instructions [[#Linux\|below]]

	On Windows, you should install GPG4Win from this location: https://gpg4win.org/download.html. Once you run the installer, you will be presented with a "components choosing dialog like this:		On Windows, you should install GPG4Win from this location: https://gpg4win.org/download.html. Once you run the installer, you will be presented with a "components choosing dialog like this:

NotATether: added version history

2021-05-09T12:09:33Z

added version history

← Older revision		Revision as of 12:09, 9 May 2021
Line 1:		Line 1:
	[[Image:Electrum_logo.png\|400px]][[Image:Capture-~~Electrum~~.~~png~~\|~~right~~\|~~600px~~\|~~Screenshot of~~ Electrum with ~~its Qt GUI~~]]		[[Image:Electrum_logo.png\|400px]][[Image:Capture-Electrum404.jpg\|thumb\|500px\|Electrum 4.0.4 on Windows 7 with showing zero balance and a connected state]]

	[https://electrum.org Electrum] is a lightweight Bitcoin client, based on a client-server protocol.		[https://electrum.org Electrum] is a lightweight Bitcoin client, based on a client-server protocol.
Line 78:		Line 78:
	[[File:GPGTools-Verify.png\|none\|frame\|The GPG Keychain message when signature verification succeeds.]]		[[File:GPGTools-Verify.png\|none\|frame\|The GPG Keychain message when signature verification succeeds.]]

	[[File:GPGTools-VerifyFail.png\|none\|frame\|The GPG Keychain ~~errormessage~~ when signature verification fails.]]		[[File:GPGTools-VerifyFail.png\|none\|frame\|The GPG Keychain error message when signature verification fails.]]

	=== Linux ===		=== Linux ===

	On Linux, the ''gpg'' command line program is preinstalled in most distributions. If for some reason it's not, look for a package called "gnupg", "gpg" or "gpg2" in your package manager.		On Linux, the <code>gpg</code> command line program is preinstalled in most distributions. If for some reason it's not, look for a package called "gnupg", "gpg" or "gpg2" in your package manager.

	Once that's done with, you run the following GPG commands to import and trust the key which Electrum binaries are signed with, and the signature files are made from:		Once that's done with, you run the following GPG commands to import and trust the key which Electrum binaries are signed with, and the signature files are made from:

	''gpg --import /<path>/<to>/<file>/<location>/ThomasV.asc''		<code>gpg --import /<path>/<to>/<file>/<location>/ThomasV.asc</code>

	[[File:GPG-Import.png]]		[[File:GPG-Import.png]]

	''gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''		<code>gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6</code>

	Then you download the Electrum program and its signature to the same folder, and check its authenticity with the following GPG command:		Then you download the Electrum program and its signature to the same folder, and check its authenticity with the following GPG command:

	''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''		<code>gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc</code>

	This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.		This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.
Line 110:		Line 110:
	==History==		==History==

	Electrum was announced 5 November 2011.<ref>[http://bitcointalk.org/index.php?topic=50936.0 Electrum - a new thin client]</ref>		Electrum was announced 5 November 2011.<ref>[http://bitcointalk.org/index.php?topic=50936.0 Electrum - a new thin client]</ref>. It has since gone through many changes in each version.

			[[Image:Capture-Electrum.png\|thumb\|500px\|An early version of Electrum with its Qt GUI]]

			Version 1.7 added support for third-party plugins.

			Version 2.0 introduced support for the [[Trezor]] hardware wallet, TrustedCoin 2FA, [[multisig]] wallets and changed the way the wallet files are stored by using [[BIP_0032\|BIP32]] derivation. These wallets are incompatible with older versions.

			Version 2.4.3 added support for the [[Hardware_wallet#KeepKey:_Your_Private_Bitcoin_Vault\|KeepKey]] hardware wallet.

			Version 2.6 introduced the new Kivy GUI for the Android client.

			Version 2.7 added a fee slider, [[RBF]] functionality and support for [[Hardware_wallet#Ledger_Nano_S\|Ledger Nano S]]. The wallet format has also been changed, making them incompatible with older versions.

			Version 3.0 introduced a new server protocol and support for generating [[Segwit]] wallets.

			On December 27, 2018, an advisory was published<ref>[https://bitcointalk.org/index.php?topic=5090097.0 Electrum vulnerability allows arbitrary messages, phishing]</ref> about a phishing vulnerability where the server returns a a fake update message after a transaction is broadcasted, with a link to a phishing domain with a malicious Electrum binary. Users who ran the malicious binary reported theft of all bitcoin funds. A mitigation was applied in version 3.2.1 which renders the rich-text message in plain-text, making it less convincing.

			Version 4.0.0 introduced support for [[Lightning Network]] wallets.

	== Server software ==		== Server software ==

NotATether: begin add captions

2021-05-09T11:09:14Z

begin add captions

← Older revision		Revision as of 11:09, 9 May 2021
Line 48:		Line 48:
	After you close the window by clicking the Certify button, click on the Decrypt/Verify button on the main window, and select the signature corresponding to the Electrum binary you have downloaded. If verification is successful, you will get the following window. Otherwise, the signature doesn't match the binary, and you need to download both of them again, and check the URL of the site you are downloading from.		After you close the window by clicking the Certify button, click on the Decrypt/Verify button on the main window, and select the signature corresponding to the Electrum binary you have downloaded. If verification is successful, you will get the following window. Otherwise, the signature doesn't match the binary, and you need to download both of them again, and check the URL of the site you are downloading from.

	[[File:GPG4Win-Verify.png]]		[[File:GPG4Win-Verify.png\|none\|frame\|The Kleopatra message when signature verification succeeds.]]

			[[File:GPG4Win-VerifyFail.png\|none\|frame\|The Kleopatra error message when signature verification fails.]]

	=== MacOS ===		=== MacOS ===
Line 74:		Line 76:
	Then, you can just double click inside Finder on the Electrum signature for the corresponding binary to start GPG Keychain verification which will inform you about the result and whether the signature and binary are good or not.		Then, you can just double click inside Finder on the Electrum signature for the corresponding binary to start GPG Keychain verification which will inform you about the result and whether the signature and binary are good or not.

	[[File:GPGTools-Verify.png]]		[[File:GPGTools-Verify.png\|none\|frame\|The GPG Keychain message when signature verification succeeds.]]

			[[File:GPGTools-VerifyFail.png\|none\|frame\|The GPG Keychain errormessage when signature verification fails.]]

	=== Linux ===		=== Linux ===
Line 94:		Line 98:
	This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.		This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.

	[[File:GPG-Verify.png]]		[[File:GPG-Verify.png\|none\|frame\|The GPG message when signature verification succeeds.]]

			[[File:GPG-Verify.png\|none\|frame\|The GPG message when signature verification fails.]]

	==Documentation==		==Documentation==

NotATether: Add steps for verifying Electrum

2021-04-19T20:24:42Z

Add steps for verifying Electrum

@@ Line 22: / Line 22: @@
 __TOC__
-== Downloading and Verification ==
+== Verifying Electrum Binaries ==
 Electrum binaries can be downloaded from https://electrum.org/#download. Next to each download link there is also a signature file which can be downloaded. The signature files are for independently verifying the Electrum files were not tampered with. This step should not be overlooked as users have reported malicious funds-stealing builds of Electeum existing in the wild.
-To verify the Electrm binaries using the signatures, you need to have GPG installed. After that, you run the following GPG commands to import and trust the key which Electrum binaries are signed with, and the signature files are made from:
+To verify the Electrm binaries using the signatures, you need to have GPG installed. Listed below is the process for each operating system. For all operating systems, you must have Electrum's signing key downloaded to verify the Electrum binaries. This can be downloaded from https://raw.githubusercontent.com/spesmilo/electrum/master/pubkeys/ThomasV.asc.
-''gpg --keyserver keys.gnupg.net --recv-keys 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6
+=== Windows ===
 gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''
 Then you download the Electrum program and its signature to the same folder, and check its authenticity with the following GPG command:
@@ Line 36: / Line 93: @@
 This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.
 ==Documentation==

NotATether: /* Downloading and Verification */ another grammar typo

2021-04-18T21:40:48Z

Downloading and Verification: another grammar typo

← Older revision		Revision as of 21:40, 18 April 2021
Line 31:		Line 31:
	gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''		gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''

	Then you download the Electrum program and its signature to the same folder, and check ~~it's~~ authenticity with the following GPG command:		Then you download the Electrum program and its signature to the same folder, and check its authenticity with the following GPG command:

	''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''		''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''

NotATether: /* Downloading and Verification */ grammar error

2021-04-18T21:40:07Z

Downloading and Verification: grammar error

← Older revision		Revision as of 21:40, 18 April 2021
Line 31:		Line 31:
	gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''		gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''

	Then you download the Electrum program and ~~it's~~ signature to the same folder, and check it's authenticity with the following GPG command:		Then you download the Electrum program and its signature to the same folder, and check it's authenticity with the following GPG command:

	''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''		''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''

NotATether: Begin add signature verification steps

2021-04-18T21:39:03Z

Begin add signature verification steps

← Older revision		Revision as of 21:39, 18 April 2021
Line 21:		Line 21:

	__TOC__		__TOC__

			== Downloading and Verification ==

			Electrum binaries can be downloaded from https://electrum.org/#download. Next to each download link there is also a signature file which can be downloaded. The signature files are for independently verifying the Electrum files were not tampered with. This step should not be overlooked as users have reported malicious funds-stealing builds of Electeum existing in the wild.

			To verify the Electrm binaries using the signatures, you need to have GPG installed. After that, you run the following GPG commands to import and trust the key which Electrum binaries are signed with, and the signature files are made from:

			''gpg --keyserver keys.gnupg.net --recv-keys 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6
			gpg --sign-key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6''

			Then you download the Electrum program and it's signature to the same folder, and check it's authenticity with the following GPG command:

			''gpg --verify /<path>/<to>/<file>/<location>/<filename>.asc''

			This is the path to the signature file you downloaded. If verification succeeds, you will get output indicating that the verification was successful.

	==Documentation==		==Documentation==