I want to remove my BTC from an online exchange... where to?
Title says it all really - not overly happy with them sitting on a server somewhere with all the recent legislation about centralised exchanges. Where can I move them where I don't have toworry about any of this? Cheers!
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.
[PSA] Dogecoin Wallet version 1.4 released. You must update.
WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar. This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text. All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file. A very important message/reminder below. 25 Jan 1.5 pre-releases have started. http://www.reddit.com/dogecoin/comments/1uhpwf/dogecoin_for_mac_14_topic_thread/ OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed. For a Windows computer the version must be 1.4. - 1.4.1 just released! See below For a Apple Mac Computer the version must be 1.4 Download links: [Windows Download Link](https://github.com/dogecoin/dogecoin/releases/download/1.4/dogecoin-qt-v14-Win.zip) <<--Click to start download Windows Download Link 1.4.1 UPDATED 19JAN Mac Download Link <<--Click to start download Mac users can join this thread if there are any problems Android (phone): Please see This post To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software. You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like. Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet. What happens if I get an error when I open the new wallet? An error was reported called "11DbException" If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes. Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting. Reebzy might have found a solution for Apple Mac Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork. How do I know if I am on the right block chain? Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number *Notetheexamplenumbersinthepicturesmightbeoutofdatebythetimeyoureadthem Now go over to http://dogechain.info/chain/Dogecoin . This website is the official Dogecoin blockchain website. Check the block number they're reporting The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging. I'M NOT ON THE CORRECT BLOCK CHAIN My numbers are very different. How do I get back onto the right block chain? IMPORTANT For windows: 1)Close down the Dogecoin wallet client. 2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin 3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file! 4)Download this update file and place it into the Dogecoin folder where the other file was deleted. For Apple Mac: 1)Close down the Dogecoin wallet client. 2)Go to your data folder: ~/Libarary/Application Support/Dogecoin 3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file! 4)Download this update file and place it into the Dogecoin folder where the other file was deleted. Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Edit: Some posts were removed from this thread. To limit confusion. Check this post for details about mining pools that were/are using the wrong fork. Did you send coins only to find out you're on the wrong chain? See this post to get them back An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards. Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
There is a huge surge in devices attached to the internet, known as the Internet of Things, and it is estimated that over 80 Billion devices will be connected to the internet by 2025, from industrial machines to devices in our home. The constant hacking and cyber attacks have increased not only the demand but the necessity of secure solutions. Our privacy and digital footprint are at risk. [b]Some examples where encryption plays a role: [b]Secure messaging - To make messages truly secure we need a process whereby a cryptography can be applied to encrypt transaction. [b]Secure calling - Secure calling is a process whereby the caller and the recipient of the call are identified and linked via a blockchain enabled cryptocurrency transfer, again creating public and private encryption keys making the call truly private. [b]Secure media storage - To safely and securely store media a process is required where 1.) Access to the media is encrypted via public and private keys of the person wanting to store the media. 2.) The media itself needs to be encrypted with a set of encryption keys and 3.) Media storage costs need to be paid via cryptocurrency [b]Secure browsing - To browse the internet securely we need to create a process of verification whereby nodes on the blockchain can verify websites as “safe”. Furthermore, the entire process needs to be encrypted as well. [b]Verification - This is one of the most important uses of a blockchain, we can verify websites as in the example above but also various other things such as identity, title and ownership, date stamps and source of products as with the verification of the source of agricultural or other products. These are just a few examples. All of this data needs to be encrypted as well. [b]“Smart home” security - Wi-Fi is often used for remote monitoring and control. Home devices, when remotely monitored and controlled via the Internet, are an important constituent of the Internet of Things - all needing encryption, otherwise, hackers paradise. [b]EOT in the future - The examples we mentioned above are only “scratching the surface” of where these technologies are applicable and who knows what will be invented in future. Google, Apple and Uber are all testing cars that drive themselves. A major issue with this technology is again the security aspect and the need to protect against hacking and who want’s to get into a spaceship to Mars that might be hacked or hijacked by ransomware? So the future for the [b]“Encryption of Things” – EOT, looks very interesting indeed and the role of crypto currencies in this will be major. Read the full white paper here - http://eottoken.com/index.php/whitepape The first device using EOT Coin is the BitVault®[/b] - the World's first crypto communicator and blockchain phone. The BitVault is a revolutionary new product that is built around security and privacy enabled through Blockchain technology. Biometric Security enabled through fingerprint and iris scan. Iris patterns are unique to you and are virtually impossible to replicate. This means that iris authentication is one of the safest ways to keep your BitVault locked and the contents private. Proven Biometric technology brings a whole new level of security to your crypto currency and blockchain transactions. Creating Military grade security for your device through third party independent Multilayer security. September 2017 – Swiss Bank in Your Pocket integrates EOT Wallet(Achived) October 2017 – BitVault®, the world’s first blockchain phone launches in London with integration of EOT for secure calling, secure messaging and secure browsing (First batch shipped) November 2017 – BitVault® Global App Store launches for developers to develop their own applications (Achived) November 2017 – Website EOT Payment Gateway for WordPress and WooCommerce (ACHIVED) December 2017 – Cryptodoc stores all your documents securely and encrypted on your PC December 2017 – Password Wallet stores all your passwords for applications and websites encrypted on your PC January 2018 – Smart Router for secure, encrypted internet which is direct, safe and easy January 2018 – EOT Camera, an Encryption of Things connected camera February 2018 – EOT Development Kit for hardware devices EOT payment gateway live on swissbankinyourpocket.com, Now you can buy SBIYP and BitVault using EOT coins More on the BitVault here:- https://swissbankinyourpocket.com/bitvault/]https://swissbankinyourpocket.com/bitvault/https://swissbankinyourpocket.com/bitvault-apps/]https://swissbankinyourpocket.com/bitvault-apps/https://bitcointalk.org/index.php?topic=2152534.0]https://bitcointalk.org/index.php?topic=2152534.0 JOIN US ON REDDIT : http://www.reddit.com/EncryptionOfThings]www.reddit.com/EncryptionOfThings JOIN US ON SLACK : [url=https://join.slack.com/t/eot-coin/shared_invite/enQtMjc3NzkxNzY5NzQ0LTFjMWI5NTJjOGEzYjU5ZDk0ZjRjZWE3MzBkNmI0MmQ2NTUzMTBkOGQ1YmEyNTllMmNiYzA3MGZjOGVmY2IyZGU The EOT Token is trading on the Waves Platform, TOKENS are 1:1 image of EOT coins, EOT coins can be converted to tokens and vice versa using gateway service in SBIYP hardware wallet. if you do not have that hardware wallet, you can contact members on slack who have purchased SBIYP to do that swap for you. TOKEN DETAILS Name : EOT Token (Verified) Identifier : GdnNbe6E3txF63gv3rxhpfxytTJtG7ZYyHAvWWrrEbK5 Total supply : 100,000,000 EOT token (EOT) markets added on the Tidex Exchange https://tidex.com/exchange/eot/btchttps://tidex.com/exchange/eot/waves EOT Coin details (currently minable) https://github.com/EmbeddedDownloads/EOTCoin windows wallet[/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v22.214.171.124/EOTCoin-win.exe windows Desktop wallet[/b] https://github.com/EmbeddedDownloads/EOT-Coin-Windows-Desktop-Wallet/releases/download/1.0/EOTCoinDesktopWallet1-0.zip MAC Wallet [/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v126.96.36.199/EOTCOIN-Qt-OSX-v1001.dmg WEB wallet [/b] http://eot.digital (Closing, please withdraw your coins) ANDROID wallet [/b] https://github.com/EmbeddedDownloads/EOTAndroidWallet/releases Block Explorer [/b] http://www.eot.digital:3622/ Block Explorer 2 [/b] http://www.eotcoin.info (created by [b]@Luanptit[/b]) [Block reward [/b] 100 Coins, [b] ALGORITHM [/b] SCRYPT, [b] BLOCK TIME [/b] 90 seconds MINING POOLS Official mining pool [/b] http://www.eot.digital:3001/ Getting Started [/b] minerd -a scrypt -o stratum+tcp://www.eot.digital:3256 -u WalletAddressWhereYouWantYourMiningCoins -p 1 unofficial Mining pools http://www.altminer.net http://antminepool.com http://coinminers.net/ http://www.vivocryptopool.com [red]Currently EOT is traded on WAVES DEX, Crypto-Bridge DEX and TIDEX. Big exchanges will be available soon, exchanges are in comkmunication. Opportunities are available with EOT - from Development, Mining, Trading as well as other business opportunities built around the EOT currency and the "Encryption of Things" [size=34px]Bitvault on Yahoo Finance https://finance.yahoo.com/news/bitvault-worlds-first-blockchain-phone-201600279.html [/size] [center][img width=770]https://i.imgur.com/UMIlRoC.png[/img][/center] [center][size=30px]Press release 4th October 2017 [/size] [size=30px]yahoo Finance https://finance.yahoo.com/news/bitvault-announces-london-launch-161000826.html?soc_src=community&soc_trk=tw [img]https://i.imgur.com/mBDZnN7.png[/img] Some Helpful Information [quote author=Story777 link=topic=2091616.msg21890405#msg21890405 date=1505551168] You have been keeping a great secret. I've been doing a bit of research with the technology behind this coin. It looks like ALOT of research has gone into this tech, since about 2004 and shortly after a patent for this P2P system was quickly issued. Bitvault (https://swissbankinyourpocket.com/product/bitvault/) who are using the worlds first blockchain phone as a secure communication device and ultimately taking [font=Verdana][b]encryption[/b][/font] to the Internet Of Things (IoT) keeping our personal and business data secure. All this is done using [b]EOT coin [/b](Encryption of Things). In todays world insecure devices are rampant. Here are a couple of links about the CIA being able to use insecure devices to 'cause accidents' http://www.sandiegouniontribune.com/news/cyber-life/sd-me-wikileaks-cia-20170307-story.html and https://www.washingtonpost.com/news/innovations/wp/2017/03/08/what-we-know-about-car-hacking-the-cia-and-those-wikileaks-claims/ It's scary to think a legal entity could posses such power over life. Just the mere fact alone the governing authority can request phone records (e.g. txt msgs, voice msgs or eavesdropping) proves most if not all telecommunication companies do not encrypt, otherwise whats the point on requesting the information!? (legal or not). Commercially sensitive information needs to be protected and most importantly in my opinion our [font=Verdana][b]rights[/b][/font] and the privacy of all citizens of the human race need to be protected. From my understanding BitVault is a platform for reference data. This would be data that is stored for compliance reasons such as e-mails, invoicing systems and check imaging (e.g. high quality imaging for x-rays, MRI scans etc) and a prototype was developed in 2004. This would means massive amount of data storage is required with fail-safe systems so a authorised user could access this information very very quickly. Three goals were needed to be achieved: Low cost, high reliability/availability and simplicity. This is the birth of Bitvault via EOT. Bitvault ultimately stores immutable objects with each new version being updated and identified with a 160-bit key. System stability is very important and must be immune to failure sequences. Parallel repair via indexing is one of the many strengths Bitvault has been able to demonstrate. BitVault is a back-end system that uses [u][b]Applications[/b][/u] to catalog object ID's. Using a catalog utility and indexing within an application prevented scalability bottlenecking under heavy loads. Fast forward 3 years to 2007 a very important decision was to [u][b]decentralise[/b][/u] BitVaults system. This in my opinion is one of the fundamental principles of cryptocurrency - [u][b]No one entity or person has any control of the data stored and only the authorised user can access this info[/b][/u]. Ultimate Security and thus personal safety (see above articles CIA hacks). BitVault using applications have been able to use provable communication and data storage with ease of retrieval with vital security measures. BitVault is not alone in researching solutions for security for the IoT, such as Venti and the like are making progress, however, BitVault is 'head and shoulders' above the few competitors and are already offering practical working solutions on the market with huge scalability that is cost effective. Well Done BitVault, well done EOT your secret is out and let the world embrace. author=Story777 link=topic=2091616.msg21462424#msg21462424 date=1504428317] I have had a response in Slack and it has satisfied my questions. Thank-you. For everyone information here it is: The currency was created with 200 Million EOT total supply on 7 July 2017 [ we showed it to the community a London Fintech week with the demonstration of the BitVault - fintechweek.com ] 100 Million was pre-mined and another 100 Million are currently being mined, 1 block every 90 seconds @ 100 coins per block. So the pre-mined coins were listed on waves as a token so that it can create a market for the coins while we are working to get listed on other exchanges. The 100 Million coins listed were distributed in several ways. Firstly, this was not an ICO because our business is already funded via private capital. We wanted to get the currency distributed a widely as possible. So most of the initial coins were given away to a number of interested parties. We distributed this to our whole development team, business partners, employees as well as to the waves and other communities. So we did not sell all these coins for the current price, most of it was given away for free to people that have an interest in our products and business. The price now is formed by whoever owns these coins. The tokens on the exchange is really a representation of the currency and as such has value because it can be interchanged, just like Bitcoin and Ethereum are on the waves exchange. This whole process is explained on page 4 of the waves whitepaper, I think they call it an asset-to-asset exchange which makes it possible to list any asset that exist on waves. Unfortunately waves only has gateways currently for Bitcoin, Ethereum, Waves, Euro and USD, so we have to develop our own gateway, which will be available on Nov 1. So to clarify 100,000,000 tokens costing $190M were not sold. It is a combination of airdrops, private sales and sales on the exchange. Some EOT coins are needed because: "A lot of EOT will be distributed through our devices. For example our encrypted routers are pre-loaded with EOT, so we need that stock and it will be distributed that way". And with the response to tokens on the Waves Exchange "This is how Bitcoin works on waves: - They created 21 Million BTC Tokens.. When you deposit Bitcoin into waves account, you receive an equal amount of tokens which you can either trade or even sent via the waves blockchain to another user.. Once you withdraw your tokens are exchanged for BTC and you receive it back into your BTC wallet.. Exactly the same for USD or EUR - You don't send Euro's to another client on waves if you transfer - you send a token that represents EUR -- This works exactly the w0083". These are the answers I was looking for and make a lot of sense now. This is indeed an exciting project. :) It's time to trade.... Now I have one question left.... Is there anyone using NiceHash to mine this coin?? I keep being disconnected because of the difficulty being too low. Can any one help? [quote author=Shews link=topic=2091616.msg22876983#msg22876983 date=1507755312] EOT (coin) is now tradable on the CryptoBridge Decentralised Exchange, you can sign up below. Please note this is for the EOT COIN ONLY, do not send tokens to this dex. This is a secure means to trade with the backend being on a blockchain. It is still in beta stage but has been working flawlessly so far. If you'd like more info I will post their website link is below. https://wallet.crypto-bridge.org/?r=388691 You can sign up with a local wallet mode, meaning you are the only one with access to your keys, this is most secure. There is also the option to sign up with and account if you require access to you funds on the go. More info: https://crypto-bridge.org/
This is my handout for paranoid people who want a way to store bitcoin safely. It requires a little work, but this is the method I use because it should be resistant to risks associated with:
Bad random number generators
Malicious or flawed software
If you want a method that is less secure but easier, skip to the bottom of this post. The Secure Method
Download bitaddress.org. (Try going to the website and pressing "ctrl+s")
Put the bitaddress.org file on a computer with an operating system that has not interacted with the internet much or at all. The computer should not be hooked up to the internet when you do this. You could put the bitaddress file on a USB stick, and then turn off your computer, unplug the internet, and boot it up using a boot-from-CD copy of linux (Ubuntu or Mint for example). This prevents any mal-ware you may have accumulated from running and capturing your keystrokes. I use an old android smart phone that I have done a factory reset on. It has no sim-card and does not have the password to my home wifi. Also the phone wifi is turned off. If you are using a fresh operating system, and do not have a connection to the internet, then your private key will probably not escape the computer.
Roll a die 62 times and write down the sequence of numbers. This gives you 2160 possible outcomes, which is the maximum that Bitcoin supports.
Run bitaddress.org from your offline computer. Input the sequence of numbers from the die rolls into the "Brain Wallet" tab. By providing your own source of randomness, you do not have to worry that the random number generator used by your computer is too weak. I'm looking at you, NSA ಠ_ಠ
Brain Wallet tab creates a private key and address.
Write down the address and private key by hand or print them on a dumb printer. (Dumb printer means not the one at your office with the hard drive. Maybe not the 4 in 1 printer that scans and faxes and makes waffles.) If you hand copy them you may want to hand copy more than one format. (WIF and HEX). If you are crazy and are storing your life savings in Bitcoin, and you hand copy the private key, do a double-check by typing the private key back into the tool on the "Wallet Details" tab and confirm that it recreates the same public address.
Load your paper wallet by sending your bitcoin to the public address. You can do this as many times as you like.
You can view the current balance of your paper wallet by typing the public address into the search box at blockchain.info
If you are using an old cell phone or tablet do a factory reset when you are finished so that the memory of the private keys is destroyed. If you are using a computer with a boot-from-CD copy of linux, I think you can just power down the computer and the private keys will be gone. (Maybe someone can confirm for me that the private keys would not be able to be cached by bitaddress?)
To spend your paper wallet, you will need to either create an offline transaction, or import the private key into a hot wallet. Creating an offline transaction is dangerous if you don't know what you are doing. Importing to a client side wallet like Bitcoin-Qt, Electrum, MultiBit or Armory is a good idea. You can also import to an online wallet such as Blockchain.info or Coinbase.
Trusting bitaddress.org The only thing you need bitaddress.org to do is to honestly convert the brainwallet passphrase into the corresponding private key and address. You can verify that it is doing this honestly by running several test passphrases through the copy of bitaddress that you plan on using, and several other brainwallet generators. For example, you could use the online version of bitaddress, and brainwallet and safepaperwallet and bitcoinpaperwallet. If you are fancy with the linux command line, you can also try "echo -n my_die_rolls | sha256sum". The linux operating system should reply with the same private key that bitaddress makes. This protects you from a malicious paper wallet generator. Trusting your copy of bitaddress.org Bitaddress publishes the sha1 hash of the bitaddress.org website at this location: https://www.bitaddress.org/pgpsignedmsg.txt The message is signed by the creator, pointbiz. I found his PGP fingerprint here: https://github.com/pointbiz/bitaddress.org/issues/18 "527B 5C82 B1F6 B2DB 72A0 ECBF 8749 7B91 6397 4F5A" With this fingerprint, you can authenticate the signed message, which gives you the hash of the current bitaddress.org file. Then you can hash your copy of the file and authenticate the file. I do not have a way to authenticate the fingerprint itself, sorry. According to the website I linked to, git has cryptographic traceability that would enable a person to do some research and authenticate the fingerprint. If you want to go that far, knock yourself out. I think that the techniques described in this document do not really rely on bitaddress being un-corrupt. Anyway, how do we know pointbiz is a good guy? ;-) There are a lot of skilled eyes watching bitaddress.org and the signed sha1 hash. To gain the most benefit from all of those eyes, it's probably worthwhile to check your copy by hashing it and comparing to the published hash. "But we aren't supposed to use brainwallets" You are not supposed to use brainwallets that have predictable passphrases. People think they are pretty clever about how they pick their passphrases, but a lot of bitcoins have been stolen because people tend to come up with similar ideas. If you let dice generate the passphrase, then it is totally random, and you just need to make sure to roll enough times. How to avoid spending your life rolling dice When I first started doing this, I rolled a die 62 times for each private key. This is not necessary. You can simply roll the die 62 times and keep the sequence of 62 numbers as a "seed". The first paper address you create would use "my die rolls-1" as the passphrase, the second would be "my die rolls-2" and so on. This is safe because SHA256 prevents any computable relationship between the resulting private key family. Of course this has a certain bad security scenario -- if anyone obtains the seed they can reconstruct all of your paper wallets. So this is not for everyone! On the other hand, it also means that if you happen to lose one of your paper wallets, you could reconstruct it so long as you still had the seed. One way to reduce this risk is to add an easy to remember password like this: "my die rolls-password-1". If you prefer, you can use a technique called diceware to convert your die rolls to words that still contain the same quantity of entropy, but which could be easier to work with. I don't use diceware because it's another piece of software that I have to trust, and I'm just copy/pasting my high entropy seed, so I don't care about how ugly it is. Why not input the dice as a Base 6 private key on the Wallet Details tab? Two reasons. First of all, this option requires that you roll the die 99 times, but you do not get meaningful additional protection by rolling more than 62 times. Why roll more times if you don't have to? Second, I use the "high entropy seed" method to generate multiple private keys from the same die rolls. Using the Base 6 option would require rolling 99 times for every private key. I'm a big nerd with exotic dice. How many times to roll? Put this formula in Excel to get the number of times to roll: "=160*LOG(2,f)" where f = number of faces on the die. For example, you would roll a d16 40 times. By the way, somewhat unbelievably casino dice are more fair than ordinary dice The "Change address" problem: You should understand change addresses because some people have accidentally lost money by not understanding it. Imagine your paper wallet is a 10 dollar bill. You use it to buy a candy bar. To do this you give the cashier the entire 10 dollar bill. They keep 1 dollar and give you 9 dollars back as change. With Bitcoin, you have to explicitly say that you want 9 dollars back, and you have to provide an address where it should go to. If you just hand over the 10 dollar bill, and don't say you want 9 dollars back, then the miner who processes the transaction gives 1 dollar to the store and keeps the remainder themselves. Wallet software like Bitcoin-Qt handles this automatically for you. They automatically make "change addresses" and they automatically construct transactions that make the change go to the change address. There are three ways I know of that the change problem can bite you:
You generate a raw transaction by hand, and screw up. If you are generating a transaction "by hand" with a raw transaction editor, you need to be extra careful that your outputs add up to the same number as your inputs. Otherwise, the very lucky miner who puts your transaction in a block will keep the difference.
You import a paper wallet into a wallet software and spend part of it, and then think that the change is in the paper wallet. The change is not in the paper wallet. It is in a change address that the wallet software generated. That means that if you lose your wallet.dat file you will lose all the change. The paper wallet is empty.
You import a paper wallet into a wallet software and spend part of it, and then think that the change is in the change address that the wallet software generated. If the transaction did not need to consume all of the "outputs" used to fund the paper wallet, then there could be some unspent outputs still located at the address of the paper wallet. If you destroyed the paper wallet, and destroyed the copy of the private key imported to the wallet software, then you could not access this money. (E.g. if you restored the software wallet from its seed, thinking all of the money was moved to the wallet-generated change addresses.)
For more on this, see here The hot paper wallet problem Your bitcoin in your paper wallet are secure, so long as the piece of paper is secure, until you go to spend it. When you spend it, you put the private key onto a computer that is connected to the internet. At this point you must regard your paper wallet address as hot because the computer you used may have been compromised. It now provides much less protection against theft of your coins. If you need the level of protection that a cold paper wallet provides, you need to create a new one and send your coins to it. Destroying your paper wallet address Do not destroy the only copy of a private key without verifying that there is no money at that address. Your client may have sent change to your paper wallet address without you realizing it. Your client may have not consumed all of the unspent outputs available at the paper wallet address. You can go to blockchain.info and type the public address into the search window to see the current balance. I don't bother destroying my used/empty paper wallet addresses. I just file them away. Encrypting your private key BIP 0038 describes a standardized way to encrypt your paper wallet private key. A normal paper wallet is vulnerable because if anyone sees the private key they can take the coins. The BIP38 protocol is even resistant to brute force attacks because it uses a memory intensive encryption algorithm called scrypt. If you want to encrypt your wallets using BIP38, I recommend that you use bitcoinpaperwallet because they will let you type in your own private key and will encrypt it for you. As with bitaddress, for high security you should only use a local copy of this website on a computer that will never get connected to the internet. Splitting your private key Another option for protecting the private key is to convert it into multiple fragments that must be brought together. This method allows you to store pieces of your key with separate people in separate locations. It can be set up so that you can reconstitute the private key when you have any 2 out of the 3 fragments. This technique is called Shamir's Secret Sharing. I have not tried this technique, but you may find it valuable. You could try using this website http://passguardian.com/ which will help you split up a key. As before, you should do this on an offline computer. Keep in mind if you use this service that you are trusting it to work properly. It would be good to find other independently created tools that could be used to validate the operation of passguardian. Personally, I would be nervous destroying the only copy of a private key and relying entirely on the fragments generated by the website. Looks like Bitaddress has an implementation of Shamir's Secret Sharing now under the "Split Wallet" tab. However it would appear that you cannot provide your own key for this, so you would have to trust bitaddress. Durable Media Pay attention to the media you use to record your paper wallet. Some kinds of ink fade, some kinds of paper disintegrate. Moisture and heat are your enemies. In addition to keeping copies of my paper wallet addresses I did the following:
Order a set of numeric metal stamps. ($10)
Buy a square galvanized steel outlet cover from the hardware store ($1)
Buy a sledgehammer from the hardware store
Write the die rolls on the steel plate using a sharpie
Use the hammer to stamp the metal. Do all the 1's, then all the 2's etc. Please use eye protection, as metal stamp may emit sparks or fly unexpectedly across the garage. :-)
Use nail polish remover to erase the sharpie
Electrum If you trust electrum you might try running it on an offline computer, and having it generate a series of private keys from a seed. I don't have experience with this software, but it sounds like there are some slick possibilities there that could save you time if you are working with a lot of addresses. Message to the downvoters I would appreciate it if you would comment, so that I can learn from your opinion. Thanks! The Easy Method This method is probably suitable for small quantities of bitcoin. I would not trust it for life-altering sums of money.
Download the bitaddress.org website to your hard drive.
Close your browser
Disconnect from the internet
Open the bitaddress.org website from your hard drive.
EDIT: Solved! I used btcrecover with help from schnief1898! Hi, I bought 0.1BTC back in 2013 for around £50. I used Bitcoin Qt on Windows 7 (or Bitcoin Core as it is called now) as a wallet to store my coins on my old PC. I don't ever remember encrypting my wallet with a password. I then pretty much forgot about it for a few years. After the price started to skyrocket I decided to transfer my wallet to a new PC as my old one was starting to show it's age and I was worried that the hard drive might die. I copied the wallet.dat onto my new PC and downloaded the latest version of Bitcoin Qt (Core) and let it re-sync the entire blockchain which took a few days. The client on my new PC is saying that the wallet is secured and encrypted and prompts for a password when I try to view the private key which I can't remember.
I don't ever remember setting a password
I specifically remember thinking "I'm not going to bother setting a password because I will probably just forget it. My Windows password is very secure which should be enough security."
I've been using the same 3-4 passwords for everything for the past 18 years of using computers and none of them are correct. I never use any other password for anything, ever.
So far I've tried around 300-400 different variations of these passwords (with different numbers, letters, upper and lower case etc) but none work.
I've searched all my old notebooks, documents, papers for anything I might have written down in case I wrote it down somewhere.
I've searched my old phones for pictures, notes, reminders, anything.
I'm not exaggerating when I say I am 95% certain I didn't set a password for my wallet. However, there is a chance I could be completely wrong and I did and I just forgot it as it was back in 2013. I can't remember how the setting of passwords even works in Bitcoin Core. Does it prompt you to encrypt as soon as you make a new wallet? Do you have to specifically set one after receiving a payment? Is there a default password? Did moving my wallet.dat from an old version of the client to the new one encrypt it somehow? Is there anything I can do or am I completely screwed? Thanks for any help in advance.
New to Bitcoin, few questions about backing up my wallet
Hey guys I'm really new to bitcoin. I did a lot of research and I mostly understand, however I just want to make extra sure I understand how to backup my wallet(s) because I know if they're lost that they're not recoverable. I have a wallet made in bitcoin-qt in windows. In that program, I was able to set a password (encrypt) it. Now, if I want to backup my wallet, do I just have to make a copy of the wallet.dat file? Will I be able to open that wallet.dat with other programs? If I open it on another computer, will I be prompted for the password? Do I need to keep up to date backups or is the wallet.dat file just a way to securely access the funds that are in my wallet which is all stored on the BTC network? Also, I have the Android bitcoin app which means I have a second wallet. I know I could transfer between the two but could I "load" my desktop (main) wallet on my phone? What is the role of the wallet keys? The Android app allows me to backup the wallet "keys" as a txt file to the sdcard. Is this equivalent to the wallet.dat file from the desktop client? Sorry I know there are lots of questions but I want to learn it properly. Thank you!
A proposal of a wallet to the clever developer shibes out there which concerns all and future shibes (Would be extremely beneficial with the Talladega race coming closer and closer)
I recently watched this talk by Andreas Antonopoulos (which I recommend every shibe to watch). In this video he explained how private keys, public keys, adresses, cryptography and wallets work. In the video, I realized how far wallets have come already, how little the QT-wallet actually matters for us common folks, and how important it is to have user friendly wallets with good features. I got especially intrigued when Alexander explained type 2 deterministic wallets based off of trees. And my question is: "Can you deveolper shibes develop a type 2 deterministic wallet (like electrum) with BIP39?" For all who don't know what I'm talking about, I will try my best to explain how type 2 deterministic wallets work by basically paraphrasing Andreas from the video. Please correct me if anything is wrong. Let me begin by saying that our, and every virtual currency QT client is more focused on implementing the stability into the core coin protocol rather than implementing user-based fancy wallet features. Recently the bitcoin QT client has been removed from the bitcoin.org site as the recommended wallet for new users. This is because it isn't a good interface for the common man, or really anyone. It has also been discussed by bitcoin developers to strip all the wallet functionality out of the QT-client just for this reason. Explaining type 2 deterministic wallets: When creating a private adress, a random number is drawn, in this process you will also generate a 128-bits random seed (for example 521566b6ebfe0ab8ff7b8110b92c57d4). A seed is generally speaking a starting point for the random number generation. This seed will therefore be the generator of all future adresses in your wallet. From this seed, you can use mathematical functions to generate keys in such a way that you can't predict those keys without having the seed. Just to clarify: If you have one private key, you can't figure out the other, and if you have the other, you can't figure out the first. This means that as long as your seed and mathematical function is not compromised, your keys won't be compromised. This is because you generate (or regenerate) all your private keys from that seed. These mathematical functions can for example be the following: "You generate the first key, then you jump over 5 keys, then generate another key etc.". What this leaves us with is that you need two types of information to "infiltrate a wallet": The seed and the gap. This means that the seed and gap still needs to be encrypted, the good thing is that there's no need for a backup if you lose your wallet because you know your seed, and the gap. Now you might be wondering: "How am I going to remember my seed? Won't this be hard? Won't it be a pain to remember?" Well there is also a new really interesting implemented technology called BIP 39. What this technology does is that it creates 12 random words (called a 12-word mnemonic code). These words are deterministically derived, in this way you can convert those 12 words back to the seed. Let me give you of an example of why this is beneficial: The first thing is that 12 random words are much easier to remember and hear than a combination of 12 random letters and numbers. This means that if you lose your wallet and you're away from where your seed is written down/stored etc., you can for example call someone you trust to help you to restore your wallet. This can be done by the person telling you the 12 words over the phone, which will again give you your seed. No need to wonder if the person said "b" or "d". The mnemonic code for the seed I wrote down (521566b6ebfe0ab8ff7b8110b92c57d4) is "pain apologize tired bar change think off outside clear fear hot stir". You can see how this could be handy. This is technology is at the moment restricted to the English language. More importantly, it is restricted to a specific dictionary. The reason for this is because based on those specifications, every single wallet in the world with these features can take 12 words with the gap and deterministically recreate the same seed. From this point it can then recreate the same keys. There's of course a checksum built in, so one of the words is a checksum for the other words. This entails that not every combination you throw at it will be correct. This means that if you remember those 12 words in that specific order, you will never have to take a backup of your wallet ever again. How great is that? So a TL:DR: I want our smart and clever developer shibes to create a type 2 deterministic wallet with BIP39 (like electrum or armory) with a great design. This would make it much easier for both newcomers and old shibes to use their wallets. The problem with backing up you wallet would also be a thing in the past. And if you know your seed or mnemonic code, you can import your wallet with extreme ease to any other device with a wallet just by typing in some words instead of moving a backup file to your device. If this wallet is being based on a litewallet, there will also be no need for synchronisation. Disclaimer: Like I said, I'm not a pro at this, please correct me if anything is wrong here. And please shibes discuss, is this something the community is also interested in? I would be so happy if we got a wallet like this.
I made this for my friends and family to use. Hope this heps someone. Much help! bitcoins first: Get a wallet - just like physical money, you need a wallet to hold the money. use multibit - for a wallet - if you want options here a few http://bitcoin.org/en/choose-your-wallet go here and download this https://multibit.org/ how to backup your wallet https://multibit.org/help_backupWalletUsingPrivateKeys.html i recommend backing it up to at least 3 separate locations. example: harddrive, usb drive, encrypted dropbox folder. go here to buy bitcoin also known as an exchange https://coinbase.com/?r=52dee75a8a2eed3e480000e5&utm_campaign=user-referral&src=referral-link don't create wallet, click sign up button on top right. add bank information, and credit card info, and phone info - phone allows 2 factor authentication so your identity becomes much more difficult to fake and steal your money and information. I asked them to send me a SMS message instead of using app. this is the most reputable place to do this at. Never never use an online wallet!!! buy some bitcoin on coinbase.com, and send yourself some bitcoin using your multibit wallet address(under the Request tab it shows your address there) Now Dogecoin First get a wallet, - use the qt wallet. You can get it here for either Mac or Windows. http://dogecoin.com/ for linux use this guide - http://www.reddit.com/dogecoin/comments/1tvmnd/dogecoin_on_linux_the_complete_beginners_guide/ For a place to buy dogecoin. Use cryptsy, here is the link. https://www.cryptsy.com/users/register?refid=138894 click register new account. enter your information. go to your settings, and enable 2 factor authentication, use your cell phone number, and put in the number that they send to your phone. This makes it much more secure. you will send your bitcoins here and then buy dogecoin, then send the dogecoin to your wallet on your own computer. Backup the wallet after every purchase. Send your Dogecoin to your own wallet. backup your wallet, at least 3 times. Use USB thumb drives. FYI, This might take away, the withdraw servers are slow as of right now. Took 3 days for me. If you have any questions ask. Also you can buy Dogecoin or Bitcoin on ebay, do that at your own risk.
If you missed Part 1 – check here! The story continues! (tl;dr at the bottom) Where were we… ah, my alarm. No sooner did I jump into bed than the alarm went off! Buzzing away under my pillow… the day was fast turning into one of the worst days of recent memory. I grabbed my phone, switched the alarm off and just lay there mumbling. ‘A1 something something something £9 something something’ ‘No, that’s not right’ ‘A1 #?’ ‘What was it – I know this, come on … visualise!’ I’ve never done that before… I was speaking to myself out loud, that was the gravity of the situation and my feelings at the time. I hate you Google Keep!!... My wife on the other hand had already dozed off (btw, I got plenty of confused.com looks during the panic station ‘moment’, she was half asleep though so it didn’t really faze her). Eventually I began to calm down. I started thinking sensibly about the situation. The first thing I was doing wrong was not writing down any of my guesses. I probably recited well over 30 phrases as I was lying there. I got up, opened my laptop and started writing them down. At the same time I noticed my mining rig was still running... RDP -> Hit Q on CGMiner – why the hell was I mining coins to address that I no longer had access to!!!! Once the fans slowed I opened the QT client and went to the send tab. Bear in mind that from the moment I lost my password to this moment I hadn’t even attempted a single passphrase even though it would have been a little fresher in my mind! Send tab -> check the addresses I have saved -> ah DogeTipBot -> that will do. 100 coins, hit send… ‘Please Enter Passphrase’. Ok here goes: First attempt ‘That’s the one for sure...’ Nope -Tries again- No -and again- Error -A further 15 times- Access Denied. Sigh F*** you Google Keep. (Yeah your gonna see a lot of this – I despise that app now). I must have tried and failed countless times before I decided to investigate other options. What do you do when you’re stuck? Google It. And that’s what I did. There were a fair few posts regarding lost pastphrases, none of them really helpful. Most replies were along the lines of ‘sorry for you loss’, ‘how much did you lose?’ and ‘nothing you can do…’. Well, screw that, I wasn’t giving up – I like a good challenge! Enter Recoinvery.com. A nice little tool albeit very slow. I came across it whilst searching for passphrase recovery options available to me specifically for coin wallets. You basically point the tool to your wallet.dat file, set a bunch of options and hit the ok button. It runs a few instances in the background attempting to recover your lost passphrase. Let me stop there for a sec and explain something quickly about passwords and recovery of one (feel free to correct me if wrong!):
If you’re trying to recover a password less than 10 characters that you can’t remember at all then there’s a decent chance for you to recover it – it may take a while though, could be months.
If you know bits and pieces of it then you can drastically reduce the time it takes for recovery using things like dictionaries or masks
If your password is 10 characters or over and you don’t know parts of it then you’re pretty much screwed
There’s more to it than just that but those are some of the key points most recovery websites will throw at you. Another vital point I learned was the difference between combinations and permutations – it goes a little like this: If I have a password ‘Abcd123’ then there’s no reason for me to check combinations – I.e. aaaaaaa, aaaaaab, aaaaaac, etc. We’re not interested in combinations here, were interested in permutations. With permutations you would provide a character set and a length you are after – this would then output unique permutations of the character set vs. the length – using the password example above, if I provided Aabcde12345 as the set and 7 as the length I would see things like Aabcde1, Aabcde2, Aabcde3, etc. (Remember ‘A’ and ‘a’ are not the same) Why is this key for me? I was 100% sure that I hadn’t used the same character twice in my passphrase. So, back to Recoinvery. As I said, great little tool but I quickly realised it was far too slow for what I was trying to achieve. There had to be other services out there. There were tools like Hashcat and John The Ripper, both great for expert hackers / crackers but for me, a novice when it comes to this type of activity, I found those tools a little out of my league. At this point I came across www.walletrecoveryservices.com – a service provided by a guy called Dave Bitcoin. You’re thinking what I’m thinking right? Scam Scam Scam. Best course of action? Google It. Dave was apparently the real deal. His method was a custom made bit of code + access to numerous workstations / servers and the use of only a small section of your encrypted wallet. This is key – the portion he was asking for was essentially useless, he wouldn’t have been able to steal my coins had he recovered it. I read up on it and him – everything seemed above board. I proceeded to contact him. In the background, I had Recoinvery chugging away at measly 100 passwords a second – it had been running for hours I think (btw this is still Friday the 28th March) and nothing. My guess would be somewhere in the region of 500,000 combinations had been checked of a 12 character password (+ it seemed a little … buggy). Wait you say? I’ve not said a word about what parameters I’ve used or what the hell it was that I was trying to look for! Fear not, details below:
I was fairly sure my password was not less than 11 characters and certainly no more than 13
I knew it had unique characters, symbols and numbers
I knew the start and the end of the password – 99% confidence
I was about 60% sure about the characters contained within the password
It was the bit in the middle that had be stumped. The good news was I was able to provide Recoinvery with a mask – set a prefix, suffix and let it chug away at the middle. The bad news, as highlighted earlier, I was struggling with permutations and speed. It was frustrating to say the least. Approaching the half day mark with nothing to report I decided to check back on Reddit to see if any more comments had been made that may guide me (I made the most in the morning before 9). A couple of useful comments however nothing to go off. I guess it was time for a little patience… woosaaaa. I should probably get some breakfast… (12.00pm) Am I doomed? It's looking increasingly likely I know .... Hitting the Wall [Part 3] tl;dr F****** Google Keep Calm down – think sensibly Research password recovery, find Recoinvery Give Recoinvery some character sets to work with Sit and wait.
[Guide] How to transfer your wallet from your computer to android.
I got tired of waiting and waiting for the whole blockchain to sync so I decided to move my dogecoins to my phone since the app does not need to download the whole chain. (Luckily there is a bounty for a electrum equivalent that will hopefully arrive soon.) It is much much easier if you just transfer some funds to a new address on your android phone, but this tutorial is for those people like me who can't even get the dogecoin app to sync. Surprisingly the whole process was very simple. Don't be put off by all the text or all the talk about security. I just want things to be accessible to beginners and to practice good habits. Root is not required. Note: I am assuming you are using the official dogecoin-qt app and the Dogecoin Wallet app by langerhans. Disclaimer: This will involve having your private key stored in plaintext. Proceed with caution and treat that file like you would a password. Do not share your private key with anyone.
Getting your private keys
A wallet comprises of public keys and private keys. Public keys are the addresses that you share, you can only use them for viewing. Private keys let you actually make transfers and are what makes you the owner of the wallet. Today we will be transferring those private keys to your phone. They will still be present on your computer unless you delete them, so keep that in mind security-wise. You will have to replace everything in '<>' with your own values.
Open the desktop app
Open the wallet console by going to: Help -> Debug Window -> Console
If your wallet is locked with a password, you'll need to unlock it by typing: "walletpassphrase 120".
Get the private key for an address by typing: "dumpprivkey "
Save the private key to a file.
Repeat this for each address that you want to transfer over.
Please think about how much dogecoins you want to transfer over. Brarsh:
Do you need that much? What if you lose your device? Just like only keeping a small amount of cash in your wallet and most safe in the bank, only carry what you could conceivably use for that time without access to your main wallet.
Creating a backup file
Next we need to create a backup file so that we can import our addresses into the android app. The android app uses the same format for its backup files as MultiBit (A popular bitcoin app). A typical file looks like the following:
# KEEP YOUR PRIVATE KEYS SAFE! Anyone who can read this can spend your Bitcoins. Kwmxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-06-22T18:36:35Z L1Sxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-04T22:47:32Z Kxwxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2013-05-08T00:58:28Z
What we want to do is put our private keys in the following format: key date-of-address-creation, where the date is in the format YYYY-MM-DDTHH:MM:SSZ. Note the T and the Z. The android app needs the date so it knows how far back into the blockchain it needs to sync. If you can't remember when you created the address, visit http://dogechain.info/address/YOURADDRESS and get the date of the earliest transaction. It says that the dates are approximate, so I'd just put 00:00:00 for the time. You should now have a valid unencrypted backup of your wallet.
Importing the backup
Transfer the backup to your android phone, placing it in your Download folder. It has to be put in the Download folder or else the dogecoin app won't find the backup. Make sure it has a name you'll remember later.
Open the dogecoin app and click on: Back Up Keys -> Restore private keys. Click on the name of the backup and from the list that shows up, look for your backup, which should be unencrypted. Click Restore.
Delete the backup in your Downloads folder. Remember, your private key is stored in plaintext in there, so it is important that you delete it. Delete the backup on your computer if it is there also.
Wait for the app to sync completely. Your addresses will be added to the addresses that were already in the app, and your transactions should show up. If they do not, make sure that the date you put was correct and early enough.
Go to Back up Keys > Back up private keys and create a backup. This time it will be encrypted with a password :). If you do not have a backup, you could lose all your coins if you lose your phone or the data on it.
To the moon!
I just got into dogecoin two days ago so correct me if any of this is wrong. Same thing with anything in the post :). Blockchain/Dogechain: The blockchain is a ledger (record) of all the dogecoin transactions that have ever taken place. As of writing it is larger than 1GB in size. The blockchain is needed to find out how many funds you have in your wallet. Wallet: A wallet is the digital equivalent of a real life wallet. It is where your money is tied to (It doesn't contain actual dogecoins, but someone else could explain that better than me). The wallet contains your addresses and your private keys, both which are needed to receive and send dogecoins respectively.
Hello fellow Shibe! We call each other shibes! With new subscribers every day I'm sure there a lot of new people who get confused by this. This is a guide for them. This is a simple guide explaining various parts of the Dogecoin experience! Let's begin with what we do here. We create and trade with Dogecoins. What is a Dogecoin? It's a cryptocurrency. How cryptocurrencies work is a really long read. Just know this. We use our computers to do really really hard math stuff and the system awards us with coins. What math stuff? The stuff that makes the whole system, which makes it safe and trustworthy. In essence, all our computers know every coin exists out there and how they were made. When a new coin appears, it comes with an instruction on how it was made. Our pc's check to see if it was made in a legal way. This way you cannot make coins out of thin air, even if someone somehow did it and told other computers "hey look, these are my coins!" are pc's would look at the coins' records and easily say "nope, they are fake, get out!" What is a wallet? A wallet is where your key is stored to access your coins. With dogetipbot (a bot used to tip other members here on Reddit as well as Twitch), you can store coins through the wallet. Alternatively, it would be a good idea to download the wallet applications recommended on dogecoin.com Keep in mind there are two types of wallets, offline and online. Offline one is the type you have on your harddrive. You store your wallet on your pc and the software called dogecoin-qt let's you do transfers using your wallet. Online ones are stored at the website you are associating with (ie: dogetipbot, or an exchange like Crtptsy). Online wallets can hacked so if you have any significant number of coins it would be a good idea to have them at the least stored on your own computer and being encrypted with a password you use for nothing else(just make sure you remember it and write it down somewhere!). If you ever lose your wallet files or your encryption key, you'll lose all your coins; just like the real world :) How can I get Dogecoins? Mining is essentially obsolete at this point unless you are mining with specialized ASIC machines. For any new Shibe we recommend getting tipped Doge by other Shibes to get started, or if you want to just jump in, there are some great sources for buying Dogecoin. Some of the most popular are "Weselldoges" and GoCelery. You can also start by buying bitcoin from Coinbase or Circle and then trading those for dogecoin on an exchange like Cryptsy. What's with all the community talk? It's us, shibes! This is my first cryptocurrency too but from what I read I learned that people are crazy with their coins on other subs about other coins. Remember how they make stock markets look on movies, with people yelling at their phones about some buy or sell order, it's much like that. It's nice here, people help each other, show their gratitude with nice words and sometimes tip each other. And that's the reason why dogecoin has some value today, it's the coin of nice people :) That's it for now! If you have any question just post them on the subreddit, you'll find our community is very helpful and usually fast to answer! Note: Guide last updated 10-26-14
Would it be possible to implement 2FA (e.g., Authy) on a local Bitcoin wallet?
When a person tries to spend money from a wallet, it should ask for the 2FA code which that person has to retrieve from a secondary device. The 2FA generation code thing should be encrypted with the wallet.dat, perhaps with an additional password (doubley encrypted?), so if someone obtains your wallet.dat and password, they still can't spend your funds. I've seen diagrams with multisig requiring a second computer or phone to allow a payment, but wouldn't this be simpler to implement and execute? Perhaps through modifying the bitcoin-qt source. This would make the wallet more secure without needing cold storage or a paper wallet, no? If I understand 2FA correctly, neither device would even have to be online to create the transaction, they would just need to have clocks set to the approximately same time.
If you do not have your backup phrase, then, unfortunately, you have lost your wallet and all funds in the wallet. For security, 12 word backup phrases are not stored on BitPay servers, so BitPay cannot recover funds for you. If you still have your backup phrase: Open the app and go to the gear icon at the bottom right. Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. QT wallet – Most of the crypto currency core wallets are developed using QT software framework. They are available for Windows, Linux and Mac. QT wallets are professional client and offers full function that’s available for a currency. Also they are heavy as it is known to download the complete blockchain to your local computer. I have two computers A and B both with Bitcoin qt client on. I have made wallets on both computers. After launching Bitcoin qt client for the first time on computer A I created two addresses using the 'new address' button. I then clicked 'Encrypt Wallet' and entered a passcode. Note I only did this process once, even though I created two addresses. @DavidKrmpotic: 1) From source code it seems the key pool is not renewed when changing passphrase, so old backup should be usable. But I'd recommend to back it up anyway just to be on the safe side. 2) Bruteforcing a bitcoin wallet is not limited by some external means (like CAPTCHAs etc), so good password for a web service might be not secure enough for a wallet.
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 ... Here is my wallet.dat file from Bitcoin-Qt client. Forgot the password so if you crack it 1BTC is yours. Price is 0.06 via satoshibox.com Forgot the password so if you crack it 1BTC is yours ... - Click settings top left of screen. - Select 'Encrypt Wallet' and follow instructions. To support me you can donate $XVG address: DQoFGdaRCMkwAqbTB7fUwN4GBrdN5Ao53c. See how easy it is to create an account with the Airbitz mobile app. Your Airbitz account allows you to create unlimited HD Bitcoin wallets. Only a login and... In this tutorial we are going to get our private keys from the bitcoin core wallet. This only works when you created the bitcoin address in the same wallet. ...