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
Not sure if there's a way to manually set the multicall contract for each network but it doesn't seem to work out of the box with base, forcing me to create/use a custom viem client. Replacing the client (to viem with base as the defined chain) below fixes my issue, despite using the same RPC on both runs
Got it. We're planning to make it possible to pass a viem Chain as an option to networks, which would solve this issue. Still working out the details of the API and migration path, cc @kyscott18.
In the meantime, you might be able to construct the multicall request using context.client.readContract, which means you'd still benefit from caching. The custom client approach will slow down reindexing significantly.
Not sure if there's a way to manually set the multicall contract for each network but it doesn't seem to work out of the box with base, forcing me to create/use a custom viem client. Replacing the client (to viem with base as the defined chain) below fixes my issue, despite using the same RPC on both runs
"@ponder/core": "^0.4.22"
The text was updated successfully, but these errors were encountered: