Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSV airdrop having skipped status on chain with 500 transfers #511

Closed
Claire-serveth opened this issue Sep 1, 2024 · 2 comments
Closed

Comments

@Claire-serveth
Copy link
Collaborator

Issue Category

Other

What happened?

User on Scroll network was having a "skipped" status on the block explorer when he executed the CSV airdrop transaction with 500 transfers:
image
image

Clarification:

  • What is the maximum number of token transfers/actions in a single transaction on CSV airdrop?
  • Does the limit depend per network (or the same for all supported network)?

Date and time this happened or you first noticed this issue

01-09-2024

Network

Aurora

Safe Address

No response

Token Address

No response

Token Type

None

Transactions

No response

@schmanu
Copy link
Member

schmanu commented Sep 2, 2024

The maximum number of transfers depends a lot on the kind of transfers:
If it contains ERC20 / ERC712 / ERC1155 transfers it depends how those token contracts are implemented.

I once tried to find good average numbers and found that the gas usage can differ a lot between contracts - even for the same standard such as ERC20.

And then the networks also have different block gas limits and therefore different restrictions for the gas usage of transactions.

Could the user try to cut the transfers into two 250 entry transfers?

@Claire-serveth
Copy link
Collaborator Author

Hi @schmanu yes, that's what the user tried and it did go through. Transaction was successful with 200+ but not 500. So, it would be best then to limit the transfers to 200 (although depending on the of the type) in order for the transaction to go through successfully. Thank you so much for the response, closing this issue now. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants