How to know private key of a address from Bitcoin Wallet clients (Ex: Bitcoin core 0.10.0)
dumprivkey command on the debug console. You get to the debug console via the help menu about dialog box I think. help menu > debug window > console tab. and how to import a address into Bitcoin wallet ?
Which bitcoin wallet? if you mean core then importprivkey command in the debug console or command line should do it. https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list |
|
|
|
Right now I'm using Bitcoin core and I want to use Electrum. What this procedure work with this combination?
It will work with electrum 1.9.8 but not 2.0.x because this version no longer supports private key imports. Instead it allows you to sweep private keys in which case all the bitcoins are sent to an address in your electrum wallet. Note that imported private keys (not swept but imported) are not backed up by the wallet seed so you'll need to backup the wallet file using file > save copy. This is one reason why importing is not allowed anymore in 2.0.x and future electrum versions. |
|
|
|
I have 0.007BTCs balance on my Electrum wallet and when I'm trying to send the funds to blockchain.info address, The Electrum wallet allows me to send only 0.003 BTCs, when I type 0.004 BTCs or more I show the number in red and says "not enough funds". So, anybody knows why this happens or it is more than 50% transaction fee?
Faucets are a waste of time because the money received from them cannot be spent without paying an exorbitant transaction fee. Transaction fee is a function of the number of bytes in a transaction. The more inputs you have the larger the transaction. In your case you have lots of small inputs that you want to spend so your transaction is very large and costs a lot in fees. Transaction fee is also affected by the age of your inputs. So wait a year or two and the cost of spending those minute amounts of bitcoin will go down because your coins will have "aged". |
|
|
|
What do you mean you need to make frequent backups of your wallet.dat? Wont one suffice?
Well, using the standard client, when you make a new receiving address or when the wallet makes a new automatic change address you'd want to save that. I think the standard wallet keeps a pool of 100 reserve addresses by default ( https://en.bitcoin.it/wiki/Key_pool) that gets saved as part of the backup, so you only need to do backups when you are about to use up the pool. In the past, many people lost BTC when they restored a wallet from an old backup that did not contain newer receiving addresses that were created after the backup was made. Of course if you don't use your wallet or your only use is for coins to keep coming in to the same address(es) then you don't need to keep making backups. Good info. Also I have a laptop and desktop. Is it possible to have Bitcoin-qt synced between the two machines so I can send and receive BTC from both machines using the same wallet and BTC funds? Does this question make sense? bitcoin-qt generates random keys so your two wallet copies will diverge at some point. You should use a deterministic wallet like electrum if you want a wallet that remains consistent on multiple devices. Encrypting a wallet with gpg does have advantages because an attacker would need the gpg private key to decrypt it. As long as you don't make the mistake of also uploading the gpg private key to your cloud backups you benefit from an additional layer of security. |
|
|
|
I see everyone saying: "Don't use web wallets!!". It looks like some people get hacked at Blockchain.info for example.
OK - fine. So use the miserable BitcoinQt instead. But where does bitcoinQt store the private keys? Isn't it just is some local .dat file? Why can't a hacker easily find that file and copy my private keys?
"Miserable" bitcoin-qt has some really smart cryptologists working on it who have made sure that brute forcing the wallet.dat password is difficult. They can't stop users from creating stupid passwords but they've done everything they can do by using a good key stretching function. 90% of the battle is getting access to the encrypted wallet file. The other 10% is brute forcing the password which tends to be easy because people suck at picking passwords. The reason desktop wallets are considered better is because you would have to be personally targeted for someone to get hold of your wallet file. In the case of blockchain.info it's easier to get hold of the encrypted wallet file because they serve it via their website. |
|
|
|
|
Have you switched to a different electrum server? Click on the red icon on the bottom right to select a different server.
|
|
|
|
Well, here's what I am confused about: If the labels and history is all backed up as files on my machine, why would it need a server synch or resynch to show up?
Labels are the descriptions *you've* given to various addresses and transactions associated with your wallet. They are not known to anyone else. There is a label sync plugin which can backup an encrypted copy of your labels on a 3rd party server. This allows you to see the labels on multiple installations of the same wallet on different devices. Is that what you mean? If you are using that then you don't have to backup the labels on your hard drive. Electrum servers provide transaction data and allow electrum clients to broadcast transactions of their own. That is their purpose. The client relies on the servers to interact with the blockchain. Out of curiosity, what programming language is Electrum written in and where can I find the source? Are there any useful tutorials for working with Bitcoin Wallets in programming? I noticed incompatibilities with so many different seed types and I wanted to possibly program something that would use all the seeds and could buy/sell on Coinbase without transferring to a centralized wallet, unless someone already did something like that, that is.
Electrum is written in python. You can see the source code here: https://github.com/spesmilo/electrum/ |
|
|
|
thx for answering me.
I did that, but in my wallet Kopie ( txt format) there are a lot of Numbers and diggits,and even my puplic Master Key.
But no private master key.
If i put the private Master Key in the field, they generate my Bitcoins, but is automati in the watching only modus :/
If i try to write my seed from tails in the field, im not able to click on "Next"....
did i lost my 3 Bitcoins ?
Is someone jusing tails with peristend Volume and Elcetrum here?
Create a new wallet and restore from seed. Instructions for creating and opening different wallets are given here: https://bitcointalk.org/index.php?topic=1006044.msg10925811#msg10925811Next time at the very least mention your electrum version. Tails uses 1.9.8 but you should not count on us knowing that and mention it yourself explicitly. |
|
|
|
|
-1 confirmations are a known bug in 1.9.8. As you said that corrects itself once you restart it.
I've only ever seen red labels right after you change the gap limit. I don't know what's going on with you.
I suggest exporting labels and then restoring the wallet from seed and importing the labels back in. But first you'll need to know how to do multiple wallets with electrum which should answer your last question as well:
- To create a new wallet use file > new/restore. Pick a directory and enter a file name for the new wallet file and then click save. It will then show the usual wallet creation/restore "wizard".
- To open a different wallet use file > open.
2.0.x is backward compatible with previous version seeds so you can upgrade if you like. I wouldn't recommend it because in my opinion 2.0.x isn't stable yet. Your choice.
|
|
|
|
You can also do this with the command line: electrum getaddressbalance 1BitcoinEaterAddressDontSendf59kuE
|
|
|
|
still unsure why my 8 btc are in one of those addresses on change...
That's because you ask questions and then don't read the answers people give you: Every time you send BTC you DO send the entire amount of each input to an address up to the amount being sent plus fee and includes inputs of other addresses as necessary. Every time you receive btc to an address it is a separate input and are entities upon themselves. What you don't spend is returned as "change" usually to a new address, which is commonly referred to as a change address. The bitcoin protocol does not allow any portion of a input to be spent. Each time the entire input is sent. So if you have 1 bitcoin in one address as one input and you send someone .05 btc with a .0001 tx fee, 0.9499 btc will be returned to you as change, usually to a new address unless you clicked the option in electrum to not use change addresses, then the change will be returned as a new input to the same address it was sent from. Every time you receive money, electrum will show a new address to receive the next payment and each time you send btc a new change address will be used.
BTW you haven't even told us what version of electrum you are using. The "receive" tab in 1.9.x and the "addresses" tab in 2.0.x are functionally equivalent. They list all the addresses *you* own. jackbox talks about electrum showing you a new address to receive to. That's Electrum 2.0.x functionality. In 1.9.x all the addresses are listed on the receive tab and you can pick a new one or an old one as you see fit. The history tab lists transactions which include your addresses *and* other people's addresses. So don't pick any address from the history tab to receive money to. |
|
|
|
I have PMed you.
Hi dear you are late i did and exchange with ume here. I forgot about you because i could not see your thread here, Can you please post here your thread so we can see it and do a business with you. Thanks I pmed you the link to my thread. Does your browser not have a bookmarks feature? Here's the link again for your reference: https://bitcointalk.org/index.php?topic=707718.newI don't deal on this site because all the escrow agents, save one, are in the west. They are never online during PK daytime hours. You will have to go through localbitcoins. |
|
|
|
It wouldn't make much sense to create a multi-sig wallet if you have all the keys.
You can implement 3rd party-less 2fa using multisig. 2 of 2 wallet with the seeds on two different PCs. Perhaps when electrum kivy gets completed you could use your mobile as one of these devices instead. Either way you would need to sign the transaction with both devices. |
|
|
|
If it works for you then go for it but the developer is not going to make that change for everyone. You can see his views on the matter in the thread you linked above. |
|
|
|
Thanks. Yes I've read a warning about using non-12 character seeds, but this was unfortunately the only path I could use at that time.
Is there a way to modify this seed (like how v2 uses an extra word) so that it will contain the version/checksum and can still be directly entered into v2?
First of all can you please confirm that my method above worked? I'd like to know in case others face this problem in future. To answer your question if you modify the seed you modify all the private keys and all the address. So it isn't possible because it results in an entirely new wallet. You can create a new wallet if that's what you want. Try this command in your shell/OS command line: electrum --nbits=256 make_seed
The above command will make a 25 word seed with 256 bits of entropy. You can then do a wallet restore specifying this new seed to create a wallet with it. electrum -w /path/to/new_wallet restore
You can then send your bitcoins from your old wallet to this new wallet. |
|
|
|
|
If you don't know how to do this yourself perhaps its best if you handed this work over to someone else? Dave of wallet recovery services gets recommended a lot on this forum.
|
|
|
|
Helloguys guys, Lets say I create a wallet, wrote my seed, and Electrum shutdown, servers goes down, Electrum bugs not dissappear, without import private keys how can I access it now put it on another service.
Sorry If it is a dumb question but previous version people can do it if things collapse
This thread is about importing private keys not exporting them. Exporting private keys is still allowed. You could export them and import them into a different wallet. To export private keys go to wallet menu > private keys > export. |
|
|
|
|
Show Posts
