Electrum actually never adopted BIP39 as their seed generation standards. They merely started support it in the more recent versions. BIP39 won't include any version byte at the start which allows the wallet to determine what addresses to generate so not really ideal for Electrum's usage.

It stores the seeds itself and also signs the transaction on it.

Your funds won't be restored. The private keys are generated from your seed. You can derive the private keys using the seeds alone. As such, you can spend the funds using your private keys.

---

Certain devices has inherent seed extraction vulnerability (Trezor), so if it gets lost/stolen I'll recommend you to transfer your funds to an address generated from a new seed ASAP.

CPFP might not work in every case though, even if you're receiving the change. If the minimum mempool fee is below the fee rates for that specific transaction, it'll be evicted from the mempool and thus making it an orphan transaction. It would probably not have very good propagation though in this case, the best course of action is to just resend the transaction and RBF won't be needed either. Two of the three options are not cancelling the transaction.

Yes. 0x47 and 0x21 defines the size of the data to be pushed. 0x47 is the hex of 71 and 0x48 is the hex of 72, which indicates either a signature with a size of 71 bytes or 72 bytes respectively.

Did you have any previous unclean shutdown or reindex? I've had this problem when I was reindexing and it got stuck at ~70% and just synchronized the header and freezes all the time. Resource constraint was not an issue; problem solved by deleting the entire data directory to synchronize again as I suspected a corruption with the blocks.

Can you check if the height of the headers of your peers and if they're constantly getting disconnected? Debug.log should give you some insight, go to Window>Information and click the open button under the debug log file text.

The salt is not the seed itself. While the BIP seems to indicate that the whole mnemonic is used as a salt again, that is not the case. The salt is only "mnemonic".

Try using this: https://stuff.birkenstab.de/pbkdf2/.

The wallet doesn't become a watch-only if there's no human intervention. Is there any other wallets on the computer that you can open using Electrum from the same directory?

Unless you're able to find either the correct wallet file or the correct seeds, you cannot convert your watch-only into a spendable wallet.

That's a solution but that doesn't address the problem directly. There is a reason why people don't stay logged in all the time and it's perfectly justified.

Topic isn't about forgetting the password but rather about mistyping it which can happen from time to time. Really doesn't need much discussion on this as it's really a non-issue. Don't need further discussion on this, go modify the html elements or use a browser script to do so.

Great, reduce your account security so that you can have a little bit of convenience?

Copying anything on a clipboard is risky to say the least. The stuff on it are often cached either in memory or just easily retrieved. If you frequently log out of your forum account, then I don't think the environment that you're in would allow you to take the risk of having something so sensitive in your clipboard.

Satoshi did have a few references in his whitepaper, notably b-money. B-money was conceptualized in 1998 by WeiDai and apparently was one of the first people whom Satoshi contacted.

I don't think the idea of cryptocurrency or any distributed currency of that sort was very new at all. There were some discussions about this during the 1990s as well, or so I've heard.

Probably not the case.
I update it via a script every 5 minutes, but I'll lower it. Probably wouldn't matter as long as the update interval is somewhat reasonable.

I'll say that your method will have limited effectiveness, if you consider the current situation. Being able to broadcast your transaction entails that the total mempool will be less than 90~100vMB or so depending on overheads. When you're able to broadcast it, it'll probably be when there are only 1 sat/vbyte transactions left in the mempool and all of the others were mined by a miner. This definitely won't happen overnight and even if miners were to mine successive blocks, which is unlikely to be sufficient, there is little chance of your 1 sat/vbyte transaction (currently there is 90vMB+ of transactions paying 2sat/vbyte or more) being confirmed even if it gets relayed. After it gets relayed, if the minmempoolfee increases at the slightest, your 1sat/vbyte transaction would be evicted again and the whole process repeats.

Just to put things into perspective and help you manage your optimism.

Public keys are not technically addresses as addresses are the hash of the public key.

Let's establish some things first for clarity. 1M311YjWBuHbZhLDynBKFCTXosJe7d2Boi did not exist in 2009; Satoshi (or whichever miner who mined that block) did not send the Bitcoins to a Bitcoin address but to a public key. Blockexplorers tend to oversimplify this and associate public keys with the corresponding addresses had it been expressed as an address. You can check it yourself by decoding the raw transaction and see that it is infact a P2PK transaction.

Blockexplorers will associate P2PK transactions to the corresponding addresses and that is fine. But, in the case of Electrum, your query to the server would be your watch-only address which is not a public key. Since Electrum nodes only fetch the transactions related to that script hash (ie. the two transactions shown) as they do not do what blockexplorers usually do, you would only see the transactions that are sent to and from that address, not public key.

No. P2PK is Pay-to-Public-Key which means you're not specifying the outputs as an address but rather an ECDSA public key.

Nope, it's not or perhaps their settings is slightly different.

Both Statoshi and my nodes are indicating it to be slightly more than 1.9sat/vbyte. You can check my node's info for something that indicates the default settings and thus the general node population: http://163.172.57.208/getmempoolinfo.txt.

I would probably expect it to be purged again after the TX volume rises by the mid week, if that happens just broadcast it again. Don't think ~2sat/vbyte has any chance for a confirmation given the current situation.

Electrum doesn't display P2PK transactions, and the earlier coinbase transactions are all P2PK transactions.

When you're importing a watch-only address, Electrum looks for the transactions which is related to you through it's script hash derived from the address. P2PK transactions are thus not related to that scripthash and not shown.

That output is usually displayed after the user runs bitcoind, or at least that's the case for me on Linux distros. It basically outputs the logs that you would see on debug.log onto command line and is usually just it accepting new blocks or peers activity. You can see it by opening the debug.log as a text file that is located in the same directory as the blocks. Default directory for Mac is ~/Library/Application Support/Bitcoin/.
If you want to get the status, try ./bitcoin-cli getblockchaininfo for the synchronization progress.

Don't really think most people actually has that much difficulty when typing passwords? Bitcointalk doesn't usually add the tiny features frequently but it would be fairly easy to do so.

Instead of asking the forum, why don't you just get a tampermonkey script that would toggle the password's visibility?

Institutional adoption is by no means a suitable indicator of mainstream adoption. It just means that its volatility nature allows some riskier firms to venture into crypto. While it isn't very hard to learn the basics of Bitcoin, which by the way would give you quite some insight if you can read the whitepaper, it just doesn't make sense for the general population to use it. There isn't really any viable and widespread real life use as of now and possibly in the near future.

Not really. 2FA only serves to protect the user from external threats and assuming that the site doesn't have any loopholes in terms of social engineering and other vulnerabilities.

Coinbase may seem secure but so did most of the exchanges before they got hacked. They are known to have outrageous policies which allows them to freeze your coins and track your transactions whenever they want. You won't know how secure it is until something happens. Trezor is a hardware wallet which mainly defeats the threats through malware and to an extent physical attacks as well. They are not a cold wallet. I consider hardware wallets to be mostly more secure than web wallets; 2FA can only protect you so much and it doesn't always fare that well against malware in the first place.

Same reason why people urge others to run a local instance of their wallet instead of having to connect to something that can be changed at a whim without any of the user's authorization.
There is[1]. It isn't necessary for the user to use SatoshiLabs' servers, they can run their own and be perfectly fine.

[1] https://wiki.trezor.io/User_manual:Running_a_local_instance_of_Trezor_Wallet_backend_(Blockbook)

Did you select the correct wallet file to open? So you're saying that you've restored the wallet using the seed months ago, left it there and you can't see anything on it now?


Did you create a 2FA wallet in the first place?
Nope, it's fine. Just go to File and New/Restore and select the options to restore your seed.