search

blockscout / frontend

Front-end application for Blockscout
https://blockscout.com
GNU General Public License v3.0
162 stars 425 forks source link

Substitute data of the verified contract when user verifies contract with the similar bytecode #1086

Open vbaranov opened 1 year ago

vbaranov commented 1 year ago

Description

Screenshot 2023-08-15 at 17 46 03

When a user tries to verify a contract with similar bytecode, Blockscout should substitute verification data from previously verified contract with similar bytecode on the verification form. This will simplify verification of the second contract. Otherwise, user should manually paste verification data from the 1st contract.

Currently, the verification form of the 2nd contract is empty.

Link to the page

https://wannsee-explorer.mxc.com/address/0xD3370101e4E39698FA85ab5d4230fbc4A879a269?tab=contract

Steps to reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

App version

No response

Browser

No response

Operating system

None

Additional information

No response

tom2drum commented 1 year ago

@vbaranov sorry, but image link is broken.

Could you provide more details, please? How do we know that user trys to verify contract with similar bytecode? What is the user journey in this case? Is there any flags or data in API about a contract with similar bytecode?

NikitaSavik commented 11 months ago

due to automatic verification on backend side, decided to skip this kind of corner cases for now

nikitosing commented 11 months ago

I suggest to add automatic verification of twin contracts on the backend side