Brainwallet Generator | Secure Bitcoin Wallet Generator


For discussion about Litecoin, the leading cryptocurrency derived from Bitcoin. Litecoin is developed with a focus on speed, efficiency, and wider initial coin distribution through the use of scrypt-based mining.

Help! I’m trying to send bitcoin from KUCoin exchange and every address my electrum is generating is invalid. I’ve made a legacy and Segwit both don’t work. And also I’m currently not connected and I’ve tried multiple servers. Can anyone help or point me in right direction?

submitted by Lololololinc to Electrum [link] [comments]

I feel like such an idiot 'cause I lost my bitcoins to mSIGNA wallet by using a newly generated invoice address to try and receive the coins. Now the coins wont show and I cant connect to the node to be able to extract them out to electrum. Please help! :(

Update: I managed to send the coins out to electrum with the help of deminero30 setting up a qt node for me to connect to. But my nubiness went and put a very low fee so god knows how long or if the transaction will happen lol.
submitted by CoconutsNeverGiveup to BitcoinBeginners [link] [comments]

12-30 21:33 - 'That's not true. The core has more features than electrum- it just requires use of the CLI. Honestly, you shouldn't be using multi-sig in the first place if you can't figure out how to generate an address using the CLI...' by /u/Nycmdthroaway removed from /r/Bitcoin within 43-53min

That's not true. The core has more features than electrum- it just requires use of the CLI. Honestly, you shouldn't be using multi-sig in the first place if you can't figure out how to generate an address using the CLI.
Open up the debug window CLI tab, type `help' and you'll see how much you can do and the information you can ascertain with the core node that you can't with electrum.
Electrum relies on the core node for all of its functionality, save their proprietary mnemonic seed backup algorithm, which is much less secure than BIP33 (which can be generated with the core; electrum literally provides you with the dictionary to carry out an attack on its addresses, and it doesn't use an EC in its cryptographic process, meaning the encryption entropy is low and the nonces are predictable).
I could order some RIPEMD-160 ASIC chips for $2/piece and have a Chinese fabricator design a PCB using some cheap 22nm SHA-256 chips and the RIPEMD chips, replace cgminer or bfgminer's computational sections with the ultra optimized vanitygen algos for brute forcing priv keys, switch out stratum for JTR-style threaded rainbow tables based on a few hundred thousand rounds of mnemonic generation using electrum's suite- along with some open source code analysis, and in a month I could create a machine that could generate and test hundreds of thousands to millions of mnemonics per second.
The only reason this hasn't been an active practice is because destroying bitcoins keypair-cryptography (or at least appearing to have done so) would send the price under a dollar in 24hours. An update would be patched within a few days and it should be a lot of hard work for nothing. But I wouldn't be surprised if this is occurring actively on a small scale, with old addresses presumed to be "lost." Even if an active address was hit, as long as it wasn't overdone, people would shrug it off as a physical compromise of their own network/machine/software, not an epidemic- but considering the frequency of exchanges getting "hacked" and the actual ease by which the attack could be carried out, I think there's an equal possibility that the security is already completely compromised.
Theoretically all mnemonic backups are inherently insecure (as is any password using dictionary words, no matter how long) but at least using ECDHE and a deterministic seed, you're actually getting a password with a strength equal to that of the sum of its characters as ASCI to BASE/56 encoded bits. Without that, you may as well have a 12 character passphrase (with the possible characters equal to the number of words in the abridged electrum dictionary.) So it's {POSSIBLE WORDS}12 for electrum vs. something closer to {(POSSIBLE WORDS60)(POSSIBLE HD-SEEDS)}256 for a BIP33 mnemonic using SecP256k ECDHE algo (assuming average number of letters in a word are 5 and HD seeds are pseudo-random.) But mnemonic seeds are still insecure even with BIP33. Use the core wallet and you get a key with true randomness using entropy from blockchain derived sources, 2 rounds of SHA-256 and a final RIPEMD-160 round with a 256-Bit secret generated in conjunction with with an extremely secure ECDHE curve=trillions upon trillions of possibilities. That not only makes a single key harder to break, it means there is a much less likely chance of someone randomly guessing secrets and testing them to see if they come out to a funded address in the whole scheme of things.
It's like if I tried to break into every Dell server. If many people were using weak passwords, and I could try a password on all of them at the same time- I'd surely crack a bunch, and make Dell look bad as a company, even though the servers were inherently fine. Keeping the network strong means making sure you do your part to save face, after all bitcoin is owned and CONTROLLED by the userbase.
As a side note, RIPEMD was only used in the public scheme along with SHA256 (despite being significantly weaker) because at the time SHA256 was the only widely implemented and highly secure algorithm- meaning it could be as widely adopted and widely mined as possible. So SHA-256 was the logical choice for the main block algorithm. There wasn't another option for the wallet address' scheme that would be secure tunneling enough and still computationally feasible and easy to integrate. So SHA-256 was most secure, but without the round of RIPEMD-160 as the deterministic round, wallets could be brute forced at the same time as mining, with the same hardware.
For the most secure, fool-proof, uncrackable wallet, here's what I do/used to do: Use the Core node to bake Segwit P2SH addresses. I don't use HD wallets period, but HD is secure enough as long as you're using a truly random secret. Remember that the secret in a BIP33 HD wallet is the master privkey, additionally, each address has it's own xpriv, which, considering the combinations possible, saving the individual xprivs makes the most sense anyway. If you plan on spending the coins soon, just secure the wallet .dat file with a strong 16+ character (A-Z,a-z,()$&@#$/?¿%÷,0-9) passphrase (this is just the wallet file pw it has nothing to do with your addresses) then just throw the wallet on a flash drive or better yet an SD card or 2 and call it a day.
For addresses you plan to put on ice for a while, concat your coins into a handful of accounts, don't store more than $1,000/address. Then using the `dumpprivkey' Core CLI command (I think that's the command, it's something like that, type help and you'll see it if I'm wrong), a text encrypting program (for good measure) and a barcode/QR code generator (all offline!), get the private keys for each address, encrypt the text with an easy to remember password (you'll be taking the keys offline, and storing physically, so no need to worry too much about that pass, it's better to just keep them physically safe), and then generate QR codes for each. Paste them all into a word doc with the corresponding (lightly) encrypted numbers you generated the QRs with. Print out a couple copies and then delete the addresses from the wallet.
Put those paper wallets somewhere safe. You could also split the key down the middle and store the 2 parts of the paper wallets in different places instead of encrypting the plaintext xprivs. So you'd need to scan both paper keys and paste the solutions together to access the coins.
That's all a bit extreme... in reality, unless you're super paranoid and storing millions, you'll be fine by keeping your coins in the core node with decent firewall and a good .dat passphrase.
Context Link
Go1dfish undelete link
unreddit undelete link
Author: Nycmdthroaway
submitted by removalbot to removalbot [link] [comments]

How to generate more change addresses manually in Electrum? [2mBTC bounty] /r/Bitcoin

How to generate more change addresses manually in Electrum? [2mBTC bounty] /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Which is safer? Reusing old offline addresses, or using new addresses automatically generated by Electrum on an online computer? /r/Bitcoin

Which is safer? Reusing old offline addresses, or using new addresses automatically generated by Electrum on an online computer? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

How does Electrum 3 generate SegWit addresses? /r/Bitcoin

How does Electrum 3 generate SegWit addresses? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

08-23 23:02 - 'How to generate a multiple recieve addresses in Electrum wallet' (self.Bitcoin) by /u/coinstreak removed from /r/Bitcoin within 0-6min

Hello, I remember that there were a multiple recieve addresses shown in electrum wallet 1-2 years ago, but now I have 2.7.9 version and there is just a single recieve address. How can I generate more recieve addresses? Thanks for heping!
How to generate a multiple recieve addresses in Electrum wallet
Go1dfish undelete link
unreddit undelete link
Author: coinstreak
submitted by removalbot to removalbot [link] [comments]

How to generate a multiple recieve addresses in Electrum wallet /r/Bitcoin

How to generate a multiple recieve addresses in Electrum wallet /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Electrum (it generates new addresses) - are they mine forever? /r/Bitcoin

Electrum (it generates new addresses) - are they mine forever? /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

A question about Electrum address generation. /r/Bitcoin

A question about Electrum address generation. /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Are all bitcoin wallets stored somewhere on a server?

Please excuse my ignorance I’m very new to this, but I understand you can recover wallets anywhere with your seed. Such as if I have an electrum wallet and I buy a ledger nano s, I can put my seed into my ledger and then now my electrum wallet is on my ledger.
Wouldn’t all wallets details have to be stored somewhere online to be able to access them like this?
submitted by Dtoks to BitcoinBeginners [link] [comments]

Hey! Time to transfer...

I did a small transfer to my wallet (to confirm things) and was just about to do the "real" transfer when i noticed the BTC address has changed (to my wallet).. Ummm I am really confused now.. I had a few idiot replies and more than a few good replies to my last post... But why would the BTC address change ???
submitted by snoopsau to ledgerwallet [link] [comments]

two questions--hacking Bitcoin and cold storage

Hi, please forgive the possibly naive and stupid questions I'm about to ask :)
1) I currently have some Bitcoin on I've decided I'd rather have that stored at home, in my fire-rated safety deposit box. I'm more interested in a physical solution than a TrezoLedgeetc...I just feel like "what would happen if the electronics in the thing get fried, or the display breaks?" Does anyone have any good solutions that would be relatively inexpensive?
2) One thing I've never really understood about Bitcoin--why couldn't I just write a computer program that "tries" a bunch of random private keys and keeps trying to send bitcoin from those keys to my public key? Wouldn't such a program eventually hit on a private key that contains Bitcoin, and thus I've then stolen it? I'm sure there's a great reason...
submitted by canadave_nyc to BitcoinBeginners [link] [comments]

Need help figuring out what I did wrong

Hi Community. A few days ago, I posted asking about what part (passphrase, seed, etc) I share to do a giveaway on a site I work for.
I set up an Electrum wallet with a small about of bitcoin in it. It was suggested by some users that the part I needed reveal for someone to claim the wallet/prize was the seed. It was a 12 word phrase.
I did that...but it doesn't seem anyone has claimed it. I have had a few people ask me how to claim it. Can anyone help me with this? I would hate for anyone to think it was a scam. I am not trying to scam anyone. I just wanted to do a fun giveaway and possibly gain some new users on the site.
submitted by tah8605 to Bitcoin [link] [comments]

Advice needed on a QR code generator for accepting payments

So I need some advice. I'm looking for a QR code generator to make it easy to receive bitcoin payments. My concern is because money is involved, I don't want to unwittingly allow a third party (the QR generator or someone else) to steal any payments being made.
Advice? Sorry I'm still new to this, and I don't think just googling for "best bitcoin QR generator" will necessarily be wise.
submitted by Wraiith303 to Bitcoin [link] [comments]

Electrum ( I'm using electrum for first time )

Hey guys, I sold some accounts and I want to widraw my money via bitcoin( I use bitcoin in first time). I dowload Electrum and made a wallet. I sent my wallet to middleman and he answered " This is a bitcoin cash address above. If we send there, we will send BCH." Can you help me please,how to get bitcoin adress in Electrum(sorry for a stupid question )
submitted by innoy13 to Bitcoin [link] [comments]

Air-gapped z-addresses; Is ZecWallet an option?

I've heard of Zcash for a while, but it wasn't until recently that I tried my hand playing around with the daemon and wallets.
Obviously, there's no point in using ZEC if you're only using t-addresses, but my desire for a z-address capable wallet certainly narrows the choice of wallets available to me.
Running a full node is no problem for me; I'd like to take advantage of a GUI if possible though. For that reason, I am drawn to ZecWallet's full node version. But I'm still uneasy when it comes to key security. (Can anyone share their experience with the ZecWallet paper wallet generator?)
From what I gather there is no wallet with HD support for t-addresses, is that right? Not much of a concern for me because I am interested in the shielded pool. I just figured t-addresses would support Electrum-style seeds but apparently not?
Sapling addresses seem to be exactly what I want; in particular I am drawn to their reusability and ability to export the view key. I was hoping this would ease the process of securing and backing up my private keys.
Here's my key handling protocol I use for Monero:
1) Generate the wallet on an air-gapped machine
2) This gives you a mnemonic seed. I write that down and keep it as an analog backup. By using a passphrase in conjunction with the seed, I can effectively encrypt this paper wallet easily.
3) Export the private view key and address to an online machine and make a watch-only wallet. This lets my watching wallet see incoming transactions
4) When outputs are received, I have to export the list of outputs to the air-gapped machine. The air-gapped machine uses this data to make signed key images.
5) I export the key images back to the watching wallet. At this point, the watching wallet can see outgoing transactions.
6) Now I can create unsigned transactions with the watching wallet, sign them in the air-gapped machine, and transmit them via the watching wallet using my full node.
The major benefit of using Monero in this way is that I only have to make a human-readable backup of my wallet once and I'm set for life.
Obviously, Zcash is going to be a little bit different. Since the core client doesn't give us mnemonic seed phrases, that complicates backup a little bit. What's the best way to back up ZEC? If I keep an up-to-date backup of my wallet.dat is that all I need? Is there an option in the wallet to encrypt this backup as well, or do I need to accomplish that externally with the likes of Veracrypt? I must admit the idea of unencrypted wallet data being written to my disk makes me uneasy.
I see that there is an option in zcash-cli to import/export the view key of Sapling addresses. However, I can't see the option to do so in ZecWallet, and when I do so manually via the CLI nothing seems to be reflected in ZecWallet.
Is ZecWallet by its very nature an obligatory hot wallet, or am I missing some functionality in the wallet?
My end goal is to run a ZEC full node on Qubes and hold my coins in z-addresses. Qubes allows me to make virtually air-gapped VMs to greatly simplify key management.
So for example when I use Bitcoin, I have a networked VM that runs a Bitcoind + Electrum Personal Server + Electrum Wallet stack, where I import my master public key. When I need to sign a transaction, I spin up a networkless VM equipped with Electrum and my private keys. Qrexec let's me easily ferry unsigned/signed transactions back and forth between the two VMs. Overall this provides a decent UX with above-average security and privacy. I'd like to port this general setup to Zcash.
To do so, I need a GUI wallet that supports both z-addresses and public/private key splitting. Does such a tool exist? (Can Electrum Personal Server be ported to ZEC?) If not, how can I streamline this process with the CLI?
I'm more familiar with Monero than Bitcoin, so the Zcash/Bitcoin CLIs are still a little foreign to me, though I am not "afraid" of CLI wallets in general. My Cryptonote muscle memory makes me prone to annoying little syntax errors I'd much rather do without.
My plan is to buy ZEC from Coinbase Pro, withdraw to a t-address, and then sweep my coins to a z-address. I want to monitor the balance of both t-addresses and z-addresses (and later send transactions) without ever exposing my private keys to the Internet.
However, it seems like the Zcash CLI is my only viable option for z-address watching wallets. Should I just play around on testnet until I get more familiar, or is there a GUI wallet solution out there that fits my needs? Does anyone have a cheat sheet for doing this via the CLI that could help me along the learning curve?
TL;DR New to Zcash, need advice as it relates to wallet backup, watching wallets, and z-addresses.
Assistance is much appreciated!
Edit: I don't suppose there's a way to use a Trezor Model T with a full node and or z-addresses?
submitted by spirtdica to zec [link] [comments]

HowTo: Create and Spend a Electrum Segwit 3of3 Multisig wallet with Trezors

I wrote a simlar post in Bitcoin about creating a MS wallet without a Trezor, this guide will focus on creating a 3of3 MS wallet with three Trezor's. Hopefully it should be obvious how to extend this to N-of-M for any value of N or M. You can also use this as a blueprint to do MS with non-HW Electrum wallets like Android.
It should be noted that this is the most general case method for setting this up. This allows to replace non-HW Electrum wallets into this procedure where HW-wallets are referenced. For the far simpler method, just pick Cosign with hardware device instead of Cosign with key as I outline here. If you choose Cosign with HW you can do the entire process in one wallet file in one session.
The main advantage of multisig is that it reduces the risk of one compromised seed exposing all your funds. Although this is exceedingly complicated, the added layer of complications make it all the more difficult to compromise your funds. Most of the complexity is on the initial wallet setup. Sending is only a bit more complicated, and Receiving is the same as it would be for any electrum wallet.
We will be creating three wallets here, and each will use a Trezor with its own seed, passphrase, and public key (Zpub). If your just wanting to play with this process you could use one Trezor with three different passphrases. Electrum will treat this like three different wallets, since... well since it is. The Zpubs will be calculated by Electrum.
For all references to wallet passphrases or encryption passwords, I highly recommend you generate six-word passphrases. Three simple ways to construct a six-word passphrase would be to either use EFF diceware long wordlist to roll for 6 words, or create a short six-word BIP39 seed and use that as a passphrase, or create a random Electrum seed and use the last 6 words. You will need to take care that all six-word passphrases are equal or less than 50 characters. Longer passphrases can produce some unexpected results. Whenever you need to create a passphrase or password from here on out, create a six-word string as described above.
Assuming your have your Trezors initialized with passphrases enabled, our first order of business will be ensuring the authenticity of Electrum. For the PC's this must be done with PGP/GPG following the procedure spelled out on the Electrum website, or the secondary docs. It is absolutely critical that you are certain your using the correct ThomasV key. As of the time of this writing, the "correct" ThomasV key was:
ThomasV PGP: 6694 D8DE 7BE8 EE56 31BE D950 2BD5 824B 7F94 70E6
Once your Electrum install is validated, here is excruciating detail on creating and spending from a 3of3 multisig wallet. This assumes you have passphrases enabled on all your Trezors and that each has a unique name. For simplicity I will simply refer to their names at "trez-1", "trez-2", and "trez-3"

Three Wallet Creation passes

Do the following first for "trez-1", then for "trez-2" and finally for "trez-3". The order is VERY important:
  1. Wallet->New, name your wallet
  2. Then insert your Trezor ("trez-1", "trez-2", or "trez-3")
  3. Choose Multisig Wallet, then 3of3
  4. Choose Use a hardware device
  5. Select device
  6. Craft (and record) a new 6 word passphrase
  7. Choose Native Segwit derivation
  8. Record Zpub
  9. Unplug your Trezor ("trez-1", "trez-2", or "trez-3")
  10. Choose Add Cosigner Key
  11. Wait at "Add Cosigner 2" dialog

Distribute Zpubs to Finish Wallet Creation

When completing the setup for each wallet below you will be prompted for a wallet encryption password. I recommend you craft a unique six-word string as described above. If Electrum asks to reconnect to your HW wallet simply say "No". You will notice that the order is the reverse of the previous portion. As before, the order is VERY important,.
  1. Swap over to your trez-3 wallet
  2. Click "Enter Cosigner Key"
  3. Enter trez-1 Zpub
  4. Click "Enter Cosigner Key"
  5. Enter trez-2 Zpub
  6. Swap over to your trez-2 wallet
  7. Click "Enter Cosigner Key"
  8. Enter trez-3 Zpub
  9. Click "Enter Cosigner Key"
  10. Enter trez-1 Zpub
  11. Swap over to your trez-1 wallet
  12. Click "Enter Cosigner Key"
  13. Enter trez-2 Zpub
  14. Click "Enter Cosigner Key"
  15. Enter trez-3 Zpub
You can now close each wallet file.
You should now have recorded:
Keep the 12 secrets secure, separate and safe.

Receive funds into your 3of3 MS wallet

Receive just like any other wallet. All three wallets will watch the same set of addresses

Spend funds from your 3of3 MS wallet

  1. Create a TXN as you normally would on your first device
  2. In the TXN dialog hit "Preview" instead of Send
  3. In the Preview screen hit "Sign", then "Export"
  4. Copy the TXN over to your second device
  5. On your second device click Tools->Load Transaction
  6. Enter your partially signed TXN
  7. Verify the Status reads "Partially signed (1/3)"
  8. In the Preview screen hit "Sign", then "Export"
  9. Copy the TXN over to your third device
  10. On your third device click Tools->Load Transaction
  11. Enter your partially signed TXN
  12. Verify the Status reads "Partially signed (2/3)"
  13. In the Preview screen hit "Sign", then "Broadcast"


Certainly more complicated than a non MS wallet, but a lot more secure. Also be aware that the Segwit MS TXNs are about 40% larger than the native Segwit TXNs, so this does generate some additional cost in TXN fees.
submitted by brianddk to TREZOR [link] [comments]

BitBox02 & KeepKey honest reviews

BitBox02 & KeepKey honest reviews

Hey, Bitcoin community 👋

I've just joined after a small research over the web, and decided to share some of my thoughts about these hardware wallets as individual experience.
The first hardware wallet I've received was the KeepKey, which acquired by the ShapeShift platform. It has some great advantages I liked at first sight:
  1. Using ShapeShift platform web to communicate between the wallet and the outside world. On the platform you could watch your assets with nice graphs, send & receive Bitcoin (and other ERC20 tokens) and trade between assets without commission (as long as you have FOX tokens - more on the ShapeShift subreddit).
  2. The most cheap hardware wallet, can be purchased for only 10$ here
  3. Great customer support! any question I sent them was answered quickly
The KeepKey via the web platform needs to be verified by a PIN (4 to 9 digits) of your choose. I didn't like it has there is no zero ("0") digit, only one to nine.
KeepKey verifies PIN screen
The PIN pattern on the KeepKey large screen (which is great advantage!) changes every time you unlock it, and numbers are not shown over the web (only dots). All actions on the web must be approved by one single button on the device it self and all the details shown very nicely!
Receiving Bitcoin on KeepKey - address and QR shown (and can be scanned)
KeepKey implemented a great privacy feature that each successful transaction changes the wallet's address. On the other, once you got the transaction done you can't see this address anywhere again.
Some of the disadvantages that made me move to the BitBox02, are:
  1. The lack of USB-C adoption. It was a bit frustrating looking for an adapter every time I wanted to connect it to my MacBook, which has USB-C ports only.
  2. Mobility isn't available, as you must use the ShapeShift platform (no native desktop program nor mobile application is available)
  3. Chrome is the only supported browser and the platform can't be used by any other.
  4. Not sure about the build quality. When I first opened the box, the upper half of the device wasn't parallel to the bottom, made me a bit nervous
  5. Not supported bech32!
  6. Lead to KYC
MicroUSB connector and edgy built
Overall, I find the KeepKey a great wallet, decently for this low price and the platform as some nice features. KeepKey has a Chrome extension which will be removed by June of this year, as the Google removes Chrome App Store.
BitBox02 Multi edition
So, after the downsides of the KeepKey I was waiting for my wallet of choice, the BitBox02 which was built by the Shift Cryptosecurity, it is much smaller device but I find it more useful and much easier to use everyday.
The BitBox02 has two types, one for Bitcoin only and one for Bitcoin and some others. Currently not many coins supported, which isn't a great (Bitcoin, Ethereum, Litecoin and some other ERC20).
Shift Cryptosecurity has some other type of threat model, it has no seal tape on the box to verify it's a legit unboxed wallet, as many manufacturers (including KeepKey) does; they actually vacuuming the box and make it almost impossible to cut it without notice. As for now, they working on new awesome feature called "Tep", a really innovative idea! watch the video, it's really great!
Inside the box there was a USB-C to USB-A adapter (awesome thing to provide!), extended USB-C cable, stickers, microSD card (soon to be explained why, but again, awesome they send it included) and the device it self.
Some of the advantages are:
  1. Native desktop program for MacOS, Windows and Linux
  2. Android application (hope for iOS soon as well), which is great for mobility
  3. Easy to use and guided through every step of the initialisation
  4. MicroSD card used to backup (not encrypted) the keys, another method for users, along with the 24 mnemonic passphrase. It's nice feature to have for those who aren't that technologically.
  5. Secure chip built-in the device
  6. Able to use with Electrum
BitBox02 has no buttons, it has a unique gesture touch sensors on it's sides and it used a slide, tap and hold gestures.
Supported low and capital letters along with all 0-9 digits
The device will wipe it self after 10 times of wrong password. Backup of the keys can be done by the microSD card or by the 24 words.
BitBoxApp, receiving address must be verified on the device
Verify on the device by single tap
Same as the KeepKey, the BitBox02 generates a new address each time you made a successful transaction, keeping the privacy in mind and focused. another nice feature to have is that the BitBox02 has U2F ability, which means websites like Google, Facebook, Twitter and else can be 2FA with a physical security key, a great way to secure accounts.
In my opinion, KeepKey is a great wallet but I liked the BitBox02 more, specially because of the mobility and the ease of use on any OS no need to download Chrome, although it's bit more expensive.
submitted by Sh0ham to Bitcoin [link] [comments]

Imported xpub from Ledger Live to Sentinel, sent BTC, doesn't show up in Ledger's wallet

As title - I exported an xpub using the advanced logs from Ledger Live into Sentinel, then generated a receiving address using Sentinel, sent some BTC there. Now the BTC don't show up in either Ledger Live or Sentinel, strangely, but prior transactions do. I've checked the xpub is correct - the coins are showing up if I do a search for that xpub using a block explorer, for example.
Anyone know how to troubleshoot this?
submitted by boyber to ledgerwallet [link] [comments]

Electrum questions

Hi everyone,
Today I decided to buy bitcoin, I've been reading about it for a long time and I finally decided to make my move. As I know, not my keys not my coins, I'll be moving them to a desktop wallet - Electrum, but before that I have some questions. I appology if some of this questions are "dumb"
1 - Why Electrum only uses 12 seed words? I thought the standard was 24
2 - Once I get my wallet, can I get an adress that I can use multiple times? One adress that whenever I buy from an exchange, I deposit to my wallet without having to go to my wallet get another adress. My "plan" is to once I get that adress to use multiple times (if thats possible) I will unistall everything about Electrum so my wallet doesn't get compromissed.
3- Is there a way to watch the balance of my wallet? On the phone for example
4- I heard that u always have to have your Electrum wallet updated. What does this mean? What happens if I don't
5- What happens if Electrum ceases to exist? Will I lose my coins? Can an Electrum employee see my seed? Why/why not?

Thanks in advance!
submitted by Alfnixpy to Bitcoin [link] [comments]

Mentor Monday, September 09, 2019: Ask all your bitcoin questions!

Ask (and answer!) away! Here are the general rules:
And don't forget to check out /BitcoinBeginners
You can sort by new to see the latest questions that may not be answered yet.
submitted by rBitcoinMod to Bitcoin [link] [comments]

How To Get Private Key of any Bitcoin Address  Generate Fund from Private Key 2020 How to find the private key of an imported Bitcoin address Mass Generator bitcoin private key and address How to Create Multiple Addresses using one Wallet by Ajah John How to get a Bitcoin Wallet Address - FREE & in under a minute

Electrum Bitcoin Wallet. Impressum This website is hosted by Electrum Technologies GmbH Electrum Technologies was founded by Thomas Voegtlin in 2013. Its mission is to develop, package and distribute Electrum software, and to provide services to Bitcoin users and businesses. - Deterministic Bitcoin Address Generator. is a deterministic bitcoin address generator. Store bitcoin in your brain by remembering your passphrase and salts. Address generation takes place in your browser, and no information is ever sent to our server. Disclaimer: Use at your own risk. A pre-calculated database of every P2PKH Bitcoin address with a positive balance is included in this project. The generated address is searched within the database, and if it is found that the address has a balance, then the private key, public key and wallet address are saved to the text file plutus.txt on the user's hard drive. Wallet words, private key and address follow the standard (derivation path m/44'/60'/0'/0/k), and can be restored in most wallets. The private key generated here is never transfered over the internet. This webpage runs entirely in your browser, in Javascript. Feel free to check out the source code on GitHub. Electrum is one of Bitcoin’s most popular wallets. It uniquely walks the fine line between beginner usability and expert functionality. This guide introduces Electrum with step-by-step examples highlighting the most important beginner features. No previous experience with either Bitcoin or Electrum is needed. Learning Electrum requires practice.

[index] [16340] [1118] [12965] [789] [13958] [5546] [3574] [1330] [7481] [20565]

How To Get Private Key of any Bitcoin Address Generate Fund from Private Key 2020

How to generate free Bitcoin 1. Enter your personal Bitcoin Wallet Address – make sure to enter a valid wallet address. I am recommended Create New Account on Blockchain or Coinbase. The probability of finding 1 address of 2 ^ 256 degrees (approximately 10 ^ 77), which is almost impossible, but this is like a free Bitcoin lottery and 1) since the creation of the project, the ... I hope you enjoyed this video on how to get a bitcoin wallet address, below are the links to the 3 methods/wallets shown in the video as well as the bonus. 1. Electrum - In this video I will explain how to generate SegWit addresses when running a Bitcoin Core full node. Bitcoin-qt does not yet support generating SegWit addresses, so in this video I will explain ... Electrum Bitcoin Wallet ... Bitcoin Q&A: Public keys vs. addresses - Duration: 12:43. aantonop 16,742 views. 12:43. Creating a HD Wallet with Metamask - Duration: ... Bitcoin For Investors #8 ...

Flag Counter