If you mean with the Kotlin binding, yes. It's possible to implement a custom signer and use it around the code. Otherwise, if you mean from directly from rust, I've started working on a NIP-55 implementation, but it is not ready yet. I haven't even tested it yet. I hope to have something working for the next releases. https://github.com/rust-nostr/nostr/tree/nip55

Good catch, thanks! I'll fix it soon

Reduced to 3 at https://github.com/rust-nostr/nostr/commit/b47962f904679e1ab75e7160982dc905ad10f133

It currently take at max the first 5 relays from the NIP65 list (I thought I had lowered it to 3, I'll decrease it soon). But also taking at max 3, the number of connections may be high. Should I lower it to 2? We've added support for "sleep when idle" for relays (in master branch). I still have to finalize the support in the SDK. With this, the gossip relays (or even all relays) can connect on-demand and sleep when idle. Another plan is to add a persistent storage for gossip data, give a rank/score to relays... but I still not found the best way to do this. Ideas are appreciated :)

, if it helps, here is how I implemented it for the nostr-relay-builder: https://github.com/rust-nostr/nostr/blob/06dd1b6e532a611929278f9374aa4340455f0f54/crates/nostr-relay-builder/src/local/inner.rs#L698

What version are you using? It should be exposed in the last ones: https://github.com/rust-nostr/nostr-sdk-js/blob/v0.42.1/src/client/mod.rs#L558

Thank you 🧡