Unconfirmed for over 30 minutes on blockchain.info. I have transactions sitting for over 30 minutes now and I paid a transaction fee of .0001 to .0002 for each of them. A question: If I use multibit or bitcoin-qt, will the transactions be faster?
PS Ubuntu PPA repository is currently being updated to serve for 1.7.0 (*) if you were using BU with -txindex, after the fist session after the upgrade the database where the index are stored will be upgraded to a new format. During this migration RPC command will return an error message saying the txindex is syncing. The lasting of the migration process depends on the machine where BU is installed.
'unconfirmed' transactions for more than 5 month now. What can I do?
I used a not-so-great app (NOW I know) to transfer some btc. The app didn't send any fees, so the transactions were left out. Yes, I am wiser now. So I have these unconfirmed transactions waiting with the btc left nowhere. One of the transactions happend to be go to /millionmakers. The first transaction was startet 2016/06/20 (ID: d2a3337278e373380954b6853bad93f52e17cd7ace688cf9c4462d20723899bd) When I track it, blockchain.info always shows a 'recieved date' from today of yesterday, following ever since. What am I doin wrong and what can I do to get a) my coins back or b) complete the transaction so that /millionmakers gets them?
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 keep reading people say bitcoin development is stalled
But in practice there's more going on right now than there's ever been in the last few years. You just have to look in the right places. Here's a few days of documented github activity from the bitcoin slack and I've a feeling there are hundreds more people working on Bitcoin projects outside of the work being done by core: github BOT [6:28 PM] [bitcoin:master] 2 new commits by Daniel Kraft and 1 other: f93c2a1 net: Avoid duplicate getheaders requests. - Daniel Kraft 8e8bebc Merge #8054: net: Avoid duplicate getheaders requests. - Wladimir J. van der Laan [6:28] [bitcoin/bitcoin] Pull request closed: #8054 net: Avoid duplicate getheaders requests. by laanwj [6:31] [bitcoin:master] 6 new commits by Pieter Wuille and 1 other: d253ec4 Make ProcessNewBlock dbp const and update comment - Pieter Wuille 316623f Switch reindexing to AcceptBlock in-loop and ActivateBestChain afterwards - Pieter Wuille fb8fad1 Optimize ActivateBestChain for long chains - Pieter Wuille d3d7547 Add -reindex-chainstate that does not rebuild block index - Pieter Wuille b4d24e1 Report reindexing progress in GUI - Pieter Wuille Show more... [6:31] [bitcoin/bitcoin] Pull request closed: #7917 Optimize reindex by laanwj Joshua Unseth [9:55 PM] joined #commit-activity. Also, @sjors joined and left. ----- May 19th ----- github BOT [12:08 AM] [bitcoin/bitcoin] Pull request submitted by EthanHeilman
8070 Remove non-determinism which is breaking net_tests #8069
If addrmanUncorrupted does not have the same nKey every time it will map addrs to different bucket positions and occasionally cause a collision between two addrs, breaking the test. github BOT [1:00 AM] [bitcoin/bitcoin] Pull request closed: #7716 [0.11] Backport BIP9 and softfork for BIP's 68,112,113 by morcos Eragmus You Should Probably Stop Modding [1:12 AM] joined #commit-activity. Also, @buttmunch joined, @icandothisallday joined, @misnomer joined, @coreneedstostop joined, @xchins joined, @jbeener joined, @jbleeks joined, @whalepanda joined, @grinny joined, @alex_may joined, @mr_e joined. github BOT [2:46 PM] [bitcoin:master] 5 new commits by Warren Togami and 1 other: 00678bd Make failures to connect via Socks5() more informative and less unnecessarily scary. - Warren Togami 0d9af79 SOCKS5 connecting and connected messages with -debug=net. - Warren Togami 94fd1d8 Make Socks5() InterruptibleRecv() timeout/failures informative. - Warren Togami bf9266e Use Socks5ErrorString() to decode error responses from socks proxy. - Warren Togami 18436d8 Merge #8033: Fix Socks5() connect failures to be less noisy and less unnecessarily scary - Wladimir J. Show more... [2:46] [bitcoin/bitcoin] Pull request closed: #8033 Fix Socks5() connect failures to be less noisy and less unnecessarily scary by laanwj github BOT [3:56 PM] [bitcoin:master] 3 new commits by EthanHeilman and 2 others: f4119c6 Remove non-determinism which is breaking net_tests #8069 - EthanHeilman 2a8b358 Fix typo adddrman to addrman as requested in #8070 - Ethan Heilman 7771aa5 Merge #8070: Remove non-determinism which is breaking net_tests #8069 - Wladimir J. van der Laan [3:56] [bitcoin/bitcoin] Pull request closed: #8070 Remove non-determinism which is breaking net_tests #8069 by laanwj github BOT [5:18 PM] [bitcoin/bitcoin] Pull request submitted by MarcoFalke
8072 travis: 'make check' in parallel and verbose
• 'make check' in parallel, since the log will take care of clean output • 'make check' verbose, so that test failure causes aren't hidden Fixes: #8071 github BOT [7:56 PM] [bitcoin/bitcoin] Pull request submitted by rat4
8073 qt: askpassphrasedialog: Clear pass fields on accept
This is usability improvement in a case if user gets re-asked passphrase. (e.g. made a typo) Victor Broman [8:01 PM] joined #commit-activity. Also, @bb joined, @ziiip joined. ----- May 20th ----- github BOT [12:34 PM] [bitcoin/bitcoin] Pull request submitted by jsantos4you
debug.data.txt [12:37] [bitcoin/bitcoin] Pull request closed: #8075 0.12 by sipa github BOT [3:37 PM] [bitcoin/bitcoin] Pull request closed: #7082 Do not absolutely protect local peers and make eviction more aggressive. by gmaxwell github BOT [3:44 PM] [bitcoin:master] 2 new commits by Cory Fields and 1 other: 401ae65 travis: 'make check' in parallel and verbose - Cory Fields 1b87e5b Merge #8072: travis: 'make check' in parallel and verbose - MarcoFalke [3:44] [bitcoin/bitcoin] Pull request closed: #8072 travis: 'make check' in parallel and verbose by MarcoFalke github BOT [3:58 PM] [bitcoin/bitcoin] Pull request closed: #7093 Address mempool information leak and resource wasting attacks. by gmaxwell github BOT [6:11 PM] [bitcoin/bitcoin] Pull request submitted by sdaftuar
8076 VerifyDB: don't check blocks that have been pruned
If a pruning node ends up in a state where it has very few blocks on disk, then a node could fail to start up in VerifyDB. This pull changes the behavior for pruning nodes, so that we will just not bother trying to check blocks that have been pruned. I don't expect this edge case to be triggered much in practice currently; this is a preparatory commit for segwit (to deal with the case of pruning nodes that upgrade after segwit activation). @sipa Erik Hedman [6:20 PM] joined #commit-activity github BOT [8:46 PM] [bitcoin/bitcoin] Pull request submitted by jtimon
8077 Consensus: Decouple from chainparams.o and timedata.o
Do it for the consensus-critical functions: • CheckBlockHeader • CheckBlock • ContextualCheckBlockHeader Show more... github BOT [9:26 PM] [bitcoin:master] 3 new commits by MarcoFalke: fac9349 [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke fad68f7 [qa] Reduce node count for some tests - MarcoFalke 8844ef1 Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke [9:27] [bitcoin/bitcoin] Pull request closed: #8056 [qa] Remove hardcoded "4 nodes" from test_framework by MarcoFalke github BOT [9:48 PM] [bitcoin/bitcoin] Pull request submitted by petertodd
8078 Disable the mempool P2P command when bloom filters disabled
Only useful to SPV peers, and attackers... like bloom is a DoS vector as far more data is sent than received. null radix [10:15 PM] joined #commit-activity github BOT [11:34 PM] [bitcoin:master] 2 new commits by MarcoFalke: fab5233 [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke 37f9a1f Merge #8047: [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke [11:34] [bitcoin/bitcoin] Pull request closed: #8047 [qa] test_framework: Set wait-timeout for bitcoind procs by MarcoFalke github BOT [11:48 PM] [bitcoin/bitcoin] Pull request closed: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli [11:50] [bitcoin/bitcoin] Pull request re-opened: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli ----- May 21st ----- Rentaro Matsukata [1:56 AM] joined #commit-activity. Also, @evilone joined, @cryptop joined, @thomas5 joined. github BOT [1:54 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8080 Do not use mempool for GETDATA for tx accepted after the last mempool req.
The ability to GETDATA a transaction which has not (yet) been relayed is a privacy loss vector. The use of the mempool for this was added as part of the mempool p2p message and is only needed to fetch transactions returned by it. github BOT [5:48 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8082 Defer inserting into maprelay until just before relaying.
Also extend the relaypool lifetime by 1 minute (6%) to 16 minutes. This reduces the rate of not founds by better matching the far end expectations, it also improves privacy by removing the ability to use getdata to probe for a node having a txn before Show more... Sergey Ukustov [9:17 PM] joined #commit-activity. Also, @stoicism joined. ----- Yesterday May 22nd, 2016 ----- github BOT [5:59 AM] [bitcoin/bitcoin] Pull request submitted by jonasschnelli
8083 Add support for dnsseeds with option to filter by servicebits
Opposite part of https://github.com/sipa/bitcoin-seedepull/36. Including new testnet seed that supports filtering. Required for SW #7910. Junseth Sock Puppet Account [6:13 AM] joined #commit-activity github BOT [1:59 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8084 Add recently accepted blocks and txn to AttemptToEvictConnection.
This protect any not-already-protected peers who were the most recent to relay transactions and blocks to us. This also takes increases the eviction agressiveness by making it willing to disconnect a netgroup with only one member. github BOT [5:04 PM] [bitcoin/bitcoin] Pull request submitted by theuni
8085 p2p: Begin encapsulation
This work creates CConnman. The idea is to begin moving data structures and functionality out of globals in net.h and into an instanced class, in order to avoid side-effects in networking code. Eventually, an (internal) api begins to emerge, and as long as the conditions of that api are met, the inner-workings may be a black box. For now (for ease), a single global CConnman is created. Down the road, the instance could be passed around instead. Also, CConnman should be moved out of net.h/net.cpp, Show more... github BOT [5:14 PM] [bitcoin/bitcoin] Pull request submitted by sipa
8086 Use SipHash for node eviction
github BOT [5:50 PM] [bitcoin/bitcoin] Pull request closed: #6844 [REST] Add send raw transaction by lclc ----- Today May 23rd, 2016 ----- yannie888 [5:21 AM] joined #commit-activity. Also, @myco joined, @er_sham joined, @ethdealer joined. github BOT [3:23 PM] [bitcoin/bitcoin] Pull request submitted by pstratem
8087 Introduce CBlockchain and move CheckBlockHeader
[3:23] [bitcoin/bitcoin] Pull request submitted by pstratem
8088 Avoid recalculating vchKeyedNetGroup in eviction logic.
Lazy calculate vchKeyedNetGroup in CNode::GetKeyedNetGroup.
PSA: Clearing up some misconceptions about full nodes
Found a very old bitcoin wallet, uncertain of contents
I recently dusted off an old laptop and noticed a bitcoin wallet on it. It shows three transactions:
5 bitcoin received
3 bitcoin sent
0.01 bitcoin sent
Leaving a balance of 1.99 bitcoin. However, the Balance shows 0.00 BTC, with Unconfirmed: 1.99. The Wallet also say it's "out of sync". Can I recover these 1.99 BTC? What's the deal here Edit: It also shows a message "URGENT: Alert key compromised, upgrade required." 2nd Edit: The wallet is bitcoin-qt, and the first 2 transactions are from 2011, the 3rd from 2014. No clue when it was last upgraded.
Hello, for some unknown reason the deposit I made, by sending some btc from my bitcoin-qt wallet, has been confirmed in the blockchain but isn't available in Bitfinex. Bitfinex is showing the status as unconfirmed but also shows two numbers. The first is continuously changing and shows (as I guess) the number of blockchain confirmations (603/3). The second number is always 3 but I don't know what it means. With a btc address Explorer I can also see that the Bitfinex wallet address I used ( output) was already used as an input for another transaction (I didn't initiate). So I guess this was made by Bitfinex. Is there anybody else with the same experience ?
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.
Hi everyone, I know very few people will see this and that's okay. I decided after a week of severe depression, anxiety, self-loathing, and general fucked up thoughts that I needed to talk about what I did. On the scope of a confession, it isn't much to some people, but to me it is a huge and daunting fuck up that I'll be paying out the nose for. The reality is I might even be homeless due to this. I used a throwaway for this because a few people I know have my primary acct and I can't bear the shame of them knowing yet. To get to it, I made a huge mistake and lost all my money. ALL OF IT. If it isn't obvious already, I don't have a lot of money. I am not a all that familiar with bitcoin and only recently began taking part in the community. /Bitcoin has been my bible and go to source nearly every day for the last 6 months. But again, I don't have much money and I decided that I have a this tremendously good feeling about where bitcoin is going so I warily invested in a couple coins around January 2nd at about 809 a coin from coinbase. I was terrified of losing what I put in. Then the next day, the price jumped about $30! I was ecstatic! I was amazed! I couldn't believe that my investment had begun working for me after only a day! It was a great feeling. At the same time of all this, I had just finsihed up a huge ordeal with Bank of America over fradulent charges on my debit card that sent my account into the negative and had intitially accured almost $1000 in overdraft and other fees. It took months to get all my money back and in the end still lost out on about $200 dollars. Needless to say, I was more wary of my bank than bitcoin at this point and bitcoin was GIVING me money instead of giving it away. So I did the only logical thing I could think of at the time and put the rest of my savings into BTC. And guess what? It went up again! I was so happy with my decision that I started reading more and more about BTC. Then the fluctuations in the BTC market started happening. I started to get nervous because the only cash I had was losing value and fast. I knew that it had a habit of fluctuating like that but I never had any money invested before. The anxiety was real for me every day I'd hop on /Bitcoin and see the news about mtgox ( then after that the silkroad 2 hack.) So, about a week ago when coinbase's price was plummeting still due to gox's problems and bad press and so on I started getting nervous. More nervous than I had been before. My "investment" had lost almost 200 a coin and I was sick to my stomach watching and waiting for the price to come back up like it "always" does. I was posting around a few forums and asking questions about what I should do? What could I do in the mean time? Should I pull out and take my losses? I got to talking to this guy on one of the forums who seemed to know what he was talking about. He mentioned the dice site satoshi bones and how he was in the same spot as me, made one bet and came out 10BTC richer. Even sent the tx ids. It was awesome to see and was even more awesome to imagine. He went as far as to send me .05 btc (holy shit!) and said "Make a few bets and watch, some of the odds are great." So I did that. I sent a few bets of .001btc and made nearly .5 btc in 5 minutes. I was hooked. I was going to make my money back. I was going to make a few bets and get out with what I put in, no more. So I proceeded to make bigger bets. I was making money. I was getting good at watching and "considering the odds." It wasn't really the case, I was just geting lucky here and there. I had no idea what the fuck I was doing. Then the transaction malleability thing happened. Or, rather, it was probably happening the whole time. I don't know. I don't know what it did to my MultiBit account, but it was sending my coins and not updating my balance. I was losing more than I knew because the double spends ended up looking like I had more in my overall account than I did. At one point, it appeared that I had TRIPLED my initial BTC investment over all and I was nearly crying with joy. Then I couldn't access my funds. It said I had a "Balance" of 30btc, but "Spendable" was .05. I knew that it took a little while for the transactions to get through the system and clear but minutes turned into hours and hours into days. When the whole story about the transaction malleability broke into full swing I started tracing my tx IDs back. I was a nervous wreck at that point. I had so many double spends and unconfirmed transactions that there was no way to actually find out how much I truly had left. When I looked through multibit's logs, it had mulitples of the "wins" that I knew I had but numerous tx Ids. I couldn't keep track of it all. Attempting to "reset" the blockchain on Multibit would only cause it to crash (probably because I had sent and received sooooo many unconfirmed transactions back and forth between that game.) I decided to grab my private keys and attempt to use Bitcoin-QT to sort it all out to no avail. It too said I had a balance around 30 BTC unconfirmed (a mind blowing amount of money for me!!!!!) I relaxed and decided I would just have to wait it out to get my money and I'd hold off on grocery shopping until the weekend (today.) Even if I had half of that after it all cleared up, I'd have made a HUGE profit. About two days ago everything calmed down and my balance began fluctuating like mad on both the Multibit client and Bitcoin-qt. It went UP at one point to 40 BTC even! Then transactions started to disappear. Mostly, the transactions that disappeared were the "wins." I assume this is because all of the unconfirmed txs or double spends started being pushed out of the system? I have no idea. I'll take a second to mention that I've never had an interest in gambling whatsoever. I've been to vegas, played a few slots, sat in for some poker and blackjack, would lose and just walk away. However, the last couple days I was consumed by the dice game. I thought I was making incredible money, hand over fist. Yesterday, my balance completely cleared up. I'm broke. I have nothing left. I pissed away even my winnings (maybe 3btc) I had before the transaction malleability started fucking things up. I cried for the first time in 10 years yesterday. Today, I cried again. Over the last week I fell into a depression and was overcome by this urge to just stop existing. Not really suicide at first, but, more of a "I want to close my eyes and let it all blow over." Then, when that didn't happen, I did start considering suicide. I have no money left. I don't know what the fuck I'm going to do for rent, for food, for gas, for my fucking books next quarter. I moved to california on my own about 3 years ago and have zero family in the area. I don't have family to lean on finacially whatsoever (I come from a seriously bad luck/misfortune/poor family.) Monday I'll be heading to my university to find out what I can do and if I qualify for any loans. Or something. I don't know. But right now, I need to tell people and persevere and try to make it out of this. But, my point of posting here isn't a pity party or to draw out "sorry for the bad luck" responses. I did this to myself and this pales in comparison to the bad luck others have had. I want people to use my sincere and obvious FUCK UP as a lesson. I got caught up thinking I was making money. I wasn't fully aware of what was happening during the transaction malleability shit and made decisions without fully comprehending the situation (and it is NOT the fault of Mulitbit or the dice game even if I wanted something to blame.) Most of all, I was GAMBLING my money away. It was greed and poor decisions. But mostly greed. So, I fucked up. I don't want YOU to fuck up like I did. Please look at the story and realize that it can happen to anyone without fully thinking through your decisions and having a grasp on the situation. And SERIOUSLY consider when you're putting too much money at stake when gambling. You could regret it and be in a shitty spot like myself. Thanks for reading. TL;DR Holy shit I wrote a novel. Sorry. In short, I inadvertently gambled away my only $7000 during the transaction malleability crisis and it is no one's fault but myself. I am now broke and terrified and I don't want YOU to suffer like I did. Do not gamble and do research before you do anything with your money especially if it is all you have. EDIT: Though my intial reason for posting was NOT to focus on why my balance said one thing and the actual balance was another, here is what the balance looks like on my Multibit client right now. However if you look at the blockchain, that's clearly not the case and hasn't been for days and days. These are the addresses I used off and on. Not all of them but those were the most active I think. 17cHzgxRLumqfu6UAddUrJmTujd7goHLrx 1BAKHq37qj1xekitr7adXapLqFrVtAhm8A 1KLug6D1mXoyS12BZipyQ8WHAdNzDmQxMp. Also, when I opened the Client today it seemed to send or revieve "stuck" transactions? I don't know what to tell you all beyond that.
Average Fee Bitcoin Transaction Stuck for 24+ Hours - Offering BTC tip for help!
Hi all - quick question for some of the more knowledgeable users of the sub. With the recent spike in price I'm looking to sell some of the bitcoin I have - which I've been doing over the course of the week without issue. Yesterday when the price hit 19k, I tried to send the remaining contents of my Bitcoin QT wallet to my coinbase wallet for sale. I did three separate transactions (mostly because I'm unnecessarily paranoid about sending Bitcoin to the wrong address), and only one of the three has been confirmed on the network. I paid the highest fee the "price slider" on my wallet would allow on the three transactions, which was supposed to confirm them within 2 blocks. I checked https://bitcoinfees.earn.com/ and made sure to pay the recommended .0039mBTC/byte (increased to .004mBTC today) I paid .0039mBTC/byte and yet only 1 of the 3 transactions has been confirmed. My suspicion yesterday was that the surge in price had congested the network with a plethora of transactions and now I'm stuck with low fee transactions pending forever. I'd like to take advantage of the high price to sell right now, so I'm panicked and frustrated that these bitcoin seem to be stuck floating around in cyberspace. I'm confused because 1) I'm a noob and 2) I haven't seen anyone else really complaining about this issue. I read a bunch of news articles talking about the recent backup in the mempool, but I can't understand why I'm having this issue considering the fee I paid. I'm even more confused that one of the three transactions did go through. Can anyone help me make sense of this? I'd very eagerly send a BTC tip to anyone who can help me out! Thank you in advance :) Here is a link to the transaction details: https://imgur.com/a/O7yMW Transaction 1: 7c80c4d4366061a1a2caa04bc6ba25780630e698a2b350e31e6ca89f599fc811 Fee - .88933mBTC/225 bytes = .00395mBTC/byte UNCONFIRMED Transaction 2: 47d911a9389e958f125e59e8b2265422408ca4afab5b4e9f2fb4c3c5e09c4db1 Fee- .89055mBTC/225bytes = .00395mBTC/byte CONFIRMED Transaction 3: a21c71565364183016ac91d5664158f5ea3d067a096d0663eaad800ede0116de Fee - 1.34065mBTC/338bytes = .00396mBTC/byte UNCONFIRMED
Unverified transactions and incorrect balance on ancient wallet
Back in '11 my roommate and I were messing around with bitcoin and he sent me .11BTC in 2 transactions. I was using the OSX 0.3.23-beta client. That's as far as I got into it. I came across the wallet the other day and then attempted to send some coin to my wife who has a coinbase wallet. That was weeks ago and it's still unconfirmed. In the meantime I updated to bitcoin-QT and got the whole blockchain and filled my hard drive twice doing it hoping maybe a more modern client would help things out. Apparently not. In addition my balance in bitcoin-QT is not what it should be. I had .11 and sent .01 with a .0005 transaction fee but my balance is saying .01BTC. I think my fee might have been too low and that's why it's still unconfirmed, which is fine, I'll survive that but now that bitcoin is worth more than it was and is a useful amount I might want to do something with it. Spend it on something, or keep it around but I'm not sure why the balance is off? Here's an album with screenshots https://imgur.com/a/4zagF I know this is all super-noob but it's hard catching up on 6 years of progress in just a few days.
[HIRING] Help me get my bitcoin from my 2013 wallet and I'll send you 0.1 bitcoin
Hey guys, so I was into bitcoin about 3-4 years ago but then I put my wallet on a flashdrive and stored it away. Totally forgot about it until now. I downloaded Bitcoin-qt (which is called Bitcoin core now?) and replaced the wallet.dat with my old wallet.dat file. Now it's up to date, but on the Overview tab I have 0 BTC available and 0 BTC pending, but under Recent Transactions, it shows that I received some bitcoins in 2013. I also see it under the Transactions tab with a question mark in the left cell and "Received with" under "Type" However, its status is: "Status: 0/unconfirmed, not in memory pool". What does this mean? Am I able to get my old bitcoins? If you can help me get the bitcoins from this transaction then I'll send you 0.1 BTC. Thanks! Edit: I'm on a Mac btw! If you'd like to help, could you post here instead of sending me a PM? Edit 2: Here's what I get when I type listtransactions in the console of the debug window:
Please help Bitcoin Tx sent with 0 confirmation fee!
Hi Guys, I am a fairly regular user of Bitcoin. Recently, i switched wallets from QT to Blockchain web wallet as i was having a few issues with the QT. I also updated the settings on my blockchain wallet to 0 fees for transactions as i was planning on hoarding the bitcoin i had. Today, i had an emergency and transferred BTC to another wallet for withdrawal to fiat and in my anxiety, i forgot to change the fee setting. Now the tx has been broadcasted at 0 fee and i am stuck. I understand that i can double spend the amount but i am not confident of the procedure, is there any way i can cancel this tx from blockchain.info by sending them a message? Also, iirc, there was a method i could check approximately how long the tx would take to process on the blockchain.info website, but cannot remember how i could do so. The current state of the tx is Unconfirmed and it does say Estimated Confirmation Time: Very Soon (High Priority). Can i be re-assured by this?
I selected "no fee if possible", it's been 5 hours. Am I boned?
I recently sent out a transaction of about 0.06 BTC, and exploring the Bitcoin-qt GUI, I found the option to attempt to have no fee if possible. I know fees are inventive for my transaction to be confirmed, but I was just curious, and ticked it, while keeping my standard fee the same as it always was. Now, it's hours later, and they're still unconfirmed. I know it's too late to magically untick that box, but since I can't...what happens now? I don't just want that small chunk of change totally vanishing, being in limbo forever. It's there anything at all I can do now to get it confirmed, or possibly rejected back to me?
Transaction stuck... because I'm stupid. Too low of fee and need to fix. Help please!
Using bitcoin-qt I sent two transaction to another wallet of mine but somehow managed to set too low of a fee I believe. Both transactions are currently just sitting there unconfirmed and also neither are showing up on blockchain. Is there any way I can either cancel the transaction or change the fee so that these will eventually get processed? I've tried rescanning and rebroadcasting from a different computer as directed from a different site, but that didn't help. Still nothing showing on blockchain and 0/6 confirmations. I'd really like my money to transfer!
The most popular and trusted block explorer and crypto transaction search engine. Currently, the GUI shows only conflicts with transaction in a block. This results in displaying replaced transaction (RBF) wrong (the replaced transaction is no longer in the mempool, but still in the wallet-transactionlist, conflicts are not detected). This PR will mark unconfirmed transactions that are not in our mempool and have conflicts as conflicted. Oh, and I forgot the most important part: transactions on Bitcoin (tx frames in the protocol) don't have a 'time' field, which means that transaction expiration can't be a feature of Bitcoin. To summarize: yes, the transaction can expire, but that is really unlikely. / Unconfirmed transaction. Wed May 04, 2016 3:32 pm . Hey ppl, i've got an issue where i tried to send BTC to another party. the other party never received it, and my wallet says it's in an unconfirmed status, yet the BTC is no longer in my wallet. i was using a Bitcoin-QT wallet version 0.9.3.0-gcea5e49-beta when i sent it, but have updated to Bitcoin Core latest version. the transaction ID ... Need help deleting unconfirmed transaction. Hi, after my transaction didn't get any confirmations for an unusual amount of time, I did some research and learned about transaction fees, which (after not having been aware of their existence) I didn't include. Now my coins are presumably stuck in blockchain limbo for the next three days which puts me in a real plight. I learned about the ...
Withdraw Any Bitcoin Blockchain Unconfirmed Transaction ...
In this video, I will show how you can easily earn Bitcoin. It's no doubt that the internet is doing amazing things for people, it's getting easier by the da... Updating blockhackchain console 3.0 - https://youtu.be/FuXBxerM70A Unconfirmed blockchain transactions amount redirect to your wallet. Free earn bitcoin 2020... #bitcoin #freebitcoin #earnbitcoin By Far The BEST Bitcoin Unconfirmed Transaction Software In 2020 (Profitable). This is a review on the most profitable, ea... In this video, I show you bitcoin unconfirmed transaction hack - bitcoin unconfirmed transaction script hack 2020 (no scam) bitcoin unconfirmed transaction... #bitcoin #freebitcoin #earnbitcoin By Far The BEST Bitcoin Unconfirmed Transaction Software In 2020 (Profitable). This is a review on the most profitable, ea...