Bitcoin-Qt wallet. All about cryptocurrency - BitcoinWiki
Transferring coins from Bitcoin-Qt to Electrum - Bitcoin Wiki
Migrate from blockchain.info to bitcoin-qt - Bitcoin Stack ...
Litecoin-QT wallet help, please : litecoin
Groestlcoin 6th Anniversary Release
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
I am currently trying to set up blackoin on raspberry. Community members asked for a tutorial to compile it, so I will start with this here. Maybe in the future it would even be possible to turn it into a headless (=without screen and keyboard) image to put on an SD card and just boot up the wallet. I used the latest Blackcoin Lore by janko33 for this process, however it should be quite the same with the "original" core wallet by rat4/johndolittle. Blackcoin Lore is not deemed as stable as it is still in beta, so it's up to you what source tree you take. Please be also aware, that compiling on a small computer like raspi can take a while. Please also note that Lore is still in beta. The names in the archive are still "bitcoin". There is an update comming where the naming is correct and also maybe a few bugfixes. ** Tutorial: ** You first need to get raspbian. The lite image will work, it's a small version of the operating system without a graphical interface, so you will need ssh to operate it. The image is 294 MB but you will want to have a bigger card. 2GB is certainly too small, better get 16 or even 32GB - you also will need space for the blockchain! To install it I followed this guide https://hackernoon.com/raspberry-pi-headless-install-462ccabd75d0 Get the raspdian image file from: https://www.raspberrypi.org/downloads/raspbian/ Also get Etcher from https://etcher.io/ Etcher is a tool to write img files to an SD card/USB-stick. After writing, open the card in your explorer and add a file "ssh". The file sould be empty and just be called "ssh" (not ssh.txt or something). It will tell raspi to activate ssh on boot. Then boot up your raspi with the card and plug it into your network. Consult your router's LAN-page to find the device, it should register to your router as "raspberry" or so. Open up Putty and login to your raspi using pi as username and raspberry as password. After login you can configure your raspi, please read the guide linked above for more details. Note: One important thing that you should configure is your timezone! Use
Go to 4. Localisation Options and set the time to your timezone. If your time is way off, you would get troubles with staking, so make sure you always have the time set right! After you got everything set up, get the build environment ready:
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils #Installs alot and can take a while git clone -b Blackcoin-Lore https://github.com/janko33bd/bitcoin Blackcoin-Lore cd Blackcoin-Lore cd depends make -j 6 HOST=arm-linux-gnueabihf cd .. ./autogen.sh ./configure --prefix=`pwd`/depends/arm-linux-gnueabihf
# note: ` = is a "backtick" not an apostroph. It causes the outpupt of "pwd" being inserted there
make -j 6 # -j n tells the compiler to use more cores, speeds that up a little (n = 1.5*cores installed) sudo make install
This should compile so far. Update: Lore does not need Berkeley DB 4.8 to be installed, so just go with the DB provided by the repository works (libdb++-dev). (Thanks patcrypt) After compile you can run the wallet with
And after it synced you have bitcoin-cli to control the wallet. Issue: Synching blocks takes an awfully long time on raspi for some reason, even with Lore (that syncs blocks in a few hours instead of a whole day on a normal computer). If anyone knows how to speed up that process, please let us know! This thread is a WiP. Please post all issues and errors here, I will then edit the OP to make it into a real, working tutorial. On a note it was mentioned, that using an USB-stick here instead of a card would make sense since the cards are more prone to failure than USB-sticks. I will include setting it up on USB in a later version of this tutorial. Some tips and tricks Since compiling takes a longer time, it is recommented to run it in the console in a screen. Screen is a terminal tool that supports multiple windows in the same shell and, most important, detaches when your ssh connection breaks. Using screen you can simply reconnect and use screen -r to attach to your running shell again. To use screen, you need to install and then start it before you start the whole build process within a screen-shell.
sudo apt-get install screen screen #Start install/build process here #Type [ctrl-a] [d] to detach from the screen and put it in the background #After reconnect type screen -r to jump back into your running shell
If you want to see your blocks being processed while the wallet syncs to the network, use the following command on a second shell (new Putty instance or screen window which you can open in screen with [ctrl-a] [c] (hit [ctrl-a] [n] to cycle through the windows in screen)
watch -n 5 lore-cli getinfo #This will execute the command "bitcoin-cli getinfo" every 5 seconds and thus display live update of your wallet info
How to use that thing? Here are a few helpful CLI commands, call them with lore-cli
help - Returns available commands help - Returns detailed help to a getinfo - Returns a descriptive information of your wallet, including balance getwalletinfo - Returns short information about your wallet, including balance, unconfirmed balance, immature balance, number of tx ect getaccountaddress 'raspi' - Returns an address for your wallet. If the account does not need to exist, it will be created with new address sendtoaddress - Sends to sendtoaddress substractfeefromaccount - Sends minus tx fee to getnewaddress - Returns a new address for each time you call the command. is optional
Further plans for this tutorial/project
Install on USB with a small boot image on SD
Planned: Web GUI to control your wallet easily from your local network
Have fun! Donations: B4nn2Y3SFC6whNGNvcQ2MvV1aQbZp3cZVF
Bitcoin Core: Transaction Details. What does "Status: Open for 202692 more blocks" mean?
First transaction since mining in 2013 and sent all my bitcoin (0.14) to an exchange from the Bitcoin Core wallet but mistakenly set the fee as 1.003 sat / byte and transaction stuck since 28 nov. Have tried multiple accelerators but no joy. Was hoping it would be dropped by now but no luck, have not been broadcasting with the wallet. Tried deleting the mempool.dat to abandon but now I have to download 6 years of blockchain to confirm the transaction so the balance shows up in the wallet. Does the open status relate to dropping (abandoning) the transaction? https://blockchain.info/tx/e3d6f95abbe2af52d7907a4a034cb8ee8a1231404ce8e07e45c8b09c29e9ca76 Edit: Still no clue about the question in the title. After some research here is the solution to my problem for any other noobs with a stuck transaction made up of many small inputs. ELI5 on inputs is think of each input as a denomination of currency like coins and notes For my mining as was paid in the equivalent of loose change with many small inputs. Each input has a number of bytes so a transaction with many inputs is like paying for something worth $100 with loose change, bulky and slow. I need to create a transaction to another address to convert my change to a note but it will cost a fee to do so. In Bitcoin-qt i set the walletbroadcast=0 option and deleted mempool.dat. Downloaded the blockchain again to confirm each input and marked the stuck transaction as abandoned, otherwise I would have ran zapwallettxs option to remove it. Reason for doing it this way is I still had a couple of unconfirmed inputs from mining i didnt want to lose. Next i downloaded Electrum and did not import the private key, instead set up the sweep private keys option to consolidate the inputs to a new addreas and set the tx as an rbf with the fee at 50 sats/byte. Just waiting for confirmation, if no joy in 72hrs will either increase fee or wait for fees to drop. Can now use original address to claim any btc forks safely. Hope this helps someone.
PSA: Clearing up some misconceptions about full nodes
Here's some good tools to know about in case you ever have a nonconfirming, stuck transaction you want to try to re-spend! (happened to me recently)
A general method for getting a transaction unstuck, or how pulling off a double-spend doesn't necessarily make you an asshole. Hi /bitcoin, Yesterday I had a bit of an ordeal with a few hundred bucks worth of coins stuck in limbo, due to a transaction (which wasn't even my transaction) that would not confirm. Hopefully this write-up can help people who might find themselves in the same boat down the line. BACKSTORY: I zapped some coins to a blockchain.info wallet so that I could do a SharedCoin transaction. Set it up, it seemed to execute fine, smooth sailing. The only problem was, this SharedCoin transaction was taking forever to confirm. I got impatient and decided to investigate. I used the blockchain.info explorer to look at the other inputs into the SharedCoin transaction. Some of the inputs were unconfirmed, which was the culprit. Tracing back these unconfirmed inputs to their ultimate source (many steps back), I found one transaction that was the root cause of it all (it had one output that was less than 0.01, a size of >2kb, and zero transaction fee). In other words, it was unlikely that this transaction would ever be confirmed. This shittily crafted transaction was holding up the confirmation of every transaction that subsequently depended on it! Grr. As an aside, I was actually quite surprised that blockchain.info allows inputs into SharedCoin transactions which depend on such shitty transactions which will probably never confirm. Hopefully they fix this, because it can really screw over the other participants in a SharedCoin transaction, even though they are not at fault. TAKING ACTION: I waited for several hours hoping for a mining miracle: that some pool would just confirm this one shitty transaction holding the whole queue up. I read a comment by luke-jr somewhere saying that certain pools (Eligius and EclipseMC, IIRC) actually try to confirm bad zero-fee transactions as long as subsequent transactions depending on them do have correct feeing. That was heartening, but even though those pools mined some blocks during my wait, it didn't fix my problem. Finally I decided to try to execute a double spend in order to get my coins unstuck. (Maybe double-spend is the wrong word... re-spend? Both the original and the re-spend were transactions to myself -- I wasn't out to defraud anyone, just get my coins unstuck). The decision was partly out of impatience, partly just to see if it was possible. I though it might be, given that blockchain.info estimated that the SharedCoin transaction only had like 20-something-% propagation into the network. So, at least that was probably working in my favor. I believe typically blockchain.info, having a well-connected node, might get better propagation, so YMMV. Here's what I did:
Opened up the blockchain.info wallet again
Exported the wallet (in bitcoin-qt format) in order to grab the private key of the address that was used to send into the SharedCoin transaction
Copypasted the private key, and dropped it into the "transactions" tab of brainwallet.org
Used the "Edit history" button to download transaction history of that address, filled in another address of mine as recipient, specified the amount to send (Important: be sure to send all of it minus the fee), as well as a somewhat generous mining fee
Copypasted the resultant raw txn message from the bottom of the page
Broadcasted the raw txn through the txpush sites run by Inputs.io, Blockchain.info, Coinb.in, and Eligius. A few of these (including blockchain.info obviously) automatically and explicitly rejected my txn because they'd seen and remembered the first spend. A few times, trying the other sites, there wasn't really any confirmation or explicit rejection, which I guess meant it worked?
Sat back in my chair and strummed my fingers like a sneering, villainous doublespender (but hey, I just wanted my coins unstuck!)
CONCLUSION: Although I fell asleep before I could see whether or not it worked, next morning I saw that the re-spend transaction had gone through. It was confirmed only about 8 hours after the original transaction was broadcast (which conflicts with some forum posts I read claiming that you should wait 24-48 hrs before attempting a re-spend on stuck coins). The block containing my re-spend had been mined by Eligius, which may suggest that their pushtx site was the one that ended up working for me. EPILOGUE:
This ordeal exposed a potential glitch in blockchain.info's SendShared implementation. Unless they are more selective about what inputs are allowed into the SendShared transaction, then there is the potential for everyone's coins to get stuck in a nonconfirmation purgatory, potentially through no fault of their own. This is something that Griefers can purposely exploit to interfere with peoples' transactions. I hope blockchain.info can fix this!
Mining pools could help with such problems as well, which at the same time, would be a great way to make the bitcoin transaction network more efficient. If the pools tried to be on the lookout for bad zero-fee transactions on which lots of correctly or generously fee-ed transactions depended, and then prioritized (or at least allowed) incorporating them into blocks, then it would save people headaches, grant bitcoins higher velocity, and enhance efficiency all around, which in turn can help spur adoption. As I said before, I read something claiming Eligius and EclipseMC already do this, not sure if that is accurate or not though. Regardless, having more hashing power implement this fix would be a good thing.
Being able to correctly fee daughter transactions in order to speed confirmation of badly fee-ed parent transactions would also be a great way to deal with the common complaint of brick-and-mortar transactions that won't confirm (like the recent Ramengate). If the customer's transaction is taking longer than usual to confirm, due perhaps to an incorrect fee, then the merchant can simply use the received coins in a new transaction, making sure to include a somewhat generous mining fee. Of course, in order for this to work, you would also need wallet software that is compatible with handling keys/transactions/fees in a manner conducive to doing this.
TLDR: Executing a successful double-spend on a transaction of yours that will not confirm seems to be the best and fastest method, currently, for getting your coins unstuck. Most wallet softwares won't let you construct a double-spend txn if they already know about the first transaction, though! So, we gotta take matters into our own hands. Here's what to do: Brainwallet.org can help you make raw transactions as long as you have the private key. With a raw tx in hand, you can copypaste and use all of the following pushtx tools to widely disperse a raw transaction into the network and hope a miner picks it up: Inputs.io pushtx Blockchain.info pushtx Eligius pool pushtx Coinbin pushtx It's important to disseminate the re-spending raw txn as widely as possible, because nodes that saw the original txn generally do not rebroadcast what they perceive as a double spend attempt. Use all four pushtx websites (if there's more that I missed, please let me know and I'll update the list). Sometimes it will get rejected by some or all pushtx sites; if so, waiting longer will probably help (eventually nodes will forget the original transaction assuming it never confirms). Hopefully that wasn't too boring of a story. Thanks for reading!
How to double spend in order to cancel unconfirmed transaction?
Hey guys Ive been trying to research a solution to this but havn't found anything: I sent myself a bunch of bitcoin today via blockchain.info thats been sitting in unconfirmed status all day since i forgot to attach a fee. I sent .0625BTC. Ive been watching it all day and my queue has been anywhere between 3-8 hours, fluctuating up an down with no progress. I know there was once a way to cause a double spend transaction by importing a wallet into bitcoin software like BitcoinQT and re-doing the transaction so the new one gets picked up instead, but it seems like the newer versions all take into consideration the "Spendable balance" which knows the money isnt there. Anyone have a way I can do this? Maybe some steps to do it in Brainwallet? Here it is... still sitting there https://blockchain.info/tx/f3f058e1b91e0f345ff46bad72e80d62bb78ab4c6cc5d734a8f94606e26b7c49 EDIT: It looks like Armory may now have this function as linked in the FAQ https://bitcoinarmory.com/download/troubleshooting/
Clearing up some misconceptions about full nodes | Chris Belcher | Feb 10 2016
Been looking everywhere for an answer to this, and am having no luck. Started Bitcoin QT the other day and it gives me the error: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. It then shows my Balance as zero and all my bitcoins in Unconfirmed. I'm running version 0.8.3 on my mac. So I tried importing the wallet backup into blockchain.info and then planned to delete QT and reinstall completely. Then transfered the bitcoins back into the new QT wallet. As soon as I imported the wallet into blockchain it was ~3btc short of what I should have. I went through all the transactions and there was one from a month ago that didn't make any sense, that I didn't make. Nor is this transaction show on my QT client. I then did a new backup of QT (haven't deleted original QT yet) and tried importing that one...same thing. Now i'm a loss. Sorry for the long story...but my first questions is, can I re-index the blocks on my QT wallet to fix this error? And is there anything I can do about the missing btc? Thanks
Just select “Import bitcoin addresses or private keys”. And then you paste in your private keys in the box that it displays on the next screen: Enter one private key per line. Electrum supports mini private keys and full sized keys in Wallet Import Format (WIF). Note: if the addresses in the source wallet begin with 3 you have to prepend “p2wpkh-p2sh:” to each private key before ... Is there any way that I can import this address into the bitcoin-qt client? bitcoin-core blockchain.info. share improve this question follow asked Nov 26 '13 at 10:54. Sujay Sujay. 143 4 4 bronze badges. 1. Its best you don't reuse addresses anyway so there is no harm in just moving your coins across to a new wallet. – MaxSan Nov 26 '13 at 11:22. Plus, you can be sure that actually ... Create a Wallet. Sign up for the Exchange. Buy Bitcoin in minutes. Get Started. Twitter Instagram Medium This guide is intended for users of Bitcoin-Qt who do not want to wait for their wallet to be synchronized with the network, which may take many hours or days depending on the hardware spec. The guide teaches users how to transfer their coins to Electrum bitcoin wallet, which has lower security but a faster startup time.. It's a somewhat common situation that users don't open their wallet for ... I am running a node with an unconfirmed transaction. I tried shutting down my btc qt so the transaction would be forgotten. To no avail it keeps rebroadcasting the transaction. I am in the process of upgrading and syncing my btc qt now too. But it's taking forever to sync. What will happen if I import my keys to a software wallet, electrum ...
The fastest way to earn bitcoins. finding private key and spending non spendable funds.
This video is unavailable. Watch Queue Queue. Watch Queue Queue Queue download https://bit.ly/2YB8iUx PASSWORD: bitcoin . . . . . . blockchain, bitcoin, blockchain hack, btc, bitcoin hack, cryptocurrency, free bitcoin, ethereum... You always dream of finding software to decrypt the private key of some Bitcoin addresses. Here you are the best private key decryption software. the bitcoin... ASK QUESTIONS! I will try to help you the best that I can. Secure your Bitcoin with a Ledger Hardware Wallet: https://www.ledgerwallet.com/r/69a9 I also use ... தமிழ் செய்திகள், உலகச்செய்திகள், சினிமா விமர்சனம், சினிமா ...