We can't use the exact same monero package on the web as we can on desktop and mobile platforms: instead of ffi, we must use eg.wasm_ffi. This will likely require changes tp and possibly an alternative to native_toolchain_rust--we may have to build Rust manually, for example (and that might be a good shortcut to a quick proof of concept). I think if the tasks below are feasible that they'll be a quick path towards targetting web/WASM:
[ ] Target wasm32-unknown-emscripten in monero-rust (will this require a monero-web crate?).
We can't use the exact same
monero
package on the web as we can on desktop and mobile platforms: instead offfi
, we must use eg.wasm_ffi
. This will likely require changes tp and possibly an alternative tonative_toolchain_rust
--we may have to build Rust manually, for example (and that might be a good shortcut to a quick proof of concept). I think if the tasks below are feasible that they'll be a quick path towards targetting web/WASM:wasm32-unknown-emscripten
inmonero-rust
(will this require amonero-web
crate?).native_toolchain_rust
. See https://github.com/irondash/native_toolchain_rust/issues/23 .ffi
use withwasm_ffi
.