Wow, Tron: Ares is ROUGH

when you have to wait a week for the next @Nostr Compass newsletter...

Initial Signet security audit going well. Found a couple issues high priority issues but nothing I would consider critical. Once I address the issues, I expect a 25%-50% improvement in memory and resource allocation so things should be even snappier, and of course, a bit more secure. The biggest failing in my book though is that when I upgraded key encryption from what nsecbunkerd was doing, I only upgraded from AES-256-CBS to AES-256-GCM. It's a definite improvement, but I will migrate to the NIP-49 XChaCha20-Poly1305 standard at some point since I'm a fan of strict spec compliance an it really is a much simpler algorithm. Once I get there, there will be no need for user interaction, I'll probably just do it on the backend on first key unlock and let users know the migration is happening. With that said, I expect Signet 1.5.1 to be out sometime tomorrow :-)

If this is you, I made a thing

GitHub

GitHub - Letdown2491/herald: A Nostr bot to auto post kind 1 notes for a selected npub with additional support for creating notes to post project git commits.

A Nostr bot to auto post kind 1 notes for a selected npub with additional support for creating notes to post project git commits. - Letdown2491/herald

View quoted note →

Its true. I invite all devs to come join the anti nsec tribe View quoted note →

And yet, people still pasting nsecs into clients because "normies"...Vitor with the truth bomb. IYKYK