Can we tie his library in somehow, with the build structure nostr:npub1ecdlntvjzexlyfale2egzvvncc8tgqsaxkl5hw7xlgjv2cxs705s9qs735 just made?
nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl thanks for the tag!
nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 I saw this repo a week or so ago, and starred it so I could find it easily later.
One of the next features I intend to add on NostrSDK is a built-in signer. Right now, I've stubbed out an interface for the sake of testing, but it doesn't actually sign anything. I think noscrypt will be a perfect fit for doing the heavy lifting of signing events. Keeping it all in C/C++ land and using only common and lightweight libraries is exactly what I'm trying to do with NostrSDK.
As an aside, I'm curious how you're setting up noscrypt to work with C#. I want to do something similar for NostrSDK–that is, make it interoperable with other languages/frameworks, so we can support more than just C/C++ devs.
Discussion
It would be tied in automatically if we make it a dependency of NostrSDK.
I'm currently working on pulling dependencies into the CMake build directly, so hopefully it will be easier to incorporate into other builds instead of using the build "scripts" I set up previously.
Definitely. This is a C library, and the structure I set in place is highly modular so it allows the insertion of any C dependencies with minimal friction. It could be as simple as adding a line in the manifest.