Merge pull request #28 from airchains-network/fix/sidebar-patch-1

fix/sidebar-patch-1 --> fix/sidebar

Author: SlayeR6889

.github/workflows/deploy.yml

@@ -0,0 +1,26 @@
+name: Auto Deploy Airchains Docs
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+
+      - name: Deploy to Server
+        uses: appleboy/ssh-action@master
+        with:
+          host: 148.113.38.220
+          username: ubuntu
+          key: ${{ secrets.DEPLOY_SSH_KEY }}
+          script: |
+            echo "🚀 Starting remote deployment..."
+            chmod +x /home/ubuntu/deploy.sh
+            /home/ubuntu/deploy.sh
+            echo "✅ Deployment complete!"

docs/data-availability/index.md

@@ -2,4 +2,41 @@
 id: data-availability
 title: Data Availability
 sidebar_position: 6
+slug: /concepts/data-availability
 ---
+
+# Data Availability
+
+## What is Data Availability
+
+Data availability addresses the issue of whether specific data has been released into a blockchain network. This aspect becomes especially significant when a network node comes across a new block proposed for addition to the blockchain. At this juncture, it's the node's duty to gather all transaction data within this new block. Successfully obtaining this transaction data is critical for the node; it verifies that the data has been effectively spread throughout the network. In essence, if a node manages to retrieve and download all the transaction data from the incoming block, it affirms that data availability is upheld, confirming that the block's data has been properly published and is accessible across the network.
+
+In blockchain systems, especially in scaling solutions like rollups or sidechains, only a summary of the data might be posted to the main chain (like Ethereum), with the detailed data hosted off-chain or on a secondary layer. Ensuring data availability in these scenarios is crucial because:
+
+- **Security**: If data is unavailable, even temporarily, it can lead to security vulnerabilities. Nodes or validators must have access to complete data to validate transactions and maintain the integrity of the blockchain.
+
+- **Decentralization**: Full data availability supports the decentralized nature of blockchain technology. It prevents central points of control or failure and ensures that all participants can independently verify the state of the network.
+
+- **Trustlessness**: In a trustless environment like blockchain, participants shouldn't need to rely on a third party to assert that the data is correct. Availability allows participants to independently verify data.
+
+## How Data Availability Works on Airchains
+
+In of our blockchain system, the Data Availability (DA) layer functions as a critical intermediary, ensuring the seamless and secure settlement of transaction batches within the settlement layer. This layer plays a pivotal role in maintaining the integrity and availability of data, a cornerstone in our blockchain's operational framework.
+
+### 1. Building a Robust Connection
+
+The process begins with the DA layer establishing a robust connection between the execution and settlement layers. This connection is not just a mere linkage; it's a crucial bridge ensuring the continuous and reliable availability of data across different segments of the blockchain. This step is fundamental in maintaining the coherence and integrity of the blockchain's state across its various layers.
+
+### 2. Requesting and Validating Data
+
+The DA layer then proceeds to perform a series of critical validation checks. It requests the state root of the execution layer along with the compressed transaction hash and other relevant metadata. The state root serves as a cryptographic representation of the entire state of the execution chain at a given point in time. By verifying the state root, the DA layer confirms the validity and consistency of the execution chain's state, an essential aspect in ensuring the integrity of the blockchain.
+
+### 3. Storing and Referencing Transaction Data
+
+In parallel, the DA layer stores the compressed transaction hash within its own framework. This stored data becomes a reference point, available for future validation and verification processes. It acts as an immutable record, confirming whether specific transaction data was available at a certain point in time. This aspect of the DA layer's functionality is vital for maintaining transparency and trust in the blockchain network.
+
+### 4. Finalizing the Settlement Process
+
+Upon successful completion of these validation checks, the DA layer provides a crucial piece of information - the block height in the case of Celestia-based systems, and the transaction hash in the case of Avail-based systems. This information is not just a confirmation but also a marker of a successful transaction settlement. It signifies the completion of a critical phase in the transaction lifecycle and the readiness of the batch for integration into the blockchain ledger.
+
+The DA layer, through these meticulously executed steps, reinforces the security, transparency, and efficiency of our blockchain system. It ensures that every transaction batch settled in the settlement layer is not only valid and consistent but also readily available and verifiable. This layer's role is a testament to our commitment to maintaining a blockchain environment that is both robust and trustworthy, aligning with the highest standards of data integrity and availability.

docs/intro-to-zkfhe/index.md

@@ -3,4 +3,9 @@ id: intro-to-zkfhe
 title: Intro to zkFHE
 description: Introduction to Zero-Knowledge Fully Homomorphic Encryption
 sidebar_position: 3
----
+slug: /concepts/intro-to-zkfhe
+---
+
+import IntroToZKFHE from '@site/src/components/Docs/intro-to-zkfhe.js';
+
+<IntroToZKFHE />

docs/introduction.md

@@ -0,0 +1,17 @@
+---
+sidebar_position: 1
+# id : introduction
+slug: /introduction
+---
+
+# Introduction
+
+<img
+    src="/img/introduction.jpg"
+    alt="Introduction"
+    className="intro_image"
+/>
+
+import IntroductionComponent from '@site/src/components/Docs/introduction.js';
+
+<IntroductionComponent />

docs/overview.md

@@ -21,7 +21,7 @@ const sidebars = {
   tutorialSidebar: [
     {
       type: "doc",
-      id: "overview",
+      id: "introduction",
       className: "custom-sidebar-item",
     },
     {
@@ -37,6 +37,10 @@ const sidebars = {
       type: "category",
       label: "Intro to zkFHE",
       className: "custom-sidebar-item",
+      link: {
+        type: "doc",
+        id: "intro-to-zkfhe/intro-to-zkfhe",
+      },
       items: [
         "intro-to-zkfhe/zk-proofs",
         "intro-to-zkfhe/fully-homomorphic-encryption",
@@ -132,6 +136,10 @@ const sidebars = {
         "rollups/cosmwasm-zk-rollup/become-a-validator",
       ],
     },
+    {
+      type: "html",
+      value: '<div class="sidebar-heading">Develop</div>',
+    },
   ],
 };
 

sidebars.js

@@ -0,0 +1,60 @@
+import Link from "@docusaurus/Link";
+import React from "react";
+
+const IntroToZKFHE = () => {
+  return (
+    <div>
+      <p>
+        Airchains leverages advanced Zero-Knowledge (ZK) and Fully Homomorphic
+        Encryption (FHE) technologies to address critical challenges in
+        scalability, privacy, and security.
+      </p>
+      <p>
+        By integrating the two technologies together, Airchains ensures that
+        computations can be performed on encrypted data, maintaining privacy,
+        while zk-SNARKs provide robust mechanisms for verifying computations
+        without exposing the underlying data, ensuring confidentiality and
+        security. This is the essence of zkFHE.
+      </p>
+      <div className="docs_heading">Useful Links</div>
+      <div className="docs_card_image_wrapper">
+        <Link
+          to={`/concepts/intro-to-zkfhe/zk-proofs`}
+          className="docs_card_without_image"
+        >
+          <div className="docs_card_heading_title">ZK Proofs</div>
+          <div className="docs_card_description">
+            Explore how ZK Proofs enable privacy-preserving computations and how
+            they are used in Airchains.
+          </div>
+        </Link>
+        <Link
+          to={`/concepts/intro-to-zkfhe/fully-homomorphic-encryption`}
+          className="docs_card_without_image"
+        >
+          <div className="docs_card_heading_title">
+            Fully Homomorphic Encryption
+          </div>
+          <div className="docs_card_description">
+            Learn how FHE enables computations on encrypted data without the
+            need to decrypt it.
+          </div>
+        </Link>
+        <Link
+          to={`/concepts/intro-to-zkfhe/zk-snark-and-fhe-integration`}
+          className="docs_card_without_image"
+        >
+          <div className="docs_card_heading_title">
+            zk-SNARK and FHE Integration
+          </div>
+          <div className="docs_card_description">
+            Learn how Provers and Sequencers maintain trust, integrity, and
+            order in decentralized networks.
+          </div>
+        </Link>
+      </div>
+    </div>
+  );
+};
+
+export default IntroToZKFHE;