Is "Use trampoline routing (disable gossip)" setting in Electrum enabled?
It can be found in "Tools->Preferences->'Lightning' tab" of the GUI or the "use_gossip": true, line of the config file.

If that's enabled, you wont be able to connect to any lightning nodes other than the (currently) 3 hardcoded Electrum trampoline nodes.

What do you mean by this? From p2pk then set it as p2sh?

In the paragraphs below it, it seems like you meant "...and set a p2sh change address". Is it?

How about an actual test? (Amounts down by 2 decimal points 'cause I don't have enough testnet coins)

Done in "testnet":
Here's the coins (UTXO), I've also added a 0.0004 amount.


When sending 0.0009 BTC @1sat/vB, it will select "0.0006" and "0.0004" since those are the best candidates to fulfill the will-be-sent amount and the fee.
Pretty much your number 2 algorithm.


But as you can see in the replies above and the overwhelming "coinchooser.py" code of Electrum, it's much more complicated that your list.

The reply above is if you want to check the balance before exporting the keys to another wallet.
I already told you in my reply in the first page the steps; it can be claimed as long as the script type is supported by BitcoinSV.

Here's some test (mainnet - p2pkh):

Electrum wallet's seed:


First and second address:

• 1274LZxnj7JmB49sHVaWo3givqpqeLUH9T
• 1DV9jegjr6BGE8KLrSM1bPHnt262DH2gw1

Restore to ElectrumSV:

1st address:


First address and the rest are the same as in Electrum so there should be a balance if you have a fork coin.

Must be talking about your original Electrum wallet where your BTC were stored;
if it's deleted, you can restore it from seed, cross-check the transaction history and address list, then find a way to get their balances in different chains.
eg.: using blockexplorers.

---

Alternatively, you can create a "watching only" wallet in Electrum clones or other Altcoin wallets to check the balances.
For example/guide:

• Get and copy your master public key from (BTC) Electrum menu: "Wallet->Information"
• Open ElectrumSV and create a new wallet, name it "watching only".
• Click "Add Account->Import from text" and paste your master public key in the next window.
• After the rest of the set-up, the balance should show-up after syncing (few minutes).
• Addresses with balance is listed in the 'Keys' tab: "View->Show keys" (double-click to display the address/key; your watching only wallet will only display 'public keys').

The watch-only wallet set-up should be similar with other Electrum clones or other wallets, the important step is the export/import of the master public key.

(You wont find Electrum users here in the Altcoin board, BTW)

Your screenshots show that your wallets aren't "HD" (Hierarchical Deterministic)
so if you ever made too many transactions after the first backup (used all addresses up to the last key in the keystore), it will contain outdated list of addresses.
Loyce's reply is true except your new addresses wont differ with a password change, it will only happen the first time you encrypted the wallet.

AFAIK, they had been recommending to frequently backup your wallet.dat file back when Bitcoin Core's wallet isn't HD.
That may be the reason why you got multiple copies of the same wallet.

Congrats BTW.

The root of the problem you had with Bitcoin Core is the "pruning" setting which avoids you to swap wallet.dat files entirely.
Plus replacing the file without shutting down Core will result with that seemingly successful (but improper) import of wallet.dat.

Electrum on the other hand is an "SPV" (Simplified Payment Verification) wallet which doesn't rely on a local copy of the blockchain.
Your wallet will only connect to the public servers for balance checking,
so you can add keys and get the correct balance without waiting for days/hours nor will encounter the same issue.

The error that you got from your "separate thread" isn't about the fee rate.
If it's a default fee issue, it should be broadcast without issue but could only stay unconfirmed until it was mined,
your transaction wasn't sent to the mempools at all.

I made a new reply to that thread and I think the main issue is your way of "replacing" the wallet.dat file so I've posted the "don'ts" of doing it.

Open the 'Addresses' tab of the "receiving one" ("View->Show addresses" to enable the tab).
Then use 'search' (CTRL+F) and paste the receiving address to see if it will appear in the address list.
If not, you've sent it somewhere else.
If it's there, the wallet may not be properly connected to a server.

If you play with the archived link of blockhain(dot)info from August 2014,
you'll see that after typing characters in the 'password', the "password strength" will only show the vulnerabilities of the current password
until you've used all character types (lowercase, uppercase, number, punctuation marks).
The constant thing is, it's recommending to use at least 10 characters.

In the latest version, it's the same rules as you mentioned.
So it's definitely not the same as 2014.

Archive:

• August 2014: https://web.archive.org/web/20140803203344/https://blockchain.info/wallet/new
• December 2021: https://web.archive.org/web/20211213225645/https://login.blockchain.com/#/signup

If this is only to find out how many characters you've used to your password, then you'll encounter worse roadblocks afterwards like explained by the reply above.

Just what I expected, for some reason that transaction is trying to spend an invalid input.
It could mean that one or all of your wallet's input(s) is already spent or not available in the blockchain.
It could be all/few of the '?' transactions are actually valid but Bitcoin Core still haven't scanned them.

Next,
If you didn't changed any setting including the first launch set-up, then your Bitcoin Core must be pruned,
yet you just replaced the wallet.dat and not opened them using the menu "File->Open Wallet".
That may have caused the wallet to keep the old status and not properly scanned.
In order for things to go smoothly, you'll need to disable pruning to be able to scan/rescan those wallets.

Double-check if prune is enabled in the settings: "Settings->Options...->Prune block storage to"
If it's 'checked', your blockchain is set to prune and you can't just replace wallet files.

To be able to load different wallet files at all times, I'd suggest you to disable it (that will require you to re-sync from scratch and lots of free disk space).
After that, you can now swap, open wallet.dat files whenever you want.
But do not just replace the wallet.dat while Bitcoin Core is running, please use the 'open wallet' menu.

---

But if your Bitcoin Core isn't pruned (the prune setting is unchecked),
try to use rescanblockchain in the console while the correct wallet is selected in the drop-down menu of the console.
That will take a few hours to complete and after that, the correct transactions should appear and marked checked in the 'Transactions' tab.

I think the underlying issue is, your transactions failed to broadcast due to some invalid input(s) or other reasons why a transaction can get rejected by the default relay settings.

And you haven't responded to my previous replies about 'test to manually broadcast the newly created "not in mempool" transaction to your mempool':

The "raw transaction" that you need to copy is the recently created "not in mempool" transaction.
I'd recommend testmempoolaccept this time.
The error message should be the best indicator of the issue.

BTW, none of your screenshots show the sync status (the check at the lower-right corner of Bitcoin Core).
The wallet may not be scanned correctly and those "send transactions" may reappear after a rescan.

(I've made some edits to your image)
Looks like only those four inbound transactions are successfully verified, the others had issues (indicated by the '?' logo).
If those are all invalid, then your final balance will be 0.5 BTC.

You can try to abandon those invalid transactions before creating a new transaction but make sure that the wallet was scanned properly when you loaded it.
Or else, it might try to spend a already spent input(s), and also to display to correct balance and transactions.

Make sure that your wallet has a backup before doing this:

• Use "Right-click->Abandon Transaction" to those boxed transactions.
• Then make a new transaction.

I see that you've moved this specific question from your other topic into its own thread.
I already got an answer in that thread, I'll quote it here if you missed it:

---

Why do you have to calculate and research just to send a transaction with "necessary transaction fee"?
Your wallet already got that covered so you don't have to go to web for statistics and calculate in order to find the optimal fee.
Amongst the options, I'd suggest you to use "mempool" and use 1~0.5mb from tip (displayed when you hover-over the slider).
Personally, my technique is: Open the 'Advanced' tab, set the fee rate slider to '1mb from tip', then edit the absolute fee by a few satoshi higher so it'll be just below the tip.

Overall, no can can really estimate if the next block will be mined quickly after you broadcast the transaction,
the mempools can grow in size during that time making your "optimal fee rate" drop out of the priority.

There shouldn't be a reason to make their web and IOS versions different from each other,
besides their latest smartphone version and web version are basically the same.
With that said, they still recommended 10-characters as the "strong password" in Aug2014.

If you want to check it firsthand, their old IOS wallet's source code is still available: https://github.com/blockchain/unused-My-Wallet-iPhone/releases/tag/v2.0.5
Sadly, there's no ready-to-install binary.

Yes, if it's an Electrum seed (not BIP39), the script type should be included in the seed so it's as simple as that.

For the other forks like Bitcoin Gold and others, I haven't tried them but I heard that most of the Electrum forks are inactive so you might need to move them individually via private key Export/Import.
Procedures depend on the wallet but I haven't tested neither of the other forks.

If you do not want to use the 'advanced' feature, you can select another slider option in the drop-down menu of the 'send' dialogue box:
From 'ETA', 'mempool' and 'static';

• ETA: the default with most accurate estimate (but most of the time over-estimates)
• mempool: for advanced users who can understand how mempool works; usually, it's "1~0.5 MB from tip" as the 'express' fee rate.
• static: the basic slider with pre-configured values from 1~300sat/vByte.

The absolute fee is displayed above as "Mining fee", but the prioritization is based from the "fee rate" (slider).

Not quite, the addresses' highlight colors wont change since the green and yellow ones are derived from different derivation paths.

As said by others, after receiving bitcoins, it will stay in your Electrum's "green line" address where it was sent.
The "yellow line" addresses will only be used exclusively for change.

It's actually as simple as that, in ElectrumSV, it has to be added as an "account" after creating a wallet.
In your newly created wallet, you just have to click "Add Account", select "Import from text (....)", then type your Electrum seed phrase.
It will be automatically detected (as long as the address type is supported by their network).
You can do it straightforward or conservative (air-gap, etc.) depending on the crypto amount left in that seed phrase.

For the "trust issues", the wallet is also open-source, so you can audit it (or someone else qualified).

The "funding transaction" isn't even available in the blockchain: 963e417c937bbd97d4e66ad3127f8168f24a4bf38cdaefc427c96922c2e5795d
I'm thinking that it may be an invalid channel in the first place, may be created in the wallet but the funding transaction was dropped from the mempools later on.

I got the funding transaction from your screenshot in GitHub.

Since it's their "Buy Bitcoin" service, there's no better way to solve this but to contact their support since that part of their wallet is custodial.
Means, they are the only one who can do something about it.

BTW, this should be posted in "Service Discussion->Web Wallets" board, I'll just ask a Mod to move this thread there.