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
technically, this means that if we had an eth_call to weiroll call converter, then we could take some of the eth_calls in the queue, convert them to weiroll calls and hence save network requests
the idea is that network requests are slow as they have roundtrip time, latency etc. and so batching network requests seems like a good idea
potentially, if we're generically translating eth_calls to weiroll calls then we should consider natively implementing it in eth-fun
so I may need to transfer this issue there.
The text was updated successfully, but these errors were encountered:
If we are to generically translate all RPC calls to weiroll then won't we be better off just using weiroll.js?
In case we want to keep it lean and just translate eth_calls then also it seems like a lot of work. This is coming from a person who just started to learn weiroll so maybe I am wrong. To reduce our work and solve the problem we can use the batch functionality of JSON RPC. It's the simplest. (Edit: Found #45)
Weiroll has a disadvantage when compared to batch JSON RPC requests. If one eth_call fails in weiroll then all the calls will fail. This can happen if we provided a wrong tokenID to one of the eth_call in the batch. This doesn't happen in JSON RPC.
I think a lot of people would appreciate a eth_call to weiroll_call function
Weiroll has a disadvantage when compared to batch JSON RPC requests. If one eth_call fails in weiroll then all the calls will fail. This can happen if we provided a wrong tokenID to one of the eth_call in the batch. This doesn't happen in JSON RPC.
The text was updated successfully, but these errors were encountered: