-
Notifications
You must be signed in to change notification settings - Fork 394
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
Error: invalid BigNumber string #445
Comments
Hi @MDimow, That data is required for us to understand what's going on and help us recreating the issue on our end. Please add all of the missing info and also provide all the steps to reproduce this error. Thank you for your understanding. |
I'm sorry @MDimow but this project is not meant to be used with Remix. You can find my YouTube tutorials about how to use it in our README file. The reason why you are getting the error regarding BigNumbers is because Remix expects Ethereum values (e.g. the I highly recommend sticking with the recommended tools or you might bump into many more issues down the road. If you really wanna continue using Remix, then it's fine, but we can't provide you with official support for that... you may try opening a dedicated discussion or ask on the HashLips Discord server and see if there's anyone who can help you. |
Hello, everybody.
I am getting this problem when I try to set the _Cost before deploying when I use decimals.
creation of YourNftToken errored: Error encoding arguments: Error: invalid BigNumber string (argument="value", value="0.1", code=INVALID_ARGUMENT, version=bignumber/5.5.0)
On the other hand, if I use a whole number like 1 for the _Cost it accepts it and the contract is being deployed, BUT! After I try to mint it returns the same error:
transact to YourNftToken.mint errored: Error encoding arguments: Error: invalid BigNumber string (argument="value", value="", code=INVALID_ARGUMENT, version=bignumber/5.5.0)
P.S. I didn't change anything in the contract. I am using Remix with compiler 0.8.9
The text was updated successfully, but these errors were encountered: