I've published the patch, make sure to use universal-time v0.3.1

I've found the issue, I'll publish the patch soon

Yes, in no_std or WASM you have to define a time provider. You can find an example here: https://github.com/shadowylab/universal-time#with-no_std-or-wasm-unknown The example just set a fake time, in your app you can get the real one using instant or webtime.

It should be fixed here: https://github.com/nostrdevkit/nostr/pull/1400

A security update is available for anyone using NIP-44 in the NostrDevKit (formerly rust-nostr) libraries. Please update to v0.44.5 or, if you’re on the pre-release, to v0.45.0-alpha.5 https://github.com/nostrdevkit/nostr/security/advisories/GHSA-hrqp-8w79-gwgw #nostrdevkit #rustnostr #rust

Thanks, I'll fix this in the next few days

It supports WASM, are you compiling it from macOS? https://github.com/nostrdevkit/nostr/tree/master/crates/nostr#wasm32-unknown-unknown

We've removed it (getrandom + wasm_js feature) because in some context was causing issues (wasm32-unknown-unknown used outside JS). You can solve the issue by adding the getrandom dep in your Cargo.toml, and enable the wasm_js feature. Make sure to do it for the right getrandom version(s), which can be found in the Cargo.lock