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
I noticed that you're using a merkle drop contract for repeated distributions of the same token. At Balancer we've got a version of this which has been gas optimised for people claiming multiple distributions to massively reduce the number of SSTOREs needed.
The only downsides I see is that we don't support zeroing out merkle roots after the fact (expireTranche) and if you're going to be making distributions from multiple addresses then you'll need a thin wrapper contract in front to ensure each distribution goes in the same "distribution channel".
If those aren't dealbreakers though you'd benefit from being able to claim distributions more cheaply, claiming in parallel with other tokens and easy integration with Balancer UI, etc.
The text was updated successfully, but these errors were encountered:
I noticed that you're using a merkle drop contract for repeated distributions of the same token. At Balancer we've got a version of this which has been gas optimised for people claiming multiple distributions to massively reduce the number of SSTOREs needed.
The only downsides I see is that we don't support zeroing out merkle roots after the fact (
expireTranche
) and if you're going to be making distributions from multiple addresses then you'll need a thin wrapper contract in front to ensure each distribution goes in the same "distribution channel".If those aren't dealbreakers though you'd benefit from being able to claim distributions more cheaply, claiming in parallel with other tokens and easy integration with Balancer UI, etc.
The text was updated successfully, but these errors were encountered: