Muhammet Kara: I didn't try it with a pending deploy yet but it seems that non-existent hashes are shown as "Unknown" and as an account hash -> that seems very confusing to me.

So yes, I think this is still relevant and could need some improvement because I've copied a deploy and modified 1 character only and it gets detected as an "Unknown account hash".

This is the original successful Deploy I've checked:

I've changed the last "f" to an "e" - not sure if that is a valid test though.

I did another test:

Testing it with a random wallet it is also just showing 0 balance -> I would expect a message like "Wallet doesn't exist. If it's your wallet make at least 1 transfer to this wallet to see the balance" or something like that because according to my knowledge a wallet which never received any CSPR doesn't exist yet.

Original random wallet:

I've changed the last "1" to a "2".

The "Named Keys" shows an error message for non-existing wallets btw. (see attached screenshot). So if this was done for security and/or against any kind of scraping protection - it failed.

Without testing on my side I would assume the same applies to some other hashes/urefs etc. as well.

Stakepire: when copying and pasting a copied hash, there shouldn't be problem with incorrect hash. I believe not many people type hashes by hand, but if someone does it this way, as in the case of entering a bank account number, he/she must be aware that in the case of a mistake, the result may be different than expected.

In theory wallet, which never received CSPR tokens doesn't exist. If you check raw data for such Public Key or Hash, it will be empty. But in practice, such wallet may have some CEP-18 tokens or some NFTs, here are such examples:

We'd rather not call such wallets non-existing. We also believe, that owners are aware, that if they didn't transfer any CSPR tokens to own accounts, the balance is 0 CSPR. From such users perspective, such account exist: they can sign in to such account, they can receive all kinds of tokens, they cannot of course create deploys, but this is consequence of having no CSPR tokens. The only more important difference is that such account cannot be set as a associated account in CSPR.live.

For the issue with Named Keys, we are aware, that such defect is present. This is a low-impact bug, so its fix was postponed due to the need to remove more important bugs and the need to focus on new features and improvements. However, I understand that for some users the displayed message may be incomprehensible, therefore we will remove this bug in one of the patches for version 1.25.