What if your remote signer could tell you if a relay connection is trustworthy? What if any client could? Soon TM 😎

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 — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

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 😎

I'm a huge fan of NIP-85 Trusted Assertions and WoT. Would love to have a system in place to establish trusted relays as well due to my work on remote signers, but NIP-85 does not handle this. While the below could really just be an extension of that NIP, here's a stab at it. Comments are welcome, it could use some tweaking for sure.

NostrHub — Build Nostr Together

NostrHub is where the developer community collaborates on building the Nostr protocol — discover, draft, and discuss NIPs together.

Tagging the maestro @Vitor Pamplona

Signet 1.5.0 will be out tomorrow rounding out full NIP-46 support with the addition of NostrConnect...NIP-55 in the planning stage for 1.6.0. LFG.

GitHub

ENHANCEMENT PROJECT: Add NIP-55 Android Signer support · Issue #32 · Letdown2491/signet

Implement NIP-55 support so Signet Android can act as a signer for other Android Nostr apps via Android Intents as per the NIP-55 spec. Architectur...

Wow this is a huge update! View quoted note →

Test post