You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, we only have one implementation of the Io trait in the Light Client, which makes use of the tendermint-rpc to fetch light blocks (over HTTP/WebSocket).
To be able to support a full WASM build of the Light Client, we need to implement a fetch API-compatible version of the Io trait.
What's the definition of "done" for this issue?
When we can compile the tendermint-light-client crate to WASM and make use of its full API (including networking) from JavaScript.
The text was updated successfully, but these errors were encountered:
Hey @thanethomson, I'd like to work on that. I was previous working on adding wasm support for tendermint-rpc (as it was specified in the previous issue). Was there any reason behind moving the implementation from the rpc to the Io trait?
Hey @thanethomson, I'd like to work on that. I was previous working on adding wasm support for tendermint-rpc (as it was specified in the previous issue). Was there any reason behind moving the implementation from the rpc to the Io trait?
Cool! Yes the main reason was that:
We're going to probably end up renaming that Io trait to something like LightBlockFetcher, since its primary purpose is not general I/O but is very specifically to provide LightBlocks.
As a result, we don't need the entire RPC to be able to build to WASM - we only need something WASM-compatible that's going to fetch and deserialize light blocks.
I'd be interested, however, to know if you feel like you'd want a more general-purpose Tendermint RPC client that compiles to WASM?
Not at all, we'll only need the Light Client to compile to WASM, so I started working on the RPC compilation.
I'll start working on WASM Io, then. Thanks for your attention!
Requires #953
At present, we only have one implementation of the Io trait in the Light Client, which makes use of the
tendermint-rpc
to fetch light blocks (over HTTP/WebSocket).To be able to support a full WASM build of the Light Client, we need to implement a fetch API-compatible version of the
Io
trait.What's the definition of "done" for this issue?
When we can compile the
tendermint-light-client
crate to WASM and make use of its full API (including networking) from JavaScript.The text was updated successfully, but these errors were encountered: