[Contract Verification] Seaport (EVM)

[coffeexcoin]

Team or Project

Abstract

ZK chain

Abstract

Environment

Testnet

Block Explorer

ZKsync explorer (e.g. https://explorer.zksync.io)

Issue Type

• Plugin
• Block Explorer

Contract Address

0x0000000000000068F116a894984e2DB1123eB395

Compiler Type

Multi-part contract

zkSolc Version

N/A

Solc Version

0.8.24

Contract Name

Seaport

Contract Code

standard input json here: https://gist.github.com/coffeexcoin/1dcfbf3476d5666f43423ab5d0e5f3cb

Constructor Arguments

N/A

Hardhat Verify Plugin Version

No response

Repo Link (Optional)

https://github.com/ProjectOpenSea/seaport/blob/main/docs/Deployment.md#verifying-seaport-and-conduitcontroller

Additional Details

Trying to verify seaport deployment in EVM bytecode compatibility mode and getting "Deployed bytecode is not equal to generated one from given source"

forge verify-contract --verifier-url "https://block-explorer-api.testnet.abs.xyz/api" --watch 0x0000000000000068F116a894984e2DB1123eB395 src/Seaport.sol:Seaport

Example verification run: https://block-explorer-api.testnet.abs.xyz/api/contract/checkverifystatus?guid=335208

Can you please provide some assistance in troubleshooting the verification here?

[dimazhornyk]

Hey! From the first glance everything looks fine, the verification command is correct.
@coffeexcoin could you please verify that the bytecode you have locally matches the deployed one?
cc @bxpana in case you would have any ideas

[dutterbutter]

I think its the same issue I am working on from: #994

I can pick up this one given I am already working on verifier fixes.

[dutterbutter]

Fix is prepared, once reviewed, merged, released I will update here.

[dutterbutter]

Rolling out to testnet today or tomorrrow.

[popzxc]

The seaport contract is now verified: https://explorer.testnet.abs.xyz/address/0x0000000000000068F116a894984e2DB1123eB395#contract