Closed JustLuuuu closed 6 months ago
is there anything we can do @vikiival ?
The art is not same:
First does not respect that api needs to be called after success mint (cc @preschian)
Second is oki
Why you see the same pictures is that app does not respect the fact that should only use image data from the iframe and not the capture service cc @Jarsen136
Does it have solution?
Why you see the same pictures is that app does not respect the fact that should only use image data from the iframe and not the capture service cc @Jarsen136
I do not understand tbh. I guess it's because the user opens two tabs at the same time and then he mints twice with the same variation. (Both #17
and #18
nft were minted by the same user)
A possible solution would be to force random variation after every refresh. In other words, the solution is to remove the default value and always return a new one. wdyt ? @vikiival
I do not understand tbh.
You should never call
And the only way how to obtain image is this:
In other words, the solution is to remove the default value and always return a new one.
There should be no default value imo
I do not understand tbh.
You should never call
And the only way how to obtain image is this:
In other words, the solution is to remove the default value and always return a new one.
There should be no default value imo
Will raise a PR for it
@vikiival @Jarsen136 should we check on the worker side also? ensure that the hash/image is unique
duplicate hash on meadow
These two mints are identical:
This one and this one.
How did it happen? This should not happen next time. Minted by the same address.