diff --git a/gitbook/SUMMARY.md b/gitbook/SUMMARY.md index 113c071..4879b8d 100644 --- a/gitbook/SUMMARY.md +++ b/gitbook/SUMMARY.md @@ -17,9 +17,9 @@ * [📜 Data Availability](general-layer-2-knowledge/data-availability/README.md) * [⚪ Light/client and full nodes](general-layer-2-knowledge/data-availability/light-client-and-full-nodes.md) * [❌ Fault Proofs](general-layer-2-knowledge/data-availability/fault-proofs.md) - * [🏄♂ Onchain Data Availablity](general-layer-2-knowledge/data-availability/onchain-data-availablity/README.md) - * [📄 EIP-4844](general-layer-2-knowledge/data-availability/onchain-data-availablity/eip-4844.md) - * [🧫 Data Availability Sampling](general-layer-2-knowledge/data-availability/onchain-data-availablity/data-availability-sampling.md) + * [🏄♂ Onchain Data Availability](general-layer-2-knowledge/data-availability/onchain-data-availability/README.md) + * [📄 EIP-4844](general-layer-2-knowledge/data-availability/onchain-data-availability/eip-4844.md) + * [🧫 Data Availability Sampling](general-layer-2-knowledge/data-availability/onchain-data-availability/data-availability-sampling.md) * [🕊 Offchain Data Availability](general-layer-2-knowledge/data-availability/offchain-data-availability/README.md) * [⚙ General Purpose DACs Mechanism](general-layer-2-knowledge/data-availability/offchain-data-availability/general-purpose-dacs-mechanism.md) * [📚 Sources and Extra Material](general-layer-2-knowledge/data-availability/offchain-data-availability/sources-and-extra-material.md) diff --git a/gitbook/api.md b/gitbook/api.md index 1e83964..dd369c1 100644 --- a/gitbook/api.md +++ b/gitbook/api.md @@ -24,7 +24,7 @@ This endpoint returns all labeled contracts for all our covered chains. It inclu v1/contracts.json ``` -#### Sample Reponse +#### Sample Response ```json [ diff --git a/gitbook/developer-content/rollup-performance/README.md b/gitbook/developer-content/rollup-performance/README.md index a1da748..1170871 100644 --- a/gitbook/developer-content/rollup-performance/README.md +++ b/gitbook/developer-content/rollup-performance/README.md @@ -11,7 +11,7 @@ description: >- To grasp the best understanding of Performance metrics of Rollups we suggest that you read the following sections in our wiki: -[data-availability](../../general-layer-2-knowledge/data-availability/ "mention");[onchain-data-availablity](../../general-layer-2-knowledge/data-availability/onchain-data-availablity/ "mention") +[data-availability](../../general-layer-2-knowledge/data-availability/ "mention");[onchain-data-availability](../../general-layer-2-knowledge/data-availability/onchain-data-availability/ "mention") [transaction-costs](../transaction-costs/ "mention"); [what-eip-4844-means-for-layer-2s.md](../transaction-costs/what-eip-4844-means-for-layer-2s.md "mention") diff --git a/gitbook/developer-content/transaction-costs/optimistic-vs.-zero-knowledge-rollups.md b/gitbook/developer-content/transaction-costs/optimistic-vs.-zero-knowledge-rollups.md index a832da0..38c544e 100644 --- a/gitbook/developer-content/transaction-costs/optimistic-vs.-zero-knowledge-rollups.md +++ b/gitbook/developer-content/transaction-costs/optimistic-vs.-zero-knowledge-rollups.md @@ -17,7 +17,7 @@ -### **ZK-Rollups (e.g. zkSync Era, Ploygon zkEVM)**: +### **ZK-Rollups (e.g. zkSync Era, Polygon zkEVM)**: * **Mechanism**: These use validity proofs, specifically ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Argument of Knowledge), to ensure the correctness of transactions. * **Cryptographic Proofs**: Each batch includes a ZK-SNARK, which cryptographically proves that the post-state root is the correct outcome of executing the batch. diff --git a/gitbook/developer-content/transaction-costs/what-eip-4844-means-for-layer-2s.md b/gitbook/developer-content/transaction-costs/what-eip-4844-means-for-layer-2s.md index 20485b9..ac6b095 100644 --- a/gitbook/developer-content/transaction-costs/what-eip-4844-means-for-layer-2s.md +++ b/gitbook/developer-content/transaction-costs/what-eip-4844-means-for-layer-2s.md @@ -1,6 +1,6 @@ # 🖼 What EIP 4844 means for Layer 2s -Just like discussed in the context of [onchain-data-availablity](../../general-layer-2-knowledge/data-availability/onchain-data-availablity/ "mention") options, EIP 4844 introduces a new Ethereum transaction format the 'BLOB\_TX\_TYPE', designed specifically for short-term data storage in a more affordable manner. +Just like discussed in the context of [onchain-data-availability](../../general-layer-2-knowledge/data-availability/onchain-data-availability/ "mention") options, EIP 4844 introduces a new Ethereum transaction format the 'BLOB\_TX\_TYPE', designed specifically for short-term data storage in a more affordable manner. ## **What are Blobs?** diff --git a/gitbook/developer-content/which-layer-2-approach-is-for-you/plasma.md b/gitbook/developer-content/which-layer-2-approach-is-for-you/plasma.md index 666f3c7..20e82e9 100644 --- a/gitbook/developer-content/which-layer-2-approach-is-for-you/plasma.md +++ b/gitbook/developer-content/which-layer-2-approach-is-for-you/plasma.md @@ -95,6 +95,6 @@ Due to its lower capital requirements and ability to handle a diverse range of t 2. [**Minimal Viable Plasma - Ethereum Research**](https://ethresear.ch/t/minimal-viable-plasma/426) **Jan 2018**: This resource provides a specification for a minimal viable plasma implementation, discussing its basic security properties and functionalities. 3. [**Plasma MVP - Learn Plasma**](https://www.learnplasma.org/en/learn/mvp.html)**:** This page offers an overview of More Viable Plasma (MoreVP), an extension to Minimal Viable Plasma, and explains how Plasma MVP operates. 4. [**Plasma Cash**](https://ethresear.ch/t/plasma-cash-plasma-with-much-less-per-user-data-checking/1298) **Mar 2018**: A specific variant of the Plasma framework, designed to enhance the scalability and security -5. [**Plasma Cashflow**](https://hackmd.io/DgzmJIRjSzCYvl4lUjZXNQ?view#%F0%9F%9A%AA-Exit) **Summer 2018**: Outlines Plasma Cashflow as an adaptation of Plasma Cash, involving depositing, transacting, and exiting a specific blockchain chain.Also Mentions ways to address the costs associated with validating tokens, such as using zkSNARKs or Plasma XT-style checkpointing. +5. [**Plasma Cashflow**](https://hackmd.io/DgzmJIRjSzCYvl4lUjZXNQ?view#%F0%9F%9A%AA-Exit) **Summer 2018**: Outlines Plasma Cashflow as an adaptation of Plasma Cash, involving depositing, transacting, and exiting a specific blockchain chain. Also Mentions ways to address the costs associated with validating tokens, such as using zkSNARKs or Plasma XT-style checkpointing. 6. [**Plasma Prime**](https://ethresear.ch/t/plasma-prime-design-proposal/4222) **Nov 2018:** This proposal delves into the utilization of the UTXO model for defining asset ownership, the mechanics of RSA proofs for transaction inclusion and exclusion within specified segments, the detailed structure of Plasma blocks 7. [**Exit games for EVM Validiums: The return of Plasma**](https://vitalik.eth.limo/general/2023/11/14/neoplasma.html) **Nov 2023:** The article revisits Plasma in light of advancements in validity proofs, such as ZK-SNARKs, which could address Plasma's main challenges, especially in managing client-side data storage. It explores potential extensions of Plasma to the EVM with parallel UTXO graphs and total state exiting diff --git a/gitbook/developer-content/which-layer-2-approach-is-for-you/validiums.md b/gitbook/developer-content/which-layer-2-approach-is-for-you/validiums.md index 14d2c6c..0777240 100644 --- a/gitbook/developer-content/which-layer-2-approach-is-for-you/validiums.md +++ b/gitbook/developer-content/which-layer-2-approach-is-for-you/validiums.md @@ -1,7 +1,7 @@ # 🔐 Validiums {% hint style="info" %} -Validiums can not be considered as Layer 2 per se. When we talk about Validiums we are talking from the Data Avalability point of view. +Validiums can not be considered as Layer 2 per se. When we talk about Validiums we are talking from the Data Availability point of view. {% endhint %} It is an approach that different Layer 2s can take towards their Data Availability concerns. To read more about this, go to our more detailed breakdown in General Layer 2 Knowledge [data-availability](../../general-layer-2-knowledge/data-availability/ "mention") @@ -61,6 +61,6 @@ Celestia, Polygon Avail, and EigenDA * Scale-demanding applications where security isn't an issue * Non-financial apps * Gaming -* Centerally-governed Ecosystems +* Centrally-governed Ecosystems ## diff --git a/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/README.md b/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/README.md similarity index 95% rename from gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/README.md rename to gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/README.md index 9cbeda8..67940b3 100644 --- a/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/README.md +++ b/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/README.md @@ -1,4 +1,4 @@ -# 🏄♂ Onchain Data Availablity +# 🏄♂ Onchain Data Availability ## Onchain :man\_surfing::chains: diff --git a/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/data-availability-sampling.md b/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/data-availability-sampling.md similarity index 100% rename from gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/data-availability-sampling.md rename to gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/data-availability-sampling.md diff --git a/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/eip-4844.md b/gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/eip-4844.md similarity index 100% rename from gitbook/general-layer-2-knowledge/data-availability/onchain-data-availablity/eip-4844.md rename to gitbook/general-layer-2-knowledge/data-availability/onchain-data-availability/eip-4844.md diff --git a/gitbook/op-chains/chain-knowledge/base.md b/gitbook/op-chains/chain-knowledge/base.md index 51bf1e4..3455216 100644 --- a/gitbook/op-chains/chain-knowledge/base.md +++ b/gitbook/op-chains/chain-knowledge/base.md @@ -36,7 +36,7 @@ Check 👇 for more dapps and platforms on base [Base | Ecosystem](https://base.org/ecosystem?tag=all) -You might also want to follow [@Base\_Explorer](https://x.com/Base\_Explorer/) for updates, facts and info in the ecpsystem and +You might also want to follow [@Base\_Explorer](https://x.com/Base\_Explorer/) for updates, facts and info in the ecosystem and {% embed url="https://x.com/Base_Explorer/status/1690679583467778048?s=20" %} @@ -96,7 +96,7 @@ To go head-on into the documentation and the boot camp to build your dapp, here You might want to look at some of our charts to help you make your financial decisions -PS; As of now there is no token for Base, but there is already some other ways to invest in the platforms built on Base +PS; As of now there is no token for Base, but there are already some other ways to invest in the platforms built on Base #### Onchain Profit