Issue Verifying and publishing contract source code....

[Tarreef]

I tried verifying and publishing the source code for SimpleStorage. i inputed the Verification details. including... Compiler Type, Compiler Version, Open Source Licence Type and Source Code

here's my source code...

// SPDX-License-Identifier: MIT

pragma solidity ^0.8.19;

// pragma solidity ^0.8.0;
// pragma solidity >=0.8.0 <0.9.0;

contract SimpleStorage {
    /*constructor() payable {
        require(msg.value > 0.001 ether, "must be atleast 1 ether");
    }*/

    uint256 myFavoriteNumber;
    struct Person {
        uint256 favoriteNumber;
        string name;
    }
    // uint256[] public anArray;
    Person[] public listOfPeople;

    mapping(uint256 => string) public nameToFavoriteNumber;

    function store(uint256 _favoriteNumber) public {
        myFavoriteNumber = _favoriteNumber;
    }

    function retrieve() public view returns (uint256) {
        return myFavoriteNumber;
    }

    function addPerson(string memory _name, uint256 _favoriteNumber) public {
        listOfPeople.push(Person(_favoriteNumber, _name));
        nameToFavoriteNumber[_favoriteNumber] = _name;
    }

    function viewPerson(
        uint256 _favoriteNumber
    ) public view returns (string memory) {
        return (nameToFavoriteNumber[_favoriteNumber]);
    }
}

i set the optimisation to "yes", did the Recaptcha thing and hit verify and publish

Although after a brief delay i got an error saying

Error! Unable to find matching Contract Bytecode and ABI

it seems the byte code of the contract dosen't match the one they're looking for...

i know the verification is optional but i still think i might want to do it cause i want to see the results against later.

[EngrPips]

Honestly, I haven't achieved any success with manual verification myself, and I have always just used Foundry verification feature to verify smart contracts I deployed while taking Cyfrin course

[chainflash]

Honestly, I haven't achieved any success with manual verification myself, and I have always just used Foundry verification feature to verify smart contracts I deployed while taking Cyfrin course

Indeed

[Tarreef]

foundry has a verification feature not in etherscan??
I probably haven't got there yet.

[Tarreef]

so i asked AI how the foundry's verification feature works. turns out, it seemed to have worked.

forge verify-contract 0x50cc3a0ab5831358ACcC5c56C9Bff258a7128154 SimpleStorage 
--etherscan-api-key 2BD7W3IWWCVPWTHAYK12JCTWEAD2K92TFW --chain-id 11155111 --watch -vvvv

please is this response accurate.

[EngrPips]

Yeah, it showed that the contract got verified

[KMean]

@Tarreef please avoid posting API Keys of any kind 😉.

[KMean]

@Tarreef If you're using remix to deploy make sure to put the actual compiler version you used to compile your contract. I was able to verifiy the contract you've pasted just using correct compiler, no optimization.

[Tarreef]

Yes i tried it @KMean. Although i don't use remix, but i still tried it and got the same response.
i use Alchemy. I tried changing the compiler version to 0.8.26 with and without optimisation, both ways failed...
By the way i presumed the ^ was supposed to tell solidity to compile any version >= to the one given. so shouldn't the code be able to verify with the version 0.8.19?. Anyway maybe i should try deploying it on remix like you did and see

[Tarreef]

I did it, it worked! using remix.
Although i'm curious tho...

If i were to be deploying two or more contracts in one file which compiles together as if they were an interface or library.
what name would be displayed as the contract name like in the red circle below

[EngrPips]

Try it and see.

[KMean]

Yes i tried it @KMean. Although i don't use remix, but i still tried it and got the same response. i use Alchemy. I tried changing the compiler version to 0.8.26 with and without optimisation, both ways failed... By the way i presumed the ^ was supposed to tell solidity to compile any version >= to the one given. so shouldn't the code be able to verify with the version 0.8.19?. Anyway maybe i should try deploying it on remix like you did and see

Oh I see... so I guess you're in forge and using Alchemy as RPC URL provider??

when you run forge build is telling you what compiler has been used

forge build
[⠊] Compiling...
[⠔] Compiling 1 files with Solc 0.8.24
[⠒] Solc 0.8.24 finished in 405.33ms
Compiler run successful!

in forge is simpler and you can do it after the contract has been deployed as you did with forge verify-contract or piping it during deployment with the --verify flag.

please refer to this for full infos.