Skip to content

Commit 503e340

Browse files
authored
Merge pull request #2415 from nijoe1/main
Fix contract verification URL paths and support links
2 parents dd3fd1e + f72c5bc commit 503e340

File tree

10 files changed

+14
-16
lines changed

10 files changed

+14
-16
lines changed

SUMMARY.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -132,11 +132,11 @@
132132
- [Filecoin.sol](smart-contracts/developing-contracts/filecoin.sol.md)
133133
- [Direct deal-making with Client contract](smart-contracts/developing-contracts/client-contract-tutorial.md)
134134
- [Using RaaS](smart-contracts/developing-contracts/using-raas.md)
135-
- [Verify a contract](smart-contracts/developing-contracts/verify-a-contract/index.md)
136-
- [Programmatic](smart-contracts/developing-contracts/verify-a-contract/programmatic/index.md)
135+
- [Verify a contract](smart-contracts/developing-contracts/verify-a-contract/verify-a-contract.md)
136+
- [Programmatic](smart-contracts/developing-contracts/verify-a-contract/programmatic/programmatic.md)
137137
- [Hardhat](smart-contracts/developing-contracts/verify-a-contract/programmatic/hardhat.md)
138138
- [Foundry](smart-contracts/developing-contracts/verify-a-contract/programmatic/foundry.md)
139-
- [Web Interface](smart-contracts/developing-contracts/verify-a-contract/web-interface/index.md)
139+
- [Web Interface](smart-contracts/developing-contracts/verify-a-contract/web-interface/web-interface.md)
140140
- [Blockscout](smart-contracts/developing-contracts/verify-a-contract/web-interface/blockscout.md)
141141
- [Filfox](smart-contracts/developing-contracts/verify-a-contract/web-interface/filfox.md)
142142
- [Best practices](smart-contracts/developing-contracts/best-practices.md)

basics/assets/transfer-fil.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,10 @@ Remember that Filecoin is fully compatible with Ethereum tools, like wallets. Bu
2626

2727
If you want to transfer FIL tokens from one `f4` address to another `f4` address using their corresponding `0x` addresses, you need to understand how to convert between `f4` and `0x` addresses.
2828

29-
* If you have `f4` address, you can convert it to `0x` address using [Beryx Address converter](https://beryx.zondax.ch/address\_converter).
30-
* If you have a `0x` address, you can directly search it on [Filfox Explorer](https://filfox.info/en), which will show the `0x` address and corresponding `f4` address.
29+
- If you have `f4` address, you can convert it to `0x` address using [Beryx Address converter](https://beryx.zondax.ch/address_converter).
30+
- If you have a `0x` address, you can directly search it on [Filfox Explorer](https://filfox.info/en), which will show the `0x` address and corresponding `f4` address.
3131

32-
Apart from that, you just need to follow the standard process using your preferred Ethereum-compatible wallet, like MetaMask, MethWallet, etc. For instance, [MetaMask has a simple guide](https://support.metamask.io/hc/en-us/articles/360015488931-How-to-send-tokens-from-your-MetaMask-wallet) for how to send Ethereum from one account to another.
32+
Apart from that, you just need to follow the standard process using your preferred Ethereum-compatible wallet, like MetaMask, MethWallet, etc. For instance, [MetaMask has a simple guide](https://support.metamask.io/manage-crypto/move-crypto/send/how-to-send-tokens-from-your-metamask-wallet/) for how to send Ethereum from one account to another.
3333

3434
## 0x => f address
3535

@@ -74,8 +74,8 @@ If you want to transfer your FIL tokens from the `f1\f3` to the `0x` address, bu
7474
8. Once the funds appear in the burner wallet, click on **Send FIL**.
7575
9. Enter the necessary information into the text fields:
7676

77-
* In the **Recipient** field, enter your `0x` style address. GLIF automatically converts it to an `f4` address.
78-
* In the **Amount** field, enter the amount of FIL to send. Make sure you have enough FIL to cover the GAS cost.
77+
- In the **Recipient** field, enter your `0x` style address. GLIF automatically converts it to an `f4` address.
78+
- In the **Amount** field, enter the amount of FIL to send. Make sure you have enough FIL to cover the GAS cost.
7979

8080
![Fill out send detail](<../../.gitbook/assets/basics-assets-transfer-fil-send-detail-burner-wallet (1).webp>)
8181

@@ -89,6 +89,4 @@ If you are transferring FIL from any exchange to your `0x` address on MetaMask,
8989

9090
There are no special steps or requirements for sending Filecoin from one Filecoin-style address to another on the Filecoin network.
9191

92-
93-
94-
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/assets/transfer-fil)
92+
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/basics/assets/transfer-fil)

smart-contracts/developing-contracts/best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ We recommend users resubmit the message with a higher gas fee or priority fee so
3030

3131
#### **Metamask**
3232

33-
If you are building your project using MetaMask, it would be easier to educate the users to speed up a transaction by increasing the gas fee directly in MetaMask. Refer to the [official MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015489251-How-to-speed-up-or-cancel-a-pending-transaction) for more details.
33+
If you are building your project using MetaMask, it would be easier to educate the users to speed up a transaction by increasing the gas fee directly in MetaMask. Refer to the [official MetaMask documentation](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction/) for more details.
3434

3535
#### **Lotus**
3636

smart-contracts/developing-contracts/client-contract-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ First, let’s grab the kit and set up the development environment.
4747
```shell
4848
mv .env.example .env
4949
```
50-
4. Within the `.env` file, replace the example private key with your actual private key. If you are using Metamask, follow [this tutorial to get your private key](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key).
50+
4. Within the `.env` file, replace the example private key with your actual private key. If you are using Metamask, follow [this tutorial to get your private key](https://support.metamask.io/configure/accounts/how-to-export-an-accounts-private-key/).
5151

5252
{% hint style="info" %}
5353
Take precautions and never share your private key with anyone! Also make sure to not check your private key into Git. The `.gitignore` of the Hardhat kit is already set to ignore `.env` files.

smart-contracts/developing-contracts/foundry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ cd fevm-foundry-kit
3333
yarn install
3434
```
3535

36-
3. Export your private key from MetaMask. See the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key) to find out how to export your private key.
36+
3. Export your private key from MetaMask. See the [MetaMask documentation](https://support.metamask.io/configure/accounts/how-to-export-an-accounts-private-key/) to find out how to export your private key.
3737

3838
4. Create your env file by running
3939

smart-contracts/developing-contracts/verify-a-contract/web-interface/blockscout.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,4 +65,4 @@ Upon successful verification, Blockscout will display a success message and redi
6565

6666
![](../../../../.gitbook/assets/smart-contracts-developing-contracts-verify-a-contract-success-blockscout.jpg)
6767

68-
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract)
68+
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract/web-interface/blockscout)

smart-contracts/developing-contracts/verify-a-contract/web-interface/filfox.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,4 +83,4 @@ Once submitted, Filfox will process your verification request. Upon successful v
8383

8484
![](../../../../.gitbook/assets/smart-contracts-developing-contracts-verify-a-contract-verified-contract-list.jpg)
8585

86-
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract)
86+
[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/smart-contracts/developing-contracts/verify-a-contract/web-interface/filfox)

0 commit comments

Comments
 (0)