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

What is the Params limit of TransferExported method? #1897

Closed
beck-8 opened this issue Mar 25, 2024 · 2 comments · Fixed by #1912
Closed

What is the Params limit of TransferExported method? #1897

beck-8 opened this issue Mar 25, 2024 · 2 comments · Fixed by #1912

Comments

@beck-8
Copy link
Contributor

beck-8 commented Mar 25, 2024

Method: datacap2.Methods.TransferExported,

Is there a recommendation for how many parameters can be stored in a message?

In addition, this writing method is not suitable for large-scale use by users. It is recommended to use parameters such as --file pieces.txt

Usage: "data piece-info[s] to create the allocation. The format must be --piece-info pieceCid1=pieceSize1 --piece-info pieceCid2=pieceSize2",

@LexLuthr
Copy link
Collaborator

Using a file restricts the users to a particular format. This way provides a more flexibility using BASH.
Most of the gas should be required for unmashalling the parameters but I don't have an exact number. Let me check with the Actors team.

@beck-8
Copy link
Contributor Author

beck-8 commented Apr 1, 2024

Using a file restricts the users to a particular format. This way provides a more flexibility using BASH.

Can you give me an example? I don't see how this is more convenient.
On the contrary, this is very painful for people who are not skilled in bash. They have no idea how to send 10,000 transactions in batches quickly.

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

Successfully merging a pull request may close this issue.

2 participants