update contract verification docs to be more precise #345
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
|
Thanks for taking the time to open this PR! We've added this to our backlog, pending to be reviewed. |
zencephalon
approved these changes
Mar 6, 2024
|
|
||
| You can interact with your deployed contract using Remix, the same as before, but it's also possible to interact with it through Etherscan. Paste your address in the search field to find it. | ||
| While you can interact with your deployed contract using Remix, you can also do so through [sepolia.basescan.org](https://sepolia.basescan.org). To find your contract, paste its address into the search field and click search. |
There was a problem hiding this comment.
Please change to reference-style links. See below for an example!
briandoyle81CB
suggested changes
Mar 8, 2024
|
@kaseLunt Hi there! Since it's been some time since @briandoyle81CB left feedback without further changes, just wanted to follow-up to see if you were still interested in pursuing this PR. |
wbnns
reviewed
May 23, 2024
| hide_table_of_contents: false | ||
| --- | ||
|
|
||
| Once your contract is deployed, you can verify it using a number of popular services. Doing so will let you users have confidence that your contract does what you claim, and will allow you to interact with it using a similar interface to what you used in Remix. | ||
| After deploying your contract, you can verify it using popular explorers like [basescan](https://sepolia.basescan.org). Verifying your contract allows users to trust that it does what you claim and enables you to interact with it using a user-friendly interface similar to Remix. |
There was a problem hiding this comment.
s/using popular explorers/using a popular explorer/
s/basescan/Basescan/
wbnns
added
change(s) requested
|
Hello, since it has been some time and we haven't heard back, I'm going to go ahead and close this PR for now. If you'd like to pursue these changes in the future please let us know and we can reopen. 👍 |
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.
What changed? Why?
Notes to reviewers
How has it been tested?
Does this PR add a new token to the bridge?