Geektoshi's avatar
Geektoshi geek@primal.net 2 months ago
Starting work on Signet 1.7.0 today which will introduce NIP-49 support (ncryptsec). AES-GCM encryption will still be available and existing keys can be easily migrated with a single key press, but NIP-49 (XChaCha20-Poly1305) will be the recommended option moving forward. AES-GCM will be deprecated in the 2.x.x series but that is months away so plenty of time to migrate. It will also add key exporting (plain nsec and ncryptsec). Signet will default to LOG_N=16 for the time being but will provide user configuration in a future release if you want stronger encryption. The NIP-49 spec allows up to LOG_N=21 but the memory requirements are higher than most users will want to spend (64mb to decrypt LOG_N=16, 3.2gb to decrypt LOG_N=21) for a signer. This is probably above most people's heads but I'll do a long form article sometime near release, but there's plenty of documentation around on NIP-49 and its encryption choices. Maybe the good folks at @Nostr Compass can add some NIP-49 info to their newsletter in the mean time 😎

Replies (14)

Logen's avatar
Logen logen@btcforplebs.com 2 months ago
I’ve never actually built a Mac application, this is my first, and it was a doozy! I should also mention I didn’t write a single line of this code. οΏΌ100% written with Google Antigravity. I’m sure what you make is going to be FAR better πŸ‘Š
2 replies ↓
Geektoshi's avatar
Geektoshi geek@primal.net 2 months ago
Honestly, I'd rather working on the backend and have the web UI just be the reference client implementation. The Android client was important though, and iOS will have some challenges (thanks Apple) but to let people play. I do my best to implement new stuff in a way that doesn't break clients that don't update as quickly as the backend so its pretty simple to just make of your own. Just have to make sure I keep the API docs up to date πŸ˜‚πŸ˜‚πŸ˜‚
1 replies ↓
Geektoshi's avatar
Geektoshi geek@primal.net 2 months ago
I will warn you, I am considering moving to websocket communication to allow device pairing but I should be able to do it in a way that doesn't impact clients much.
↑