Well found. I also just rebroadcast it on blockchair.com, and it is showing up there currently.

Having a quick look at the parents, the issue with this transaction is the same as the other one. Although this transaction pays 151 sats/vbyte, I've found an unconfirmed parent with 907 inputs, which is 82,292 vbytes and only pays a fee of 3 sats/vbyte.

Whoever is making these transactions has picked a very bad time to try to consolidate their inputs.

These rebroadcasting services can only rebroadcast a transaction from its transaction ID if they have the transaction in their mempool already. From searching for his second transaction, I cannot find it in any mempool. If he wants to broadcast it, he'll need a copy of of full transaction. You cannot broadcast a transaction from scratch using just the transaction ID.

This is by no means unique to cex.io. Pretty much every crypto exchange in existence has problems with poor customer support. It is particularly bad at the moment due to the bull run, increased volume which means increased problems and issues, and them having to process thousands of new accounts. This is what you have to put up with when you use any centralized exchange which takes custody of your coins.

All you can do now then is to wait. In the meantime, download an open source 2FA app which allows full encrypted back ups so this doesn't happen again.

SMS is a very insecure method of 2FA and should be avoided where possible.

Yeah, you are kind of stuck with the one due to the huge size of the unconfirmed parents. To boost the entire fee up to somewhere in the region of 40-50 sats/vbyte, you would need to do a CPFP and pay a total fee of around 1,500,000 sats, or 0.015 BTC. And as with nc50lc, that assumes no unconfirmed parents higher up. Realistically, you are just going to have to wait for the mempool to empty for this to be confirmed.

If you have a copy of the second transaction then you can rebroadcast it. If not, you'll need to ask the sender to rebroadcast it.

Please stop just making up things you want to be true without presenting any evidence.

US stats:
17% of those who died aged under 65 had no underlying health conditions.

UK stats: https://www.ons.gov.uk/aboutus/transparencyandgovernance/freedomofinformationfoi/covid19deathswithnounderlyingconditionsbyageband
Attention drawn to table 6a.
Of 542 deaths in age range 0-44, 101 (18.6%) had no underlying health conditions.
Of 457 deaths in age range 45-49, 91 (19.9%) had no underlying health conditions.
Of 847 deaths in age range 50-54, 123 (14.5%) had no underlying health conditions.

Yes, older people and those with comorbidities have a higher risk of death from COVID (and I never claimed otherwise), but young people are dying, healthy people are dying, and young healthy people are dying.

You cannot import a private key in to a hardware wallet. Doing so would negate the entire point of the hardware wallet.

Hardware wallets are designed to create and store you keys in a secure environment. The keys are created inside the hardware wallet, stored inside the hardware wallet, and never exposed to your computer or the internet, which therefore removes the most likely attack surface to having your keys (and therefore your coins) stolen. If you create a private key on a computer yourself, then it has already been exposed to this attack surface. Later importing it in to a hardware wallet doesn't suddenly scrub all traces of it from the computer you created it on, or scrub any traces of it that may have leaked to the internet. The hardware wallet may be able to keep your key safe, but that doesn't really matter if an attacker already has another copy of it.

For that reason, you cannot import private keys in to a hardware wallet. If you want to use a hardware wallet, you must create a new wallet on it from scratch, and then transfer funds to it from your Bitcoin Core wallet.

US stats: https://www.cdc.gov/nchs/nvss/vsrr/covid_weekly/index.htm#Comorbidities
6% of deaths had no underlying health conditions.

UK stats: https://www.ons.gov.uk/aboutus/transparencyandgovernance/freedomofinformationfoi/covid19deathswithandwithoutpreexistingconditions
8.9% of deaths had no underlying health conditions.

Because the study you quoted proves my point.

Jet Cash said "Natural immunity has 100% success". I said "COVID reinfections do happen". You then linked a study which shows reinfections happening. Not sure what I'm supposed to respond to. It's a small number, yes, but reinfections do happen.

So you have managed to recover four private keys from your back up, but your screenshot shows 5 addresses?

The only possibilities then are that there is a fifth private key which you have, for some reason, failed to back up properly, or perhaps you generated more than one address from a single private key. I know the Schildbach wallet gives you the option to generate both legacy and segwit addresses now, but I'm not sure what its behavior was back in 2013 or what address types it supported then. In your screenshot of addresses, are all the addresses of the same type (i.e. they all begin with the same character - "1" or "3"), or is there a mix?

Provided you only edit that field then you should be safe. Be aware that editing something critical could corrupt your wallet file and render it useless unless you can figure out how to revert the changes you made. I would always make a back up of your wallet file first, and also make sure you have your seed phrase backed up safely before attempting to edit your wallet file.

If you cannot remember your second password, then BitMaxz is correct in saying your only remaining option is to attempt to brute-force the second password. I assume you will have tried everything you think it could be, variations of your primary password, every password you used around the time of setting up the wallet, etc.

To use btcrecover, make sure you download the up-to-date fork from here (https://github.com/3rdIteration/btcrecover), since the original program ceased development over 3 years ago.

There are also more tutorial regarding using btcrecover for a blockchain.com secondary password at the following links:
https://btcrecover.readthedocs.io/en/latest/Usage_Examples/2020-05-08_Recovering_Blockchain_Wallet_Passwords/Example_Recovering_Blockchain_Wallet_Passwords/
https://www.youtube.com/watch?v=eS0VUl3w69Y

Your password is either going to have to be short enough to be brute forced, or you are going to have to have some idea of what it is. If you set a long and complex password, then brute forcing it from scratch may be impossible.

I understand what you mean, but for the sake of explaining it to newbies, that's not the best way of phrasing it. No wallet just picks some numbers and presto - that's the address. The wallet may pick some random numbers at the start of the process as an entropy source, but the process of turning the entropy in to a seed, the seed in to a private key, the private key in to the public key, and the public key in to an address is very specific and reproducible.

To expand on the answers above - you can create as many addresses as you want. If you want a billion bitcoin addresses, then you can create a billion addresses. I mean, there's no point in doing this and all it would do is probably crash your wallet if you create them all at once, but you could if you wanted. Any bitcoin present at one address will remain at that address until it is transacted. Anything that happens with any other address is irrelevant.

Try reaching out on social media. Unfortunately a lot of exchanges have very poor customer support, and only actually address problems when there is the threat of negative publicity for them.

You can Tweet at them @cex_io: https://twitter.com/cex_io
You can post in their subreddit here: https://www.reddit.com/r/cex_io/
You can message their account on Reddit here: https://www.reddit.com/user/CEX_IO

There are a few posts from that last account I linked saying that their Support Team is overloaded with requests (aren't they always?), and so any response will take some time.

Coinbase and other big exchanges have an unknown number of hot wallets and an unknown number of cold wallets, each with an unknown number of addresses in them. Only a small number of their wallets are publicly known about, and they will be generating new wallets and new addresses all the time to accommodate new customers and new deposits.

It is entirely possible that the address you used for Coinbase back in 2016 was part of one wallet "cluster", was consolidated with other deposits to this cluster, and was used to process withdrawals from this cluster, while OP used an address in another "cluster", and the two clusters never mixed.

I'm sure some of the big blockchain analysis companies could analyze this transaction some more and discover whether or not it really did end up on Coinbase (or perhaps someone with a lot of time on their hands), but the quickest option for OP is simply to contact Coinbase, state they made a deposit to the address 1Q6Boa9VQxxcCCNDKK1dennXSud1m5ALAc, and ask why it was never credited to their account.

bitaddress.org does not accept 12 word seed phrases in the normal sense. If you entered them as a brain wallet, then it has simple hashed those words and produced a private key and address from the hash. You will not be able to import those words in to another wallet and recover the same private key.

If you have the private key printed on the paper wallet, then that is what you will need to use. Follow Maus0728's link above to download and verify Electrum, import the private key to an Electrum wallet, and then send the funds to your Coinbase exchange account to be sold.

Note that the Coinbase Wallet App and the Coinbase Exchange are two completely separate platforms. If you send the coins to the wallet app you will not be able to sell them on the exchange. Make sure you transfer them to your exchange account.

They still make most of their profits in bitcoin from trading fees, withdrawal fees, etc., and they charge a flat bitcoin rate for these things. If they take in 0.01 BTC in fees from a trade, then it makes a huge difference to their profits in USD if bitcoin is valued at $50,000 or at $5,000. Sure, there will be increased volume in the short term, but they could still realistically be concerned about a prolonged bear market lasting a few years due to the sudden influx of 1 million coins back in to active circulation and the panic among newbies that would create.

Coinbase don't really care much about the illegality of manipulating the market. They illegally manipulated the market during their launch of support for BCash, insider traded, and caused their customers to lose a lot of money for their own benefit. But they investigated themselves and found they did nothing wrong, so it's all forgotten about now.

Healthy != immortal. Healthy people are dying from COVID.

I don't blindly trust anyone. I read the trials. This is the exact opposite. People on here who say "Listen to what this expert says" - that is asking you to blindly trust the opinion of one person. Reading a trial with millions of participants is not blindly trusting anything. It is verifying.

It absolutely does not.

And I've told the families of healthy people in their 20s and 30s over the phone that their loved one is going to die and they are not allowed to visit. Small individual samples are not indicative of the wider situation.

The vaccine does not change your DNA. There is no way it even could change your DNA without rewriting everything we know about cell biology.

Nothing in life is ever going to be 100%, vaccines included, so every unvaccinated person does indeed pose a risk.

That is the whole point. A simple face mask is not designed to protect the wearer, but to protect others.

You are probably right. I suppose it comes down to who is buying Coinbase stock, and therefore who would be holding stock which they could panic sell at the news of "Satoshi Revealed!!1!1"

People who actually understand bitcoin and the necessity of a signed message are far more likely to buy bitcoin, whereas I suspect there will be a lot of traditional investors who see Coinbase stock as a kind of surrogate for exposure to bitcoin itself. There are obviously bitcoin ETFs that also serve this purpose, but perhaps Coinbase will be seen as a kind of hedged asset, less prone to the big price fluctuations we see with bitcoin and bitcoin ETFs. You are probably right that these people will react to whatever hits mainstream news as opposed to what is actually going on, and we know from the last 10 years that mainstream news gets it wrong on bitcoin with a frequency approaching 100%.

Still, at the end of the day, if some Faketoshi causes Coinbase to lose a bunch of money, you won't see any tears from me.

Possibly, but I don't think anyone would be able to convince the majority of users without being able to sign a message, which leads us back to my point above.

That idea has literally never crossed my mind before. The reason I attack imposters and fraudsters who claim to be Satoshi with zero proof or evidence is because they are criminals, identity thieves, scammers, and are trying to trick people in to thinking they are Satoshi for their own benefit. I'm sure most others think the same.

This is an automated reply. Your case will never have been looked at by an actual person. Contact them again. Try reaching out on Twitter or their Reddit channel. Get a real person to take a look.

There is no need to send coins to your Coinbase wallet first, or indeed to even have a Coinbase wallet at all. Your transaction was definitely not sent to your Coinbase wallet based on the subsequent consolidation transaction the coins were included in.

By all accounts, you made a successful transaction, and it ended up on an address which is certainly in keeping with an address belonging to an exchange. Did you have any other exchange accounts you were using at the time?

The coins you sent were quickly moved on, so it certainly wasn't an inactive address. Looking at the onward transaction, your coins were combined with coins in dozens of other addresses and consolidated in to one single address. This is the kind of transaction we see from an exchange or service consolidating deposits from many different customers in to one address. This would certainly be in keeping with a deposit to Coinbase, but also to any other exchange. It is not really in keeping with a transfer to another individual person.

Zero chance, unless you know who owns this address. There is no way to "contact" an address.

I'm afraid so.

Your best bet is probably to contact Coinbase, explain the above, and ask them to check if the address you deposited to belongs to them.