Skip to content

Use separate Solc inputs to verify different proxy contracts #754

@ericglau

Description

@ericglau

Currently the Solc input for all proxy-related contracts are packaged into one build-info.json file. When using this to verify source code on Etherscan, this causes the contracts for every different proxy kind to be included.

For example, even if the user is only using ERC1967Proxy, the source code for TransparentUpgradeableProxy would also be included in the verified source code.

To improve this, we should verify each proxy-related contract using its own Solc input for that contract and its dependencies only.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions