-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Smart contract verification improvements #6481
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikitosing
changed the title
Refactor smart contract verification form; Add support for smart cont…
Smart contract verification improvements
Nov 20, 2022
6 tasks
nikitosing
force-pushed
the
np-smart-contract-fixes
branch
from
November 21, 2022 13:46
934b03c
to
26bc139
Compare
nikitosing
force-pushed
the
np-smart-contract-fixes
branch
from
November 21, 2022 19:35
8423de9
to
f0217ee
Compare
nikitosing
force-pushed
the
np-smart-contract-fixes
branch
from
November 22, 2022 08:21
f0217ee
to
1f79d09
Compare
…ract verification without creation bytecode
…input or Sourcify
vbaranov
force-pushed
the
np-smart-contract-fixes
branch
from
November 28, 2022 09:48
1f79d09
to
3d20b82
Compare
vbaranov
requested changes
Nov 28, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nikitosing label association is still broken
- for Compiler field at
verify-via-standard-json-input/new
- for Compiler field at
verify-via-multi-part-files/new
nikitosing
force-pushed
the
np-smart-contract-fixes
branch
from
November 28, 2022 10:36
3d20b82
to
d2a9d4a
Compare
vbaranov
approved these changes
Nov 28, 2022
cedricfung
pushed a commit
to MixinNetwork/blockscout
that referenced
this pull request
Dec 2, 2022
* Refactor smart contract verification form; Add support for smart contract verification without creation bytecode * Add compiler settings for smart contracts verified via standard JSON input or Sourcify * Add verified twin name as fallback name for unverified contract; Fix compiler label
fx0x55
pushed a commit
to FunctionX/blockscout
that referenced
this pull request
Feb 9, 2023
* Refactor smart contract verification form; Add support for smart contract verification without creation bytecode * Add compiler settings for smart contracts verified via standard JSON input or Sourcify * Add verified twin name as fallback name for unverified contract; Fix compiler label (cherry picked from commit a63db41)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #5675
Close #6463
Close #5746
Close #4571
Motivation
Changelog
compiler_settings
field tosmart_contracts
tableChecklist for your Pull Request (PR)
CHANGELOG.md
with this PRmaster
in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.