Signing messages inconsistent between read-only and standard wallets

[esot321c]

A standard wallet signature appends the source URL to the message, whereas the read-only wallet does not do this. If you are verifying that the message was created by a specific domain, it will throw an error when the user uses a read-only wallet, however there is no way to verify a read-only wallet is being used, so the URL feature cannot be used to verify signed messages.