![]({useBaseUrl("img/knowledge-base/bad_block.png")}/)
+- Check if everything is working correctly.
-Once you know the Bad block number, you could roll back your Blockchain by a few hundred blocks and resync from a previous block. In order to do this, you will first need to convert the Block number to hexadecimal. You can use [this tool](https://www.rapidtables.com/convert/number/decimal-to-hex.html) for converting decimals to hexadecimals.
+- Additionally, check your REST server logs,
+
+ ```bash
+ journalctl -u heimdalld-rest-server -f
+ ```
-Once you have your Hexadecimal ready, you can run the following commands;
+- Restart the services not running.
+
+ This should cause Bor to automatically resolve the problem
+
+
+If restarting both the Bor and Heimdall services doesn't solve the problem, it could be that Bor is stuck on some block.
+
+**Solution 3**: Check the bad block in logs for Bor.
+
+- Check Bor logs with this command
+ ```bash
+ journalctl -u bor -f
+ ```
+
+ The bad block is typically displayed in the logs as shown in the below figure:
+
+
+
+- Note the bad block number.
+- Convert the block number to a hexadecimal number.
+
+!!!info
+
+ Use this [tool](https://www.rapidtables.com/convert/number/decimal-to-hex.html) to convert the block number to a hexadecimal number.
+
+
+- Roll back the Blockchain by a few hundred blocks. That is, set Bor at the right block height, with the `debug.setHead()` function. Use the following command
```bash
-bor attach ./.bor/data/bor.ipc
-> debug.setHead("0xE92570")
+ bor attach ./.bor/data/bor.ipc
+ > debug.setHead("0xE92570")
```
-`debug.setHead()` is the function that will allow your Bor to set the tip at a particular Block height.
+The `debug.setHead()` function allows Bor to set the tip at a particular block height, resyncing from a previous block.
-Once you run these commands, the output for this would be `null` . Null means good and it is intended. You can now start monitoring your logs for Bor again and see if it passes that block number.
+A successful output of the above command is a `null`. Once this is achieved, monitoring of the Bor can resume and see if the blochain goes passed the previously bad block number.
-If in any case, none of these solutions work for you, please contact the Polygon Support team immediately.
+If none of these solutions works for you, please contact the Polygon Support team immediately.
### Log: Error validating checkpoint module=checkpoint startBlock
-If your node throws up these logs, please check the following:
+If the node throws these logs, check the following:
-- Ensure that the **Bor node is in sync**. To check, run the following command:
+- Check if the Bor node is in sync by running the following command
```bash
bor attach .bor/data/bor.ipc
eth.syncing
```
- If the output is **false**, then the Bor node is in sync.
+ If the output is "false", then the Bor node is in sync.
-- Another possible cause of this issue is that **your node might be on the wrong fork**. To check, run the following command to find the current block on your node:
+- Check if the Bor node is on the wrong fork by running this command
```bash
bor attach .bor/data/bor.ipc
@@ -67,24 +100,25 @@ If your node throws up these logs, please check the following:
eth.getBlockByNumber("![]({useBaseUrl("img/knowledge-base/block_number.png")}/)
+ 
If the hashes match, then the node is on the right fork.
### Log: Error dialing seed
-Please check whether your Heimdall node is configured with the latest seeds as listed on the [node setup documents](../../operate/full-node-binaries.md).
+- Check whether your Heimdall node is configured with the latest seeds as listed on the [node setup documents](../../operate/full-node-binaries.md).
+
+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.
-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.
1. Open the `config.toml` file in your terminal: ```vi /var/lib/heimdall/config/config.toml```
2. Stop `heimdalld` service: ```sudo service heimdalld stop```
3. Clear your `addrbook`
-
+
```
sudo service heimdalld stop
cp /var/lib/heimdall/config/addrbook.json /var/lib/heimdall/config/addrbook.json.bkp
@@ -92,17 +126,22 @@ If you're still encountering the error after either updating to the latest seeds
```
4. Increase `max_num_inbound_peers` and `max_num_outbound_peers` in `/var/lib/heimdall/config/config.toml`:
-
+
```
max_num_inbound_peers = 300
max_num_outbound_peers = 100
```
-5. Start `heimdalld` service: ```sudo service heimdalld start```
+5. Start `heimdalld` service with the following command
+
+ ```bash
+ sudo service heimdalld start
+ ```
+
### Log: Demoting invalidated transaction
-This log is not an error. It is a process in **txpool** which rearranges the transactions and removes some of them (as per specific conditions).
+This log is not an error but a process in the transactinos pool `txpool` which rearranges the transactions and removes some of them (as per specified conditions).
It should in **no way affect the checkpointing mechanism**.
@@ -162,6 +201,7 @@ Check if your Heimdall Bridge is running or not or if it has any errors in the l
This typically means that your Sentry Heimdall is running into issues.
**Solution:**
+
- Check your Sentry Heimdall and see if the service is running fine.
- If the service is stopped then restarting the service on your Sentry should resolve this issue.
- Similarly, after fixing your sentry, a restart of your Heimdall service should also resolve the problem.
@@ -462,36 +502,37 @@ To fix this issue, the signer address that is used to mine must be added inside
Please use the below steps:
1. Check your Bor data size before pruning
-
-```bash
-du -sh /usr/bin/bor
-```
+
+ ```bash
+ du -sh /usr/bin/bor
+ ```
2. Stop Bor
+
+ ```bash
+ sudo service bor stop
+ ```
-```bash
-sudo service bor stop
-```
-
-3. Start **tmux** to ensure that even if your SSH connection is reset, the process is running on the remote machine
-tmux.
-
-4. Start pruning
-
-```bash
-sudo bor snapshot prune-state --datadir /usr/bin/bor
-```
+3. Start `tmux` to ensure that even if your SSH connection is reset, the process is running on the remote machine
+`tmux`.
-The default --datadir is `/usr/bin/bor`.
+4. Start pruning.
+
+ ```bash
+ sudo bor snapshot prune-state --datadir /usr/bin/bor
+ ```
-5. Once the pruning is completed, you will see success logs and details. Then start Bor again:
+ The default --datadir is `/usr/bin/bor`.
-```bash
-sudo service bor start
-```
+5. Once the pruning is completed, you will see success logs and details. Then start Bor again.
+
+ ```bash
+ sudo service bor start
+ ```
-6. Check your Bor data size after pruning:
-```bash
-du -sh /usr/bin/bor
-```
+6. Check your Bor data size after pruning.
+
+ ```bash
+ du -sh /usr/bin/bor
+ ```
diff --git a/docs/pos/operate-node/validator/staking-faq.md b/docs/pos/operate-node/validator/staking-faq.md
index 45f80bc93..67581faa0 100644
--- a/docs/pos/operate-node/validator/staking-faq.md
+++ b/docs/pos/operate-node/validator/staking-faq.md
@@ -1,4 +1,14 @@
+### What is the Staking Dashboard URL?
+
+The staking dashboard URL is https://staking.polygon.technology/.
+
+
+### What is the minimum stake amount?
+
+There is no minimum stake amount to delegate. However, you can always start with 1 MATIC token.
+
+
### How to stake tokens on Polygon?
For Staking you would need to have funds on the Ethereum Mainnet (more information [here](https://etherscan.io/gastracker)). Log into your wallet on the Ethereum network using the Staking Dashboard. https://staking.polygon.technology/
@@ -11,6 +21,13 @@ Please watch this video for a graphical illustration of how this works:
+### Why does my transaction take so long?
+
+All staking transactions of Polygon happen on Ethereum for security reasons.
+The time taken to complete a transaction depends on the gas fees that you have allowed, and the network congestion on Ethereum at that time.
+The “Speed Up” option is to increase the gas fees you are willing to spend.
+
+
### I've staked my Matic tokens. How can I stake more?
You can navigate to "Your Delegations", choose one of the stakes and click on "Stake More".
@@ -185,6 +202,7 @@ Please watch the video for a graphical illustration of how this works:
Your browser does not support the video element.
+ ### Which browsers are compatible with the staking dashboard? Chrome, Firefox, and Brave. diff --git a/docs/pos/operate-node/validator/technical-faqs.md b/docs/pos/operate-node/validator/technical-faqs.md index 36fe8e16a..daaebacf4 100644 --- a/docs/pos/operate-node/validator/technical-faqs.md +++ b/docs/pos/operate-node/validator/technical-faqs.md @@ -267,7 +267,7 @@ Check the value of catching_up. If it is false then the node is all synced up. ### 15. If someone becomes a top 10 staker, how do they receive their MATIC reward? -Stage 1 rewards are not based on stake. Please refer to this document [here](../../how-to/operating/validator-node/rewards.md) for the reward details. Participants with high stake don't automatically qualify for a reward in this stage. +Stage 1 rewards are not based on stake. Participants with high stake don't automatically qualify for a reward in this stage. ### 16. What should the Heimdall version be? diff --git a/docs/zkEVM/get-started/historical-data.md b/docs/zkEVM/get-started/historical-data.md new file mode 100644 index 000000000..2220b26be --- /dev/null +++ b/docs/zkEVM/get-started/historical-data.md @@ -0,0 +1,231 @@ +Find in here a record of the zkEVM’s historical data. This document records timelines, major milestones, forks, and updates to the zkEVM. + +Join discussions or ask questions on Telegram: https://t.me/polygonzkevm_technical_updates/31 + + +### 13th Dec, 2023 + +**zkEVM mainnet update** + +This update included a reduced number of RPC logs and aligned error messages to match geth error messages pertaining to gas estimation for unsigned transactions. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.4.4 | +| Prover | v3.0.2 | +| Bridge | v0.3.1 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.4 | + + + +### 23rd Nov, 2023 + +**zkEVM mainnet update** + +The changes made in this update were mainly in the node (Additional CORS header fix and features in v0.4.0). + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.4.1 | +| Prover | v3.0.2 | +| Bridge | v0.3.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.1 | + +Infrastructure partners were instructed to update, and then use instructions given here (https://polygontechnology.notion.site/Instructions-zkEVM-Mainnet-Node-v0-4-1-Prover-v3-0-2-7a585f394cd24b90b90283086276533c) + + + +### 21st Nov, 2023 + +**zkEVM mainnet update** + +This update brought several significant changes to zkEVM node, bridge, prover infrastructure, including changes to RPC, sequencer, synchroniser, database. It also includes WS improvements, along with other fixes. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.4.0 | +| Prover | v3.0.2 | +| Bridge | v0.3.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.4.0 | + + + +### 9th Nov, 2023 + +**zkEVM mainnet upgrade: Incaberry hardfork** + +The changes made in this update brought cryptographic optimisations and bug fixes to Polygon zkEVM mainnet. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.3 | +| Prover | v3.0.0 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.3 | + + + +### 7th Nov, 2023 + +**zkEVM mainnet: Upcoming Incaberry hardfork preparation** + +The changes made in this update were the node and prover versions, as well as updates to the RPC, sequencer, and synchroniser. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.3 | +| Prover | v3.0.0 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.3 | + + + +### 24th Oct, 2023 + +**zkEVM testnet upgrade: Incaberry hardfork** + +The changes made in this upgrade were cryptographic optimisations and some bug fixes. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.2 | +| Prover | v3.0.0 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.2 | + + + +### 26th Sep, 2023 + +**Mainnet beta update** + +The changes made in this update were new version updates of the prover and node. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.1 | +| Prover | v2.2.2 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.1 | + + +### 20th Sep, 2023 + +**Mainnet beta Dragonfruit (ForkID5) upgrade** + +The changes made in this update were a range of improvements to the network, including support for the latest Ethereum opcode, PUSH0. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.0 | +| Prover | v2.2.0 | +| Bridge | v0.2.0 | +| Change logs url | https://www.notion.so/polygontechnology/Mainnet-Beta-UPDATE-zkEVM-Node-version-0-3-0-Sep-6-e150867951cd46c088f6d6c03b2cb5db | + + + +### 18th Sep, 2023 + +**Mainnet beta event** + +The main changes made in this update were the mainnet beta rehashing and L2 bridge resync. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.0 | +| Prover | v2.2.0 | +| Bridge | v0.2.0 | +| Change logs url | https://www.notion.so/polygontechnology/zkEVM-mainnet-beta-Instructions-for-permissionless-nodes-to-rehash-the-network-53b525498bc94c03ab02bba621f8d8e3 | + + + +### 6th Sep, 2023 + +**zkEVM mainnet beta update** + +The changes made in this update were new versions of the node and prover. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.3.0 | +| Prover | v2.2.0 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.3.0 | + + + +### 31st Aug, 2023 + +**zkEVM mainnet update** + +The changes made in this update were new versions of the node and the prover. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.2.5 | +| Prover | v2.1.2 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.2.5 | + + + +### 27th Jul, 2023 + +**zkEVM mainnet beta update** + +The changes made in this update were version upgrades for the prover, node and bridge. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.2.0 | +| Prover | v2.0.1 | +| Bridge | v0.2.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.2.0 | + + + +### 8th Jun, 2023 + +**Mainnet beta update** + +The changes made in this update are detailed in the `change logs`. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.1.2 | +| Prover | v1.1.4-fork.4 | +| Bridge | v0.1.0 | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/v0.1.2 | + + +### 2nd May, 2023 + +**First node update** + +Corresponding commits found here https://github.com/0xPolygonHermez/zkevm-node/tree/v0.0.7 + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.0.7 | +| Prover | - | +| Bridge | - | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.0.7 | + + + +### 25th Apr, 2023 + +**Mainnet update** + +The changes made in this update were new versions of the node and prover containers. The prover had some new config parameters. + +| | Version | +| :-------------: | :----------------------------------------------------------: | +| Node | v0.0.6 | +| Prover | - | +| Bridge | - | +| Change logs url | https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.0.6. | + + + +Telegram: https://t.me/polygonzkevm_technical_updates/31 diff --git a/mkdocs.yml b/mkdocs.yml index f44c00462..2bddd4e78 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -88,7 +88,7 @@ nav: - Activate forced transactions: zkEVM/get-started/deploy-zkevm/activate-forced-transactions.md - Setup a Goërli node: zkEVM/get-started/deploy-zkevm/setup-goerli-node.md - Sync state with snapshots: zkEVM/get-started/state-sync-snapshots.md - # - Sync state with snapshots: zkEVM/get-started/state-sync-snapshots.md + - Historical data: zkEVM/get-started/historical-data.md - How to: - How to: zkEVM/how-to/index.md - Write a contract: zkEVM/how-to/write-contract.md @@ -298,7 +298,7 @@ nav: # - Validator performance: pos/operate-node/validator/validator-performance-overview.md - Troubleshooting: - Validator performance: pos/operate-node/validator/validator-performance.md - - Staking FAQs: pos/operate-node/validator/staking-faq.md + # - Staking FAQs: pos/operate-node/validator/staking-faq.md - Technical FAQs: pos/operate-node/validator/technical-faqs.md - Known issues and errors: pos/operate-node/validator/kb/known-issues.md - Reporting issues: pos/operate-node/validator/issues/reporting-issues.md