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
The fundings are done through a multicall, and enough multicalls will exceed the block size and stall operation. At what tree size this becomes a problem is chain-specific (though anything below 100 recipients should always work). If the bot was able to batch multicalls in smaller sizes, this wouldn't be a problem. To avoid unnecessary complexity, I'd say let's wait and see what the actual user needs are.
The text was updated successfully, but these errors were encountered:
Note that this suffers from a similar issue as in #27 because the static multicalls will also need to be batched, which means they will be done in separate block numbers. The potential solutions are again the same, either don't care about the maximum tree size (probably have MAXIMUM_TREE_SIZE=200 hardcoded in this repo that is validated wherever possible) or serve different batches of the same tree using different mnemonics (which sounds much worse than serving different depositories with different mnemonics).
The fundings are done through a multicall, and enough multicalls will exceed the block size and stall operation. At what tree size this becomes a problem is chain-specific (though anything below 100 recipients should always work). If the bot was able to batch multicalls in smaller sizes, this wouldn't be a problem. To avoid unnecessary complexity, I'd say let's wait and see what the actual user needs are.
The text was updated successfully, but these errors were encountered: