If there's one major bug like that, it'll be included in the release notes: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES
I didn't find any, but try to search thoroughly.

It's always been the same as the desktop version and using the standard algorithm Bitcoin uses: ECDSA with Secp256k1 curve.
It'll derive a "compressed" pubKey from WIF with compressed flag (your 'L' prvKey) and create a legacy address from it if a script type isn't appended before the privKey.

---

My assumption is the same as the other first two replies, your address may be derived from the uncompressed public key.
An alternative tool is Ian Coleman's "compression tool":  https://github.com/iancoleman/keycompression
If you're not worried about privacy, you can use the web version, of course, only use your public key.
Otherwise or if the above is true, use an Air Gap machine to get the uncompressed versions of your keys/address.

Is this about unrecoverable passwords of wallet.dat or other wallet files that are already sent to a "company"?
And by saying "company that recycles wallets", you mean any password-recovery services?

If so, then we can never be assured of since those are entirely trust-based.
But if you want assurance that the scenario wont happen, you can select the company with an option to send your wallet file's "hash" instead. (search their options)
In that case, they can try to bruteforce your password without getting access to the actual wallet file.

Can you cross-check the "transaction id" txid on other blockexplorers to see if the transaction is not exclusively in the link that they've gave you.
The TXID is the 64 hex characters that's referencing your transaction.

Some blockexplorers:

• https://blockstream.info/
• https://www.blockchain.com/explorer/api
• https://live.blockcypher.com/

If it's in the three blockexplorers above, chances that it's an issue with cryptospend is very high unless the deposit address is incorrect.

I did a quick Google search and saw that cryptospend has a quite low trust rating in Trustpilot while the other has good standing.
Perhaps you're experiencing one of those issues in the negative reviews; in that case, only their support can help you since it's already sent to them.

Electrum cannot do that by itself, specially in "watching-only" wallets where it cannot even sign transactions to consolidate.
Your watching-only wallet cannot create fully-signed transactions that can be sent to the network.

The thread isn't proceeding with the given information and assumptions, please describe the issue:

• Is your wallet showing the correct balance? (even so, it may be fake if the hardware wallet is fake)
• Did you bought you Coldcard from a reputable distributor?
• Did it came with a pre-generated seed phrase?
• Did those "consolidation" and "privacy" transactions, occur without your intervention?
• Have you sent any other transaction aside from those mentioned two?

With Electrum, your only option is to "Sweep" its private key (Wallet->Private key->Sweep) and Electrum will be able to spend that P2PK unspent txn output.
When sweeping, do not append any script type before the private key (it wont work in uncompressed WIF) and it'll search for P2PK together with P2PKH outputs.
Take note that sweep automatically sends the amount of BTC to the wallet where you've used the menu.

Reference PR: https://github.com/spesmilo/electrum/pull/3125

This post describes the steps on how to export the keys from your Armory and two replies below it has an example import process to Electrum.

Link: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691
The provided images no longer updated since the user is a bit inactive but the post itself should be easy to follow.

And yes, you certainly need Armory to be able to export the keys but you don't need it to be active during import to the wallet of your choice.

I was talking about: config.ini_sample which is copied to config.ini as per the instructions.
My reply is just based off the notes in the commented lines; if it doesn't work then you may have to stick with the working config.

Yeah, so as all wallets that use mnemonic phrase backup, this isn't just a problem with Electrum. (Bitcoin Core doesn't use mnemonic)
All the programmer has to do is to wait for his script to find a hit within the 2048^12 range of word combinations, maybe after 5trillion years.

There are profiles (core developers) who are working on Electrum's development here: https://github.com/orgs/spesmilo/people
But they do not have access to every Electrum user's funds, users' master keys are locally saved in the individual's own drive.
There's source code that you may audit to see if it's really the case: https://github.com/spesmilo/electrum

If this is one of the main motivation for the feature, then you don't have to worry about it because addresses already have a "checksum" that ensures that users wont be able to send to a mistyped address.

It's not 100% reliable since the checksum's size is limited but it does its purpose. (how about 99% reliable?)
For example: A P2PKH address' checksum is 4Bytes in size which has 1 out of 2^32 chance of collision.

Lucky for you, Electrum client is also pure Python.
You can review its source code to see how it communicates with the specified or public Electrum servers.
Most notably, "network.py".

Link to source: https://github.com/spesmilo/electrum/tree/master/electrum

This is the issue, the proposed feature needs a database but Bitcoin do not have a dedicated central database to keep data like those addresses and references.
It's out of the question to save it to each nodes since it'll add unnecessary bloat to the already-growing data that they keep.

If it's something like a plugin, maybe it's possible if it works like PayNym which needs to be integrated with all Bitcoin wallets for your example "signature campaign use-case" to be realistic.

Those "tor_host" and "tor_port" options aren't commented-out by default, is there a reason why you disabled them?
If so, it could be the reason since it explicitly noted that those are required for broadcast_method = tor.

Also, 127.0.0.1 IP already reserved for localhost, although putting duplicate wont cause harm, setting both at the same time is still unnecessary.

What does the "account name" looks like?
For safety and privacy, you can replace every character or a few, but do not change the format.
This is essential to know which wallet it is from.

Those "not website" wallets usually stores the wallet file in the device itself.
But applications that require username and password usually has it in their server.

The beauty of Bitcoin is it's non-custodial, means that there's no custodial service or server who hodls your Bitcoins for you.
With it, no one can recover your bitcoins from a server, even the developers do not have access to anyone's bitcoins.
You need to recover the wallet file or any backup of it.

That's unless your login details are from an exchange, some custodial wallet, or web wallets.
In that case, it depends if the service or owner is still active.

That's only mandatory in importdescriptors command.
But scantxoutset will work regardless of the presence or absence of the checksum as of v25.0

---

Anyways, OP was asking for the "syntax" so most likely, he knows what arguments to include, just how to put them together which he already did in the edit.

Those are certainly from scammers to get your account details to swindle your prize.
You absolutely shouldn't put your email and password in that link which obviously not from freebitco.in.
Also, they will not ask you to deposit any BTC to claim it (did you just logged-in to a fake freebitco.in page?)

If you already did logged in to that scammer's site, PM TheQuin immediately about it so that he wont accidentally send it to them.
Don't rush it, double-check any link you've been receiving and think twice before logging-in.

By posting that "you've won a lambo", you're instantly became a target by hackers, please exercise extreme caution.

-edit-
Here, The Quin has a reply in the official thread: https://bitcointalk.org/index.php?topic=320959.msg63044451#msg63044451

Additionally, to differentiate the two and for others to better understand of the term "encrypt":

• With encryption, the original data can be recreated from the secret and the encrypted data.
• PBKDF2 functions like HMAC, however is a "one-way" function, there's no going back from 'seed' to 'seed phrase'.

It's a pretty close example for the maximum combinations that a 2048 words can do but that images is mostly used to explain the Bitcoin private key range of 256bits.
My post is mostly about the reason for having only 2048 words.

Just two posts above yours.
I think I did a pretty good explanation and example to make 2^11 which represents each word understandable even for beginners.

Was it because of the last possible number is 2047, Yes?
If you count "00000000000" in which is counted, that'll be a total of 2048 words.

Here's the small answer  

Because the entropy (plus checksum) where the mnemonic seed is based from is sorted per 11-bits, each of those 11-bit part corresponds to a word.
Then the reason for "2048" is because that is the limit that an 11-bit number can do, from 00000000000 (0 in decimal) to 11111111111 (2047 in decimal)

If you think that it's the cause of the issue, then try to uninstall the latest updates of your W11 machine.
Refer to this article to see how: support.microsoft.com/en-us/windows/how-to-uninstall-a-windows-update

Then, since you've already downgraded and confirmed that you have the complete blockchain but the issue remains, then we can deduct Bitcoin Core out of the suspects.

Aside from the readily-available in the market,
he may be able to fulfil his "Homemade ASIC" objective by modifying the control board schematics available in the internet.
Of course, he need a qualified (ASIC) computer engineer to do this.

Some of those who still own those old Bitcoin ASICs do exactly that: they use it to mine low-hashrate Altcoins with compatible algo to earn $0+.

ASIC's full name could be the answer to that question: "Application Specific Integrated Circuit".