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
Currently, sozo needs to fetch data from the world to have compare it to the local representation of it.
However, on public networks, when too much blocks are in the network, the nodes are refusing returning data if the block range used to get events is too big.
As a temporary fix, sozo is relying on a world_block parameter:
The idea of this issue, is to remove this world_block, and instead making smaller block ranges if sozo detects the block range is too wide.
The exact limit of blocks is not benched yet, but 50k blocks could be a good start.
The text was updated successfully, but these errors were encountered:
Currently, sozo needs to fetch data from the world to have compare it to the local representation of it.
However, on public networks, when too much blocks are in the network, the nodes are refusing returning data if the block range used to get events is too big.
As a temporary fix, sozo is relying on a
world_block
parameter:dojo/crates/dojo/world/src/config/environment.rs
Line 13 in a2f00ed
And this is used in sozo here:
dojo/bin/sozo/src/commands/events.rs
Lines 65 to 71 in a2f00ed
The idea of this issue, is to remove this
world_block
, and instead making smaller block ranges if sozo detects the block range is too wide.The exact limit of blocks is not benched yet, but 50k blocks could be a good start.
The text was updated successfully, but these errors were encountered: