-
Notifications
You must be signed in to change notification settings - Fork 0
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 #3
Labels
Comments
xBalbinus
moved this from 🖊 Planning
to 🚧 In progress
in Filecoin DX Painpoints Tracker
Jul 17, 2024
Idea: https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract We should probably update this page with the latest of FILFOX et al.'s APIs for verification. |
@xBalbinus What are the next steps or proposed action items for this pain point? |
Bump please @xBalbinus can we close this off? |
… On Tue, Sep 10, 2024 at 1:41 PM Sarah Thiam ***@***.***> wrote:
Bump please @xBalbinus <https://github.com/xBalbinus> can we close this
off?
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASH4FPUZIXF3JK5YLREGHQDZV5KOBAVCNFSM6AAAAABK7UXJQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRHE3TCOBQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Verifying smart contracts at the moment is a pain for users. There are unknown errors that are 'hard to fix'
[Provide a detailed description of the issue here, including any links to available evidence or original user posts as much as possible]
https://filecoinproject.slack.com/archives/CRK2LKYHW/p1720593649171469?thread_ts=1720447325.817329&cid=CRK2LKYHW
[Specify the feature or component related to the issue]
FILFOX contract verification API
[Explain why this issue is important and how it affects development]
Cannot verify smart contracts
[Describe the desired solution or the happy path]
Additional Context:
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: