ape icon indicating copy to clipboard operation
ape copied to clipboard

General: Add support for smart contract verification to ExplorerAPI

Open fubuloubu opened this issue 4 years ago • 6 comments

Overview

When you deploy a smart contract to a public network, you often want to verify that contract's source code through one (or more) blockchain explorer(s) source code verification API (if it exists).

Specification

Add a kwarg verify=None to AccountAPI.deploy(ContractType, ..., verify=True) that will publish the corresponding smart contract code to any loaded ExplorerAPI plugin

Also prototype a way to verify source code "after the fact", maybe via ContractInstance or ReceiptAPI of the deployment txn.

Dependencies

Have to be able to link back to the Source(s) (or just use the package manifest directly) from a ContractType of the deployed contract.

fubuloubu avatar Jul 04 '21 01:07 fubuloubu

there is also an issue for this found in ape-etherscan: https://github.com/ApeWorX/ape-etherscan/issues/22 Now, they are linked :)

antazoey avatar May 17 '22 16:05 antazoey

dependency #792 to get compiler values to pull data required for verification dependency #530 to get deployed contract to pull data required for verification dependency https://github.com/ApeWorX/ape/issues/793 to get meta information required for contract verification

sabotagebeats avatar Jun 08 '22 22:06 sabotagebeats

related: https://github.com/ApeWorX/ape/issues/794

sabotagebeats avatar Jun 08 '22 22:06 sabotagebeats

@NotPeopling2day I believe this is the information you were requesting above 👍

sabotagebeats avatar Jun 08 '22 22:06 sabotagebeats

dependency for vyper: https://github.com/ApeWorX/ape/issues/850

sabotagebeats avatar Jul 01 '22 19:07 sabotagebeats

status: blocked by https://github.com/ApeWorX/ape/issues/948 and https://github.com/ApeWorX/ape/issues/530

sabotagebeats avatar Aug 05 '22 23:08 sabotagebeats