Trying to create a eBay listing automation workflow for my dad using Google Lens & Gemini (based on his preference) which involves using their API keys
and came across this for the first time. What the f?
I worked on the NIP spec last night and just uploaded the updated version - let me know what you think of it & also left you a technical question that needed clarification
I think your npub-derivation approach is the most trust-minimized implementation of the other iterations, but there’s still some work to do on client-side guidance
But for now, the foundation of NSW seems promising
The question is the derivation method. Your diagram shows BIP32. The NIP draft uses BIP340 tagged hashes: scan_privkey = int(tagged_hash(“nostr-sp/scan”, sk)) mod n. Same tag strings, different operation, different output keys.
Which does your code actually use? If it’s BIP32 I can align the NIP to match.
Hey Tim — I've been working on a NIP draft for private on-chain zaps using Silent Payments and your OpenETR work is directly relevant.
Quick technical question before I open the PR: your diagram shows BIP32 derivation for nostr-sp/scan and nostr-sp/spend — is that what your code actually uses, or tagged hashes under the hood? The answer affects interoperability between OpenETR and the NIP.