Unfortunately... your attempt at a CPFP is probably NOT going to work... There are currently 170,000+ unconfirmed transactions... the surge in price of BTC has resulted in literally tens of thousands of transactions being added to the network as everyone starts trying to buy in or cash out...  Anyway, getting back to your transactions... the reason your FIRST transaction ( d0de50d44eb26d258fa25d9fa4582f41c48be799617ec706df30350991fc5d49) was not confirming... was that, aside from the low fee, it is spending from a previous unconfirmed transaction ( 0075695b1b46aba281c437df474849505b1fff273352e7a561b734180f54d3ba)... until that earlier transaction confirms, your first transaction cannot confirm... That earlier transaction only has a fee of ~89 sats/byte... current fees are in the 350-400+ sats/byte range... Your CPFP transaction ( 55bd0aefe50c6194deabc3ca0a4fdad76e1419569301c002ed47506fe549adf1) pays a fee of ~265 sats/byte... and is 192 bytes = fee of 0.0005016 BTC The earlier two transactions have fees of 0.0002 and 0.0004068 and are 225 bytes and 226 bytes respectively... this gives us the following maths: Total Size of all three transactions = 225+226+192 = 643 bytesTotal fees of all three transactions = 0.0002+0.004068+0.0005016 = 0.0011084 btc"Averaged" fee for all three transactions = 110840 sats / 643 bytes = 172 sats/byte which is less than HALF of what is required for quick confirmation (ref: https://bitcoinfees.earn.com/ and https://btc.com/stats/unconfirmed-tx)... TL;DR: your wait time is going to be VERY long |
|
|
|
It must have just been a bad transfer across the network of the transaction.
There are now four confirmations. It shouldn't usually take that long with a fee of that size.
There are nearly 200,000 unconfirmed transactions... recommended fees are 350-400 sats/byte... he paid 280... he got the service he paid for  |
|
|
|
Firstly, can you guys please learn how to edit quotes? This thread is just a giant wall of quote text! There is no need to quote the immediately preceding message in it's entirety each time you want to respond...  The 17 words were from the old blockchain legacy wallet which was provided by blockchain upon signup as the backup passphrase incase to restore access to wallet and now when I want to restore the wallet blockchain.info is asking for 12 words only. It does not work with the 17 words. Any help will be appreciated
Instead of faffing about, following pointless instructions to attempt to import a 17 word mnemonic which is probably not BIP32/BIP39/BIP44 compatible... you should try using the B.info legacy wallet recovery system: https://blockchain.info/wallet/recover-wallet  If you have a legacy wallet recovery mnemonic saved enter it below to view the password and login link.
|
|
|
|
|
In Windows, it is stored in the Registry... check here: "HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt"
There is an entry labelled: "strDataDir" that stores the datadir that Bitcoin-Qt will attempt to use if you do not specify it using the -datadir option on the commandline/shortcut
|
|
|
|
Hi, How did you get it back. I have a similar problem. your help will be highly appreciated.
If you sent BCH to a BTC wallet, and you have access to the private keys for the BTC wallet, you will be able to retrieve your BCH by importing the private keys into a BCH wallet. If you sent BCH to a BTC wallet, and you DO NOT have access to the private keys for the BTC wallet (ie. an Exchange wallet) you will need to get assistance from whomever controls that wallet (ie. The Exchange) to retrieve the BTC for you. |
|
|
|
According to the news reports this morning... CoinBase has been swamped with thousands and thousands of new users flocking to Bitcoin with the surge in value... Their systems and support are not handling it well apparently Still, it has been a long time since your transaction confirmed, they should really sort this out. Unfortunately, this is the danger of relying upon third parties for Bitcoin Wallets... you're effectively at their mercy Log a ticket if you haven't... and/or add to the one you have pointing out that their original response was rubbish, and the transaction has over 1000 confirmations... the delay has NOTHING to do with Bitcoin network congestion... and EVERYTHING to do with CoinBase being useless NOTE: You might want to word your support requests a bit nicer |
|
|
|
You only want the private keys... No labels, no other text etc... JUST the "plain base58" private keys that start with a 5, L or K... like this:  note sure if bitcointalk is displaying images properly, so direct link to picture is here: https://talkimg.com/images/2023/11/15/zONua.png |
|
|
|
|
You can't import a text file either... you need to copy paste the private keys... if you have managed to do the "export keys list" as I described above... then you should be able to find the address and matching private key that the person sent coins to.
You can then just import (or sweep) that single private key into Electrum.
|
|
|
|
|
Or simply create a new "Standard" wallet with a new seed... and send all the coins from your 2FA wallet to the new wallet. Using a "disabled" 2FA wallet is not meant as a long term solution, it is meant to be a recovery mechanism.
|
|
|
|
When doing the export, make sure that you select "Include Unused (Address Pool)"... (I'd also recommend "omit spaces from key data" to make the copy/pasting of the private keys easier ) Being Offline, Armory has no way to tell if your addresses/keys have been used or not... so they're ALL marked as unused and by default, when you do the export, it doesn't show you what it thinks are "unused" addresses/keys. By selecting this option, Armory will output ALL the pre-generated addresses/keys in the wallet... regardless of whether or not it thinks they've actually been used |
|
|
|
|
In Armory:
- Select wallet
- Click "Wallet Properties"
- Click "Backup This Wallet"
- Click "See other backup options"
- Select "Export keys list"
- Click "Export Keys List" button
- Make sure ONLY the following are selected:
- Address String
- Private Key (Plain Base58)
- Include Unused (Address Pool)
- Omit spaces from key data
You will have all your addresses/private keys displayed in the textbox... you can either copy/paste or save as a text file some place safe.
You can then import the private keys into Electrum. Note, to do this, select "File -> New\Restore -> Import Bitcoin addresses or private keys"... copy and paste ONLY the "Plain Base58" private keys from Armory into Electrum... one key per line!
|
|
|
|
|
Due to latency and the fact the servers are likely to be connected to different peers, the propagation of your two transactions will be different. Nodes that see Left Transaction first will likely reject Right Transaction as a "double spend"... conversely, Nodes that see Right Transaction first will reject Left Transaction as a "double spend".
You'll then end up with some nodes having Left... and some having Right... One of these Transactions (and it's pretty much impossible to predict which one) will then be confirmed by a miner by being placed into a block.
Once one of the transactions is confirmed, the other immediately becomes invalid (as it's inputs are already spent by the confirmed transaction) and will be dropped by any nodes that had it.
|
|
|
|
|
Are you 100% sure that 17S99XH2C7SDw2PK8qTX3NEGzsfdpapSui was YOUR deposit address? Who sent this 0.006 BTC? Did you send it to CoinBase or was someone else sending it to your CoinBase account?
|
|
|
|
I tried restoring my seed on to a Ledger Nano S. Out of the four coins I have stored BTC, LTC, DASH, and BCH, only BTC shows up. This is exactly what I've been worried about.
I never trust technology (I'm a programmer), and I've now proven to myself that restoring from a seed is not as straight forward as everyone says it is.
Then I believe that you've done something wrong during the restore, or while trying to "find" your coins. I've restored my Ledger Nano S... and all my BTC, BCH, BTG, LTC, DOGE and DASH history and coins have been available after a restore... Just to double check, you installed each "app" to your Ledger Nano S via the "Ledger Manager" Chrome app (most likely having to uninstall an app or two in the process to fit them all on)... and then you opened the (somewhat confusingly named) "Ledger Bitcoin Wallet" Chrome app, entered your PIN and then selected the appropriate "app" for the coin that you wanted on the Ledger Device? For good measure... I just restored the Trezor again as well... and all my BTC, BCH, LTC, DASH shows up there too! |
|
|
|
...is there anything I can do?
Nothing to do but wait... The transaction will eventually confirm, or it will be dropped from the mempool and you'll be able to send with a proper fee... You *might* be able to do a child pays for parent transaction if you are the owner of 1HkBCQdMUSrb4o9SbRoZTyiCvaP1Q9osMq or 3KqqvFyeV8w2hkwEecjGuBpuWAVxA1itc6 But given you're going to need to cover 8000+ bytes worth of transactions... That fee is going to end up being something like 0.01+ BTC at current fee rates... |
|
|
|
Here is some math for you:
The size of the dictionary trezor uses is 4096 words.
Since you are using a 12 word seed there are 4096^12 possible combinations, thats roughly 10^43.
Slight correction... The BIP39 wordlist has 2048 words... And the seeds used by Trezor (and Ledger) are 24 words... Providing 256bits of Entropy. The general theory however is correct... The search space is MASSIVE... And effectively not able to be brute forced in anything resembling a "reasonable amount of time" (assuming that the process of seed creation was properly random etc) |
|
|
|
Most likelyDefinitely a scam wallet for a (possibly) scam coin. Given there is no code available for Bitcoin Diamond... I highly doubt anyone has actually coded a wallet for it There is nothing to download there... And the "source code" link just takes you to the generic GitHub homepage... Be VERY wary of this... #youHaveBeenWarned EDIT: As predicted... this is what the OFFICIAL BitcoinDiamond Twitter has to say: https://twitter.com/BitcoinDiamond_/status/935694581324169217ie... it's a scam |
|
|
|
|
Show Posts
