Thanks for the zaps! Itās a fun project to be honest, but has its challenges š¤£ but being able to sign and decrypt nostr notes on the go from any app that implements the NSD without the app ever needing to know the private key will be amazing.
Pushed a new EXPERIMENTAL build to my NAD repo if anyone wants to give it a go. It now supports NIP-44 and BLE.
The main experimental bit is the batching as part of the BLE implementation to support larger payloads over GATT. I did consider pivoting to L2CAP to get around it, but want to ensure compatibility with libraries so doing it at application layer.
https://github.com/cr0bar/nostr-signing-device
Iāve also updated my NIP PR to take this requirement into account.
NSD repoā¦ not NAD š©
Pushed a new EXPERIMENTAL build to my NAD repo if anyone wants to give it a go. It now supports NIP-44 and BLE.
The main experimental bit is the batching as part of the BLE implementation to support larger payloads over GATT. I did consider pivoting to L2CAP to get around it, but want to ensure compatibility with libraries so doing it at application layer.
https://github.com/cr0bar/nostr-signing-device
Iāve also updated my NIP PR to take this requirement into account.
I should have done thisā¦ ended up coding for about 2 hours, trying to troubleshoot why my new code wasnāt working, only to realise that the code base Iād started working on this evening, had a bugā¦ the new code probably wasnāt even faulty to start withā¦
Lesson learnedā¦ donāt code when tired. š© nostr:note1kwtwgy2xhpeh65y9kdmu95x049p74n2x87afmsfk84yl8kymfuhqm0lzse
Iām not going to do any coding tonight, just an evening with my feet up I think āŗļø
I go for headphones on, ignore important stuff for other people, work on important stuff to me.
Im assuming thatās my issue anyway. All other gift wrapped notes Iāve received decrypt fine, itās just my dev key which Iāve used for secret chat between my primary and dev key which donāt decrypt. Assuming itās using one of the aliased keys.
Yeah, itās not in with the other approved nips, but it is listed on 0xChat covering key aliases used for āsecret chatā.
Found the issue, had nothing to do with NIP-44 and everything to do with NIP-101ā¦ š© nostr:note13ujz9agyyqjfsclgxjeajp6fwjr69fcklsec6wfvmfpmuyyta4wsdtq0z7
Can someone send me a message on 0xChat please using my npub. Thanks š #asknostr
Wonder if thatās what confusing it. Looks like I may have been trying to decrypt the optional one. Looked at others sent to me from other people and they fully decrypt as expected.
Does anyone understand how kind 13 works? Iāve captured a message sent to myself on 0xChat, kind 1059. I then decrypted the content using NIP-44 and the pubkey on the note. The result is a kind 13.
Iāve the attempted to perform the same NIP-44 decryption steps for the content of the kind 13 using the pubkey in the note, but decryption fails.
Burnt a few hours on this. Any ideas? Tried with multiple message and get the same issue. #asknostr #nostrdev
Nevermind, it works now šš nostr:note102apcspz746g75ngzpc7supyaknpz0f6l00pem9vyu5fhluqz8wqqt379q
Been looking to add NIP-44 to the NSD as it already supports NIP-04. Not sure if Iāve just overloaded by brain with BLE recently, but I canāt get my head around NIP-44ā¦
The code Iāve written seems fine (it encrypts and decrypts its own data), but wonāt decrypt a note I sent from another npub to myself via 0xChatā¦ š¤·āāļø
Check out this PR that implements support for the T-Display-S3. This build doesnāt implement BLE, but Iāll be raising that PR next. https://github.com/lnbits/nostr-signing-device/pull/20
Imagine losing the private key for the 100+ š¤£
It holds your nostr private keys and allows you to sign notes and encrypt/decrypt them from a client which only has the public key. The current version only supports over USB but this build does it over BLE too.
The chip though only has 1mb flash and 512kb ram so it would be hard to implement.
Not sure the BLE rings would have enough program memory to hold the library required to sign it unfortunately. But you can have a separate device like the LilyGo T-Display-S3 that holds your private key so your apps donāt need it or ever see it.
Raised š #nostrdev https://github.com/nostr-protocol/nips/pull/1706
To raise a PR the NIP needs a number right? How does the numbering work, pick the next free or raise with a place holder and itās allocated one? š¤
Does this look like a good starter for 10? š¤ Iāve never written a NIP before used others for inspirationā¦ https://github.com/cr0bar/nips/blob/patch-1/XX.md #nostrdev nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1c878wu04lfqcl5avfy3p5x83ndpvedaxv0dg7pxthakq3jqdyzcs2n8avm nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Easiest option is just pick up a LilyGo T-Display-S3 (the one with 2 buttons, not the touch version) from AliExpress or anywhere you can get cheap electronics from, and keep an eye on my feed for when my next PR is merged š
Once testing is done.. I might have to add functionality to #damus ā¦ š¤ nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:nevent1qqsvj4pdrmgq8zgelvk5w3jdpkx9rp4699mqhsrxhwj0h522l509k5qppamhxue69uhh5cts9emkzarrdq6szexs
Still work in progress #nostrdev #nostr #nsd 
Itās friday!
First successful tests this evening signing a note from my laptop using the NSD plugged into a USB charger at the other side of the room. Tomorrow, write an iOS app to do the same thing as the code on the laptop. šš nostr:note1w9ktxwq6jkmwur6y3cc4vae4al7dyf55mwu54h8ktukezswaezpqq9fw5m
