-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sourcify support #1822
Comments
Blockscout uses Sourcify, so we should just support that |
@robertabbott check this out |
+1 |
@onbjerg blockscout exposes etherscan like api, so current verification flow should work. see the description of gakonst/ethers-rs#1343 |
did i have to install anything to make blockscout work with foundry, error: unexpected argument '--blockscout' found tip: to pass '--blockscout' as a value, use '-- --blockscout' Usage: forge create --constructor-args ... --verify <--rpc-url |--flashbots|--jwt-secret <JWT_SECRET>> <--interactive|--private-key <RAW_PRIVATE_KEY>|--mnemonic |--mnemonic-passphrase |--mnemonic-derivation-path |--mnemonic-index > <--gas-limit <GAS_LIMIT>|--gas-price |--priority-gas-price |--value |--nonce |--legacy> For more information, try '--help'. |
Component
Forge
Describe the feature you would like
I have checked a several ways to verify codes for blockscout v4.1.3 or above. There is no api-key needed for verification. Currently there is a way to upload the standard json for the process however the json that created from the regular
forge
does not work.It should be nice to have blockscout specific solution for source verifications with this flag
--blockscout
for example:
Additional context
No response
The text was updated successfully, but these errors were encountered: