Compatibility with Wasm

[jamesray1]

Just flagging this in case it hasn't been raised: golang/go#18892. It's important to keep track of compatibility with Wasm as Rust and C++ are both compatible, while Go isn't, so Parity and cppethereum seem likely to become faster than Go-Ethereum when they run Wasm.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fjl]

I don't fully understand the purpose of this issue. Go can compile to WASM, and WASM code can be run from a Go program by executing a virtual machine. Ergo, Go and WASM are compatible.

[goldbock]

@fjl that's indeed the way it should work except that go-ethereum seems to use several libraries that are not compatible with wasm. Please consider reopening this issue.

I've been using go-ethereum successfully for a while but the whole compatibility fall apart when I've tried to use the signer/core package as it has dependencies on libraries [0] that use mmap and other low level file locking systems even if I don't use any feature that needs that kind of locking(i.e. I just need to use core.TypedData struct)

See for example this #23972

[0] github.com/prometheus/tsdb/fileutil
github.com/edsrzf/mmap-go
github.com/syndtr/goleveldb