Nostr Notifications¶

Nostr notifications provide the highest level of privacy, delivering encrypted direct messages to your Nostr identity.

What is Nostr?¶

Nostr (Notes and Other Stuff Transmitted by Relays) is a decentralized protocol for social networking. It uses public-key cryptography for identity and message encryption.

Key Concepts: - npub - Your public key (identity) - nsec - Your private key (keep secret!) - Relays - Servers that store and forward messages - DMs - Encrypted direct messages between users

Setup¶

Prerequisites¶

You need: - A Nostr public key (npub) - A Nostr client to receive DMs - Configured relays

Adding Nostr Channel¶

Go to Settings → Notifications → Add Channel
Select Nostr
Enter your npub
Select encryption method (NIP-04 or NIP-17)
Click Save

Encryption Methods¶

Method	Description	Compatibility
NIP-04	Original DM encryption	Wide support
NIP-17	Gift-wrapped DMs, better privacy	Newer clients

Recommendation: Use NIP-04 for maximum compatibility, NIP-17 for maximum privacy.

How It Works¶

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Vigil     │────▶│   Nostr     │────▶│    Your     │
│   Server    │     │   Relays    │     │   Client    │
└─────────────┘     └─────────────┘     └─────────────┘
                          │
                          ▼
                    Encrypted DM
                    (only you can read)

Vigil creates a notification message
Message is encrypted to your npub
Encrypted message sent to Nostr relays
Your client fetches and decrypts the message

Notification Format¶

NIP-04 DM Example¶

From: Vigil Notifications (npub1vigil...)
To: You (npub1your...)

🔔 Deposit Detected

Wallet: My Cold Storage
Amount: +0.05 BTC
Address: bc1qxyz...
Status: Unconfirmed

TX: abc123...
https://mempool.space/tx/abc123...

NIP-17 Gift-Wrapped¶

NIP-17 messages appear the same to you but have additional privacy: - Message timestamps are hidden - Reduced metadata exposure compared to traditional DMs - Better metadata protection

Vigil's Nostr Identity¶

Vigil sends from: - npub: npub1vigil... (full key in app) - Relays: Multiple public relays

Add Vigil's npub to your contacts for easy identification.

Relay Configuration¶

Vigil delivers DMs via a set of Nostr relays. Relay availability can change over time, so if you’re not receiving messages:

Make sure your client is connected to commonly-used public relays
Try a different client that supports the protocol you selected (NIP-04 or NIP-17)

Nostr Clients¶

Recommended Clients¶

Platform	Client	Notes
iOS	Damus	Full-featured, NIP-04 support
Android	Amethyst	Good DM support
Web	Snort, Iris	Browser-based
Desktop	Gossip	Privacy-focused

Client Configuration¶

Ensure your client: - Has your nsec configured - Is connected to relays Vigil sends to - Has DM notifications enabled

Privacy Benefits¶

vs. Email¶

Aspect	Email	Nostr
Identity	Email address	Pseudonymous npub
Encryption	TLS to server	End-to-end
Provider access	Can read emails	Cannot read DMs
Metadata	Visible to provider	Minimal (especially NIP-17)

What Vigil Knows¶

Your npub (public)
That we sent you a notification

What Relay Operators Know (NIP-04)¶

Vigil's npub sent a message
Your npub received a message
Message timestamp

What Relay Operators Know (NIP-17)¶

A message was sent
(Sender/recipient hidden)
(Timestamp hidden)

Troubleshooting¶

Not Receiving DMs¶

Check relay overlap
Ensure your client uses relays Vigil sends to
Or configure custom relays in Vigil
Check client DM settings
Ensure DMs from unknown contacts are visible
Some clients filter unknown senders
Verify npub is correct
Double-check the npub in settings
npubs start with npub1
Send a test
Go to Nostr channel settings
Click the Test button
Check your client

Message Decryption Issues¶

Ensure your nsec is correctly configured in your client
Try a different Nostr client
Check that the client supports the encryption method you selected

Delayed Messages¶

Nostr messages may be delayed if: - Relays are slow or offline - Your client isn't connected - Network issues

Messages are stored on relays and delivered when your client connects.

Security Considerations¶

Protect Your nsec¶

Your nsec (private key) is like your seed phrase: - Never share it - Store it securely - Use a dedicated key for notifications if paranoid

npub is Public¶

Your npub is safe to share—it's like a Bitcoin address: - Anyone can send you messages - Does not reveal your identity (unless you link it)

Back to: Notification Channels →