filecoin-project
Update Contract Verification page to list all possible tools
Need to update https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract to include:
- BlockScout (recommended)
- Sourcify.dev (also recommended if others do not work)
(Context: https://filecoinproject.slack.com/archives/CRK2LKYHW/p1738226742036079?thread_ts=1738172697.643169&cid=CRK2LKYHW)
shall we wait for blockscout's verification on testnet to be completed before adding it?
Not necessary
On Fri, 31 Jan 2025 at 02:13, Sarah Thiam @.***> wrote:
shall we wait for blockscout's verification on testnet to be completed before adding it?
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-docs/issues/2357#issuecomment-2626069858, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHYPITC5XQ3J6G5P24RKT32NLE43AVCNFSM6AAAAABWEX2U6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRWGA3DSOBVHA . You are receiving this because you authored the thread.Message ID: @.***>
Suggestion: Make verify-a-contract a folder
verify-a-contract/
├── ui-guide/ # Filfox + Blockscout manual steps
└── programmatic/ # Scripts for automated verification
For the programmatic part, we could update the fevm-hardhat-kit and while referring to it add verification for Blockscout, Filfox, and Sourcify guides.
What do you think @eshon?
I think that makes sense.
FYI - Generally it might be okay to default to ask for verification on Blockscout.
If a contract is not verified on Filfox, Filfox has added a link to it on Blockscout since they have an EVM bytecode database. Example:
https://filfox.info/en/address/f410faoeyphqbkybteawejp3yjlay7qbo33sp7xjo7sa?t=3
Asking developers to verify on both Blockscout and Filfox sounds like a lot to me so it might be fine to have them default to Blockscout.