Hi guys, I am developing a dapp where anyone can deploy their nft collection. Here I have two contract: A & B. Contract A is a deployer which calls contract B, which is collection contract, every time when a person wants to launch collection. Here everything is fine and collection launches successfully. But after launching collection, when I see contract creator address in explorer, contract creator is contract address of contract A. But for us, contract creator should be the address of the person who call contract A. Can anyone help me to solve this problem? Please ask me if anyone could not understand the problem.

Jul 26, 2022, 10:54 AM

offcourse contract creator address will be the contract A since it deploys the contract

Jul 26, 2022, 10:56 AM

So how can i solve this? In LaunchMyNFT platform, contract creator is the one who call the contract. Are they doing something different?

Jul 26, 2022, 10:58 AM

The user address should deploy the contract to make it like this,
but which address deploys the contract isn't a big deal since access control is the crucial part.

Jul 26, 2022, 11:01 AM

So in collection contract, I should define owner as the address who calls the contract A and give owner control? Is that right practice?

What about verifying contract? Might be there need contract creator

Jul 26, 2022, 11:05 AM

I can't say whether it's a right or wrong practice, it depends on your project.
If you don't want access to users' nfts, give them their fair ownership

etherscan auto verifies all subsequent contracts

if matches the bytecode

Jul 26, 2022, 11:05 AM

Yes we don't want to access user's nfts. So giving them their ownership means through variable like owner?

Jul 26, 2022, 11:08 AM

yep like that

Jul 26, 2022, 11:08 AM

There won't be further security issue when contract creator address in contract A?

Jul 26, 2022, 11:12 AM

I see zero issues, the access control is the main part
not whoever deploys the contract

Jul 26, 2022, 11:15 AM

Thank you man!

Jul 26, 2022, 11:15 AM