[UX PROBLEM] - payments to unregistered public keys are confusing users.

[TruthMachine]

There is an issue with sending to a public key from the payments tab. If you input a Bitcoin public key and send payment, the address sent to does not correspond to the public key. You can input a private key on bitaddress and then extract the compressed or uncompressed public key and send coins to it in the BSV desktop wallet, but the coins will go to a completely different address than the one associated with the public/private key on bitaddress. I tested this after a user notified me about losing funds on the wallet, and I confirmed it is indeed an issue.

[sirdeggen]

These funds are not lost. The payments feature uses unique addresses per output. This is a design choice recommended by Satoshi. Identities are firewalled from the public transactions.

You can obtain the funds by using the private key in question (hex, not wif) to login to BSV-Desktop using the latest version which allows self managed private keys.

Login with that privkey then configure message box client to use https://messagebox.babbage.systems (most likely to have been, really you must use the message box of the sending party).

Then check for incoming payments and use internalize action. Again, funds are not lost they're just in a message box waiting to be picked up by whoever has that private key.