somebody tell me how I get my "missing" money....and why are there no phone numbers to call? Is the the place to get answers? I need someone to walk me through where my money is. where is the support? is the goal to not have me use electrum again? why is this so hard. i'm showing a 0 balance, and it says low fee...what the hell does that mean? am I supposed to just know all of that?
don't freak out if your transaction is stuck. it's happening to a lot of people nowadays but it eventually sorts itself out in a few days time. so don't worry.
|
|
|
- Then there were those users who received money to their wallets but when they went to spend it they found that they didn't know the password and neither did they have the seed. A few of them have complained here that they shouldn't be allowed to receive money into a wallet when they can't spend it. If the whole wallet is encrypted then they can't see their receiving addresses and so can't lose their money!
Yeah, that would certainly help as I've seen quite a number of users receive coins to a wallet that they can't send from. Encrypting the entire wallet would certainly help in this regard. looks like it is as i suspected. 2.8.0 has been released and if you set a password for your wallet then the wallet cannot be viewed until the password is provided.
|
|
|
so the wallet cannot be viewed until a password is provided. this is an interesting change indeed. it'll certainly protect people from sending money to wallets they can't spend from. edit: I also see you've added support for bitcoin unlimited's testnet nolnet. I guess you are hedging your bets
|
|
|
That would be for the standard wallets, but what about the multisigs? is there any cosigner index implied? that post didn't point that out. The derivation path is the same for multisig addresses. If you want to check for yourself then restore a wallet with the following xprivs: a: xprv9s21ZrQH143K2j4ApvAWXbXnRQxxY1175NJFyzRSL3copkzRrmR9iFju2bPKMThZZ5X8dBHY8Hn So3Tp1mosezGpbhMxjFewR7fWsWqVuzd b: xprv9s21ZrQH143K2dEFaB8GQ9FmTdLyMijhPngdimqyUiwXgh5rmh92n4x6JEWutHeDi2qAAHPv92S 3SuhNuktYZt22p2jgWMoK5WkDXBnkj4S The above two are generated using bip32.org (passphrase a and b resp.) The first address pubkeys of the above two are (m/0/0): a0: 0223bb76b4e6844a6bde363057fab2aa5df5bc3a7e89c7e8124f6265f8080065fa b0: 0246277670f2d0ff5e86af5e82f8f98d3e1cd90d0b0f252df6518fd842568a5551 And the resulting address is 3Nw1BqfMgdLDAsu67g74dJLxSPAxQEmfZz. This is what you will see in electrum as well as on coinbin: https://coinb.in/#newMultiSig
|
|
|
just download the binary tarball from bitcoin.org, untar it and run bitcoind. that's all.
|
|
|
-snip- So I'm still left wondering what benefit using public key crypto to encrypt the wallet seed has over the old aes way?
No private key in memory needed to add more data. But you are not writing encrypted data most of the time. The only thing encrypted with the password is the seed and any imported private keys. The seed is generated once at wallet creation, encrypted and stored. Same goes for private keys at the time of import. You only need the password for signing transactions and you will still need that even if you use public key crypto. Just did a quick check searching for keywords in the repo, but it looks like this changed or will so in the future. Look at the wording of this dialog -> https://github.com/spesmilo/electrum/blob/fcc92c1ebdee77a4a414384f23f85d37152fbe7b/gui/qt/password_dialog.py#L175Maybe now electrum will hide the wallets contents until you enter a password. I can see a few instances where this might be a good idea: - There were some users who complained that anyone with access to the wallet file could see the balance and transactions. The advice for such users has always been to use the multiuser functionality of their OS if they don't want other people seeing their files. Now they have another option. - Then there were those users who received money to their wallets but when they went to spend it they found that they didn't know the password and neither did they have the seed. A few of them have complained here that they shouldn't be allowed to receive money into a wallet when they can't spend it. If the whole wallet is encrypted then they can't see their receiving addresses and so can't lose their money!
|
|
|
Thanks for all the replies. I',m making screenshots and saving all the good information for reference, thanks
Perhaps for now I will trust that what I installed using apt-get is already verified by apt prior to installation, so no need for to to further verify...
you misunderstood apt doesn't verify the electrum download. You did that using pip. You installed dependencies via apt and those are verified: sudo apt-get install python-qt4 python-pip
But the pip install step did not involve apt. You have to verify the electrum tar ball manually sudo pip install https://download.electrum.org/2.7.18/Electrum-2.7.18.tar.gz
|
|
|
Hi, guys. I had generated multisig address with bitcore-lib on JS: 1. Generate 3 HD private keys and HD public keys. 2. Converted HD public keys to relugar keys. 3. Created the multisig address. And everything goes fine. But, when I restore multisig address in Electrum with HD keys, I don't see there are my multisig address. Has anyone encountered a similar problem? I would be grateful for your help. There could be a few reasons for this: - the order of the pub key matters. a different order will yield a different address. electrum puts the pub keys in lexicographic order first: http://bitcoin.stackexchange.com/a/40382 so make sure you do the same - the address derivation path matters. This is what electrum uses: http://bitcoin.stackexchange.com/a/36956So make sure the above is all consistent with what electrum does. Alternatively you could create a watch only installation of electrum on your server and have electrum derive addresses. Electrum has a daemon mode that you can use. You use the addrequest command to get addresses but note that it won't create more addresses than the gap limit so you'll have to increase the gap limit + keep track of which addresses have been used in case you exceed the gap limit.
|
|
|
Thanks, then I guess I need to uninstall Electrum first as I installed using the sudo apt-get install python-qt4 python-pip etc etc terminal cmmands to install it, and then follow the installation using Python sources
no you don't have to uninstall anything. the instructions there are correct. what you install using apt-get is already verified by apt prior to installation. you only need to verify the electrum tar ball that you downloaded.
|
|
|
bip39 supports passphrases so you can have more than one secret behind your HD wallet. Spare me your opinion. It's fine that you don't like my idea, but I don't think you really understand what I am doing or talking about.
I admit that I'm not sure what you are up to because you've done a piss poor job of explaining it. Maybe you control the bitcoin clients your users use in which case you can do what you like. Having the ability for the client to verify a payment address with cryptography is not a bad thing, and if implemented you don't have to use that feature if you do not want to.
Once again that's what payment requests do. Anyway I'm out.
|
|
|
-snip- So I'm still left wondering what benefit using public key crypto to encrypt the wallet seed has over the old aes way?
No private key in memory needed to add more data. But you are not writing encrypted data most of the time. The only thing encrypted with the password is the seed and any imported private keys. The seed is generated once at wallet creation, encrypted and stored. Same goes for private keys at the time of import. You only need the password for signing transactions and you will still need that even if you use public key crypto.
|
|
|
Seems like a malicious url!!!
good catch. i used a bookmark so i didn't notice that. you should remove the fake url from your quote. we don't want it to show up in google results now do we? the release notes are correct though: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTESSo I'm still left wondering what benefit using public key crypto to encrypt the wallet seed has over the old aes way?
|
|
|
Hi All,
A vendor wants to refund me two amounts. He has sent me two private keys but how do I handle this in Electrum? I can't find it anywhere in the manual.
Thanks,
F.
Strange, Usually, a vendor asks for your address to issue a refund. If it was really a private key, you can swipe it in electrum. Using electrum 2.7.18 go to wallet => private keys => sweep But once again, i find this kind of refund rather strange... That being said, i don't think you can do harm by using this procedure. If the vendor didn't send real private keys, you should probably just get an error, and that's it... That indeed is is a strange way of refunding someone. TS, make sure after doing the steps mentioned that you move the coins to a new address that you own yourself. Otherwise, the vendor can swoop in at any point to take the coins back. he doesn't have to do anything else after sweeping because by sweeping the private keys he is moving the funds to an address only he controls. that is what sweeping means.
|
|
|
* Asymmetric wallet file encryption: A keypair is derived from the wallet password. Once the wallet is decrypted, only the public key is retained in memory, in order to write the encrypted file.
What is the advantage of this over the earlier symmetric encryption?
|
|
|
Maybe I am being paranoid - but when you use a deterministic address where the address is generated from a public key such that the corresponding private key can know there was a payment, I suspect there is a mathematical way to determine payment addresses are related.
No there isn't. The only way to tell they are related is because they show up in transactions together when you go to spend your coins. This applies to all wallet types including the old fashioned non-deterministic ones. Of course if you are worried about people finding out that the addresses are related by looking at the blockchain you can simply use coin control features as found in electrum or bitcoin core to pick your inputs manually and avoid revealing any links between your addresses. Also in case you didn't know even Bitcoin Core is now deterministic. BTW regarding generating lots of private keys offline please do read this: https://bitcointalk.org/index.php?topic=912337.0Pay special attention to posts by gmaxwell and dabura667 (especially post #8) Also if the client is coming up with a deterministic address, how the fuck do I know what invoice it is for?
I just made all that up. No client supports picking up xpubs from DNS, validating DNSSEC and then generating an address to send payments to. Stealth addresses are the closest thing to that but they are not widely supported. Payment requests OTOH are very well supported. Just use that and spare us
|
|
|
- Replace the web page file on the webserver with one that has the attacker's master public key
Why not just replace the web page? Payment requests work because we rely on commercial CAs to validate identities. How is the server's public key going to be checked in this scenario? What I'm suggesting has nothing to do with certificate authorities. The public key would be in DNS - and secured by DNSSEC. I would suggest using libsodium for signing the payment address, because libsodium is a lot easier to implement and also has support in PHP via a PECL module and will have native support in PHP in PHP 7.2. So sign the address with libsodium, and put the public key in DNS secured by DNSSEC. If users' bitcoin clients are going to check dns then why publish the address on the web page at all? Let the bitcoin wallets grab the xpub from dns and send to some address derived from that.
|
|
|
Hello, i want to transfer a few btc addresses from Armory Wallet to Electrum. I have extracted the private keys from Armory : the ones are PrivBase58 and the others are PrivHexBE. After installing the latest official version of Electrum Wallet, using the next chain : Wallet-Private Keys-Sweep-Enter private keys /Electrum let only to enter these with PrivBase58/ i receive only this message: "No inputs found.(Note that inputs need to be confirmed)" What to do My purpose is to load the balance of the addresses in Electrum and to handle them, because iam out of nerves to wait 5 or 6 days in order Armory to load the blockchain... First of all you should have created your own thread instead of bumping this one year old one. The OP was trying to sweep keys to an offline wallet and that was his problem. So obviously make sure electrum is connected to the net. There should be a green orb icon in the bottom right corner of the electrum window. To add to what Hi-Tec99 said your private keys should be in wallet import format. They look like this: >For private keys associated with uncompressed public keys, they are 51 characters and always start with the number 5. Private keys associated with compressed public keys are 52 characters and start with a capital L or K. https://en.bitcoin.it/wiki/Private_key#Base58_Wallet_Import_formatSo 51-52 characters starting with 5, L, or K.
|
|
|
|