Fixing the problem of an ERC721 on Chain NFT smart contract
Budget: $750 – $1,500 USD
I have the following smart contract for ERC721 which I used base64 to embed it on chain.
Main smart contract
https://gist.github.com/dr-data/cf3180b5244f4cc2f09d3bdab7973dd7
The Base64 library used
https://gist.github.com/dr-data/1b66fa6ed4e1bf9246ea72cde8e8eff2
I can deploy it correctly in rinkeby and mainnet but I can't make this show correctly in opensea (just 404 error). It doesn't validate the asset / metadata according to the tool from opensea: https://testnets-
api.opensea.io/asset/0x12DAb9a7211Af3B75381A541adf816A1B328b490/0/validate/?format=api
I need someone to deploy and show, validate the metadata / asset it correctly in opensea (in rinkeby network) and provide me the solution both in remix and hardhat
*I will pay more if you can fix it within 2 hours*
Main smart contract
https://gist.github.com/dr-data/cf3180b5244f4cc2f09d3bdab7973dd7
The Base64 library used
https://gist.github.com/dr-data/1b66fa6ed4e1bf9246ea72cde8e8eff2
I can deploy it correctly in rinkeby and mainnet but I can't make this show correctly in opensea (just 404 error). It doesn't validate the asset / metadata according to the tool from opensea: https://testnets-
api.opensea.io/asset/0x12DAb9a7211Af3B75381A541adf816A1B328b490/0/validate/?format=api
I need someone to deploy and show, validate the metadata / asset it correctly in opensea (in rinkeby network) and provide me the solution both in remix and hardhat
*I will pay more if you can fix it within 2 hours*