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
{{ message }}
This repository was archived by the owner on Apr 18, 2023. It is now read-only.
There's no advantage of using your smart contract vs regular jsonrpc batching. In fact the performance is worse.
Get the return value(s) of multiple smart contract function calls in a single call
This is not superior to using a batch because the batch is in parallel.
Guarantee that all values are from the same block
You can specify a block number in the call. Polling "latest" results in unnecessary calls since you should only poll when you get a new block. A block is already a snapshot.
Use watchers to poll for multiple blockchain state variables/functions
Get updates when a watcher detects state has changed
Results from out of sync nodes are automatically ignored
Get new block updates
These are valid and useful, but don't require the batch contract.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's no advantage of using your smart contract vs regular jsonrpc batching. In fact the performance is worse.
This is not superior to using a batch because the batch is in parallel.
You can specify a block number in the call. Polling "latest" results in unnecessary calls since you should only poll when you get a new block. A block is already a snapshot.
These are valid and useful, but don't require the batch contract.
The text was updated successfully, but these errors were encountered: