17:26:48 Arguably the whole point of no_std (not just one overlooked) is embedded hardware compatibility. We are not discussing running thousand row BPs on hardware wallets at this time so that's an irrelevant discussion. 17:26:48 The seeded RNG design would add crates for the discussed deployment and therefore should not be done for monerod. 17:26:49 There are actual discussions on how to properly shrink binary sizes of libs if that's a concern. Chucking no_std at it isn't a great solution. 17:30:08 @SyntheticBird Much better point, though probably for -dev? 17:30:08 Also, per https://github.com/monero-project/monero?tab=readme-ov-file#cross-compiling, Monero only lists riscv64-linux-gnu (not risc-v openbsd). 17:32:28 @SyntheticBird Great question, though probably for -dev? 17:32:28 Also, per https://github.com/monero-project/monero?tab=readme-ov-file#cross-compiling, Monero only lists riscv64-linux-gnu (not risc-v openbsd). 20:47:49 > Arguably the whole point of no_std (not just one overlooked) is embedded hardware compatibility. We are not discussing running thousand row BPs on hardware wallets at this time so that's an irrelevant discussion. 20:47:50 Not necessarily embedded imo, UEFI and Wasm aren't embedded. but still fair to not use no_std 20:47:51 > There are actual discussions on how to properly shrink binary sizes of libs if that's a concern. Chucking no_std at it isn't a great solution. 20:47:52 `build-std` is still a nightly feature but could show itself handy for that purpose in the future 20:47:53 > though probably for -dev? 20:47:54 Ok I move on -dev