Hi @adityapk00 - thank you for your feedback! Wanted to share a few thoughts we have in response.
As to demand for a web wallet, we appreciate your user conversations. Our interest in the project came, in part, from the web wallets that already exist for other currencies. Two examples:
Ryo Wallet Quasar
The existence of these web wallets for other coins makes us think that having a similar option available for Zcash would be an overall plus for the ecosystem, and implies a general demand. In addition, I think there is messaging that can be communicated to the people through the user experience to address concerns.
To your second point on the speed factor, especially as it pertains to the WASM engine: we believe that we can build an engine that performs well. To your specific point on thread support, we do think that WASM now supports multi-threading. Please check out this article for more details:
To your more general point of WASM vs. native code, please see this discussion:
@fireice_uk has found that number to be generally correct in his experience.
To your points about network access - we feel that those are factors where the chief limiting factor ends up being bandwidth, and not latency capped. On the Rx side, we can set batch size to the most optimal value, thus minimizing latency. On the Tx side, only a few KB of transaction data is set, which should be a negligible hurdle.
Of course sharing article links is one thing, and the true proof would be in the code itself. That’s why we have our initial performance tests in our second milestone - so that we can see real numbers around how our approach performs early in the project.
Hope these points have been helpful - looking forward to continuing the conversation.