Dan Gould

replaced by #692

Not in all targets, but in web targets (wasm32-unknown-unknown?) the browser has a way to get the time. We can use an optional web-time dependency to get this https://docs.rs/web-time/latest/web_time/

I think for Node.js we couldd target wasm32-wasi instead of wasm32-unknown-unknown, which has access to std::time, and otherwise when wasm32-unknown-unknown. I think web-time handles this. They show some CI tests...

Don't worry too much about ReactNative. It's interesting but very much not a bottleneck in the way of our forward progress the way other changes are.

Yeah unclear to me if this is sufficient or if it'll throw an error because of `NewReceiver::new`'s signature. If we have a Proof of Concept I'm convinced to move forward...

My point is that this approach is ok now but is a step backwards in terms of ergonomics. My comment was based on the misinterpretation that `new_with_time` accepted a u64...

Not Bull Bitcoin exchange, Bull Bitcoin non-custodial Mobile wallet https://play.google.com/store/apps/details?id=com.bullbitcoin.mobile&hl=en-US (which requires no KYC)

Because this needs a rebase, I don't think a little delay to get this to be actually reproducible is the worst thing in the world. Makes sense to figure out...

From @nothingmuch > tl;dr requirements.txt is like cargo toml > > poetry and now uv make something like cargo lock possible > > poetry has kinda fallen out of favor...

I think you've got a pretty good sense of what's missing and what to document. Our requirements are far similar to [bitcoin's own CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md) rather than bitcoin.org, which does not...