📦 Signet commit
Added NostrConnect support. Implemented new inactivity lock to autolock keys and autosuspend app permissions after user defined period. Additional work on connection health monitoring. Updated documentation.
11b890e
https://github.com/Letdown2491/signet/commit/11b890e5010c430d174a5f9b48320ec87ea034b3
Nostr is automation-friendly. Events are just JSON, signing is straightforward with libraries, and relay connections are standard WebSockets. This means bots are easy to build, including scheduled posts, automated responses, data aggregation, and cross-posting. If you can script it, you can automate it on Nostr.
Signet supports automation through its CLI. Import a key, sign events programmatically, and integrate into pipelines. Remote signing is especially useful for automation. Your automation scripts request signatures from Signet, and you can set auto-approve policies for routine automated actions.
The protocol doesn't distinguish human posts from automated ones. Use this power responsibly.
📦 Signet commit
Added admin event logging to track key lock/unlock, app suspend/resume, etc. Improved pool tracking to prevent stale SSE connections from not restarting during long sleep/wake cycles. Replaced relays widget with system status widget. Added option kill switch to send daemon commands via NIP-04 and NIP-17 DMs from user-defined admin npub. Updated documentation.
a0deae7
https://github.com/Letdown2491/signet/commit/a0deae76709ea7bf947563bf818f056023d5104e
Nostr keys come in two formats: hex and bech32.
Hex is the raw format: 64 characters using 0-9 and a-f. This is what the cryptography actually uses. Bech32 is the human-readable format that starts with npub for public keys and nsec for private keys, and includes a checksum to catch typos. An npub1abc... is the same key as a 64-character hex string, just encoded differently.
Use bech32 when sharing or storing keys since the prefix makes it obvious what you're looking at and the checksum prevents errors. Use hex when interfacing with low-level tools or libraries that expect it. Most apps accept both, and Signet accepts both.
📦 Signet commit
Improvement bunker URI workflow with QR codes and expiring secrets; improved permission approval process; ability to lock/unlock keys and suspend app permissions with additional time-based suspension.
5227ca5
https://github.com/Letdown2491/signet/commit/5227ca51881c53d51cba4f89eb28f701e0ffbf01
Spam is a challenge for Nostr. Anyone can create a keypair and anyone can post. Low barrier to entry means spammers can create endless accounts.
Defenses exist. Proof of work raises the cost of bulk posting. Paid relays filter out casual spam. Web of trust can prioritize content from people your follows follow. Clients can implement spam filters, with some hiding posts from accounts with no followers and some using reputation systems.
No solution is perfect, and spam is an ongoing arms race. But the decentralized architecture means different relays can try different approaches, and what works will spread. Your personal defense: mute aggressively and use relays with good policies.
📦 Signet commit
Brought web UI and Android app UI closer in line. Fixed approval/denial bug in Recents widget. Additional UI tweaks and bug fixes.
e32d1c8
https://github.com/Letdown2491/signet/commit/e32d1c8bc143d5b7db6dc9344cdd1faaf59183e0
📦 Signet commit
Fixed an issue that prevented the Android app from detecting version number.
ee0b3d1
https://github.com/Letdown2491/signet/commit/ee0b3d105cd8684fcc04f25f70fde69043ee36f7
📦 Signet commit
Update http-proxy to fix DoS CVE, added QR codes to each IP the daemon detects for easier Android app setup, labeled Tailscale IPs as such for differentiation, updated build scripts and Dockerfiles to eliminate build warnings and daemon inconsistencies.
6693383
https://github.com/Letdown2491/signet/commit/66933837e1a482df88185c06e7089c6e858cda7b
Nostr Connect is another term for NIP-46 remote signing. You might see "Connect with Nostr" buttons on apps, and this usually means NIP-46. The app wants to connect to your signer.
The flow is to scan a QR code or paste a bunker URL, approve the connection, and the app now uses your signer for signatures. Different implementations have quirks, with some using nostr+walletconnect:// URIs and some using bunker://. The underlying protocol is the same.
If something calls itself "Nostr Connect," it's probably NIP-46 compatible. Check the docs if you're unsure. With Signet, you should be able to connect.
Android app has been updated to version 1.1.1
📦 Signet commit
Added QR code to daemon for non-Docker instances which can be scanned via the Android app to set up a new server. Additionally, fixed several compilation issues that could cause issues when running signet-ui via pnpm.
7a0cf23
https://github.com/Letdown2491/signet/commit/7a0cf23fee3277d234af0cee42c4015db6ebfe6c