ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Geektoshi61d 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 @775954f7โ€ฆ79c57a80 can add some NIP-49 info to their newsletter in the mean time ๐Ÿ˜Ž
๐Ÿ’ฌ 14 replies

Replies (14)

Logen61d ago
This is definitely over my head. But it didnโ€™t stop me from making a standalone Mac version of Signet today! https://github.com/btcforplebs/Signet/releases/tag/0.0.1
0000 sats
Geektoshi61d ago
Beat me to it but glad you did this! I'll be starting work on iOS after 1.7.0 ๐Ÿ˜Ž
0000 sats
Logen61d 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 ๐Ÿ‘Š
0000 sats
Geektoshi61d 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 ๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚
0000 sats
Logen60d ago
I have never built an iOS app either, might just FAFO ๐Ÿ˜…
0000 sats
Geektoshi60d ago
Only thing is you can't publish without paying apple their tax lol
0000 sats
Logen60d ago
Does Altstore sideloading still work?
0000 sats
Geektoshi61d 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.
0000 sats
Geektoshi60d ago
No clue. Honestly of rather pay apple their $99
0000 sats
Logen60d ago
Somehow, my Apple ID is already in a developer plan and I donโ€™t pay $99 ๐Ÿ˜ˆ๏ฟผ
0000 sats
Logen60d ago
I just got an iOS version working with Xcode ๐Ÿ‘€
0000 sats
Geektoshi60d ago
That was fast lol
0000 sats
Logen60d ago
I surprised myself to be honest
0000 sats
Geektoshi60d ago
Now I feel like I need to check mine lol
0000 sats