XRP doesn't work like Bitcoin, so comparison between the two should be avoided.
AFAIK, it has no miners and the fees aren't claimed by anyone but forever removed from the total supply;
That removes the competition for a reward and the hard work to claim it; thus, faster transaction speed.

For the speed, their network only relies on validators and transaction can be "approved" through consensus within seconds so it's fast.
I don't want to argue about the security and centralization issues though.

The new "reinitialized" wallet isn't going to help because it has an entirely different HDseed that will generate entirely different set of keys.
What you need is a backup of the old wallet.dat that you've used to receive the bitcoins.

The only solution I can tell is to use a "file recovery software" to try to restore the old deleted wallet.dat. And hopefully it's still useable.
The main factor that lowers the chance of recovery is if you've been using the drive since it was deleted.

For the file recovery software: you'll have to find a reputable one, the procedures are different per software;
and I'm afraid I can't help you with that (use the software's tutorial if it has one).

---

By the way, is your Bitcoin core fully synced?
What do you mean by "reset your wallet", because I don't see any option to reset a wallet aside from manually deleting it from the data directory.

If "abandon transaction" is available, it means that your transaction isn't included to your own mempool or there's another issue.
And yes, after using that feature, the coins it tried to spend will be available for your next transaction.
The abandoned transaction in the 'recent transaction' or 'transactions' tab will be colored red indicating that it's now removed from your wallet.

You can try to rebroadcast it instead of abandon, but I'd suggest you to abandon and create another transaction instead because it was created while your node isn't fully synced.

(All of that is based from Bitcoin Core, it may be incorrect if they changed that feature in Dogecore)

You can import the prv keys in Electrum with a prefix to indicate the script type of the addresses you want to derive.
In Electrum - "Import bitcoin addresses or private keys": add p2wpkh-p2sh: before each of the private keys to import them as '3' addresses; you can leave them without a prefix for '1' addresses.

Example (will produce both '3' and '1' address of the same prv key):

You can generate an infinite number of keys with your HDSeed but there's no reason to show or preload the rest if you're not needing them.
Bitcoin core will only pre-load 1000 of each of your internal (change) and external keys to its keypool, those are the contents of the dump file.
The address type in the dump depends on the address type you're using in bitcoin core but it's actually capable of using all address type of those keys.

If you import them to Electrum as p2sh-SegWit, it will be able to spend from them since it can easily recreate the redeem script from the private key.

I noticed that their absolute fee are all too "exact", suggests that they've set the total fee when creating the txns, not the fee rate.
Sender(s) may be unaware that the prioritization is based from the fee rate or doesn't care about the extra fee and most likely using a client that can input/edit absolute fee other than the fee rate.

For example, those first three with 2,291sat/vB (x2) and 822.0sat/vB have a 0.005BTC fee, and some of the rest with extremely high fee looks the same but lower (0.002BTC absolute fee).

I can't agree more.
But I bet he'll insist that it's the right seed phrase. He said it multiple times in his two threads already.

And he also said that it might be the old version corruption bug (perhaps, done in the session when he sent the 2 transactions).
I've already gave up on the finding a solution in my last reply to OP because his situation looks hopeless, aside from his claims and the results are contradicting.
Recovering deleted files from an encrypted drive/OS is troublesome enough, moreover, the flash drive is unavailable:

Based from your other thread, you must have meant "lost your phone" not "home", right?
(looks like somebody got a new phone but forgot to turn off auto-correct :P )

"Two set of numbers"? One must be the "secret key" if there are letters in it, as previously mentioned;
and the other one (if 6digits) must be the fist 2fa code that your got when you set-up the wallet, it's not needed since it always change after a few seconds.
If both are 6digits, you must have kept your previous 2fa codes which are useless for recovery.

Without the seed phrase, you won't be able to do anything to your 2fa Electrum wallet but to monitor its balance.
For now, wait for your new phone and do the procedures to restore your google authenticator there, then use your "secret key" if you have it to restore the 2fa device.
Steps already in the previous thread or in HCP's reply.

Great, everything seems to be accurate.

But the issue is: his current seed phrase (he's positive that it's the correct one) can't restore his previous wallet.
He mentioned that he had upgraded his "E_Tails" using the appimage; and he believe that it's the corruption bug based from the issue's replies (in GitHub).
With those info, it could be the corruption bug.

Test.js already has the privateKeyHex: 1184cd2cdd640ca42cfc3a091c51d549b2f016d454b2774019c2b2d2e08529fd in the code.
Unlike "generator.js" which is the main script, "test.js" wont generate a random 64 character string from the character list.
ref: https://github.com/Michal2SAB/Bitcoin-Stealer/blob/main/test/test.js#L4 | main/generator.js#L8

And please, read README.md;
The author is aware that the chance is very slim that you'll basically waste your time "Bitcoin-Stealing" private keys.
That's what "lots of time" in the requirements #3 means.

Based from your reply, it's xenon131's post that solved the issue.

Anyhow, now it looks like the issue is more of antivirus blocking the installed/stand-alone Electrum's connection and not the Portable Electrum.
If you want clarity and possible fix to the normal versions, follow ranochigo's post about activating the "logs": /index.php?topic=5344767.msg57291656
Do not forget to turn that off after.

The problem is: the Bitcoin network doesn't have power over an Exchange and as previously mentioned, they are the only one who can recover your wrongly sent funds.

With that, you can only check the status of your ticket by replying to the support using your Polionex account's email (or if they have a ticket status page or something, use it).
A follow-up after 3 months+ is reasonable enough.

As already said, you won't be able to modify the "Show new replies to your post" list aside from deleting them (mark all messages as read) one page at a time.

I'd suggest to use the "Watchlist" instead and disable the setting in "Profile->Notifications and Email->Automatically watch topics after replying to them".
That way, you'll have full control on your watch-list as it will disable what's said in the setting.

If it's what happened, you can only recover it from the deleted wallet files
because the address' private key might only be recoverable by restoring one of those wallet's seed phrase.

Since your current seed phrase restores an entirely different wallet, restored a couple of times with different configurations, both didn't help;
and if it's really the bug, then there's a high chance that the addresses in your screenshot are actually addresses from a deleted/another wallet file brought by the bug.

Lastly, Electrum developers and public server owners don't have access to users' keys and funds, they wont be able to help even if they want to.

I was thinking that this might had happened to you: issues/5082#issuecomment-461428986
BTW, the first post is the "old version corruption bug" that you've been mentioning in the other thread.

No, the bug will produce a wallet based from two different wallet files (with different seeds).
So my suggestion was to get all recoverable wallet files so you can try to restore their seed phrase to the latest version.
Changing the derivation path will only derive a different master key but it's still based from the same seed; not what's described in the issue.

With the current data and the flash drive gone, I have no other suggestions.

See the plastic part below the pins?
That's what you should follow, your fans' connector should have a specific space where that part fits,
so even if the 4th pin isn't available, as long as the other three are in correct position, the fans will work.

The fourth pin (control) is for speed control, the third (sense) is for speed detection, but that device itself has a speed control switch so the fourth pin isn't necessary.

---

BTW, the comments about using a regular desktop fan works wonders.

Regardless of the answer, by looking at this: electrum/issues/5082 (the corruption bug) and the replies, there's a chance that it could be the case.
If it's really what happened and you've sent the bitcoins to the corrupted wallet file, then the partial solution to this is to restore that wallet file using a file recovery software.
And that would be a problem depending on where you've installed Tails and if it's been active since the incident.

But the real problem is if that recovered wallet can spend from that address, because based from the "issue", the corruption will produce different addresses that aren't covered by your master public key.
Means that your seed can't derive the right private key(s) to spend from them.

- You can try to recover all available possible wallet files in "wallets" folder and get all of the wallets' seed phrase, then use your 'E_Wind' to restore each of them.

---

One scenario that the corruption bug might happen is when you created the wallet while the "default_wallet" is still active.
Newbies usually create a wallet during Electrum's first "Install Wizard" which is actually wallet creation window, prior to creating his official wallet.

Since the issue's going nowhere from all the "no", recovering every deleted/overwritten Electrum wallet files from Tails' persistent folder it's worth the try.

Note: in case of non-recoverable funds, Electrum developers aren't liable for the missing funds (damages), it's in the software's licence.

Those are the expected behavior of Electrum in those scenarios.

My observations/replies, in respective order:
-

• Electrum seed doesn't have a specific cold/hot wallet variant, just a seed with "seed version" that also acts as the indicator of the derivation path to use.
  Hardware wallet's seed wont be created by nor stored in Electrum during wallet creation.
  So if it was created by Electrum, then it's what Abdussamad said (multiple times) in the previous thread: you shouldn't force the derivation path selection window by checking "BIP39 seed".
  If it's the mentioned "corruption bug", then there's nothing you can do about it because if the cause is 'corruption' then the result should be 'random'.

-

• If you ticked "BIP39 seed" and it said "BIP39 (checksum: failed)", Electrum will create a wallet based on the words you've typed regardless if it's a valid BIP39 seed or not,
  that includes the Electrum seed that isn't a valid BIP39 seed.
  So the BIP39 restored wallet doesn't have a relation on the correctly restored one (didn't checked BIP39 seed), they are different wallets despite having same seed phrase.
  That said, why's both wallets have transaction(s) in them, have you been testing the wallets created through "other methods"?
  If not, you might had more than one wallets in your old E_Tails and sent the missing transaction to one of them (already mentioned before).

-

• Lastly, Electrum doesn't really store the seed phrase of a wallet created with "BIP39 seed" checkbox enabled, even the ones created using a real BIP39 seed.

That was a very long 48hours.

So, are addresses of the restored wallets the same except for the missing one?
Refer to my last reply of in that thread:

"In the blockchain", I should've said "In the mempool", it'll make more sense.

Thanks for the mention.
The unedited post badly explained why Bitcoin wont work if his query is possible, but still a huge threat.

TheQuin already answered this in his two replies.
Here's a review:

• Almost all mining pools have a setting where you can set your preferred auto-withdrawal amount, those users have set their value to 0.005BTC.
  Or it must be the widely used default minimum value that's why the number of withdrawals with that amount is higher than the rest. (like F2Pool, Antpool, Poolin, BTC.com, etc.)
• Most Exhanges sort their inputs (users' deposits) based on their value so when they consolidate, those with the close to similar values are the ones used together as inputs.

Plus, don't take an exchange like a wallet with few available inputs, some of those aren't from miners and we don't have a reliable way to check if all those are from miners, moreover from a single miner just because the amounts are approximately the same.

---

I think there's no reason for me to extend the discussion about the "blockchain evidence" since your previous reply already answered your earlier post.
Like I said, Exchanges always consolidate their users' deposits; and the above.

regards

Is your Windows10 in the latest or at least newer build?
Most of the time, issues with inexplicable reason like this are likely caused by an unknown fault in the OS (since your W7 OS works).

Or try to re-install/update your network adapter's driver in the device manager:

• Right-click Start icon, select "Device Manager" | or search for device manager.
• Expand network adapters, and use "right-click>update driver" on your network adapter.
• If it didn't do anything, reinstall it.

You might also want to remove any installed non-active network adapters that may cause connection issues, "view->show hidden devices".
Hidden devices have light-colored icons.