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

When writing contract, what value to use for data? #3

Open
james-lukensow opened this issue Apr 9, 2022 · 2 comments
Open

When writing contract, what value to use for data? #3

james-lukensow opened this issue Apr 9, 2022 · 2 comments

Comments

@james-lukensow
Copy link

Not a bug, just a question as the Readme didn't address this...

Just deployed this on the mumbai test network. When executing a mint, I can get it to work. But I have to put in a fake value for data input. What in a real world, would be the value of the data field?

data (bytes)

@MatthewSherlin
Copy link

Hey @james-lukensow
The preset contract doesn’t actually use the data (bytes) parameter but passes it on for certain cases. If you needed to pass additional data for mint and transfers, then you could use data parameter to pass the information. Since you don't need it, passing anything won't break, nor do anything for you. This is essentially here to keep compliance with the standard

@james-lukensow
Copy link
Author

Makes sense, thank you!

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