I think if we have that, it would be beneficial to also change the signature scheme to not require an ambiguous JSON conversion process. That could work, but probably want to prefix them with a byte to make the length different. And some of my software has length assumptions but that is not very hard to fix

Replies (1)

I’m not sure if deriving cryptocurrency keys from an npub is a good idea, better to have an updateable event instead. Also, you need two keys, view and spend, and an npub can give you only one. So you either need to introduce a second one or make them the same If you do the latter, your blockchain node would need the view key = spend key = nsec to scan for TXs