Electrum
electrum.org BitcoinLong-standing Python-based Bitcoin wallet with good security features. Private keys are encrypted and do not touch the internet and balance is checked with a watch-only wallet. Compatible with other wallets, so there is no tie-in, and funds can be recovered with your secret seed. It supports proof-checking to verify transactions using SPV, multi-sig, and add-ons for compatibility with hardware wallets. A decentralized server indexes ledger transactions, meaning it's fast and doesn't require much disk space. The potential security issue here would not be with the wallet, but rather your PC - you must ensure your computer is secure and your wallet has a long, strong passphrase to encrypt it with.
- Homepage: electrum.org
- GitHub: github.com/spesmilo/electrum
- Privacy: tosdr.org/en/service/2761
- Web info: web-check.xyz/results/electrum.org
Electrum Source Code
Author
Description
Electrum Bitcoin Wallet
Homepage
https://electrum.orgLicense
MIT
Created
02 Aug 12
Last Updated
29 Nov 24
Latest version
Primary Language
Python
Size
62,860 KB
Stars
7,526
Forks
3,105
Watchers
7,526
Language Usage
Star History
Top Contributors
- @ecdsa (4791)
- @SomberNight (4598)
- @accumulator (1378)
- @ysangkok (353)
- @bauerj (150)
- @genjix (128)
- @bitromortac (113)
- @wozz (73)
- @jimboman77 (59)
- @romanz (52)
- @neocogent (40)
- @chrisglass (28)
- @benma (25)
- @wakiyamap (24)
- @akshayaurora (23)
- @fluffypony (21)
- @EchterAgo (20)
- @JeremyRand (20)
- @matejcik (18)
- @dabura667 (17)
- @verretor (16)
- @toxeus (15)
- @m0mchil (14)
- @ovidiusoft (14)
- @cculianu (14)
- @stefaang (13)
- @zebra-lucky (12)
- @gruve-p (11)
- @darrindaigle (10)
- @rofl0r (10)
Recent Commits
- ThomasV (29 Nov 24)
Merge pull request #9327 from hishope/master chore: fix 404 status URL
- ThomasV (29 Nov 24)
CLI: raise UserFacingException when passed unknown channel point. fixes #9326
- hishope (29 Nov 24)
chore: fix 404 status URL Signed-off-by: hishope <[email protected]>
- ThomasV (28 Nov 24)
psbt_nostr: minor fix
- bitromortac (15 Nov 21)
watchtower: only send first-stage HTLC justice txs Due to malleability of HTLC-transactions, we can't send presigned justice transactions for the second-stage HTLC transactions, which is why we now send first-stage justice transactions for anchor channels.
- bitromortac (15 Nov 21)
htlctx: deal with possible peer htlctx batching Due to anchor channel's sighash.SINGLE and sighash.ANYONECANPAY, several HTLC-transactions can be combined. This means we must watch for revoked outputs in the HTLC transaction not only at index 0 but at any index.
- bitromortac (12 Nov 21)
sweep: rename sweep creation functions naming scheme: tx(s)_our/their_ctx/htlctx_output-description function names are shortened to whether a single (tx) or several sweep transactions (txs) are generated
- bitromortac (08 Nov 21)
unit tests: tests for both anchors and old ctx types * in test_lnutil, patch htlc weight to pass original anchor commitment test vectors * activate tests for both commitment types
- ThomasV (25 Nov 24)
fix test_lnchannel (follow-up ea584e13fc10d0c5d5038e7113b94e48191c55f7)
- ThomasV (25 Nov 24)
lnwatcher: if broadcast is successful, add tx immediately, so that second-stage htlc can be added as well
- bitromortac (15 Oct 21)
anchors: switch to zero-fee-htlcs * sets the weight of htlc transactions to zero, thereby putting a zero fee for the htlc transactions * add inputs to htlc-tx for fee bumping * switches feature flags * disable anchor test vectors, which are now partially invalid
- bitromortac (15 Sept 21)
enable anchor_channels for regtest * lower the final balance of the backup regtest, which is due to additional sweep transactions * adapt ctx index
- ThomasV (23 Nov 24)
fix unit test (follow-up 78d19c6e2fd3219366cb064563d63000e0228516)
- ThomasV (23 Nov 24)
amchor outputs: fixes after rebase
- ThomasV (23 Nov 24)
follow-up ece1fb39d214e6772b86f1c1fa9aa152beaef386
- ThomasV (24 Sept 22)
enable anchor outputs via config option
- bitromortac (13 Sept 21)
unit tests: test anchors in lnpeer and lnchannel * testing of anchor channels is controlled via TEST_ANCHOR_CHANNELS * rewrite tests in test_lnchannel.py
- bitromortac (15 Sept 21)
backups: restore from closing tx, sweep to_remote * add a method for backups to sweep to_remote * to_remote sweeping needs the payment_basepoint's private key to sign the sweep transaction * we restore the private key from our funding multisig pubkey (pubished with the closing transaction) and a static payment key secret
- bitromortac (11 Oct 21)
qt: add anchor channel icon source: https://tabler-icons.io/anchor
- bitromortac (13 Sept 21)
lnsweep: update sweeps to_remote and htlcs * sweep to_remote output, as this is now a p2wsh (previously internal wallet address) * sweep htlc outputs with new scripts
- bitromortac (13 Sept 21)
lnwatcher: add field for onchain htlc settlement control
- bitromortac (13 Sept 21)
lnwatcher: renaming and comments for clarity
- ThomasV (20 Nov 24)
fixes after rebase
- bitromortac (13 Sept 21)
tests: add anchor commitment test vectors from rfc
- ThomasV (20 Nov 24)
lnutil minor fix after rebase
- bitromortac (13 Sept 21)
lnutil+lnchannel: add anchors, adapt to_remote * to_remote has now an additional csv lock of 1 * anchor outputs are added if to_local/remote outputs are present * funder balance is reduced to accomodate anchors
- bitromortac (13 Sept 21)
lnchannel+lnutil: change htlc output, send new sig * changes the htlc outputs' witness script to have a csv lock of 1 * send signatures for remote ctx with ANYONECANPAY|SINGLE * refactor htlc weight (useful for zero-fee-htlc)
- bitromortac (13 Sept 21)
lnutil: update ctx fee calculation for anchors
- bitromortac (22 Sept 21)
add static payment key * in order to be able to sweep to_remote in an onchain backup scenario we need to retain the private key for the payment_basepoint * to facilitate the above, we open a channel derived from a static secret (tied to the wallet seed), the static_payment_key combined with the funding pubkey (multisig_key), which we can restore from the channel closing transaction
- bitromortac (13 Sept 21)
prepare a channel to have anchors * add anchor ln features * peer.use_anchors is added * channel.has_anchors is added
Electrum Website
Website
Electrum Bitcoin Wallet
Electrum Bitcoin Wallet.
Redirects
Does not redirect
Security Checks
All 66 security checks passed
Server Details
- IP Address 104.21.91.204
- Location San Francisco, California, United States of America, NA
- ISP CloudFlare Inc.
- ASN AS13335
Associated Countries
- US
- FR
Saftey Score
Website marked as safe
100%
Blacklist Check
electrum.org was found on 0 blacklists
- ThreatLog
- OpenPhish
- PhishTank
- Phishing.Database
- PhishStats
- URLhaus
- RPiList Not Serious
- AntiSocial Blacklist
- PhishFeed
- NABP Not Recommended Sites
- Spam404
- CRDF
- Artists Against 419
- CERT Polska
- PetScams
- Suspicious Hosting IP
- Phishunt
- CoinBlockerLists
- MetaMask EthPhishing
- EtherScamDB
- EtherAddressLookup
- ViriBack C2 Tracker
- Bambenek Consulting
- Badbitcoin
- SecureReload Phishing List
- Fake Website Buster
- TweetFeed
- CryptoScamDB
- StopGunScams
- ThreatFox
- PhishFort
Website Preview
Electrum Reviews
More Crypto Wallets
-
An open source, native desktop wallet for Windows, Linux, and MacOS. Wasabi implements trustless CoinJoins over the Tor network. Neither an observer nor the participants can determine which output belongs to which input. This makes it difficult for outside parties to trace where a particular coin originated from and where it was sent to, which greatly improves privacy. Since it's trustless, the CoinJoin coordinator cannot breach the privacy of the participants. Wasabi is compatible with cold storage and hardware wallets, including OpenCard and Trezor.
-
Open source, cross-platform, offline, crypto wallet, compatible with 1000+ coins. Your private key is generated on the device, and never leaves it, all transactions are signed by the Trezor, which ensures your wallet is safe from theft. There are native apps for Windows, Linux, MacOS, Android, and iOS, but Trezor is also compatible with other wallets, such as Wasabi. You can back the Trezor up, either by writing down the seed, or by duplicating it to another device. It is simple and intuitive to use, but also incredibly customizable with a large range of advanced features.
-
An easy-to-use, super secure Bitcoin hardware wallet, which can be used independently as an air-gapped wallet. ColdCard is based on partially signed Bitcoin transactions following the BIP174 standard. Built specifically for Bitcoin, and with a variety of unique security features, ColdCard is secure, trustless, private, and easy-to-use. Companion products for the ColdCard include: BlockClock, SeedPlate, and ColdPower.
-
Sparrow is a Bitcoin wallet for those who value financial self-sovereignty. Sparrow’s emphasis is on security, privacy, and usability. Sparrow does not hide information from you - on the contrary, it attempts to provide as much detail as possible about your transactions and UTXOs, but in a way that is manageable and usable.
-
Atomic is an open-source desktop and mobile-based wallet, where your private keys are stored on your local device, and do not touch the internet. Atomic has a great feature set, and supports swapping, staking, and lending directly from the app. However, most of Atomic's features require an active internet connection, and Atomic does not support hardware wallets yet. Therefore, it may only be a good choice as a secondary wallet, for storing small amounts of your actively used currency.
-
A steel plate, with engraved letters which can be permanently screwed - CryptoSteel is a good fire-proof, shock-proof, water-proof, and stainless cryptocurrency backup solution.
-
Open source hardware wallet, supporting secure multisig with the option for making encrypted backups on a MicroSD card.
About the Data: Electrum
API
You can access Electrum's data programmatically via our API.
Simply make a GET
request to:
https://api.awesome-privacy.xyz/finance/crypto-wallets/electrum
The REST API is free, no-auth and CORS-enabled. To learn more, view the Swagger Docs or read the API Usage Guide.
About the Data
Beyond the user-submitted YAML you see above, we also augment each listing with additional data dynamically fetched from several sources. To learn more about where the rest of data included in this page comes from, and how it is computed, see the About the Data section of our About page.
Share Electrum
Help your friends compare Crypto Wallets, and pick privacy-respecting software and services.
Share Electrum and Awesome Privacy with your network!