You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pos/get-started/becoming-a-validator.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ Bor is the Block producer node and layer for the Polygon Network. It is based on
57
57
* Blog post: [Heimdall and Bor](https://blog.polygon.technology/heimdall-and-bor/)
58
58
59
59
60
-
## Validator responsiblities
60
+
## Validator responsibilities
61
61
62
62
!!!tip "Stay in the know"
63
63
@@ -68,7 +68,7 @@ A blockchain validator is someone who is responsible for validating transactions
68
68
69
69
!!!info "Active validator limit"
70
70
71
-
Currently, there is a limit of 100 active validators at a time. For a detailed description on what a validator is, see [<ins>Validator</ins>](./getting-started.md).
71
+
Currently, there is a limit of 100 active validators at a time.
72
72
73
73
Also, after the [<ins>PIP4 governance proposal</ins>](https://forum.polygon.technology/t/pip-4-validator-performance-management/9956) is implemented on the contract-level, the minimum staking amount will increase to 10,000 MATIC.
<p>Your browser does not support the video element.</p>
174
174
</video> -->
175
175
@@ -183,7 +183,7 @@ Check if you have funds on the Main Ethereum Network, to delegate your tokens. A
183
183
184
184
You just need to access **https://staking.polygon.technology/**, where you will see the following landing page:
185
185
186
-

186
+

187
187
188
188
189
189
@@ -196,13 +196,13 @@ It depends on your understanding and research on which validator you would want
196
196
To unbond from a validator, navigate to MyAccount, where you find **Your Delegations**.
197
197
There you will see an **Unbond** button for each of the validators. Click on the **Unbond** button for whichever validator that you want to unbond from.
<p>Your browser does not support the video element.</p>
291
291
</video>
292
292
@@ -296,7 +296,7 @@ Please watch the video for a graphical illustration of how this works:
296
296
We have recently upgraded the wallet support to WalletConnect v2.0. Now you can choose from a plethora of wallets, including Metamask, Coinbase, and others, on both desktop and mobile devices to log in.
@@ -311,14 +311,14 @@ Staking through Binance is not yet supported. There will be an announcement if a
311
311
312
312
Once you have completed your delegation, wait for 12 block confirmations on Ethereum (approx. 3-5 minutes), then on the Dashboard, you can click on **My Account**.
313
313
314
-

314
+

315
315
316
316
317
317
### Where can I check my rewards?
318
318
319
319
On the Dashboard, you can click on the **My Account** option on the left-hand side.
320
320
321
-

321
+

322
322
323
323
324
324
### Do I need ETH to pay for gas fees?
@@ -355,7 +355,7 @@ Rewards will be higher, to begin with, and will keep decreasing as the locked su
355
355
356
356
You can claim your rewards instantly by clicking on the **Withdraw Reward** button. This will transfer the rewards accumulated to your delegated account on Metamask.
<p>Your browser does not support the video element.</p>
391
391
</video>
392
392
@@ -441,7 +441,7 @@ The Claim Stake button will only be enabled when your unbonding period is comple
441
441
442
442
Under the **Claim Stake** button you should see a note on how many checkpoints are pending before the **Claim Stake** button is enabled. Every checkpoint takes approximately 30 minutes. However, some checkpoints could be delayed upto ~1 hour due to congestion on Ethereum.
Copy file name to clipboardExpand all lines: docs/pos/how-to/full-node/full-node-binaries.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
2
-
This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [Minimum Technical Requirements](../validator/validator-node-system-requirements.md) guide.
2
+
This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [Minimum Technical Requirements](../validator/validator-system-requirements.md) guide.
Copy file name to clipboardExpand all lines: docs/pos/how-to/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,4 +33,4 @@ Depending on the extent to which you're looking to participate in different netw
33
33
34
34
Included in the section is an elaborate startup guide for users who wish to implement the Polygon DID, which is a three-part package consisting of an identity-registrar, identity-resolver, and identity-registry-contract.
35
35
36
-
*[Polygon DID integration guide](polygon-did/)
36
+
*[Polygon DID integration guide](./polygon-did.md)
Copy file name to clipboardExpand all lines: docs/pos/how-to/operate-maintain-node/validator-commission-operations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ A validator is entitled to charge any commission rate. The minimum commission wo
5
5
6
6
You are allowed to change the commission rates as many times as you would like.
7
7
8
-
As a validator, it is one of your responsibilities to inform the community on commission changes. See [Validator Responsibilities](../../operate-node/validator/responsibilities.md).
8
+
As a validator, it is one of your responsibilities to inform the community on commission changes. See [Validator Responsibilities](../../get-started/becoming-a-validator.md#validator-responsibilities).
Copy file name to clipboardExpand all lines: docs/pos/how-to/snapshots.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ When setting up a new sentry, validator, or full node server, it is recommended
11
11
12
12
## Client snapshots
13
13
14
-
To begin, ensure that your node environment meets the **prerequisites** outlined [here](https://docs.polygon.technology/pos/operate-node/operate/full-node-binaries/). Before starting any services, execute the shell script provided below. This script will download and extract the snapshot data, which allows for faster bootstrapping. In our example, we will be using an Ubuntu Linux m5d.4xlarge machine with an 8TB block device attached.
14
+
To begin, ensure that your node environment meets the **prerequisites** outlined [here](/pos/how-to/full-node/full-node-binaries). Before starting any services, execute the shell script provided below. This script will download and extract the snapshot data, which allows for faster bootstrapping. In our example, we will be using an Ubuntu Linux m5d.4xlarge machine with an 8TB block device attached.
15
15
To transfer the correct chaindata to your disk, follow these steps:
16
16
17
17
- All one has to do is specify the network ("mainnet" or "mumbai") and client type ("heimdall" or "bor" or "erigon") of your desired snapshot and run the following command:
Copy file name to clipboardExpand all lines: docs/pos/how-to/troubleshoot/known-issues.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ If restarting both the Bor and Heimdall services doesn't solve the problem, it c
50
50
51
51
The bad block is typically displayed in the logs as shown in the below figure:
52
52
53
-

53
+

54
54
55
55
- Note the bad block number.
56
56
- Convert the block number to a hexadecimal number.
@@ -102,13 +102,13 @@ If the node throws these logs, check the following:
102
102
103
103
Inspect the block number to identify if you are running on the right fork. One way to do this is to search for the block number on an explorer like [PolygonScan](https://polygonscan.com/).
104
104
105
-

105
+

106
106
107
107
If the hashes match, then the node is on the right fork.
108
108
109
109
### Log: Error dialing seed
110
110
111
-
- Check whether your Heimdall node is configured with the latest seeds as listed on the [node setup documents](../../operate/full-node-binaries.md).
111
+
- Check whether your Heimdall node is configured with the latest seeds as listed on the [node setup documents](../full-node/full-node-binaries.md).
112
112
113
113
If you're still encountering the error, after either updating to the latest seeds or confirming that you are using the right seeds, you may need to clear the `addrbook.json` file. To do this, follow the steps below.
0 commit comments