I think this approach would be okay if we stopped here at features, but I think it would also be nice to eventually add an option to ignore balances below some custom level. That way an eToken creator could encourage people to hold some kind of arbitrary minimum balance of their eToken to be eligible for airdrops.

For the dust case, just popping out the dust values does not have a major impact on the size of the total airdrop. However, for a custom min threshold, there would be this impact.

So -- we'll have to run the calc twice, or start with a list of airdrop addresses and their eToken balance

Option A

1. Get all addresses and their airdrop amount
2. Remove all addresses where airdrop amount < dust
3. Now, get all addresses and airdrop amount again (so that the dust amounts you ignored become distributed over the other addresses)

Option B

1. Get all addresses and their eToken balance
2. Remove all addresses with balances below minEligibleBalance
3. Now, calculate addresses and airdrop amount

For the purposes of this specific diff...it's okay to land this diff using your current approach, but please create a task to solve the problem described above. This will eventually need to be the way it's done for dust, so it is probably less complicated in the long run to do it now.

Use a switch