How can I transfer a Bitcoin-qt wallet to Electrum ...
How can I transfer a Bitcoin-qt wallet to Electrum ...
bitcoin core - How do I load wallet.dat on new PC and ...
Can you Importa wallet.dat file into Electrum? : Bitcoin
Where can I import my wallet.dat? : Bitcoin
Importing your private keys into Electrum – Bitcoin Electrum
Was using bitcoin-qt on OSX, blockchain got corrupted and now it is impossibly big to re-download, what thin clients can I import my wallet.dat into?? OSX 10.7.5. I already tried electrum and looks like I'd have to build it from github, can't figure it out. please help.
Send help! is there a safe way I could download a torrent of the blockchain? i tried to reindex the blockchain (after my harddrive got unplugged while bitcoin-qt was running) and it looks like it would literally take a week of spinning my poor laptop fan balls out. edit: wallet.dat is encrypted and safely backed up.
Can I import my wallet.dat file from Bitcoin-qt into Electrum or some other light-weight or online wallet?
I can't get the entire blockchain on my computer, but I have the wallet.dat file from Bitcoin-qt. I'm wondering if there is an online wallet or other light-weight wallet I can import the wallet.dat file into and send my bitcoin out to my electrum wallet. I just need to get my bitcoin out of the bitcoin-qt client with nothing but the wallet.dat file. I'm on a mac.
Storing your coins safely while not risking loss of keys
This was originally an answer to a question that was asked here, but OP deleted their post. This might help some newbies (especially the multisig edit at the end), so I want to make sure it's still accessible here. The original question was whether the Electrum wallet stores a Trezor's private key when using a passphrase. OP noticed that their Trezor wouldn't connect to their Electrum wallet when entering a different passphrase than they used when creating the wallet. Thus, OP (likely) assumed that the wallet stored the private key, as it somehow knew that a different private key was now used. Here is my original answer (with some modifications): IMPORTANT: I'm assuming here that you connected your Trezor by choosing the "hardware wallet" option in Electrum, rather than giving Electrum your 12/24 seed words. TL;DR: No, your coins are safe :) I'm assuming by passphrase) you mean the 25th (or 13th) word. When you have this feature enabled, a private key gets generated every time you enter a passphrase. When you enter the same passphrase you used to create the wallet, the wallet with your funds shows up. Whenever you enter something different, a different private key is generated on your Trezor. This allows you to have multiple different wallets, for example by choosing the passphrases "First Wallet", "Second Wallet", "Third Wallet", or a secret wallet with a secret passphrase. So whenever you enter a new passphrase when connecting your Trezor to Electrum, the Trezor will send a new public key to Electrum. Electrum will then derive addresses from this public key and check those for balances. It won't find any, as you used a new passphrase. EDIT: I just realized that you said your wallet doesn't connect to Electrum when you use a different passphrase. This is simply because Electrum doesn't receive the correct public key from the Trezor and therefore Electrum thinks it's a different wallet (which it is). When you enter the passphrase you used during creation of your wallet, the Trezor will send your actual public key to Electrum, which will then find addresses with balances, which it will show to you. EDIT (to clarify): Connecting your Trezor after creating the wallet is only necessary to send funds or verify addresses, as the public key is already stored in the wallet.dat. The only thing Electrum actually stores is the public key, which can only be used to look at your Bitcoin, not to move them. You might want to keep this public key a secret as well though, since it links all your funds to you. This is what Electrum stores in the wallet.dat file, which you can just encrypt by choosing a password for it. Well done using a passphrase by the way! Should someone get their hands on your Trezor, a sophisticated attacker can get the secret key off the device in 15 minutes. Using a passphrase makes this attack almost useless, as the both secret key AND the passphrase are needed to move your funds, and the passphrase is not stored on the device. A passphrase also allows you to hide funds from potential robbers that force you to unlock your wallet. You can do this by activating the passphrase feature and sending your funds to a wallet with a secret passphrase (do NOT lose this, as losing your passphrase renders your funds inaccessible). Afterwards, you can safely deactivate the passphrase feature, so the device doesn't even ask for one should you get robbed. Simply reactivate it when you need to access your funds. EDIT: Should you be worried that you might forget your passphrase, you should look into multisig wallets. Depending on how you set this up, you can make it more secure against theft and less likely for you to lose access to your funds. Say for example you get four wallets: two hardware wallets, a well-protected (airgapped) laptop with Electrum, and a secure mobile wallet that allows for multisig (like Fully Noded). You can then create a 2-of-4 multisig wallet that requires you to sign transactions with any two of these four wallets. The increase in security comes from the fact that an attacker now needs full access to two of your devices (or their stored private keys) at once. At the same time, the fact that you yourself now also need access to only half of your devices means that in the event of a total loss of one (or even two) of them, you can still move your funds to a new wallet. As long as you do regular checks (e.g. first day of each month), ensuring that you still have access to all your devices' stored private keys, you can always catch a loss of keys and fix this without losing funds (by creating a new multisig wallet and sending the funds there). This allows you to use a passphrase on your wallets without storing it anywhere physically or digitally. This would usually be very risky, as forgetting the passphrase would lead to a loss of funds, but this risk is now close to eliminated. (The following part was not in the original answer) Some IMPORTANT general secruity tips:
Consider including trusted friends and/or family members as co-signers for a multisig wallet. This ensures that it's not even possible for you alone to hand over funds to an attacker. Depending on your level of trust, you might want to make sure that your co-signers can't collaborate to steal your funds (if you include 3 people, create at least a 4-of-n multisig). You could also deliberately make it possible for all or even just some of your co-signers to move your funds (3 co-signers, 3(or less)-of-n multisig) to make sure your funds aren't lost should pass away unexpectedly.
Consider running your own full node and Electrum server (also check the alternatives), which you connect your Electrum wallet to. This ensures that you don't send your public key to anyone else. If someone knows your public key, they know how much BTC you own, making you a potential target.
Always encrypt your wallet.dat (or whatever you called your wallet file), even if it's a watch-only wallet. This protects your public key (see 1. for why you want that).
Create watch-only wallets: Use an airgapped) device to create a wallet with Electrum (make sure to back up the seed phrase) and export the public key. Then create a new watch-only wallet on another device (like your everyday laptop) with that public key to be able to check your funds. To create the initial wallet, you can also use any other hard- or software wallet that allows you to export the master public key.
Hide, or (when using a hardware wallet with a passphrase) even delete your watch-only wallets. Hiding your funds makes you less of a target. When using a hardware wallet, recreating the watch-only wallet is fast and simple, so you don't need to store it if you don't want to check your funds every day. Note that this approach doesn't help much when you don't use a passphrase, as an attacker will obviously check the passphrase-less wallet no matter what.
Keep some funds on your hardware wallet(s). If an attackers sees funds on the wallet(s), they might not force you to enter a passphrase or ask if you have any multisig wallets (lying under pressure is hard).
Hide all your wallets in different places. If someone sees that you have multiple wallets lying around, they might realize you have a multisig wallet.
Don't risk a robber getting (for example) two keys to your 2-of-4 multisig wallet and then racing them to move your funds with the other two keys when they leave. They're gonna come back and be pissed. If it comes to this, you need protection until the robber is caught. STAY SAFE!
The easiest way to solve a problem is to never have it. Don't make yourself a target. If nobody even suspects that you have a multisig (or any wallet at all), they're probably not gonna look for it.
Please correct any mistakes you find and I will edit my post. I will also gladly add more tips to the list. I will of course credit anyone who helps. Tip for devs who want something cool and important to work on: Make the creation and usage of multisig wallets as noob-friendly as possible. If someone expresses worries about losing access to their funds by forgetting the seed phrase, wallet pin, etc. (someone in my family actually brought this up to me), multisig wallets are the perfect solution as they add redundancy.
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?
past week installed the new plugin that allow me to connect my electrum wallet to bitcoin-core, i use a hardware wallet and worked like a charm. Then today was updating the node and used bitcoin-qt instead of bitcoind and when was waiting suddendly i see some text in the gui where it says "recent transactions", and a lot of transactions where there. Then was like WTF happened here, someone stole my btc?, or installed a compromised version of electrum(i use archlinux and install from the repos). Why some transactions where there, i neved imported my wallet to bitcoin-gui. Inmediately deleted the wallet.dat and did the same in electrum, but my question is: Was something imported into bitcoin-qt?, all my history was redeable from the gui, i never imported into bitcoin-qt, and as far i know the seed never leave the hardware wallet. This is normal?, at least all my funds are still there but im really worried. PS: everything happened with my hardwallet unplugged. TL:DR: Connected my cold wallet to electrum(connected to bitcoind) past week, never to bitcoin-qt, today opened bitcoin-qt and all my history of transactions from my cold wallet(unplugged) was there(bitcoin-qt), is this normal?.
past week installed the new plugin that allow me to connect my electrum wallet to bitcoin-core, i use a hardware wallet and worked like a charm. Then today was updating the node and used bitcoin-qt instead of bitcoind and when was waiting suddendly i see some text in the gui where it says "recent transactions", and a lot of transactions where there. Then was like WTF happened here, someone stole my btc?, or installed a compromised version of electrum(i use archlinux and install from the repos). Why some transactions where there, i neved imported my wallet to bitcoin-gui. Inmediately deleted the wallet.dat and did the same in electrum, but my question is: Was something imported into bitcoin-qt?, all my history was redeable from the gui, i never imported into bitcoin-qt, and as far i know the seed never leave the hardware wallet. This is normal?, at least all my funds are still there but im really worried. PS: everything happened with my hardwallet unplugged. TL:DR: Connected my cold wallet to electrum(connected to bitcoind) past week, never to bitcoin-qt, today opened bitcoin-qt and all my history of transactions from my cold wallet was there(bitcoin-qt), is this normal?.
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
I found a Bitcoin on a wallet on an old laptop I was going to throw out. I'ts taking forever to synchronise as it was last used about 2 years ago and it keeps overheating and switching itself off. Is there a way of speeding up the synch?
Years back I installed bitcoin QT (I think) and bought around .1BTC. I spent most of it, but I think there's some left, I kept the wallet .dat after I deleted the client. Is there any easy way to extract the keys so I can import them into exodus? I'm on Ubuntu, but I have access to a windows machine if necessary. Also I'd rather not download the whole blockchain.
Electrum doesnt reconigze my wallet.dat (from bitcoin QT) what to do?
Guys, i downloaded electrum on my laptop and tried to import my old wallet.dat from (bitcoin QT) 2017. But Electrum doesn't recognize the file. Anyone know how to solve this f*cking problem. Perhaps any other suggestions ?
WILL PAY .25 BTC TO WHOEVER CAN HELP ME SOLVE MY PROBLEM
Hey guys, so long story short i have a btc core wallet on my computer that I hadn’t opened in a while. When I did my hdd didn’t have enough space to download the full blockchain, so i googled how to prune and did that. Only problem was it kept saying error for some reason after sometime of downloading the blockchain. So i backed up my wallet and downloaded the new btc core wallet because my current one was from 2014. Now it doesn’t show any of my btcs or transactions! When I tried moving my wallet.dat file into the new btc core it shows absolutely nothing. Since then i have deleted the old btc core wallet and am afraid that i lost my bitcoins. Does anyone have any solutions? Anyone that can get help get my bitcoins back I WILL GIVE .25BTC! Thank you!
Think I might've lost 5 btc, reward for someone who can help me sort this situation out.
I purchased a few items on newegg and decided to pay it with bitcoin. Then newegg launches bitcore from my computer and so I sent my btc from blockchain.info to my bitcore address (which i now realize was dumb of me). So i'm sitting here and my btc hasnt shown up in my bitcore and I realize that bitcore is "out of sync" and is 3 years behind synchronizing with network. So my question is there anyway I can retrieve my btc quicker or maybe find them if they got lost i'm fairly new to btc so I dont know much. Edit: Still looking for help on this problem. Current reward is 1BTC, if you're sure that you know how to fix this then request my skype so we can im and get this done asap. EDIT2: thank so much to carsten_ger for helping me,I got my btc back :D !
I had an offline Armory wallet storing my bitcoins at the time of the fork. Since then I have moved my coins to Trezor but never claimed my BCH. I have the private key for the old wallet in hand. I read about putting the old private key in coinomi as a BCH "wallet sweep". That didn't work. I downloaded electrumcash but that app wants me to enter in my private key before even making an account, that doesn't seem right?? Is there a better solution out there for this? I know trezor supports BCH now but from what I can tell, they can only help me claim it if I had my BTC in the trezor at the time of the fork. Anyone with experience doing this able to advise me?
So I opted to migrate from coinbase to a local wallet. Naturally, I download Armory and shoot it a send for 1BTC. 225 confirmations on the SEND, but wallet never receives it. Turns out, running Armory wallet has been corrupting my database. Every time I run it a background process it spawns causes Bitcoin-QT to fail. I've tried uninstalling and re-installing bitcoin, armory wallet three times. I've deleted my bitcoin directory in %appdata%, ensured downloads are never interrupted. Is there any way at all for me to recover the BitCoin I sent to armory wallet provided I can never get armory wallet to work correctly? Any help appreciated. Here is the errors: 2015-08-21 14:48:15 init message: Activating best chain... 2015-08-21 14:49:23 Corruption: block checksum mismatch 2015-08-21 14:49:23 *** System error while flushing: Database corrupted
I am trying to move my BCC from Electrum to an exchange, but need help. I followed the first few steps in Electrum's guide- I created a new seed and moved all my BTC from my original wallet to a new wallet. My original wallet is now empty according to Electrum, but I believe there is BCC in there, right? Now I need to import my original wallet's private key(s) to a new wallet that supports BCC. How do I do that, I don't see an exchange that accepts BCC and allows to import private keys. I would prefer to use Bittrex if possible. I'm very new to this, so as much detail as possible on how exactly, step-by-step, I would do this would be much appreciated. Thanks for the help!
Hey everyone, I've been out of the crypto game for a long time, but managed to dig up a wallet that I had stored on an old PC from early 2015. It wouldn't have much in it, maybe a few BTC at most, but it would be nice to recover it and cash out. The machine had Bitcoin Core installed, hasn't been connected to the internet since 2015, and is currently interstate - I've copied wallet.dat and that's all I have access to for now. The wallet is encrypted, backed up, copied to multiple secure locations, etc, and I remember the passphrase, but from what I've read in other threads, the private keys are the important part and I may need to do a "key dump"? I tried installing Electrum and importing the wallet, but Electrum doesn't recognise the file. Am I right in thinking that the following would be the best solution?
Download and install Bitcoin Core.
Place wallet.dat into the appropriate directory.
Open Bitcoin Core and allow it to "catch up" and download 240 GB worth of blockchain history.
Possibly be forced to input the passphrase to access the wallet again, and transfer BTC out to an exchange of my choosing (unsure if this is how it would work at this stage).
Is there a way to recover the wallet without being forced to download hundreds of GB worth of data? I live in Australia, with typical Australia-tier internet, and it could quite literally take up to a week to download. Apologies if there's any shortfall of knowledge on my end of things, it's been a long time since I've kept up with crypto and things seem to have changed quite a bit over the last four years. I appreciate any advice, and y'all are welcome to shame me on my relative ignorance, lol. Thanks!
Edit: warning, rant Has anyone else had the experience that running/maintaining a Monero node is much easier than Bitcoin? I've been dorking around since July, doing everything in the terminal on a Qubes VM. Monero comes with simple monerod status and monerod sync_info commands to give you a range of useful info and overview of the current state of your node. Bitcoin has a bunch of individual commands you can aggregate to partially deduce progress, which I have arranged into my own little script. But I didn't find the target block until parsing through the log file. And you have to use other terminal commands like du - ahmd 1 | grep .bitcoin and then run a timer, just to see what your dl speed is, whereas Monero tells you outright. This is important for monitoring your connection over multiple days of download. I had a hard time finding a BTC wallet that could remotely connect to my own damn node without installing additional software (such as electrum server). I had the silly idea that I could just point a mobile SPV wallet to my own remote node. Hell, the BTC core wallet didn't even have code separation between the node and wallet until just a few months ago. And now I'm restoring an old Bisq wallet which I only have the seed for. While Bisq was scanning my node, it got hung up at corrupt blk01234.dat file, which actually crashes my Bitcoin node when it receives the data request. So my node had a corruption for 2 months without it knowing, which I only found caz Bisq (I think occurred during a hiccup in transfer from 512GB SD card to SSD). I tried to drop/replace the blk and rev files, then reindex. But once again, stupid reindex doesnt show progress with any obvious terminal commands. Monitoring disk space, it seemed to be progressing abysmally slow with most my CPU/RAM dedicated to it. I was close to done until a power outage overnight and not enough battery to complete. And even though Bitcoin Core stores everything as individual files, seems it lacks the ability to detect corruption/discard corrupt files and go backwards to the last good file. So I get to start over. At this point Im actually syncing from scratch in a separate VM while simultaneously reindexing just in case reindex doesnt fix the problem. I give it 50/50. I know this is kind of a rant. But I wanted to share my experience with some people who can relate or at least understand. It's weird that for a project like Bitcoin, that the core software and UI would be so rudimentary, non-versatile, and even fragile. Given the ease to configure Monero (including using Qubes qrexec to isolate the wallet in an offline VM), it's straightforward UI and documentation, that it was designed to have separate node and wallet functions, I'm guessing that these problems are much more rare, and easily fixed. That's just an educated wild ass guess of course, since I haven't had any problems. At any rate, props to the Monero devs for making software that is straightforward and easy to use.
Long time BTC hodler needs help with claiming fork airdrops
I haven't touch my BTC for a long time but due to tax reasons (not an US citizen) it's a good time for me to claim and sell the different air drops/forks that are available before end of December this year, especially BCH and BSV. Yes, I know I'm late to the game but my BTC holdings are a long bet and I don't easily risk or touch them. I've read a lot of threads and guides on BCH/BSV splitting but haven't found all answers I need, so here it goes. Any help is appreciated! Some background info: MY BTC UTXOs are from 2013 and early 2017 and are in a Bitcoin Core 0.19.0.1 wallet.dat (Windows). For preparation I have just moved all my UTXO's to a completely new Bitcoin Core wallet.dat and made several backups of the two wallet.dat files both before and after I moved the UTXOs. Question 1) Running Bitcoin ABC wallet 0.20.7 with the original BTC wallet.dat displays the correct number of BCH available for me to transfer where i want. Can I safely transfer all those UTXOs from Bitcoin ABC wallet 0.20.7 to my Exchange (Bittrex) without risking the transaction to replay on the BSV chain? Question 2) If the answer to question 1 above is no - From what I understand from all guides and other threads I've read (although some of them are old) I should import the private keys from Bitcoin ABC wallet in to Electron Cash. I read that the Electron Cash 3.3.4CS is no longer recommended for splitting and latest version only supports BCH. So my guess is I should use Electron Cash 4.0.12 from https://electroncash.org/ and Electrum SV 1.2.5 from https://electrumsv.io ? Is that correct? Is the following a correct procedure? (or is there an simpleother method?) a. Move all BTC UTXOs in Bitcoin Core wallet to a new wallet.dat DONE b. Import old BTC wallet.dat to Bitcoin ABC wallet. (Full amount of BCH are displayed) DONE c. dumpprivatekey command in Bitcoin ABC wallet d. Import the private key in to Electron Cash 4.0.12 e. Buy some BCH on Bittrex and send it to the Electron Cash address f. Send entire BCH to Bittrex (and sell for BTC....) g. Import the private key in to Electrum SV 1.2.5 h. Send entire BSV to Bittrex (and sell for BTC....) Question 3) Are there any other forks worth claiming (for immediately selling) and are fairly easy to self extract non custodial? I hold exchange accounts at Bittrex and Poloniex so the forks should be available to sell there. I do not want to go through the hassle and privacy risks of registering yet another KYC account unless the fork reward is substantial. Cheers!
Electrum - Bitcoin Wallet 4.0.2 Englisch: Mit dem kostelosen Tool Electrum erhalten Sie eine Bitcoin Wallet für den PC. Just select “Import bitcoin addresses or private keys”. And then you paste in your private keys in the box that it displays on the next screen: Enter one private key per line. Electrum supports mini private keys and full sized keys in Wallet Import Format (WIF). Note: if the addresses in the source wallet begin with 3 you have to prepend “p2wpkh-p2sh:” to each private key before ... Create a new Electrum wallet, select "Import Bitcoin addresses or private keys", convert your keys according to the rules available by clicking on "Info" button (you may not need to convert if your wallet.dat is quite old) and you're good to go! The above is tested on Bitcoin Core 0.20.1 and Electrum 4.0.2. March 12, 2014 Importing Bitcoin from a paper wallet into Electrum. Sending money to a paper wallet is the easy part. Getting it out is a little more complicated. So here’s a step-by-step guide. Below is a paper wallet containing 0.36477 BTC (at the time of this writing). The paper wallet was made with bitaddress.org, using BIP38 encryption for the private key. (To see more about creating ... Create a new Electrum wallet, select "Import Bitcoin addresses or private keys", convert your keys according to the rules available by clicking on "Info" button (you may not need to convert if your wallet.dat is quite old) and you're good to go! The above is tested on Bitcoin Core 0.20.1 and Electrum 4.0.2.
Backing up Your bitcoins using the Electrum Bitcoin Wallet ...
There are two ways to move private keys into the ZClassic Electrum Wallet: either by importing or sweeping. This video shows how to import and sweep private keys into your wallet as well as how to ... How to Restore a Bitcoin Wallet from a Seed (Electrum ... Bitcoin How to import your old wallet into new one tutorial works 100% Recovered 1.7 BTC - Duration: 8:26. XOOMdotWS 10,023 views. 8:26 ... How to Import & Use Paper Wallets for Beginners - Duration: ... Fix Verge Electrum Wallet Network Issue - Duration: 4:44. maxjac 7,808 views. 4:44. BitShares Tutorials - How-to set up a Wallet ... Erster versuch eine #Wallet.dat zu importieren in eine #ElectrumWallet, ein Privat Key. Alle Dateien habe ich vorher von meinem Computer gelöscht, so das keine Reste übrig sind die evtl. bei ... Even if you lost the seed, as long as you have the correct private key, you can access your money. This is a useful resource for accessing, securely storing,...