Public key with 0 at beginning can't be handled by Nostr Console

[vishalxl]

If a private key generates a public that has 0's at the beginning, the application does not generate the correct signature or hash, with the result that such accounts can't really work with this application right now.

On sending a kind 1 post, this account's event will be invalid and will be rejected by relays.

On creating an encrypted room by such account, the application crashes.

An example private/public key pair is is c39a51b254c6d0ee022083c271afb4bba3e9ac8b004b7577200f31d6f44d96ef / 000006ed14c0337a42e434cf926252bc77b8788b58d78e8be43f416a43ea771a

originally reported by Sabah.

[vishalxl]

related issue in dart 340 library

[vishalxl]

With recent commit, it does not crash. It can read its inbox or dm sent to it, but can't send dm.

Astral can send a dm using this account. This account on console can read that dm. but it still can't send a dm.

problem is likely in dart340 package's sign() function. It seems to be creating wrong signature.

[vishalxl]

Same status as above with release 0.1.5-beta.