Have been secretly building an initial Trusted Relay Assertions implemention based on @Vitor Pamplona NIP-85...this is still probably a month away from an alpha public release, but starting to take shape. You can read more on Nostrhub:

NostrHub

NostrHub | Discover and Publish NIPs

Explore official NIPs and publish your own custom NIPs on NostrHub.

When Bitcoin podcasts quit talking about price, I'll start listening.

Yesssss View quoted note →

NIP-49 implementation is complete (import/migrate/export), should be out in a day or two after I work through some edge cases Coming in the next few weeks: event database encryption (maybe SQLCipher?), migration to websockets, and a new device pairing mechanism. We're going to make nsec bunkers fucking awesome this year.

Good thing I don't earn fist anymore View quoted note →

Anyone can build a Signet client and I hope we see more. View quoted note →

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 😎

Spent a couple days in the wilds of Wyoming (beautiful by the way), but I'm back and ready to knock some shit out. LFG.

Did some additional work on Signet today to continue to improve memory allocation. This is a daemon only update. I'll be gone until Thursday so any issues, please file a bug report on Github.

GitHub

signet/CHANGELOG.md at main · Letdown2491/signet

Signet is a self-hosted NIP-46 compliant remote signer for Nostr. This project is an extensive rewrite of nsecbunkerd. Companion app for Android av...

What a beautiful day! View quoted note →

Cryptic note that will make sense in a week... LOG_N RAM (mb) Time Relative 16 64mb 100ms 1x 17 128mb 200ms 2x 18 256mb 400ms 4x 19 512mb 800ms 8x 20 1gb 1.6s 16x 21 2gb 3.2s 32x

Signet 1.6.1 pushed to @Zapstore to fix an issue with biometric unlock.

App Details - Zapstore

Just submitted a follow up bugfix release to Signet to fix a memory leak in AdminCommandService and SSE event handlers. If you didn't use the DM commands, you could probably skip this update, but the SSE changes are worth the upgrade, even if it's just a couple new lines of code.