feat: add verify-by-api documentation for FILFOX#2313
feat: add verify-by-api documentation for FILFOX#2313xBalbinus wants to merge 2 commits intofilecoin-project:mainfrom
Conversation
|
|
||
| This section provides detailed documentation for the Filfox Contract Verification API. The API allows you to verify your smart contracts programmatically, and is the recommended method for verifying contracts. Below, you will find information on how to use the API, including the available endpoints, request and response formats, and example code snippets. | ||
|
|
||
| Please refer to the [documentation](https://filfox.info/api/v1/docs/static/index.html) for more information on how to verify contracts using the Filfox API. |
There was a problem hiding this comment.
This documentation links to Filfox API Documents which does not include verifyContract API. Is it a wrong link? Or maybe we can just remove it.
There was a problem hiding this comment.
@xBalbinus can you address the comments, so we can get this merged?
| * [Remix](https://remix.ethereum.org/) | ||
|
|
||
| ### Procedure | ||
| #### Via. API (Recommended) |
There was a problem hiding this comment.
This is the same content as Filfox docs. I am wondering if this is necessary to have the same content here in Filecoin docs to bring the extra work of maintaining here comparing with just providing a link to it.
There was a problem hiding this comment.
I agree with @longfeiWan9, I think a better option would be to list the different platforms that do contract verification, like at the top of this document, and then under each platform list links to their tutorials.
| * [Remix](https://remix.ethereum.org/) | ||
|
|
||
| ### Procedure | ||
| #### Via. API (Recommended) |
There was a problem hiding this comment.
Why it is the recommended way of verifying the contract?
|
@xBalbinus Since there has been no progress on this PR since January, I'm going to close it for now. If you still think it's an important change to make, feel free to re-open and we can continue discussing. |
5 participants
No description provided.