US is not known to do things like this. In fact they are mostly pushing away hashrate, not just with taxes but also with laws that are damaging to the reputation and the earning potential of any miner who is going to mine inside US.
The Office of Foreign Assets Control has been going as far as forcing US miners to censor transactions!

That's because $59k is not important, the $60k is. Similar to $53k not being important (support) but $50k is.
The day traders are also still pretty busy pump and dumping shitcoins so they are remaining in the altcoin market for the time being and won't jump back for $59k. They are waiting until the newbies run out of money in altcoin market then dump and come back or for bitcoin to break $60k to dump and run back.

They don't have to publicly announce it and it is not that hard to figure out.
If a centralized business such as a mining pool is operating inside a certain jurisdiction that demands a license then you can simply look at the terms in that license and know what that business is doing.

The malicious site would have created a key that is known by the owner of the website and any coins that you had sent to that address would have been stolen by the time it was created. So if they are untouched until today, there is a good chance that they are safe; however, I wouldn't take any risks if I were you, I'd simply create a new paper wallet the "correct way" and move the coins to the new one.

What you have to keep in mind is that mempool is not a global/shared pool. It is an individual memory that each node has regardless of other nodes. The 14 day (or whatever else) limit is also that individual node's settings not a global setting.
If your node receives transaction A on May 1 you'll drop it on May 15 but if my node comes online on May 4 and receives that transaction I'll drop it on May 18. That means transaction A will remain in my mempool for 4 more days and if during those days any node that doesn't have this tx connects to me and asks for my mempool I'll give transaction A back to them and they'll end up with it in their mempool again.
So technically transactions that are valid will never actually disappear and will always remain out there on bitcoin's network among some nodes.

Armory is not a standalone full node, it is a wallet written on top of bitcoin core.

You could but the odds are not the same at all.
Think of it as a lottery, if you buy one ticket you only have 1 chance and your odds are low. If you buy 10, 10000, ... then you increase your odds.
Considering the fact that mining is not a competition for find only one block, but it is a competition to find every block every day of every month in every year the long duration makes it so that the odds of finding the block is proportional to the amount of hashrate you have compared to total hashrate.

This is actually saying "thanks for supporting our reason" not "cause" which makes no sense. Someone used google translate to turn an English phrase to Farsi and pushed it there which is funny
I wonder if the Department of Treasury is going to look into their business or maybe we see a million dollar fine for sanction violations lol. It would be funnier if their business went under because of mining this block and a good lesson for other centralized entities in bitcoin world who bend the knee so easily.

Their stock dropped another $1.25 (3.8%) in the past 24 hours. Maybe bitcoiners should start shorting their stock on NASDAQ to teach them a lesson? Their volume is definitely low enough to be able to crash it from $31 to $0.1 easily in a day or two.

There is nothing recent about the (small) popularity of bitcoin and the attention they are giving bitcoin.

There is no difference between the attitude of any of these governments towards bitcoin, all US, UK, China, Russia and even to some extent India are the same when it comes to bitcoin. They aren't banning it but they don't like it either.

You do realize that KYC is in direct contradiction with mixing, right? That means none of them have anything remotely related to AML/KYC otherwise they wouldn't be called a mixer!

With that logic banking system must be shut down yesterday since criminals have been using them to launder their money for decades.

Anything centralized can and will be shut down eventually as long as they don't bend to the stupid law and more importantly not pay taxes. That is why more decentralized way of doing everything is being introduced. Such as bitcoin instead of using corrupt banks, DEX instead of CEX, decentralized marketplace instead of centralized, decentralized mixing (eg.  coinjoin) instead of centralized ones,...

Brute forcing is already meaningless because the entropy size is big enough to make it impossible. Adding a very small step on top of it can not be considered a security measure. Also if we assume that the seed phrase is leaked, it is safe to assume that the extra words are also leaked.
Also saying one impossible thing is easier than another impossible thing is like saying going to Uranus is easier than going to Neptune! Or in this case not even Neptune but only one of Uranus's close by satellites.

You can derive child keys from an extended public key as long as the derivation path is not hardened which yours isn't (m/0/2). So just enter the zprv in "BIP32 Root Key" field and then from "Derivation Path" select the "BIP32" tab and enter your derivation path in "BIP32 Derivation Path" textbox. You'll get the addresses and the first one is: 16K7HfL33irnJtQrKDqYp5rphhG5LrG8hS
If you want native SegWit addresses (since you have a zpub) then choose "BIP141" tab and switch the "Script Semantics" to P2WPKH and enter your path and you'll get this first address: bc1q8fz464z359mef4qykpyl4axauemacqzs0fjpfz

Transaction history of any address is already visible to everyone who has access to the blockchain, which is basically anyone who runs a full node or can open a block explorer website. Receiving dust spam doesn't change that.

The way dust attack works is that it forces the wallet receiving the dust in lets say address A to have to mix address A with another address like B to be able to spend the dust output received in A which effectively links A and B and invades the privacy of the owner of that wallet.

If address A and B are already linked or you don't care about your privacy then you have nothing to worry about apart from the possible increased fee you'll have to pay to include that dust output in your next transaction. The solution is to freeze that output so that the wallet doesn't spend it ever and always use coin control features that your wallet offers (or use a wallet that does) to manually select or check all outputs being spent.

You mean shitcoins can pump.
That's normal and the altcoin market has always been behaving like this for as long as I have been around. Each time bitcoin is stuck in a sideways action (that is going from $57k to $53k and back up to $57k again) the day traders move their funds to the shitcoin market and start pump and dumping them to increase their capital while bitcoin is getting ready for the next leg up.
That is why as soon as bitcoin breaks $60k the streets will be painted by altcoin bloods.

A mining pool that censors transactions is going to shoot itself in the foot. Miners will never connect to such a pool when there are other pools that aren't so "malicious" and aren't attacking bitcoin.
This will always be true since if a pool turns malicious new ones would be created to absorb the migrating mining power.
If you want to see "shooting in the foot" just look at their stock price (Marathon Digital Holdings) that has been dumping over the past month and got dumped about 10% after they mined this block.

What "bull market" are you talking about?

Bitcoin bull market is just getting started and will probably continue into 2022.
The altcoins on the other hand don't have bull markets, they have pumps and many of their pumps are already over as they enter their dumping phase and some of the bigger altcoins that always have smaller pumps last longer but they too will soon enter their dumping phase.

You should note that this is not a master key, it is a child extended key at depth 1.
That means if you want the addresses derived from the BIP-39 mnemonic at m/0/2 you first have to know what the path of the master public key was because any key you derive from this zpub will be at m/?/0/2 where you don't know what ? is.
Otherwise do what @SquirrelJulietGarden suggested, enter your zpub in Ian Coleman tool and switch to BIP32 tab at the bottom to modify the derivation path to m/0/2 and see the derived addresses.

I believe OP was under the impression that the seed phrase the wallet create is shared with Electrum servers! which is obviously not true.

The extra words do not provide any meaningful security to your wallet.
And the odds of finding a collision is already high due to the big size of the entropy used to generate the seed phrase and is not really improved by adding extra words.

Yours is more like a selected paranoia. You appear to be paranoid about some things and not others. For example how are you paranoid about software wallets calling them scams and not an offline python tool that converts your randomly dice generated private key to public key and address? You definitely can't do that conversion by hand and can't write the code yourself. Heck why trust python or even your computer?

That's correct but it is not about "forgetting", Satoshi may have intentionally avoided adding that transaction to the UTXO database because the genesis block (i.e. block 0) was technically "premined" before the client was released a couple of days later whereas block 1 was mined after release.

You could maybe ask an exchange owner to release such statistics although they may refuse because the real unadulterated results may be bad for their business since newbies may see the disaster others are in specially in altcoin trading and stop losing their money in trading which would result in drop in that exchange's volume and revenue.
But in any case the exchange is the only one that can correctly answer this question because they have access to history of all their users and they can write a small and simple code that analyzes their database and releases the final results (net loss versus net profit one average for all users) and do that all in a way that privacy of nobody is invaded.

Am I understanding this correctly that the Email itself doesn't contain the malware but a command that when executed through Excel(?) downloads the actual malware from the internet (paste.ee?), right?
In that case wouldn't this be mitigated by your firewall blocking the Excel access to the internet altogether and by default?