Note: This contract matches the deployed ByteCode of the Source Code

also got this error “Compiler specific version warnings:

The compiled contract might be susceptible to ABIDecodeTwoDimensionalArrayMemory (very low-severity), EmptyByteArrayCopy (medium-severity), DynamicArrayCleanup (medium-severity), MissingEscapingInFormatting (very low-severity), ImplicitConstructorCallvalueCheck (very low-severity), TupleAssignmentMultiStackSlotComponents (very low-severity), MemoryArrayCreationOverflow (low-severity) Solidity Compiler Bugs.”

what is the address of the contract?

did you created that on mainnet? or on mumbai?

0x2C4520D0955eB06DA3E774Bf3802e4c3b0578c43 on matic(polygon)

mainnet

WHat are you trying to verify?

The code is already verified:

https://polygonscan.com/address/0x2C4520D0955eB06DA3E774Bf3802e4c3b0578c43#code

can’t verify ownership

https://i2.paste.pics/041e30884bfa55aef0dd19bc568516fe.png
https://i2.paste.pics/5f2e3e90710e36a903aa6f68b9e468ea.png

There is no such thing as “Ownership” in the smart contract, this is a polygonscan issue, you need to talk with them.

u have to claim ownership to update token info and i need to add logo to token
https://i2.paste.pics/50aebdec592c725942c5abe435b24509.png

Sorry, but we do not have control over polygoscan system,

Other customers have solve this talking directly with them.

@wpsmartcontracts

And what problem could this bring to NFT Marketplace?

• This reply was modified 2 years, 11 months ago by mattiellox.

to all,

this is due to the contract being created by another contract. polygon requires the origin creating contract creator to verify that a sub contract that their orgin contract created is in fact “owned” by the person whos requesting access to have updating authority over their “owned” smart contract. ignore my terminology, no need to nitpick it. im trying to make this readable for all. but ownership, plainly in polygonscan terms would mean you have full rights to changing meta and info related to the smart contract on polygonscan. without those rights you are just some anonymous person trying to use someone elses contract. atleast thats how polygon sees it. im a polygon community organizer in my region and ive discussed this issue with them a few times already. if i need to elaborate more in depth i can. but i think i made it pretty easy to understand here. to make changes you need to be recognized as the “owner” or the person whos authorized to make changes to the polygonscan record and if its minted by way of another contract you cant with that origin minter’s verification that you are infact authorized to make changes. theres some work arounds with polygon but its headache. its easier for the origin minter to verify new owner, per the team who handles this at polygon. to speed it up just start a conversation using the correct request form on polygonscan and discuss it with them. they will give you things they need to do it.