Update contract addresses

crustio · Feb 27, 2024 · 73eaf37 · 73eaf37
1 parent 75e9573
commit 73eaf37
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 13 deletions.
diff --git a/docs/overview/introduction.md b/docs/overview/introduction.md
@@ -5,14 +5,14 @@ slug: /
 hide_table_of_contents: false
 ---
 
-EthDA is an Ethereum ZK L2 with native [EIP-4844](https://www.eip4844.com) blob-carrying transactions (Blob TX) support. This seamless interface makes EthDA a perfect fit for Alt-DA for Ethereum L2s and dStorage solution for EVM DApps.
+EthDA is a native and seamless DA network for aggregated growth of L2s. It's running as [Polygon CDK](https://polygon.technology/polygon-cdk)-based L2, with standard [EIP-4844](https://www.eip4844.com) Blobs support and Data Availability Sampling for Blob permanent storage. DA fees, paid with $ETH by Alt-DA L2s, is rewarded to L2s and their DApp users. Also, with native support of Blobs, EthDA could potentially be extended as dStorage solution for users.
 
 There are various Ethereum scaling solutions like sidechains, rollups, plasma and validium, etc, with different characteristics and trade-offs between security, decentralization, and throughput, etc. One of the most essential differences is Data Availability. Using Ethereum L1 as DA derives security from Ethereum and that's the reason why rollups are widely regarded as the only trustless scaling solution in the medium and long term. But posting L2 transaction data to L1 requires high gas consumption and may cause congestion on L1. This situation becomes even worse as L2 ecosystem prospers.
 
-The long term and canonical solution to this DA dilemma is Danksharding, and the medium term solution is EIP-4844, or Proto-Danksharding, which the Ethereum community is actively working on as part of the upcoming Cancun-Deneb upgrade. EIP-4844 introduces a new type of Blob TX that rollups could use to post their L2 transaction bundle to L1 in a gas efficient manner. Blob transaction is forwards compatible with Danksharding, and the carried Blobs will be persisted by the consensus layer for a limited period like 4 weeks.
+The long term and canonical solution to this DA dilemma is Danksharding, and the medium term solution is EIP-4844, or Proto-Danksharding, which the Ethereum community is actively working on as part of the Cancun-Deneb upgrade. EIP-4844 introduces a new type of Blob TX that rollups could use to post their L2 transaction bundle to L1 in a gas efficient manner. Blob transaction is forwards compatible with Danksharding, and the carried Blobs will be persisted by the consensus layer for a limited period like 4 weeks.
 
-However, since EIP-4844 takes time to implement and deploy (not to mention the full Danksharding), it's observed that some rollups are opting for Alt-DA solutions like Celestia, and Avail, etc. Both Celestia and Avail are separate blockchains built on top of different technical stacks and providing their own Data Availability interface.
+However, since EIP-4844 took time to implement and deploy (not to mention the full Danksharding), it's observed that some rollups are opting for Alt-DA solutions like Celestia, Avail, etc. Both Celestia and Avail are separate blockchains built on top of different technical stacks and providing their own Data Availability interface.
 
 EthDA, as a contrast, is an Ethereum native Alt-DA solution, in that:
-- EthDA itself is an Ethereum ZK validium, and is administered by a collection of smart contracts deployed on Ethereum L1
-- EthDA provides a seamless Data Availability interface as L1 to Alt-DA chain users, allowing their sequencers to pay storage fees with native $ETH
+- EthDA itself is an Ethereum ZK rollup, and is administered by a collection of smart contracts deployed on Ethereum L1
+- EthDA provides a seamless Blob-based DA interface to Alt-DA chain users, allowing their sequencers to pay storage fees with native $ETH
diff --git a/docs/resources/ethda-contracts.md b/docs/resources/ethda-contracts.md
@@ -6,10 +6,10 @@ hide_table_of_contents: false
 
 ## Devnet
 
-- CDKValidium: [0x38f83C62BE0BB7D7337E0e4d58f2A1F66F0C69D9](https://goerli.etherscan.io/address/0x38f83C62BE0BB7D7337E0e4d58f2A1F66F0C69D9)
+- CDKValidium: [0x6af6A2F1ed424097b29609CC0dD12e4812155295](https://sepolia.etherscan.io/address/0x6af6A2F1ed424097b29609CC0dD12e4812155295)
 
-- PolygonZkEVMBridge: [0x20749f9ddc416306eA6836609D13754D372b5bc7](https://goerli.etherscan.io/address/0x20749f9ddc416306eA6836609D13754D372b5bc7)
+- PolygonZkEVMBridge: [0x1d981B754EF5daA27AB0Be566a3F052c3E020186](https://sepolia.etherscan.io/address/0x1d981B754EF5daA27AB0Be566a3F052c3E020186)
 
-- PolygonZkEVMGlobalExitRoot: [0x7A054897662806990061c14236B4B9a9227e8783](https://goerli.etherscan.io/address/0x7A054897662806990061c14236B4B9a9227e8783)
+- PolygonZkEVMGlobalExitRoot: [0x54af4E46E26feAb73f9089583fF4D79a31C243eC](https://sepolia.etherscan.io/address/0x54af4E46E26feAb73f9089583fF4D79a31C243eC)
 
-- CDKDataCommittee: [0xFce6458993c81F1404835a3f385E41bB50009Dfc](https://goerli.etherscan.io/address/0xFce6458993c81F1404835a3f385E41bB50009Dfc)
+- CDKDataCommittee: [0xf35Cd7211737792D14BC6D2A992714C71C21C6D3](https://sepolia.etherscan.io/address/0xf35Cd7211737792D14BC6D2A992714C71C21C6D3)
diff --git a/sidebars.js b/sidebars.js
@@ -41,13 +41,13 @@ const sidebars = {
     },
     {
       type: 'doc',
-      id: 'overview/blobsphere',
-      label: 'Blobsphere'
+      id: 'overview/technologies',
+      label: 'Technologies'
     },
     {
       type: 'doc',
-      id: 'overview/technologies',
-      label: 'Technologies'
+      id: 'overview/blobsphere',
+      label: 'Blobsphere'
     },
     {
       type: 'html',