Midnight Kitties contract address

General
,
1

I am new to smart contracts and I have completed the midnight kitty walk-through DAPP so many times and I get to the quest and I have no idea where to find my contract address. I even asked AI and it said it’s there. It just wouldn’t tell me where it was. I don’t know what I’m looking for. I hate being stuck like this.

2

Hi Steph! Make sure you are using version 0.25.0 of the compiler. I will update the Zealy quest to make a note of it.

Once you run the proof server, you will be prompted to make a wallet or connect one. Then you should be prompted with the contract options. There you can deploy your contract, and grab your contract address.

3

OK.. I swear I did all that.. It say’s it compiled the NFT’s I link my wallet.. that part works.. but I stuck some random number in the zeally quest just because I was trying to get your attention…lol. but it went through! This is something I am tryng hard to make work.. I think it will be a great onboarding tool to be able to burn an xrp token to receive a midnight nft.. It can show how it works together..

thanks jay.. I am using .25 of the compiler. I am trying to get everything I have “built” to work with the new install, but I havn’t gotten far..I keep hitting a road block

4

A few thoughts.

  1. For clarity, compiling a contract successfully just means it will run without errors but it’s not public to anyone. You will need to deploy the contracts for them to be accessible onchain.

  2. I attached a screenshot of the cli. The last line when you deploy a new Crypto Kitties contract will give you the address.

    Deployed
    Deployed760×698 23.2 KB

  3. We have someone verifying submissions in Zealy, so it going through, just means it was received, but it should be rejected once reviewed if it is not a valid contract.

  4. I think the idea is cool, you need to generate a proof that the token was burnt, then you can token gate the mint button. That’s just one approach. Let me know how it goes.

  5. If you did yarn install in the project, and then you changed compilers, it will reference the older compiler. You can remove the old package with rm -rf node_modules **/node_modules yarn.lock

    then install again with yarn install

5

Thank you!!! I will give it another go.. with this info.. I am licking this forum by the way!

1 Like