How to import private keys - BitcoinWiki

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet?

Hi,
I want to import the bitcoins of my bitcoin-qt wallet into another client.
I understand that this is done by importing a private key, that I can get with the "dumpprivkey" command on the public address.
However, there are multiple addresses in my wallet when I type "listaddressgroupings"
Which one of the addresses should I use to get the private key allowing to import the total bitcoin balance of the wallet into another client wallet?

Thanks
submitted by mparkit to BitcoinBeginners [link] [comments]

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet?

Hello please a friend of mine lives in Granada Nicaragua and he's relatively new to crypto. please can you recommend a site in which he can buy Bitcoin and the processes thanks. Hi, I want to import the bitcoins of my bitcoin-qt wallet into another client.
submitted by priscillamhudak to ProjectOblio [link] [comments]

Why isn't there a Wallet.dat or private key import feature in bitcoin-qt?

This is what I am asking myself for two years now and I finally decided to ask. In addition to that: why not a paper wallet print and import feature (maybe webcam support)?
I now that there is a ton of other potential features and the development takes time and so on. But these here appear to be extremely essential since using bitcoin is in fact very risky without these simple precautions.
You want unskilled users to search for a folder that is not even visible on a fresh system? The people who cant find this folder are the ones who also make other mistakes and the ones who get their bitcoins stolen.
submitted by rchlx to Bitcoin [link] [comments]

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet? /r/BitcoinBeginners

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet? /BitcoinBeginners submitted by cryptoallbot to cryptoall [link] [comments]

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet? /r/BitcoinBeginners

Which private key in bitcoin-qt wallet is needed to recreate total balance when importing to new wallet? /BitcoinBeginners submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Problems importing private key from paper wallet to bitcoin-qt

For testing purposes I sent some BTC to a paper wallet from my bitcoin-qt client and later, after ~50 confirmations I imported the private key from the paper wallet back into bitcoin-qt with the command importprivkey $key $label rescan and after half an hour of rescan it doesn't show anything. Well, almost nothing, it renamed the paperwallet address I sent to in the first place to "$label" in the outgoing transaction, but no other sign of the imported private key, especially the balance didn't change. The Blockchain explorer shows the funds are still under the associated paper wallet address. Anybody knows what's going on here, what I did wrong and how to do it correctly? Thanks!
submitted by kbdwarrior to Bitcoin [link] [comments]

How to import Private Keys in Bitcoin-Qt

How to import Private Keys in Bitcoin-Qt submitted by denart4 to Bitcoin [link] [comments]

Importing private keys into Bitcoin-qt

Hello all,
I’m looking for some advice for a problem I’m having. If this is the wrong sub for it please let me know and I'll be glad to post somewhere else. I need to access funds from a wallet that was generated on blockchain.info which uses seed words on a bitcoin-qt windows wallet. Since bitcoin-qt doesn’t support seed words it’s my understanding that I need to use a BIP39 generator to use my seed words to generate private keys. I’ve done this and was able to generate 30+ private keys which I managed to import into bitcoin-qt using the debug console. After the import I was able to see my tx’s up until the end of July 2017, but I cannot seem to find any transactions past July. These transactions im looking for include a balance of 1BTC which I simply cannot see from any of the private keys I imported. I could try to generate more than 30 private keys and see if any of them have tx’s but past the 25th key there are zero transactions so I’m doubtful that generating 40 or 50 will be anything more than a waste of time. I could be wrong though so I’m curious if anyone has any suggestions here? I need to import into the bitcoin client and using another wallet which supports seed words is not an option at this time. Thanks in advance. PS Is there any possibility the BIP39 generator is not showing me some of the keys? Isn't July 31 when a fork happened? Is it possible the generator isn't able to produce a newer format of key? (segwit?) . I'm using the BIP39 standalone generator from GitHub.
submitted by ryanisflying to Bitcoin [link] [comments]

I just made a video for Newcomers about importing private keys in Bitcoin-Qt

I just made a video for Newcomers about importing private keys in Bitcoin-Qt submitted by digilychee to Bitcoin [link] [comments]

Importing private keys into Bitcoin-qt /r/Bitcoin

Importing private keys into Bitcoin-qt /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Problems importing private key from paper wallet to bitcoin-qt /r/Bitcoin

Problems importing private key from paper wallet to bitcoin-qt /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here
Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe shell
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to Bitcoin [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Windows Guide to using Trezor with Bitcoin Core (HWI)

This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest TLDR is here

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

  1. Download and isntall Python
  2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
  3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
  4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
  5. Setup venv python -m venv .venv
  6. Enter venv .venv\Scripts\activate.bat 1
  7. Install dependencies python -m pip install -U setuptools pip wheel
  8. Install TrezorCTL python -m pip install trezor[hidapi]
  9. Install HWI python -m pip install hwi pyside2
  10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
  11. Extract MS64\dll\libusb-1.0.dll from the archive
  12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

  1. Download and install MSYS2
  2. Launch a mingw64.exe
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

  1. Launch hwi-qt.exe --testnet (assuming testnet)
  2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
  3. Select you trezor from the list then click Set Pin (if needed)
  4. Ensure your Trezor in the dropdown has a fingerprint
  5. Select Change keypool options and choose P2WPKH
  6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

  1. Launch Bitcoin Core (testnet) (non-pruned) 2
  2. Select Console from the Window menu
  3. Create a wallet createwallet "hwi" true
  4. Ensure that hwi is selected in the console wallet dropdown
  5. Verify walletname using the getwalletinfo command
  6. Import keypool importmulti '' (note ' caging)
  7. Rescan if TXNs are missing rescanblockchain 3

( C.I ) Grab Tesnet coins

  1. Select the Receive tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Select Create new receiving address and copy address
  4. Google "bitcoin testnet faucet" and visit a few sites
  5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

  1. Select the Send tab in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Verify your balance in Watch-only balance
  4. Rescan if balance is wrong (see B.II.7) 3
  5. Craft your TXN as usual, then click Create Unsigned
  6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

  1. In HWI-QT click Sign PSBT
  2. Paste what you copied in D.I.6 in PSBT to Sign field
  3. Click Sign PSBT
  4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

  1. Select the Console window in Bitcoin Core (testnet)
  2. Ensure that the Wallet dropdown has hwi selected
  3. Finalize PSBT: finalizepsbt
  4. Copy the signed TXN hex from the hex field returned
  5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
Footnotes:
  • 1. - Later version of python put the activate script under 'bin' instead of 'Script'
  • 2. - You can run pruned, but you need to have a fresh wallet
  • 3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd
submitted by brianddk to TREZOR [link] [comments]

How-to: setup your multisignature Cold wallet in Bitcoin Core 0.20 (highest security setup)

Last release of Core is amazing !
The main new feature is sortedmulti descriptor. This allows you to import your multisig setup in Core almost as if it was Electrum when combine to the new PSBT export in GUI !
As it needs command line and some weird checksum, you also need to input very long command in the console and if you made a mistake, you cannot copy the last command you made. So take your time when the commands are long to check everything and don't miss anything, use copy paste before validating the long command. You only have to do this once fortunately :)
I detail here how you do it with a k of n setup, good luck:
And you are DONE ! You should get the exact same addresses than Electrum and you can created receiving addresses in Qt ! To send money, just go to the send section, use the new coin control feature and export a partially signed transaction. You can use HWI or Electrum to sign it with your hardware wallets !
Notice: You can import more or less than 2000 addresses of each type. If less, blockchain rescan is faster but you may need to redo what we have done here later when all addresses will have been used once. If more, it is the contrary.

You now have the most possibly secure setup in one software: multisig with hardware on the full node wallet. When Bitcoin Core 0.21.0 will be out, we will also have native descriptor wallet so maybe we will have HD version of this. But for now, this is the best you can do ! Enjoy :)

P.S. : if you like doing things in one shot you can do the last two steps in one big command: importmulti '[{"desc": "wsh(sortedmulti(k,[path1]xpub1.../0/*,[path2]xpub2.../0/*,...,[pathn]xpubn/0/*))#check_sum0", "timestamp": birth_timestamp, "range": [0,2000], "watchonly": true, "keypool": true}, {"desc": "wsh(sortedmulti(k,[path1]xpub1.../1/*,[path2]xpub2.../1/*,...,[pathn]xpubn/1/*))#check_sum1", "timestamp": birth_timestamp, "range": [0,2000], "watchonly": true, "internal": true}]'
submitted by Pantamis to Bitcoin [link] [comments]

Segwit paper wallet sweep to destination address. HOW?

So a friend bought his first amount of bitcoins. He does not and will not buy a hardware wallet yet, so I offered to help him store/retrieve his BTC.
I suggested the setup I used before having a Ledger Nano S (I still use it, my BTC are not yet on the Ledger because of the high fees):
1) Make paper wallet offline
2) Store it on an encrypted veracrypt container
3) When it's time to sell the coins, sweep the private key using Mycelium directly to destination address (usually deposit address on an exchange).
This works, and it is quite safe. Private key is offline always, encrypted, never touches the clipboard, and is swept using Mycelium straight to destination, so it does not get stored on the android phone as well.
Thing is: To save fees, I suggested that we use a Segwit Address generated from segwitaddress.org, but I don't believe there is a wallet that supports sweeping segwit private keys directly to destination. I believe Samourai wallet does sweep segwit ones, but they will be transferred to the Samourai wallet, and the transfer to the destination will be another transaction (defeats the purpose of using segwit to pay less if I have to do two transactions).
This is the use case. Does anyone know how to sort it out?
Note: I don't really "trust" the wallet sweep feature on segwitaddress.org. I tried to run it offline with an empty wallet, but it did not generate a transaction or I did something wrong. I would like to use a better stablished open source code wallet to do the sweep.
Note 2: we did not send the money to the segwit address yet. If I don't have an alternative, I will just generate a normal address for him.
Help?
submitted by cryptosnake to Bitcoin [link] [comments]

PSA: Using paper wallets, understanding change addresses.

Paper wallets are a handy little store of a private key offline. Unfortunately, many people seem to misunderstand one of the fundamentals of how they work, and subsequently lose vast amounts of money. Storage in a paper wallet is completely safe, retrieving the funds from one is less so.
In typical use, a paper wallet would be retrieved into a client using the importprivkey command, and from there it should be assumed at the paper wallet is completely useless. From the moment the first transaction is made, the paper wallet is empty, this is due to the way to the way that the client handles change.
Lets explore this with an example.
Let's imagine that I send the full contents of my paper wallet (5BTC) to a new address, once I have imported it to bitcoin-qt.
+-------+ | paper | +-------+ | | | V +--------------------+ | destination (5BTC) | +--------------------+ 
This is the expected behaviour, my paper wallet now contains 0 bitcoin, and the receiving address contains 5BTC.
This time, I am going to send 1BTC to an address from my 5BTC wallet, and keep 4BTC in my paper wallet for later.
+-------+ | paper | +-------+ | +------------------------+ | | V V +--------------------+ +---------------+ | destination (1BTC) | | change (4BTC) | +--------------------+ +---------------+ 
Unfortunately this isn't how bitcoin works. There is now nothing in my paper wallet, and 4BTC has been moved to a new "change" address. If you wish to keep this amount in an offline address than, you must create a new paper wallet for this change.
The mistake people have made in the past is to import a paper wallet with 100BTC in it, spend one or two, and then assume that the paper wallet still holds 98BTC.
This situation is only an issue if you reimport a wallet and expect the funds to remain on it. This issue doesn't apply if you are using your wallet normally.
Hope this saves people some serious hassle, and money.
This text is unlicensed. Print it, modify it, sell it.
submitted by explainschange to Bitcoin [link] [comments]

Bitcoin client developers - default to sending transaction "change" to sending address

I've been here for almost a couple of years now and seen too many times people losing coins because the change does not go back to the sending address. Most users do not understand that this new "change" address will not exist in an imported paper wallet (requiring creating a new paper wallet) or that the wallet file in Bitcoin-Qt has only a limited number of addresses and needs to be backed up multiple times with continued use.
The default behavior in all clients should be to send the change back to the sending address. Sending change to a different address, while obfuscating the owner of coins, is an advanced feature - not a default.
submitted by themgp to Bitcoin [link] [comments]

Mentor Monday, August 01, 2016: 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 BashCoBot to Bitcoin [link] [comments]

Where can I import my wallet.dat?

Hello!
I am fairly new to Bitcoin, but one year ago, I made a Bitcoin address on Bitcoin-Qt, but I stopped using it, because the whole database downloading took so much space on my disk.
I have my wallet.dat file, but I don't know, where can I use it. I tried Electrum, but it seems that the wallet.dat import doesn't work there.
Can you recommend me any other wallets, where I can import that file?
Thank you.
submitted by Amic58 to Bitcoin [link] [comments]

This obviously isn't reaching anyone

This obviously isn't reaching anyone submitted by themusicgod1 to Bitcoin [link] [comments]

Moving wallet.dat to Ledger and splitting off BCH?

I've been out of bitcoin for a few years but had a little sitting in a wallet.dat file. I don't have bitcoin-qt loaded anymore, just the .dat file. Can anyone point me to the process for sending that to my new Ledger nano and how to split the BCH from it?
submitted by justajackassonreddit to Bitcoin [link] [comments]

Bitcoin-Core: Import private key from old watch only ... How to Import a Private Key for Bitcoin and Other Cryptos ... How to import Private Key (Bitcoin Address) into ... Hack bitcoin (private script) 2019 Import non spendable bitcoin with private key - YouTube

If no errors occurs, the import is a success and Bitcoin-QT users will be able to see the new address in the GUI immediately. If you need to import more keys, just repeat the instructions above. There is currently no command to import a batch of private keys so you will need to wait a minute or two for each key to be imported. Cleaning up bitcoind walletlock This will lock your wallet again ... Since Bitcoin-QT/bitcoind v0.6.0, you can import private keys using built-in RPC command importprivkey. Before v0.6.0, you needed to rely on third-party wallet.dat manipulation tool such as Pywallet. This article describes how to import a private key through the RPC API of bitcoind, which is a topic for advanced users. Export: The process of creating a file containing a wallet's private key data. Exported keys can be imported to a new/different wallet to give access to the Bitcoins associated with the exported private key(s). Import: The process of gaining control of Bitcoin via an exported backup. Wallets can import private keys via text files or QR code ... Then click Import Existing Bitcoin Address. You can enter WIF (Wallet Import/Export Format) or compressed private key. Also you can scan QR code keys from paper wallet. This will allow you to actually send and receive bitcoins to and from this bitcoin address. Site may propose you to transfer all bitcoins from imported address to integrated HD ... Help:How to import private keys in Bitcoin Core 0.7+ From Bitcoin Wiki. Jump to: navigation, search. This page contains sample addresses and/or private keys. Do not send bitcoins to or import any sample keys; you will lose your money. Before reading this page, users should note that messing with ECDSA private keys is very dangerous and can result in losing bitcoins, even long after the import ...

[index] [9629] [40724] [46497] [5950] [16608] [14920] [36114] [3794] [13569] [36373]

Bitcoin-Core: Import private key from old watch only ...

Dash is built from Bitcoin's core code, meaning that it remains compatible with systems that are already designed to work with Bitcoin. The creator of Dash, Evan Duffield, works with a "core team ... Learn how to import a private key. If you’re just getting started or would like to move your BTC, BSV, BCH, LTC or other blockchain assets from another walle... தமிழ் செய்திகள், உலகச்செய்திகள், சினிமா விமர்சனம், சினிமா ... Know how to import private key or sweep private key. A quick way to sweep bitcoin private key safely. I've swept my private key using Blockchain.info to show how to do that. You always dream of finding software to decrypt the private key of some Bitcoin addresses. Here you are the best private key decryption software. the bitcoin...

#