Skip to content

Commit 16c2b07

Browse files
Merge branch 'main' of https://github.com/0xPolygon/polygon-docs into cdk/erigon-setup
2 parents cc6ccd7 + ba71ea5 commit 16c2b07

File tree

32 files changed

+776
-549
lines changed

32 files changed

+776
-549
lines changed
17.6 KB
Loading
24.6 KB
Loading
14.4 KB
Loading
28.6 KB
Loading

docs/index.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -100,32 +100,32 @@ hide:
100100
</div>
101101
<p class="feature-paragraph">Deep dives only. Further your understanding of Polygon scaling technology.</p></br>
102102
</div>
103-
<a href="innovation-design" class="flex-card-item w-inline-block">
103+
<a href="cdk/agglayer/overview" class="flex-card-item w-inline-block">
104104
<div class="product-list-item-header">
105-
<div class="feature-card-heading">Innovation & design</div>
105+
<div class="feature-card-heading">AggLayer</div>
106106
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
107107
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
108108
</svg></div>
109109
</div>
110-
<p class="feature-paragraph"> Resources focused on both current and future Polygon technologies. It features detailed guides, foundational concepts, and previews of upcoming innovations. </p>
110+
<p class="feature-paragraph">Introducing the multi-chain, multi-transaction, Polygon AggLayer; what it is and how it works.</p>
111111
</a>
112-
<a href="cdk/architecture/type-1-prover/intro-t1-prover" class="flex-card-item w-inline-block">
112+
<a href="innovation-design" class="flex-card-item w-inline-block">
113113
<div class="product-list-item-header">
114-
<div class="feature-card-heading">Type 1 prover</div>
114+
<div class="feature-card-heading">Innovation & design</div>
115115
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
116116
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
117117
</svg></div>
118118
</div>
119-
<p class="feature-paragraph">The Polygon type 1 proving component used for creating proofs on your ZK-EVM chain.</p>
119+
<p class="feature-paragraph"> Resources focused on both current and future Polygon technologies. It features detailed guides, foundational concepts, and previews of upcoming innovations. </p>
120120
</a>
121-
<a href="https://polygon.technology/blog/aggregated-blockchains-a-new-thesis" class="flex-card-item w-inline-block">
121+
<a href="cdk/architecture/type-1-prover/intro-t1-prover" class="flex-card-item w-inline-block">
122122
<div class="product-list-item-header">
123-
<div class="feature-card-heading">AggLayer</div>
123+
<div class="feature-card-heading">Type 1 prover</div>
124124
<div class="arrow-embed w-embed"><svg xmlns="http://www.w3.org/2000/svg" display="block" width="100%" height="auto" viewbox="0 0 16 17" fill="none">
125125
<path d="M9.98805 5.70133L3.41071 12.2787L4.58922 13.4572L11.1666 6.87976V12.2013H12.8333V4.03467H4.66665V5.70133H9.98805Z" fill="currentColor"></path>
126126
</svg></div>
127127
</div>
128-
<p class="feature-paragraph">Introducing the multi-chain, multi-transaction Polygon Agg Layer; what it is and how it works.</p>
128+
<p class="feature-paragraph">The Polygon type 1 proving component used for creating proofs on your ZK-EVM chain.</p>
129129
</a>
130130
<a href="./innovation-design/plonky" class="flex-card-item w-inline-block">
131131
<div class="product-list-item-header">

docs/pos/concepts/transactions/meta-transactions.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -95,11 +95,11 @@ For any action that requires blockchain interaction,
9595
Steps:
9696

9797
1. Let's register our contracts to Biconomy dashboard
98-
1. Visit [Biconomy's offical docs](https://docs.biconomy.io/dashboard)
99-
2. Navigate and login to the Dashboard
100-
3. Select `Polygon Mumbai` when registering your dapp
101-
2. Copy the`API key` to use for you dapp's frontend
102-
3. And Add function `executeMetaTransaction` in Manage-Api and make sure to enable meta-tx. (Check 'native-metatx' option)
98+
1. Visit [Biconomy's offical docs](https://docs.biconomy.io/dashboard).
99+
2. Navigate and login to the Dashboard.
100+
3. Select **Polygon Amoy Testnet** when registering your dApp.
101+
2. Copy the API key to use for you dApp's frontend.
102+
3. And add function `executeMetaTransaction` in **Manage-Api** and make sure to enable meta-tx (Check **native-metatx** option).
103103

104104
- If you'd like to use your own custom API that sends signed transactions on the blockchain, you can refer to the server code here: [https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer](https://github.com/angelagilhotra/ETHOnline-Workshop/tree/master/2-network-agnostic-transfer)
105105

docs/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ let receiver = new matic.eth.Contract(JSON.parse(receiverABI), receiverAddress)
151151
152152
We're using `@maticnetwork/meta` package for the RPCs, the package isn't a requirement to run the script.
153153
154-
`matic` and `main` objects refer to the web3 object initialized with Polygon's and Ropsten's RPC respectively.
154+
`matic` and `main` objects refer to the web3 object initialized with Polygon Amoy and Sepolia network's respective RPC URLs.
155155
156156
`sender` and `receiver` objects refer to the contract objects of `Sender.sol` and `Receiver.sol` that we deployed in Step 1 and 2.
157157

docs/pos/how-to/snapshots.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,15 @@ When setting up a new sentry, validator, or full node server, it is recommended
88

99
Polygon PoS has transitioned to a community-driven model for snapshots. Active community members now contribute to provide snapshots. Some of these members include:
1010

11-
| Name | Available snapshots | Note |
12-
| -------------------------------------------------------------------- | --------------------- | -------------------------------------------- |
13-
| Stakecraft | Mainnet, Amoy, Erigon | Support for Erigon archive snapshot |
14-
| [PublicNode (by Allnodes)](https://publicnode.com/snapshots#polygon) | Mainnet, Amoy | Support for PBSS + PebbleDB enabled snapshot |
15-
| Stakepool | Mainnet, Amoy | - |
16-
| Vaultstaking | Mainnet | - |
17-
| Girnaar Nodes | Amoy | - |
11+
| Name | Available snapshots | Note |
12+
| ---------------------------------------------------------------------- | --------------------- | -------------------------------------------- |
13+
| Stakecraft | Mainnet, Amoy, Erigon | Support for Erigon archive snapshot |
14+
| [PublicNode (by Allnodes)*](https://publicnode.com/snapshots#polygon) | Mainnet, Amoy | Support for PBSS + PebbleDB enabled snapshot |
15+
| Stakepool | Mainnet, Amoy | - |
16+
| Vaultstaking | Mainnet | - |
17+
| Girnaar Nodes | Amoy | - |
18+
19+
> *\*The PBSS + PebbleDB snapshot provided by PublicNode is currently in the beta phase.*
1820
1921
!!! info "Snapshot aggregator"
2022

@@ -70,7 +72,7 @@ sudo service bor start
7072
| Metric | Calculation Breakdown | Value |
7173
| --------------------------------- | ----------------------------------- | ------- |
7274
| approx. compressed total | 250 GB (Bor) + 35 GB (Heimdall) | 285 GB |
73-
| approx. data growth daily | 10 GB (Bor) + .5 GB (Heimdall) | 10.5 GB |
75+
| approx. data growth daily | 10 GB (Bor) + 0.5 GB (Heimdall) | 10.5 GB |
7476
| approx. total extracted size | 350 GB (Bor) + 50 GB (Heimdall) | 400 GB |
7577
| suggested disk size (2.5x buffer) | 400 GB * 2.5 (natural chain growth) | 1 TB |
7678

@@ -88,7 +90,7 @@ sudo service bor start
8890
| Metric | Calculation Breakdown | Value |
8991
| --------------------------------- | ----------------------------------- | ------ |
9092
| approx. compressed total | 210 GB (Erigon) + 35 GB (Heimdall) | 245 GB |
91-
| approx. data growth daily | 4.5 GB (Erigon) + .5 GB (Heimdall) | 5 GB |
93+
| approx. data growth daily | 4.5 GB (Erigon) + 0.5 GB (Heimdall) | 5 GB |
9294
| approx. total extracted size | 875 GB (Erigon) + 50 GB (Heimdall) | 925 GB |
9395
| suggested disk size (2.5x buffer) | 925 GB * 2.5 (natural chain growth) | 2.5 TB |
9496

docs/pos/how-to/troubleshoot/technical-faqs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ and start Heimdall services again. You can refer to this [guide](../validator/pr
176176

177177
### 5. From where do I create the API key?
178178

179-
You can access this link: [https://infura.io/register](https://infura.io/register) . Make sure that once you have setup your account and project, you copy the API key for Ropsten and not Mainnet.
179+
You can access this link: [https://infura.io/register](https://infura.io/register) . Make sure that once you have setup your account and project, you copy the API key for Sepolia and not mainnet.
180180

181181
Mainnet is selected by default.
182182

docs/pos/reference/rpc-endpoints.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -117,5 +117,6 @@ Public RPCs may have rate limits or traffic restrictions. For dedicated free RPC
117117
- [4EVERLAND](https://docs.4everland.org/rpc-beta/polygon)
118118
- [SubQuery](https://subquery.network/rpc)
119119
- [Validation Cloud](https://app.validationcloud.io)
120+
- [dRPC](https://drpc.org/chainlist/polygon)
120121

121122
For a complete list of public endpoints, visit [Alchemy's Chain Connect](https://www.alchemy.com/chain-connect/chain/polygon-pos) and [Chainlist](https://chainlist.org/?search=Polygon+Mainnet).

0 commit comments

Comments
 (0)