diff --git a/components/AllocationTable.tsx b/components/AllocationTable.tsx
new file mode 100644
index 00000000..bfca2b6d
--- /dev/null
+++ b/components/AllocationTable.tsx
@@ -0,0 +1,229 @@
+import React from "react";
+import styled from "styled-components";
+
+const TableContainer = styled.div`
+  overflow-x: auto;
+  margin: 20px;
+`;
+
+const Table = styled.table`
+  width: 100%;
+  border-collapse: collapse;
+  text-align: left;
+  font-size: 14px;
+
+  @media (max-width: 768px) {
+    font-size: 12px;
+  }
+`;
+
+const Header = styled.th`
+  background-color: #f1f1f1;
+  padding: 12px;
+  font-weight: bold;
+  border: 1px solid #ddd;
+  white-space: nowrap;
+`;
+
+const Row = styled.tr`
+  &:nth-child(even) {
+    background-color: #f9f9f9;
+  }
+`;
+
+const SubtotalRow = styled(Row)`
+  background-color: #e6f2ff !important;
+  font-weight: bold;
+`;
+
+const TotalRow = styled(Row)`
+  background-color: #d9ead3;
+  font-weight: bold;
+`;
+
+const Cell = styled.td`
+  padding: 12px;
+  border: 1px solid #ddd;
+  white-space: nowrap;
+`;
+
+export default function AllocationTable() {
+  return (
+    <TableContainer>
+      <Table>
+        <thead>
+          <Row>
+            <Header>Allocation Category</Header>
+            <Header>Entity Name</Header>
+            <Header>Allocated Share (%)</Header>
+            <Header>Vesting Plan</Header>
+            <Header>Cliff (Months)</Header>
+            <Header>Vesting Period (Months)</Header>
+            <Header>Immediate Liquidity (%)</Header>
+            <Header>Initial Liquid Tokens</Header>
+            <Header>Cliff-Release Tokens</Header>
+            <Header>Monthly Vesting Rate</Header>
+            <Header>Total Tokens Allocated</Header>
+          </Row>
+        </thead>
+        <tbody>
+          <Row>
+            <Cell>Contributors</Cell>
+            <Cell>Webb (Developer)</Cell>
+            <Cell>28.56%</Cell>
+            <Cell>B-Vesting</Cell>
+            <Cell>12</Cell>
+            <Cell>24</Cell>
+            <Cell>5%</Cell>
+            <Cell>1,356,250.00</Cell>
+            <Cell>12,884,375.00</Cell>
+            <Cell>2,147,395.83</Cell>
+            <Cell>27,125,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Contributors</Cell>
+            <Cell>Investors</Cell>
+            <Cell>13.64%</Cell>
+            <Cell>A-Vesting</Cell>
+            <Cell>12</Cell>
+            <Cell>24</Cell>
+            <Cell>0%</Cell>
+            <Cell>0.00</Cell>
+            <Cell>6,820,000.00</Cell>
+            <Cell>1,136,666.67</Cell>
+            <Cell>13,640,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Contributors</Cell>
+            <Cell>Indiv. Webb Contributors</Cell>
+            <Cell>1.44%</Cell>
+            <Cell>B-Vesting</Cell>
+            <Cell>12</Cell>
+            <Cell>48</Cell>
+            <Cell>5%</Cell>
+            <Cell>71,750.00</Cell>
+            <Cell>340,812.50</Cell>
+            <Cell>37,868.06</Cell>
+            <Cell>1,435,000.00</Cell>
+          </Row>
+          <SubtotalRow>
+            <Cell colSpan={2}>
+              <strong>Contributors Subtotal</strong>
+            </Cell>
+            <Cell>43.64%</Cell>
+            <Cell colSpan={4}></Cell>
+            <Cell>1,428,000.00</Cell>
+            <Cell colSpan={2}></Cell>
+            <Cell>42,200,000.00</Cell>
+          </SubtotalRow>
+          <Row>
+            <Cell>Governance-Managed</Cell>
+            <Cell>Treasury</Cell>
+            <Cell>36.36%</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>100%</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>36,360,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Governance-Managed</Cell>
+            <Cell>Foundation</Cell>
+            <Cell>15.00%</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>100%</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>n/a</Cell>
+            <Cell>15,000,000.00</Cell>
+          </Row>
+          <SubtotalRow>
+            <Cell colSpan={2}>
+              <strong>Governance-Managed Subtotal</strong>
+            </Cell>
+            <Cell>51%</Cell>
+            <Cell colSpan={7}></Cell>
+            <Cell>51,360,000.00</Cell>
+          </SubtotalRow>
+          <Row>
+            <Cell>Airdrops</Cell>
+            <Cell>Leaderboard Participants</Cell>
+            <Cell>2%</Cell>
+            <Cell>C-Vesting</Cell>
+            <Cell>1</Cell>
+            <Cell>24</Cell>
+            <Cell>5%</Cell>
+            <Cell>100,000.00</Cell>
+            <Cell>79,166.67</Cell>
+            <Cell>82,608.70</Cell>
+            <Cell>2,000,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Airdrops</Cell>
+            <Cell>DOT Validators Snapshot</Cell>
+            <Cell>1%</Cell>
+            <Cell>C-Vesting</Cell>
+            <Cell>1</Cell>
+            <Cell>24</Cell>
+            <Cell>5%</Cell>
+            <Cell>50,000.00</Cell>
+            <Cell>39,583.33</Cell>
+            <Cell>41,304.35</Cell>
+            <Cell>1,000,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Airdrops</Cell>
+            <Cell>EDG Genesis Participants</Cell>
+            <Cell>1%</Cell>
+            <Cell>C-Vesting</Cell>
+            <Cell>1</Cell>
+            <Cell>24</Cell>
+            <Cell>5%</Cell>
+            <Cell>50,000.00</Cell>
+            <Cell>39,583.33</Cell>
+            <Cell>41,304.35</Cell>
+            <Cell>1,000,000.00</Cell>
+          </Row>
+          <Row>
+            <Cell>Airdrops</Cell>
+            <Cell>EDG 2023 Snapshot</Cell>
+            <Cell>1%</Cell>
+            <Cell>C-Vesting</Cell>
+            <Cell>1</Cell>
+            <Cell>24</Cell>
+            <Cell>5%</Cell>
+            <Cell>50,000.00</Cell>
+            <Cell>39,583.33</Cell>
+            <Cell>41,304.35</Cell>
+            <Cell>1,000,000.00</Cell>
+          </Row>
+          <SubtotalRow>
+            <Cell colSpan={2}>
+              <strong>Airdrops Subtotal</strong>
+            </Cell>
+            <Cell colSpan={5}></Cell>
+            <Cell>250,000.00</Cell>
+            <Cell>197,916.67</Cell>
+            <Cell colSpan={1}></Cell>
+            <Cell>5,000,000.00</Cell>
+          </SubtotalRow>
+          <TotalRow>
+            <Cell colSpan={2}>
+              <strong>Total Supply</strong>
+            </Cell>
+            <Cell>100%</Cell>
+            <Cell colSpan={4}></Cell>
+            <Cell>1,678,000.00</Cell>
+            <Cell colSpan={2}></Cell>
+            <Cell>100,000,000.00</Cell>
+          </TotalRow>
+        </tbody>
+      </Table>
+    </TableContainer>
+  );
+}
diff --git a/components/MainnetConfig.tsx b/components/MainnetConfig.tsx
new file mode 100644
index 00000000..d4ab685a
--- /dev/null
+++ b/components/MainnetConfig.tsx
@@ -0,0 +1,106 @@
+import React, { useState } from "react";
+import Link from "next/link";
+import styles from "./NetworkConfig.module.css";
+
+const NetworkCard = ({
+  cardTitle,
+  network,
+  type,
+  symbol,
+  decimals,
+  chainId,
+  rpcUrl,
+  wssUrl,
+  explorerUrls,
+  fundingInfo,
+}) => {
+  return (
+    <div className={styles.networkCard}>
+      <div className={styles.networkType}>
+        {type} {cardTitle}
+      </div>
+      <div className={styles.titleContainer}>
+        <h2 className={styles.networkTitle}>{network}</h2>
+      </div>
+      <table className={styles.table}>
+        <tbody>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Network Type</th>
+            <td className={styles.tableCell}>{type}</td>
+          </tr>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Native Asset Symbol</th>
+            <td className={styles.tableCell}>{symbol}</td>
+          </tr>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Native Asset Decimals</th>
+            <td className={styles.tableCell}>{decimals}</td>
+          </tr>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Chain ID</th>
+            <td className={styles.tableCell}>{chainId}</td>
+          </tr>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Public RPC URL</th>
+            <td className={styles.tableCell}>
+              <Link href={rpcUrl}>{rpcUrl}</Link>
+            </td>
+          </tr>
+          <tr className={styles.tableRow}>
+            <th className={styles.tableHeader}>Public WSS URL</th>
+            <td className={styles.tableCell}>
+              <Link href={wssUrl}>{wssUrl}</Link>
+            </td>
+          </tr>
+          {explorerUrls.map((explorer, index) => (
+            <tr key={index}>
+              <th className={styles.tableHeader}>
+                {index === 0 ? "Interfaces & Explorers" : ""}
+              </th>
+              <td className={styles.tableCell}>
+                <Link href={explorer.url}>{explorer.name}</Link>
+              </td>
+            </tr>
+          ))}
+        </tbody>
+      </table>
+    </div>
+  );
+};
+
+const NetworkInfo = () => {
+  // Define the network details here or fetch from an API
+  const networks = [
+    {
+      cardTitle: "Network Information",
+      network: "Tangle Network",
+      type: "Mainnet",
+      symbol: "TNT",
+      decimals: 18,
+      chainId: "5845",
+      rpcUrl: "https://rpc.tangle.tools",
+      wssUrl: "wss://rpc.tangle.tools",
+      explorerUrls: [
+        { name: "BlockScout", url: "https://testnet-explorer.tangle.tools" }, // Update this
+        {
+          name: "PolkadotJS",
+          url: "TBD", // Update this
+        },
+      ],
+      fundingInfo: {
+        url: "https://discord.gg/PQDYv5GT",
+      },
+    },
+    // Add Tangle Mainnet details here when available
+  ];
+
+  return (
+    <div className={styles.networkInfo}>
+      {networks.map((network, index) => (
+        <NetworkCard key={index} {...network} />
+      ))}
+    </div>
+  );
+};
+
+export default NetworkInfo;
diff --git a/next.config.mjs b/next.config.mjs
index acc5feb6..b36667ac 100644
--- a/next.config.mjs
+++ b/next.config.mjs
@@ -1,6 +1,4 @@
 import nextra from "nextra";
-import rehypeKatex from "rehype-katex";
-import remarkMath from "remark-math";
 
 /**
  * @type {import('next').NextConfig}
@@ -39,11 +37,8 @@ const withNextra = nextra({
   themeConfig: "./theme.config.js",
   staticImage: true,
   flexsearch: true,
-  latex: true,
-  mdxOptions: {
-    remarkPlugins: [remarkMath],
-    rehypePlugins: [rehypeKatex],
-  },
+  latex: true, // Ensure this is enabled to use Nextra's native LaTeX support
+  // Since Nextra supports LaTeX natively, remove the custom MDX option for remarkMath and rehypeKatex
 });
 
-export default withNextra(nextConfig);
+export default withNextra(nextConfig);
\ No newline at end of file
diff --git a/package.json b/package.json
index d8e8d4f1..9ff9b189 100644
--- a/package.json
+++ b/package.json
@@ -21,6 +21,7 @@
     "@mdx-js/react": "^2.2.1",
     "@react-aria/ssr": "3.4.0",
     "@sentry/nextjs": "^7.27.0",
+    "@types/styled-components": "^5.1.34",
     "@vercel/analytics": "^0.1.6",
     "axios": "0.27.2",
     "classnames": "2.3.2",
@@ -29,10 +30,10 @@
     "js-cookie": "3.0.1",
     "katex": "^0.16.4",
     "ms": "^2.1.3",
-    "next": "^13.0.0",
+    "next": "13.0.0",
     "next-themes": "^0.2.0",
-    "nextra": "^2.12.3",
-    "nextra-theme-docs": "^2.12.3",
+    "nextra": "2.12.3",
+    "nextra-theme-docs": "2.12.3",
     "react": "^18.2.0",
     "react-dom": "^18.2.0",
     "react-hot-toast": "2.4.0",
@@ -42,6 +43,7 @@
     "rehype-katex": "5.0.0",
     "remark-math": "4.0.0",
     "sharp": "^0.31.3",
+    "styled-components": "^6.1.8",
     "swr": "1.3.0"
   },
   "devDependencies": {
@@ -63,7 +65,18 @@
   },
   "prettier": {
     "embeddedLanguageFormatting": "off",
-    "htmlWhitespaceSensitivity": "strict"
+    "htmlWhitespaceSensitivity": "strict",
+    "overrides": [
+      {
+        "files": "*.mdx",
+        "options": {
+          "parser": "mdx",
+          "plugins": [
+            "prettier/parser-babel"
+          ]
+        }
+      }
+    ]
   },
   "engines": {
     "npm": "please-use-yarn",
diff --git a/pages/docs/_meta.json b/pages/docs/_meta.json
index 9815666f..80d8f977 100644
--- a/pages/docs/_meta.json
+++ b/pages/docs/_meta.json
@@ -1,19 +1,69 @@
 {
   "index": {
-    "title": "Overview"
-  },
-  "usecases": "Use Cases",
-  "network-information-configuration": "Network Configuration",
-  "build": "Build",
-  "node": "Node",
-  "use": "Use",
-  "governance": "Govern",
-  "community": "Community",
-  "faq": "FAQ",
-  "glossary": "Glossary",
-  "contribute": "Contribute or Submit a Bug",
+    "title": "Overview",
+    "type": "doc"
+  },
+  "launch": {
+    "title": "Network Launch",
+    "type": "doc"
+  },
+  "tokenomics": {
+    "title": "Tokenomics",
+    "type": "doc"
+  },
+  "usecases": {
+    "title": "Use Cases",
+    "type": "doc"
+  },
+  "services": {
+    "title": "Services",
+    "type": "doc"
+  },
+  "----": {
+    "type": "separator"
+  },
+  "network-information-configuration": {
+    "title": "Network Configuration",
+    "type": "doc"
+  },
+  "build": {
+    "title": "Build",
+    "type": "doc"
+  },
+  "node": {
+    "title": "Node",
+    "type": "doc"
+  },
+  "use": {
+    "title": "Basics",
+    "type": "doc"
+  },
+  "governance": {
+    "title": "Govern",
+    "type": "doc"
+  },
+  "---": {
+    "type": "separator"
+  },
+  "community": {
+    "title": "Community",
+    "type": "doc"
+  },
+  "faq": {
+    "title": "FAQ",
+    "type": "doc"
+  },
+  "glossary": {
+    "title": "Glossary",
+    "type": "doc"
+  },
+  "contribute": {
+    "title": "Contribute or Submit a Bug",
+    "type": "doc"
+  },
   "webb_docs_link": {
     "title": "Webb Docs",
-    "href": "https://docs.webb.tools/docs"
+    "href": "https://docs.webb.tools/docs",
+    "type": "doc"
   }
 }
diff --git a/pages/docs/build/_meta.json b/pages/docs/build/_meta.json
index a20be584..00f31156 100644
--- a/pages/docs/build/_meta.json
+++ b/pages/docs/build/_meta.json
@@ -1,6 +1,8 @@
 {
+  "developer-overview": "Understanding Tangle for Developers",
   "deploy-using-hardhat": "Deploy on Tangle with Hardhat",
   "json-rpc-endpoints": "RPC Endpoints",
+  "integrate": "Integrate Tangle",
   "pallets": "Pallets",
   "precompiles": "Precompiles"
 }
diff --git a/pages/docs/build/developer-overview.mdx b/pages/docs/build/developer-overview.mdx
new file mode 100644
index 00000000..88b470d3
--- /dev/null
+++ b/pages/docs/build/developer-overview.mdx
@@ -0,0 +1,44 @@
+# Developer Introduction to Tangle Network
+
+Tangle Network is an innovative blockchain platform that empowers developers to build cutting-edge applications with advanced privacy features and distributed trust. By leveraging multi-party computation (MPC) and zero-knowledge proofs (ZKPs), Tangle Network provides a secure and scalable infrastructure for developing blockchain solutions across various domains, including custody, oracles, and bridges.
+
+## Key Features and Services
+
+### Threshold Signature as a Service (TSSaaS)
+
+Tangle Network offers Threshold Signature as a Service (TSSaaS), which enables developers to integrate threshold signature schemes into their applications. Threshold signatures enhance security by distributing the signing authority across multiple parties, eliminating single points of failure. This service is particularly useful for wallet infrastructure, custody solutions, and managing digital assets securely.
+
+### Proof Generation as a Service (ZKSaaS)
+
+Tangle Network provides Proof Generation as a Service (ZKSaaS), allowing developers to access zero-knowledge proof generation functionality directly through the network's infrastructure. ZKPs are critical for maintaining privacy and implementing complex cryptographic protocols within decentralized applications. With ZKSaaS, developers can easily integrate privacy-preserving features into their applications without the need for extensive cryptographic expertise.
+
+### Benefits of MPC
+
+Tangle Network leverages multi-party computation (MPC) to provide a range of benefits for developers and organizations:
+
+- Protection of sensitive data
+- Distributed model for enhanced security
+- Removal of single points of failure
+- Compliance with data sharing restrictions
+- Protection against malicious parties and attacks
+- Enhanced trust and security for users
+
+## Protocol Extensions and Customization
+
+Tangle Network allows developers to extend and customize the protocol to suit their specific application requirements. Some of the possibilities include:
+
+- Adding new threshold signature schemes like ECDSA, Schnorr, BLS, and FROST
+- Integrating fully homomorphic encryption (FHE) solutions for secure computation on encrypted data
+- Incorporating randomness beacons for unbiased randomness in cryptographic protocols
+- Integrating federated learning protocols for privacy-preserving AI and ML model training
+- Developing general MPC compiler infrastructure to simplify the creation of secure multi-party applications
+
+## Getting Started
+
+To get started with Tangle Network, developers can explore the open-source repositories available on GitHub. Some of the key repositories include:
+
+- **tangle**: The main repository of Tangle Network, built on Substrate, which powers cross-chain and zero-knowledge application development.
+- **gadget**: A common platform for MPC gadgets, allowing peers to query the blockchain for job information and perform cooperative work based on on-chain jobs.
+- **zk-SaaS**: Rust implementation of the zkSaaS protocol, leveraging secure multi-party computation to generate zkSNARKs.
+
+Developers can also refer to the comprehensive documentation and join the vibrant community of builders to enhance their understanding of Tangle Network and contribute to the development of privacy-centric cloud solutions.
diff --git a/pages/docs/build/integrate.mdx b/pages/docs/build/integrate.mdx
new file mode 100644
index 00000000..1065098f
--- /dev/null
+++ b/pages/docs/build/integrate.mdx
@@ -0,0 +1,24 @@
+# Integrating with Tangle Network
+
+## Integration Resources
+
+| Category                     | Details                                                                                            |
+| ---------------------------- | -------------------------------------------------------------------------------------------------- |
+| **Blockchain Name**          | Tangle Network                                                                                     |
+| **Blockchain Type**          | Substrate with EVM compatibility via Frontier                                                      |
+| WebSocket RPC Endpoint\*\*   | `wss://rpc.tangle.tools`                                                                           |
+| **HTTP RPC Endpoint**        | `http://rpc.tangle.tools`                                                                          |
+| **Chain ID**                 | 5845                                                                                               |
+| **Address Prefix**           | `tg`                                                                                               |
+| **Network**                  | `tangle`                                                                                           |
+| **Symbols**                  | `TNT`                                                                                              |
+| **Decimals**                 | `18`                                                                                               |
+| **Standard Account**         | `*25519`                                                                                           |
+| **Website**                  | https://www.tangle.tools/                                                                          |
+| **EVM Block Explorer**       | https://testnet-explorer.tangle.tools/                                                             |
+| **Runtime Types**            | https://github.com/webb-tools/tangle/blob/main/types/src/interfaces/lookup.ts                      |
+| **Substrate Block Explorer** | Coming soon.                                                                                       |
+| **Polkadot Apps**            | https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftestnet-rpc.tangle.tools#/explorer                   |
+| **Node Telemetry**           | https://telemetry.polkadot.io/#/0x3d22af97d919611e03bbcbda96f65988758865423e89b2d99547a6bb61452db3 |
+| **Whitepaper**               | https://github.com/webb-tools/tangle/blob/main/Tangle_Network_Whitepaper-VerrsFeb282024.pdf        |
+| **Github Repo**.             | https://github.com/webb-tools/tangle                                                               |
diff --git a/pages/docs/index.mdx b/pages/docs/index.mdx
index e6fb6130..e674420d 100644
--- a/pages/docs/index.mdx
+++ b/pages/docs/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Overview, Use Cases and Actions
-description: Explore the Tangle Network ecosystem at a glance including use cases including interoperable shielded pools, identity-based systems, decentralized private finance, and secure multi-party computation, as well as features, and roadmap.
+description: Explore the Tangle Network ecosystem at a glance including use cases including secure multi-party computation, as well as features, and roadmap.
 ---
 
 import { RepoArea } from "../../components/RepoArea";
@@ -15,60 +15,74 @@ import { CommonActions } from "../../components/CommonActions";
 
 ## Introduction
 
-Tangle Network is a Substrate-based mainnet crafted to deliver decentralized cloud services, emphasizing Multi-Party Computation (MPC) as a Service (MPCaaS). Enabled by validator restaking, Tangle provides an ideal framework for application development that prioritizes privacy through the secure computation of private inputs.
+The Tangle Network is a pioneering blockchain platform, uniquely positioned to advance cross-chain and zero-knowledge (ZK) applications within a collaborative ecosystem. Built on the robust Substrate framework, Tangle seamlessly combines Multi-Party Computation (MPC) primitives with an innovative restaking mechanism. This fusion not only empowers developers to forge privacy-enhancing ZK applications and cross-chain solutions but also establishes a decentralized, crypto-economically secured service landscape.
 
-Our platform supports an array of critical services tailored for developers working on advanced Zero-Knowledge (ZK) and cross-chain solutions. Central to that is the fusion of cross-chain interoperability, Ethereum Virtual Machine (EVM) compatibility, sophisticated governance protocols, and ZK services.
+Central to Tangle's ethos is the creation of a united community of developers, validators, and innovators, all driven to co-create cutting-edge, privacy-preserving applications. By focusing on the development of specific MPC-driven blockchain solutions, such as Threshold Signature as a Service (TSSaaS) and Proof Generation as a Service (ZKSaaS), Tangle offers tangible benefits across its user base:
 
-These services include zkSNARKS-as-a-Service (zk-SNARKsaaS) and Trusted Setups-as-a-Service, as well as non-ZK MPC services like Threshold Signature Schemes as-a-Service (TSSaaS) and threshold encryption. Together, these strengths set the stage for an era of rapid implementation of privacy-centric applications.
+**For Application Developers:** Unlock scalable and secure development environments with MPC solutions, ensuring seamless integration into existing and future projects.
+
+**For Protocol Developers:** Explore new horizons and contribute to the MPC infrastructure through innovative protocol upgrades, enhancing the network's capabilities.
+
+**For Validators:** Participate in Tangle's restaking framework to earn additional rewards while providing essential cryptographic services to the network.
 
 ## Key Features
 
-**1. Cross-Chain Functionality and EVM Compatibility**
+- **MPC-as-a-Service (MaaS)**: Tangle natively supports various multi-party computation primitives and zero-knowledge proving services that facilitate the development of new applications, particularly in the privacy-preserving space. These services benefit the Tangle community by positioning the network as a core infrastructure for any ZK application across multiple ecosystems.
 
-The Tangle Network breaks traditional chain boundaries, allowing seamless interaction, data exchange, and operation of ZK applications across different blockchain networks. Leveraging the power of the Ethereum Virtual Machine (EVM) on Substrate, developers can utilize familiar EVM tooling and compatibility to build decentralized applications (DApps), create Non-Fungible Tokens (NFTs), and utilize ERC20 tokens across multiple networks.
+- **Restaking**: Tangle's restaking system is directly integrated into its MPC-as-a-Service infrastructure. Validators can restake directly on the set of roles available to them in the runtime, with each role representing an eligible service. This mechanism incentivizes validators to provide high-quality MPC services.
 
-**2. Advanced Governance**
+- **Interoperability**: Tangle is dedicated to enabling fluid cross-chain interactions, from asset bridging to advanced cross-chain communication. We imagine this will be achieved through various technologies such as private bridges, zkBridges, IBC pallets, and XCM.
 
-The Tangle Network implements an innovative governance model based on Distributed Key Generation (DKG) protocol. The DKG protocol serves as a security instrument for the Tangle Network's cross-chain Anchor zkApps, ensuring the validity of bridge updates with crypto-economically secured threshold-signatures.
+- **EVM Compatibility**: The Ethereum Virtual Machine (EVM) is a critical component of Tangle Network, serving as a conduit for compatibility and interoperability with Ethereum-based tools and applications. Developers can seamlessly construct decentralized applications (DApps), generate Non-Fungible Tokens (NFTs), and utilize ERC20 tokens across diverse networks.
 
-DKG is a cryptographic method where multiple entities collaboratively produce a shared public and private key. In the Tangle Network, DKG fortifies the governance of distributed applications, particularly the Anchor System. It bolsters the security of the network by ensuring the integrity of signed messages via threshold signatures. This not only provides resistance against potential threats but also amplifies the Tangle Network's credibility.
+## Services
 
-**3. Privacy-Enhancing ZK Applications**
+Tangle Network offers a range of services to support the development and deployment of advanced cryptographic applications:
 
-Privacy is a paramount concern in the Tangle Network. By providing an infrastructure for Zero-Knowledge (ZK) applications, we enable users to experience a new generation of privacy-enhancing functionalities. ZK applications empower users to transact, communicate, and interact privately while maintaining the security and immutability of blockchain technology.
+- **Signing as a Service (TSSaaS)**: Tangle provides threshold signatures as a service, enabling the creation of decentralized bridges, oracles, and custody solutions. This service leverages a distributed key generation protocol to ensure robust security.
 
-**4. Built on Substrate**
+- **zkSNARKs as a Service (zkSaaS)**: To address the computational challenges faced by resource-constrained devices when running ZK applications, Tangle offers proof generation as a service. This allows developers to outsource the proof generation process to a privacy-preserving infrastructure.
 
-The Tangle Network is built on Substrate, an advanced blockchain framework renowned for its flexibility, scalability, and cutting-edge features. This strategic choice ensures that our platform remains at the forefront of speed, security, and scalability, serving as a reliable backbone for the Tangle Network. Leveraging Substrate's modular architecture, we enable seamless interaction and interoperability with other blockchain networks.
+- **Trusted Setups as a Service (TaaS)**: Tangle streamlines the trusted setup process for ZK applications by providing this as a service. This reduces the friction for developers, enabling them to deploy ZK applications to production without organizing a trusted setup themselves.
 
----
+## Governance and Community
+
+Tangle Network employs an advanced governance model underpinned by a Distributed Key Generation (DKG) protocol. This protocol serves as a security mechanism for the network's cross-chain applications, validating bridge updates with crypto-economically protected threshold signatures.
+
+The Tangle community is a vibrant mix of developers, privacy researchers, decentralized app (dApp) users, bridge users, and token holders. Community members assume various roles within the ecosystem, including technology advocates, validators, data relayers, governance participants, and open-source contributors.
+
+## Conclusion
+
+Tangle Network introduces an innovative platform to support cross-chain Zero-Knowledge (ZK) applications and enhance privacy in the blockchain ecosystem. With its unique offering of MPC-as-a-Service, restaking mechanism, and commitment to interoperability, Tangle is well-positioned to become a core infrastructure for enabling privacy-first and interoperable blockchain solutions.
+
+As the network continues to evolve, it aims to expand its services, foster community growth, and drive the adoption of advanced cryptographic techniques in the blockchain space. Tangle Network invites developers, validators, and users to join its mission of building a more private, secure, and interconnected decentralized future.
 
 ## Roadmap
 
 The following is subject to change as DAO governance supports different initiatives.
 
-**Phase 1**
+**COMPLETE: Phase 1**
 
-- Test Runtime Upgrade
+- Launch democracy governance.
 - Finalize Tangle Token Distribution
 - Launch Incentivized testnet
 
 **Phase 2**
 
-- Update Tangle Genesis for Launch
-- Distribute TNT Tokens
-- Launch Democracy Governance
-- Launch OFAC VAnchor Bridges
+- Launch mainnet on **April 10, 2024** and allocate TNT tokens.
+- Deploy threshold signature scheme (TSS) as a service.
+- Deploy restaking: linking validators to the MPC services.
 
 **Phase 3**
 
-- Launch Cross-chain Transfers
-- Validator Staking Upgrades
-- Launch Semaphore VAnchor bridges
+- Launch cross-chain transfers.
+- Initialize proof generation (ZKSaaS) as a service.
+- Deploy ETH2 Light Client
 
 **Phase 4**
 
-- Remove Sudo
-- Improve Relayer & Proposer Security
+- Remove Sudo and fully delegate authority to the on-chain community.
+- Expand MPC service offerings.
+- Integrate with EigenLayer.
 
 <FullWebbCTA />
diff --git a/pages/docs/launch.mdx b/pages/docs/launch.mdx
new file mode 100644
index 00000000..33746f45
--- /dev/null
+++ b/pages/docs/launch.mdx
@@ -0,0 +1,21 @@
+# Tangle Network Mainnet Launch
+
+## Launch Date
+
+- **Mainnet Activation**: Scheduled for April 10, 2024, Tangle Network will make its entrance as a fully operational NPoS network, virtually permissionless, decentralized and community governed from the start. Validators will be able to participate in validation on the 10th.
+
+## NPoS Launch and Operations
+
+- **NPoS Framework**: Upon launch, Tangle Network will adopt a Nominated Proof of Stake model as its foundational security mechanism. This allows TNT holders to engage directly in the network's security by nominating validators they trust to be responsible for block production and transaction validation.
+- **Validator Participation**: Validators are essential to the network's integrity and performance from the very beginning. Potential validators are thus encouraged to prepare for their roles by learning to stake TNT tokens and signaling their commitment to maintaining network protocols.
+
+## Governance Activation
+
+- **Initial Governance**: Concurrent with the NPoS launch, governance modules will be activated, granting TNT holders the power to participate in decision-making processes through proposals, referenda, and council elections, ensuring a democratic approach to the network's development.
+- **Webb's Sudo Key Role**: Initially, Webb, a core development team, will hold a Sudo key to ensure smooth operations and governance transitions. This temporary measure allows for efficient implementation of critical updates and decisions during the early stages of the network.
+- **Sudo Key Deactivation**: A timeline is in place for deactivating the Sudo key, transitioning to a fully decentralized governance model. This significant step is expected to occur within the first few months after launch, with input from the token holders to affirm the network's readiness.
+
+## Core Functionality
+
+- **Balances and Transfers**: From launch day, TNT token balances will be active, with token transfer capabilities generally enabled to ensure liquidity and participation in the network's economy. **If you recieve tokens through the airdrop or other allocation processes, up to 95% of these may be subject to a lockup. [See the Allocation page for details.](/docs/tokenomics/allocation)**
+- **Community Proposals for Additional Features**: Post-launch, the community will be empowered to propose and vote on activating additional core functionalities. This encompasses enhanced transaction types, new governance mechanisms, and network upgrades, among others.
diff --git a/pages/docs/services/_meta.json b/pages/docs/services/_meta.json
new file mode 100644
index 00000000..a849ea52
--- /dev/null
+++ b/pages/docs/services/_meta.json
@@ -0,0 +1,4 @@
+{
+  "services": "MPC and ZK Services",
+  "service-provider": "Provide Services"
+}
diff --git a/pages/docs/services/service-provider.mdx b/pages/docs/services/service-provider.mdx
new file mode 100644
index 00000000..610b3fcf
--- /dev/null
+++ b/pages/docs/services/service-provider.mdx
@@ -0,0 +1,176 @@
+# Validator Restaking and Job Provision
+
+## 1. Introduction
+
+This guide will help you understand the concept of restaking, the various roles available, and how to maximize their earnings through active participation in the Tangle network.
+
+Restaking is a unique feature of the Tangle network that allows validators to commit their staked Tangle Native Tokens (TNT) to additional roles beyond the initial validation responsibilities. By restaking, validators can contribute to the network's security, efficiency, and growth while earning rewards for their efforts.
+
+## 2. Understanding Restaking on Tangle
+
+### What is Restaking?
+
+Restaking is the process of allocating a portion of a validator's staked TNT to specific roles within the Tangle network. These roles include Threshold Signature Scheme (TSS) and Zero-Knowledge Proofs as a Service (ZkSaaS) roles, which are crucial for maintaining the network's integrity and supporting advanced features like privacy-preserving transactions.
+
+By restaking, validators demonstrate their long-term commitment to the network and align their incentives with its performance and growth. Restaking offers flexibility and additional opportunities for validators to earn rewards while contributing to the network's overall health.
+
+## 3. Validator Roles and Responsibilities
+
+By opting into various roles through restaking, validators can contribute to different aspects of the network.
+
+### TSS Roles
+
+Threshold Signature Scheme (TSS) roles involve participating in collective signing processes to secure multi-signature transactions and contracts. Validators can opt into the following TSS roles:
+
+- DfnsCGGMP21Secp256k1
+- DfnsCGGMP21Secp256r1
+- DfnsCGGMP21Stark
+- ZcashFrostP256
+- ZcashFrostP384
+- ZcashFrostSecp256k1
+- ZcashFrostEd25519
+- ZcashFrostEd448
+- ZcashFrostRistretto255
+
+Validators in TSS roles are responsible for collaborating with other validators to generate and manage shared keys, ensuring the security and integrity of multi-signature operations.
+
+### ZkSaaS Roles
+
+Zero-Knowledge Proofs as a Service (ZkSaaS) roles require validators to provide computational resources for generating zero-knowledge proofs, enabling private and scalable transactions on the Tangle Blockchain. The main ZkSaaS role is:
+
+- ZkSaaSGroth16
+
+Validators in ZkSaaS roles contribute their computing power to generate zero-knowledge proofs, facilitating privacy-preserving transactions and enhancing the network's scalability.
+
+### Responsibilities for Each Role
+
+Regardless of the specific role, all validators are expected to:
+
+- Maintain high availability and uptime to ensure the network's smooth operation
+- Actively participate in the consensus mechanism and fulfill their validation duties
+- Perform role-specific tasks, such as collaborating in TSS or generating zero-knowledge proofs
+- Stay updated with network upgrades and adhere to best practices for security and performance
+
+By fulfilling these responsibilities, validators contribute to the overall health, security, and efficiency of the Tangle Blockchain.
+
+## 4. Restaking Mechanisms
+
+### Maximum Restake Amount
+
+Currently, validators can restake up to 50% of their initially staked TNT for participating in additional roles. This limit ensures a balance between the network's security needs and the flexibility for validators to engage in various functions.
+
+### Independent vs. Shared Restaking
+
+Validators have two options when it comes to restaking:
+
+1. **Independent Restaking**: Validators can allocate specific amounts of TNT to different roles, tailoring their risk and reward distribution according to their preferences and strategies. This approach allows for more granular control over the allocation of staked TNT.
+
+2. **Shared Restaking**: Validators can choose to distribute a single restake amount across multiple roles. This simplifies stake management and potentially diversifies risk by participating in various roles simultaneously.
+
+### Process for Opting into Roles and Restaking TNT
+
+To opt into roles and restake TNT, validators should follow these steps:
+
+1. **Evaluate Roles**: Carefully consider the available TSS and ZkSaaS roles and assess their technological requirements, potential rewards, and risks.
+
+2. **Restaking Decision**: Decide between independent and shared restaking based on your preferred strategy and risk tolerance.
+
+3. **Restake Execution**: Allocate TNT to the selected roles through the Tangle Blockchain's interface using the appropriate dispatchable calls (detailed in Section 7).
+
+## 5. Economic Incentives and Rewards
+
+The Tangle Blockchain employs a comprehensive rewards system to incentivize validators for their active participation and contributions to the network.
+
+### Rewards System Breakdown
+
+Validator rewards are calculated based on two main factors:
+
+1. **Active Validator Rewards (50%)**: Rewards for validators who have completed jobs in the current era.
+
+   - The total jobs completed (TJC) by all active validators are calculated.
+   - Each validator's share (VS) of the rewards is determined by the proportion of their completed jobs relative to the TJC.
+   - The validator reward (VR) is computed as: VR = VS × Total Rewards
+
+2. **Validator Rewards by Restake (50%)**: Rewards for validators based on their restaked amount.
+   - The total restake (TR) in the system is calculated by summing all validators' restaked amounts.
+   - The restake-to-stake ratio (RSR) is computed as: RSR = TR / Total Stake in the Era
+   - The missing restake ratio (MRR) is calculated as: MRR = Maximum Restake Ratio - RSR
+   - The adjusted total rewards (ATR) are computed based on the MRR to ensure proper reward distribution.
+   - Each validator's reward share (RS) is determined by their restaked amount relative to the TR.
+   - The final reward for each validator is calculated as: Reward = RS × ATR
+
+#### Example Reward Calculation
+
+Let's consider an example in era 100, with 20 restakers and a total role reward of 1000 TNT:
+
+- **Active Validator Rewards**:
+
+  - 10 restakers have completed 5 jobs each.
+  - 50% of the 1000 TNT (500 TNT) is equally divided among the 10 active restakers.
+  - If one restaker had completed more jobs than the others, they would receive a larger share of the rewards.
+
+- **Rewards by Restake**:
+  - The remaining 50% of the 1000 TNT (500 TNT) is distributed among all restakers based on their restaked amount.
+  - If a restaker has restaked 100 TNT out of a total restake of 1000 TNT, they are eligible for 10% of the rewards.
+  - The rewards are adjusted based on the total restake relative to the total stake in the system.
+
+### Capital Efficiency and Reward Optimization
+
+Restaking allows validators to earn rewards from multiple roles without requiring additional capital. This mechanism encourages efficient stake allocation and active participation in the network. By strategically allocating their staked TNT to various roles, validators can optimize their potential rewards while contributing to the network's security and functionality.
+
+## 6. Risks and Mitigation Strategies
+
+While restaking offers validators the opportunity to earn additional rewards, it is essential to be aware of the potential risks involved.
+
+### Slashing Risks
+
+Validators who fail to fulfill their responsibilities or engage in malicious behavior may be subject to slashing penalties. Slashing involves the loss of a portion of the validator's staked and restaked TNT. To mitigate slashing risks, validators should:
+
+- Maintain high availability and uptime
+- Adhere to the network's rules and protocols
+- Regularly monitor their validator nodes and address any issues promptly
+
+### Centralization Risks
+
+If a significant portion of the network's staked TNT is concentrated among a few validators, it could lead to centralization risks. To mitigate these risks, the Tangle Blockchain has implemented a maximum restake amount limit and encourages a diverse set of validators to participate in the network.
+
+### Yield Risks
+
+The rewards earned through restaking may vary depending on factors such as network activity, total staked TNT, and the number of validators participating in each role. Validators should be aware of the potential fluctuations in rewards and make informed decisions when allocating their staked TNT to different roles.
+
+## 7. Dispatchable Calls and Validator Management
+
+The Tangle Blockchain provides a set of dispatchable calls for validators to manage their profiles, opt into roles, and perform various actions related to restaking and job provision.
+
+### Dispatchable Calls for Validators
+
+- `create_profile`: Allows validators to create a profile, specifying the roles they want to participate in and the restaking amounts for each role. Profiles can be shared or independent, and the total restaking amount should meet minimum requirements.
+
+- `update_profile`: Enables validators to update their profiles, adjusting restaking amounts for roles. The update operation ensures that the new restaking amounts meet the minimum requirements and do not exceed the maximum allowed.
+
+- `delete_profile`: Allows validators to submit a request to delete their profile, initiating the process to exit from all services. This operation fails if there are pending jobs associated with the roles.
+
+- `chill`: Enables validators to declare no desire to validate or nominate, effectively opting out of all roles and services.
+
+- `unbond_funds`: Allows validators to unbond funds. These operations are only allowed when the validator has no active roles.
+
+- `withdraw_unbonded`: Enables validators to withdraw unbonded funds after a certain period. These operations are only allowed when the validator has no active roles.
+
+_Detailed examples and technical steps for each call will be provided in the technical documentation._
+
+### Best Practices for Managing Validator Profiles
+
+To effectively manage their profiles and optimize their participation in the Tangle Blockchain, validators should:
+
+- Regularly review and adjust TNT allocations to optimize for reward potential and adhere to network updates.
+- Monitor the network's performance and adapt their restaking strategies accordingly.
+- Keep their validator nodes updated with the latest software versions and security patches.
+- Participate in the Tangle community and stay informed about upcoming changes and improvements to the network.
+
+By following these best practices, validators can ensure a smooth and profitable experience while contributing to the overall health and growth of the Tangle Blockchain.
+
+## 8. Conclusion
+
+Restaking and job provision on the Tangle Blockchain offer validators exciting opportunities to earn additional rewards, contribute to the network's security and efficiency, and support advanced features like privacy-preserving transactions. By understanding the various roles, restaking mechanisms, and economic incentives, validators can make informed decisions and optimize their participation in the network.
+
+As a validator on the Tangle Blockchain, you play a crucial role in the network's success and growth. By actively participating in restaking and job provision, you can maximize your rewards, contribute to the network's security and functionality, and be a part of the exciting journey towards a more efficient, privacy-focused, and decentralized future.
diff --git a/pages/docs/services/services.mdx b/pages/docs/services/services.mdx
new file mode 100644
index 00000000..3084dc27
--- /dev/null
+++ b/pages/docs/services/services.mdx
@@ -0,0 +1,68 @@
+---
+title: Services on Tangle Network
+---
+
+# Services on Tangle Network
+
+Tangle Network provides developers with a suite of multi-party computation (MPC) services to power privacy-enhancing applications, cross-chain applications, and other complex cryptographically secure decentralized applications. By leveraging restaking, Tangle Network enables staked validators to provide these MPC services to paying developers over a decentralized network.
+
+![MPC User Flow](/images/MPCaaS-flow.png)
+
+Through these services, Tangle Network aims to achieve the following for these developers:
+
+1. Reduced friction in deploying advanced cryptographic and zero-knowledge applications.
+2. Expanded frontier of possible zero-knowledge application space through cross-chain interoperability and privacy-preserving tools.
+3. Simplified APIs for interacting with zero-knowledge applications.
+4. Outsourced proof generation and trusted setup generation, eliminating operational burdens.
+
+## Core Services
+
+### Multi-Party Computation (MPC)
+
+#### Threshold Signing as a Service (TSSaaS) MPC
+
+Signatures are pervasive in the design of blockchain bridges, oracles, and custody solutions. Tangle Network offers signature schemes as a service using threshold cryptography, enabling developers to build private and non-private cross-chain applications.
+
+Tangle currently supports several Threshold signature schemes:
+
+- DfnsCGGMP21Secp256k1
+- DfnsCGGMP21Secp256r1
+- DfnsCGGMP21Stark
+- ZcashFrostP256
+- ZcashFrostP384
+- ZcashFrostSecp256k1
+- ZcashFrostEd25519
+- ZcashFrostEd448
+- ZcashFrostRistretto255
+- GennaroDKGBls381
+
+Use cases include bridges, oracles, interoperable shielded pools, and social and identity bridges.
+
+### Proof Generation
+
+#### zkSNARKs as a Service (zkSaaS)
+
+Proof generation is critical for maintaining privacy and implementation of complex cryptographic protocols within decentralized applications. Tangle's zkSnark service allows users to access proof generation functionality directly through the network. This allows developers to outsource the computationally expensive tasks to a privacy-preserving infrastructure.
+
+Tangle currently supports zkSaaS for Groth16 proofs, and our targeted systems will include:
+
+- Groth16
+- PLONK
+- Nova
+- Halo2
+- Stark
+
+#### Trusted Setups as a Service (TaaS)
+
+Tangle Network streamlines the trusted setup process for zero-knowledge applications, reducing friction and enabling faster deployment to production.
+
+## Future Services
+
+We're exploring the development of new privacy technologies for the future:
+
+- Witness generation
+- Data storage and availability for privacy applications
+- Private information retrieval as a service
+- Threshold decryption as a service
+- Sequencing as a service
+- Randomness beacons
diff --git a/pages/docs/tokenomics/_meta.json b/pages/docs/tokenomics/_meta.json
new file mode 100644
index 00000000..fc1cfd1f
--- /dev/null
+++ b/pages/docs/tokenomics/_meta.json
@@ -0,0 +1,5 @@
+{
+  "usage": "Token Overview and Utility",
+  "allocation": "Allocation",
+  "inflation": "Inflation"
+}
diff --git a/pages/docs/tokenomics/allocation.mdx b/pages/docs/tokenomics/allocation.mdx
new file mode 100644
index 00000000..915e6da2
--- /dev/null
+++ b/pages/docs/tokenomics/allocation.mdx
@@ -0,0 +1,93 @@
+---
+title: Genesis Allocations and Token Allocation Details
+tags:
+  - Token
+  - Tokenomics
+---
+
+import AllocationTable from 'components/AllocationTable.tsx';
+
+### Overview: Genesis Allocations
+
+Observing successful networks as a benchmark, Tangle Network has tailored its genesis allocation to meet its unique needs and goals.
+
+![Allocation Pie Chart](/images/allocation-pie-chart.png)
+
+### Vesting Schedules
+
+Vesting schedules in Tangle Network are designed to promote long-term commitment and ensure a phased distribution of tokens. The network adopts a structured vesting strategy with distinct categories:
+
+**A-Vesting:** This category is characterized by a vesting period of 2 years, with a 12-month cliff. This means that no tokens are released in the first year. After completing the first year (the cliff period), the tokens allocated for that year become immediately available in full. The remainder of the allocation is then distributed monthly in equal 1/12 increments over the second year, facilitating a gradual release of tokens. This approach aligns with the policy of Immediate Vesting Post-Cliff with Retroactive Accumulation.
+
+**B-Vesting:** For participants in this category, a small portion of the tokens (as specified, 5% or a different predetermined percentage based on individual agreements) becomes immediately available upon claiming. The remaining 95% of the tokens are then vested over a period of 2 years, with the vesting commencing one month after allocation. The first month serves as a cliff, during which no tokens are vested. Following this cliff, the tokens begin to vest linearly each month, ensuring a steady distribution until the end of the 2-year period. This vesting schedule adheres to the policy of Immediate Vesting Post-Cliff with Retroactive Accumulation, allowing for a proportional monthly distribution of tokens.
+
+**C-Vesting:** This vesting category is tailored for airdrop participants, featuring a 2-year vesting period with a notably short cliff of just 1 month. A predefined percentage of tokens becomes immediately available at the start. Subsequent to the cliff period, the remaining tokens are distributed on a monthly basis, ensuring a consistent flow of tokens into circulation. This strategy also follows the Immediate Vesting Post-Cliff with Retroactive Accumulation policy, aiming to reward early supporters while promoting long-term holding.
+
+### Detailed Allocation Overview
+
+The Tangle Network's allocation model is designed to support our foundational structures, incentivize community participation, and ensure long-term sustainability and success:
+
+- **Contributors** allocation supports the core teams, core-team investors and advisors essential for the network's development and strategic direction.
+- **Airdrops** are aimed at rewardingg and incentivizing validators, early supporters and participants, fostering a strong and engaged community from the outset.
+- **Governance-Managed** funds are earmarked for community decisionmaking, future development, network success programs, liquidity provisions, and partnerships critical for launch and growth.
+
+<AllocationTable />
+
+# Token Allocation and Vesting Schedule Formulas
+
+This section outlines the formulas used to calculate various aspects of our token allocation and vesting schedules, presented in a way that's compatible with Markdown rendering.
+
+### Initial Liquid Tokens
+
+```plaintext
+=Total_Tokens_Allocated * Immediate_Liquidity_Percentage
+```
+
+**Description:** Calculates the number of tokens that are immediately liquid and available at launch, based on the total tokens allocated to an entity and the percentage designated as immediately liquid.
+
+### Cliff-Release Tokens (for entities with a retroactive vesting cliff)
+
+```plaintext
+=Total_Tokens_Allocated * (Cliff_Duration / Total_Vesting_Period)
+```
+
+**Description:** For allocations with a retroactive vesting cliff, this calculates the number of tokens released at the end of the cliff period, based on the total allocation and the proportion of the vesting period represented by the cliff.
+
+### Monthly Vesting Rate (for entities with post-cliff monthly vesting)
+
+```plaintext
+=(Total_Tokens_Allocated - Initial_Liquid_Tokens - Cliff_Release_Tokens) / (Vesting_Period - Cliff_Duration)
+```
+
+**Description:** Determines the monthly rate at which tokens vest after the cliff period, considering the total tokens allocated minus any initially liquid tokens and tokens released at the cliff, divided by the remaining months of the vesting period.
+
+### Special Considerations
+
+For entities without a vesting plan (e.g., Treasury, Foundation)
+**Entire allocation is considered liquid at launch,** though it is only utilized through governance and so not 'liquid' in the traditional tokenomic sense.
+
+```plaintext
+=Total_Tokens_Allocated
+```
+
+## Definitions
+
+1. **Allocation Category**: A grouping used to categorize the distribution of tokens or shares within a project or organization, typically indicating the purpose or recipient of the allocation.
+2. **Entity Name**: The name of the individual or organization receiving the allocation of tokens or shares.
+3. **Allocated Share (%)**: The percentage of the total token supply allocated to a specific entity or category.
+4. **Vesting Plan**: A structured timeline outlining how allocated tokens or shares become available to the recipient over a period, usually to incentivize long-term commitment or performance.
+5. **Cliff (Months)**: The initial period after which a portion of the allocated tokens or shares becomes accessible to the recipient, often used as a safeguard against early departures or underperformance.
+6. **Vesting Period (Months)**: The total duration over which allocated tokens or shares gradually become available to the recipient according to the vesting schedule.
+7. **Immediate Liquidity (%)**: The percentage of allocated tokens or shares that are immediately accessible or liquid upon allocation, without being subject to vesting restrictions.
+8. **Initial Liquid Tokens**: The number of tokens or shares initially available for immediate use or transfer upon allocation.
+9. **Cliff-Release Tokens**: The number of tokens or shares released after the cliff period, becoming accessible to the recipient according to the vesting schedule.
+10. **Monthly Vesting Rate**: The rate at which tokens or shares vest on a monthly basis after the cliff period, determining the pace of distribution to the recipient.
+11. **Total Tokens Allocated**: The overall sum of tokens or shares allocated to a specific entity or category, representing the total amount of ownership or participation assigned.
+12. **Contributors**: Individuals or entities actively involved in contributing to the project's development, growth, or success.
+13. **Governance-Managed**: Tokens allocated for governance purposes and managed by a designated entity or organization within the project, typically used for decision-making or protocol governance.
+14. **Airdrops**: Distribution of tokens to a specific group of recipients, often as a promotional or community-building activity, without requiring direct financial investment.
+15. **Leaderboard Participants**: Participants who engage with the project's leaderboard, often in competitions or challenges, and receive tokens as rewards or incentives.
+16. **DOT Validators Snapshot**: Participants included in a specific snapshot of DOT (Polkadot) validators and rewarded with tokens accordingly.
+17. **EDG Genesis Participants**: Participants involved in the project's genesis event or initial launch phase and eligible for token rewards.
+18. **EDG 2023 Snapshot**: Participants included in a snapshot taken in the year 2023 and eligible for token rewards based on their inclusion in the snapshot.
+19. **Total Supply**: The overall quantity of tokens or shares in existence within the project or organization, representing the maximum potential ownership or participation.
diff --git a/pages/docs/tokenomics/inflation.mdx b/pages/docs/tokenomics/inflation.mdx
new file mode 100644
index 00000000..b59b580c
--- /dev/null
+++ b/pages/docs/tokenomics/inflation.mdx
@@ -0,0 +1,56 @@
+# Tangle Network's Inflation Model
+
+## Overview
+
+Tangle Network utilizes a Nominated Proof of Stake (NPoS) system to secure its network and incentivize participation. The creation (minting) of new Tangle Network Tokens (TNT) serves as the primary mechanism for rewarding validators and nominators, which in turn introduces inflation into the system. This document outlines the key aspects of how rewards are distributed and how inflation is managed within Tangle Network.
+
+## NPoS Payments and Inflation
+
+- **Purpose**: Rewards are distributed to validators and nominators for their roles in block production and network security.
+- **Inflation**: The minting of new TNT for rewards is the main source of inflation within Tangle Network.
+- **Exclusions**: This overview **does not** account for penalties (slashings), rewards for reporting misconduct, or transaction fee rewards, which are covered separately.
+
+## Inflation Model Simplified
+
+- **Staking Rate:**
+
+($$x$$)
+
+Represents the proportion of total TNT supply that is staked in the NPoS system.
+
+- **Ideal Staking Rate**
+
+($$\chi_{\text{ideal}}$$)
+
+The target staking rate Tangle Network aims to achieve for optimal security and liquidity balance.
+
+- **Yearly Interest Rate:**
+
+($$i(x)$$)
+
+The rate at which rewards are paid out relative to the amount staked, adjusted based on the staking rate to incentivize desired staking levels.
+
+### Key Concepts:
+
+- **Incentives**: The system adjusts rewards to encourage a staking rate close to $\chi_{ideal}$, reducing rewards as staking exceeds this target to prevent liquidity issues.
+- **Inflation Rate ($I$)**: Calculated based on several factors, including rewards for NPoS participation, treasury funding, penalties, and transaction fees. The goal is to balance inflation with network security and operational needs.
+- **Adjustable Parameters**: The model includes variables like the ideal interest rate ($i_{ideal}$) and inflation limits that can be tuned to manage the network's economic dynamics effectively.
+
+![Inflation](/images/desmos-graph.png)
+
+## Reward Distribution Mechanism
+
+- Validators and nominators receive rewards for their contributions to block production and network security, with rewards calculated based on several factors including the total points earned for various actions within the network.
+- **Payment Details**: Rewards are allocated based on a point system, where different network contributions earn different points. The total payout is then distributed proportionally to the points earned by each participant.
+
+## Inflation Control and Staking Incentives
+
+- The inflation model is designed to encourage a balanced staking rate by adjusting rewards based on the current staking rate relative to the ideal target.
+- **Ideal Staking Rate Adjustment**: Factors such as network growth and operational needs may lead to adjustments in the ideal staking rate to maintain network security and efficiency.
+
+## Simplifying Complexities
+
+- While the underlying mechanics are complex, the essence is to incentivize behaviors that secure the network and ensure its smooth operation, balancing between rewarding participation and controlling inflation.
+- **Governance Role**: The community and governance processes play a crucial role in adjusting parameters within the inflation model to respond to evolving network needs and conditions.
+
+This simplified overview aims to provide a clearer understanding of how Tangle Network manages inflation and rewards within its NPoS system, making the information accessible to a broader audience without diminishing the intricacies of the underlying mechanisms.
diff --git a/pages/docs/tokenomics/usage.mdx b/pages/docs/tokenomics/usage.mdx
new file mode 100644
index 00000000..fb078345
--- /dev/null
+++ b/pages/docs/tokenomics/usage.mdx
@@ -0,0 +1,38 @@
+# TNT Token Information and Utility
+
+The Tangle Network's native token is TNT, critical for the capabilities in Zero-Knowledge (ZK) and Multiparty Computation (MPC) as-a-service. TNT also underpins the entire ecosystem's operation and governance.
+
+| Token Name                   | Symbol | Decimal Places |
+| ---------------------------- | ------ | -------------- |
+| Tangle Network Token         | TNT    | 18             |
+| Testnet Tangle Network Token | tTNT   | 18             |
+
+## Usage Cases
+
+### Consensus Mechanism and nPoS:
+
+The Tangle Network's nominated proof-of-stake (nPoS) consensus mechanism requires TNT to be staked by validators to participate in validating blocks. Additionally, nominators can nominate their TNT to individual validators to participate in the rewards to that validator and increase that validator's tokens-at-stake.
+
+### Network Economics
+
+Tangle Network dynamically mints or burns TNT tokens to reward consensus protocol participants like validators and nominators, partially fund its treasury, manage inflation, and ensure the network's economic stability.
+
+### ZK and MPC Operations
+
+TNT serves as the currency for transactions between job submitters and validators within the Tangle Network's ZK and MPC services. This facilitates seamless, secure, and efficient execution of complex computations and privacy-preserving operations.
+
+### Validator Restaking:
+
+Validators are required to restake TNT tokens to maintain their role in performing ZK and MPC services. This mechanism promotes ongoing commitment and participation in the network's core functionalities.
+
+### Slashing Mechanisms:
+
+To safeguard against malicious activities, TNT tokens are integral to Tangle's slashing protocols across consensus and the restaking system. These measures are designed to deter attacks and incentivize adherence to network protocols.
+
+### Governance Empowerment:
+
+TNT holders wield governance power, enabling them to partake in pivotal network decisions through referenda. This democratic approach ensures that the Tangle Network evolves in alignment with its community's interests.
+
+---
+
+A considerable portion of TNT will be actively engaged in the network, either staked by validators and nominators for network security or utilized in the execution of ZK and MPC tasks. This not only ensures the network's resilience and security but also drives engagement and utility within the Tangle ecosystem.
diff --git a/public/images/allocation-pie-chart.png b/public/images/allocation-pie-chart.png
new file mode 100644
index 00000000..ad5bdea4
Binary files /dev/null and b/public/images/allocation-pie-chart.png differ
diff --git a/public/images/desmos-graph.png b/public/images/desmos-graph.png
new file mode 100644
index 00000000..27a3d768
Binary files /dev/null and b/public/images/desmos-graph.png differ
diff --git a/yarn.lock b/yarn.lock
index 21cc9011..12020c32 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -203,6 +203,13 @@
   resolved "https://registry.yarnpkg.com/@braintree/sanitize-url/-/sanitize-url-6.0.4.tgz#923ca57e173c6b232bbbb07347b1be982f03e783"
   integrity sha512-s3jaWicZd0pkP0jf5ysyHUI/RE7MHos6qlToFcGWXVp+ykHOy77OUMrfbgJ9it2C5bow7OIQwYYaHjk9XlBQ2A==
 
+"@emotion/is-prop-valid@1.2.1":
+  version "1.2.1"
+  resolved "https://registry.yarnpkg.com/@emotion/is-prop-valid/-/is-prop-valid-1.2.1.tgz#23116cf1ed18bfeac910ec6436561ecb1a3885cc"
+  integrity sha512-61Mf7Ufx4aDxx1xlDeOm8aFFigGHE4z+0sKCa+IHCeZKiyP9RLD0Mmx7m8b9/Cf37f7NAvQOOJAbQQGVr5uERw==
+  dependencies:
+    "@emotion/memoize" "^0.8.1"
+
 "@emotion/is-prop-valid@^0.8.2":
   version "0.8.8"
   resolved "https://registry.npmjs.org/@emotion/is-prop-valid/-/is-prop-valid-0.8.8.tgz"
@@ -215,6 +222,16 @@
   resolved "https://registry.npmjs.org/@emotion/memoize/-/memoize-0.7.4.tgz"
   integrity sha512-Ja/Vfqe3HpuzRsG1oBtWTHk2PGZ7GR+2Vz5iYGelAw8dx32K0y7PjVuxK6z1nMpZOqAFsRUPCkK1YjJ56qJlgw==
 
+"@emotion/memoize@^0.8.1":
+  version "0.8.1"
+  resolved "https://registry.yarnpkg.com/@emotion/memoize/-/memoize-0.8.1.tgz#c1ddb040429c6d21d38cc945fe75c818cfb68e17"
+  integrity sha512-W2P2c/VRW1/1tLox0mVUalvnWXxavmv/Oum2aPsRcoDJuob75FC3Y8FbpfLwUegRcxINtGUMPq0tFCvYNTBXNA==
+
+"@emotion/unitless@0.8.0":
+  version "0.8.0"
+  resolved "https://registry.yarnpkg.com/@emotion/unitless/-/unitless-0.8.0.tgz#a4a36e9cbdc6903737cd20d38033241e1b8833db"
+  integrity sha512-VINS5vEYAscRl2ZUDiT3uMPlrFQupiKgHz5AA4bCH1miKBg4qtwkim1qPmJj/4WG6TreYMY111rEFsjupcOKHw==
+
 "@eslint/eslintrc@^1.3.3":
   version "1.4.1"
   resolved "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-1.4.1.tgz"
@@ -454,10 +471,10 @@
     "@napi-rs/simple-git-win32-arm64-msvc" "0.1.9"
     "@napi-rs/simple-git-win32-x64-msvc" "0.1.9"
 
-"@next/env@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.npmjs.org/@next/env/-/env-13.3.0.tgz"
-  integrity sha512-AjppRV4uG3No7L1plinoTQETH+j2F10TEnrMfzbTUYwze5sBUPveeeBAPZPm8OkJZ1epq9OyYKhZrvbD6/9HCQ==
+"@next/env@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/env/-/env-13.0.0.tgz#38527956680693c90b4522ab4ab9a2fbe3a17f67"
+  integrity sha512-65v9BVuah2Mplohm4+efsKEnoEuhmlGm8B2w6vD1geeEP2wXtlSJCvR/cCRJ3fD8wzCQBV41VcMBQeYET6MRkg==
 
 "@next/eslint-plugin-next@12.3.1":
   version "12.3.1"
@@ -466,50 +483,70 @@
   dependencies:
     glob "7.1.7"
 
-"@next/swc-darwin-arm64@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-13.3.0.tgz"
-  integrity sha512-DmIQCNq6JtccLPPBzf0dgh2vzMWt5wjxbP71pCi5EWpWYE3MsP6FcRXi4MlAmFNDQOfcFXR2r7kBeG1LpZUh1w==
-
-"@next/swc-darwin-x64@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-darwin-x64/-/swc-darwin-x64-13.3.0.tgz#b670ed1fd1d231aa21279173ec52e3ad56dc6aeb"
-  integrity sha512-oQoqFa88OGgwnYlnAGHVct618FRI/749se0N3S8t9Bzdv5CRbscnO0RcX901+YnNK4Q6yeiizfgO3b7kogtsZg==
-
-"@next/swc-linux-arm64-gnu@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-13.3.0.tgz#b114935f6b4c94c123f6cac55a4823d483209ba5"
-  integrity sha512-Wzz2p/WqAJUqTVoLo6H18WMeAXo3i+9DkPDae4oQG8LMloJ3if4NEZTnOnTUlro6cq+S/W4pTGa97nWTrOjbGw==
-
-"@next/swc-linux-arm64-musl@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-13.3.0.tgz#67a57309f8761c7d00d629d6785d56ed0567a0d2"
-  integrity sha512-xPVrIQOQo9WXJYgmoTlMnAD/HlR/1e1ZIWGbwIzEirXBVBqMARUulBEIKdC19zuvoJ477qZJgBDCKtKEykCpyQ==
-
-"@next/swc-linux-x64-gnu@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-13.3.0.tgz#11bd2bea7c00b40be111c0dd16e71171f3792086"
-  integrity sha512-jOFlpGuPD7W2tuXVJP4wt9a3cpNxWAPcloq5EfMJRiXsBBOjLVFZA7boXYxEBzSVgUiVVr1V9T0HFM7pULJ1qA==
-
-"@next/swc-linux-x64-musl@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-13.3.0.tgz#d57e99f85890799b78719c3ea32a4624de8d701b"
-  integrity sha512-2OwKlzaBgmuet9XYHc3KwsEilzb04F540rlRXkAcjMHL7eCxB7uZIGtsVvKOnQLvC/elrUegwSw1+5f7WmfyOw==
-
-"@next/swc-win32-arm64-msvc@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-13.3.0.tgz#0c209aa35d1c88b01e78259a89cd68f4139b5093"
-  integrity sha512-OeHiA6YEvndxT46g+rzFK/MQTfftKxJmzslERMu9LDdC6Kez0bdrgEYed5eXFK2Z1viKZJCGRlhd06rBusyztA==
-
-"@next/swc-win32-ia32-msvc@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-win32-ia32-msvc/-/swc-win32-ia32-msvc-13.3.0.tgz#52ae74da1dd6d840c3743923367d27ed013803dd"
-  integrity sha512-4aB7K9mcVK1lYEzpOpqWrXHEZympU3oK65fnNcY1Qc4HLJFLJj8AViuqQd4jjjPNuV4sl8jAwTz3gN5VNGWB7w==
-
-"@next/swc-win32-x64-msvc@13.3.0":
-  version "13.3.0"
-  resolved "https://registry.yarnpkg.com/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-13.3.0.tgz#db7b55fee834dc8c2c484c696469e65bae2ee770"
-  integrity sha512-Reer6rkLLcoOvB0dd66+Y7WrWVFH7sEEkF/4bJCIfsSKnTStTYaHtwIJAwbqnt9I392Tqvku0KkoqZOryWV9LQ==
+"@next/swc-android-arm-eabi@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-android-arm-eabi/-/swc-android-arm-eabi-13.0.0.tgz#15cd89d19d3c00d123fdfe367bab38c362f6c515"
+  integrity sha512-+DUQkYF93gxFjWY+CYWE1QDX6gTgnUiWf+W4UqZjM1Jcef8U97fS6xYh+i+8rH4MM0AXHm7OSakvfOMzmjU6VA==
+
+"@next/swc-android-arm64@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-android-arm64/-/swc-android-arm64-13.0.0.tgz#9410365bb07097268d4773a46b02cfe6b3fe3ab7"
+  integrity sha512-RW9Uy3bMSc0zVGCa11klFuwfP/jdcdkhdruqnrJ7v+7XHm6OFKkSRzX6ee7yGR1rdDZvTnP4GZSRSpzjLv/N0g==
+
+"@next/swc-darwin-arm64@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-darwin-arm64/-/swc-darwin-arm64-13.0.0.tgz#caf262fb5cb8bb335f6f344fd67a44dc8bf6a084"
+  integrity sha512-APA26nps1j4qyhOIzkclW/OmgotVHj1jBxebSpMCPw2rXfiNvKNY9FA0TcuwPmUCNqaTnm703h6oW4dvp73A4Q==
+
+"@next/swc-darwin-x64@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-darwin-x64/-/swc-darwin-x64-13.0.0.tgz#6b214753410e1d8512a1491045acea1e188df7d6"
+  integrity sha512-qsUhUdoFuRJiaJ7LnvTQ6GZv1QnMDcRXCIjxaN0FNVXwrjkq++U7KjBUaxXkRzLV4C7u0NHLNOp0iZwNNE7ypw==
+
+"@next/swc-freebsd-x64@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-freebsd-x64/-/swc-freebsd-x64-13.0.0.tgz#eeb176bdb585f48882bdac1d04271b918ca87590"
+  integrity sha512-sCdyCbboS7CwdnevKH9J6hkJI76LUw1jVWt4eV7kISuLiPba3JmehZSWm80oa4ADChRVAwzhLAo2zJaYRrInbg==
+
+"@next/swc-linux-arm-gnueabihf@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-linux-arm-gnueabihf/-/swc-linux-arm-gnueabihf-13.0.0.tgz#2c2a9622c93f87a8baca94e068f674da4cae6018"
+  integrity sha512-/X/VxfFA41C9jrEv+sUsPLQ5vbDPVIgG0CJrzKvrcc+b+4zIgPgtfsaWq9ockjHFQi3ycvlZK4TALOXO8ovQ6Q==
+
+"@next/swc-linux-arm64-gnu@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-13.0.0.tgz#69505827e2928fb18034150fd4d754d54c4a1c4b"
+  integrity sha512-x6Oxr1GIi0ZtNiT6jbw+JVcbEi3UQgF7mMmkrgfL4mfchOwXtWSHKTSSPnwoJWJfXYa0Vy1n8NElWNTGAqoWFw==
+
+"@next/swc-linux-arm64-musl@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-13.0.0.tgz#487a88f2583a046e882328fe0665b37eca4fd0f6"
+  integrity sha512-SnMH9ngI+ipGh3kqQ8+mDtWunirwmhQnQeZkEq9e/9Xsgjf04OetqrqRHKM1HmJtG2qMUJbyXFJ0F81TPuT+3g==
+
+"@next/swc-linux-x64-gnu@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-13.0.0.tgz#29e89c7e4fd2e2b16ad059076f6261998aee53df"
+  integrity sha512-VSQwTX9EmdbotArtA1J67X8964oQfe0xHb32x4tu+JqTR+wOHyG6wGzPMdXH2oKAp6rdd7BzqxUXXf0J+ypHlw==
+
+"@next/swc-linux-x64-musl@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-13.0.0.tgz#2f63aae922d2b2829aec21bf8f9adda8b6c16365"
+  integrity sha512-xBCP0nnpO0q4tsytXkvIwWFINtbFRyVY5gxa1zB0vlFtqYR9lNhrOwH3CBrks3kkeaePOXd611+8sjdUtrLnXA==
+
+"@next/swc-win32-arm64-msvc@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-13.0.0.tgz#4117bad96c2a6775f70294fba45c63951a8a21ac"
+  integrity sha512-NutwDafqhGxqPj/eiUixJq9ImS/0sgx6gqlD7jRndCvQ2Q8AvDdu1+xKcGWGNnhcDsNM/n1avf1e62OG1GaqJg==
+
+"@next/swc-win32-ia32-msvc@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-win32-ia32-msvc/-/swc-win32-ia32-msvc-13.0.0.tgz#5914eb86f9ea92a00d76cb094dd9734b3bf2012c"
+  integrity sha512-zNaxaO+Kl/xNz02E9QlcVz0pT4MjkXGDLb25qxtAzyJL15aU0+VjjbIZAYWctG59dvggNIUNDWgoBeVTKB9xLg==
+
+"@next/swc-win32-x64-msvc@13.0.0":
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-13.0.0.tgz#c54a5a739dee04b20338d305226a2acdf701f67f"
+  integrity sha512-FFOGGWwTCRMu9W7MF496Urefxtuo2lttxF1vwS+1rIRsKvuLrWhVaVTj3T8sf2EBL6gtJbmh4TYlizS+obnGKA==
 
 "@nodelib/fs.scandir@2.1.5":
   version "2.1.5"
@@ -696,10 +733,10 @@
     "@sentry/cli" "^1.74.6"
     webpack-sources "^2.0.0 || ^3.0.0"
 
-"@swc/helpers@0.4.14":
-  version "0.4.14"
-  resolved "https://registry.npmjs.org/@swc/helpers/-/helpers-0.4.14.tgz"
-  integrity sha512-4C7nX/dvpzB7za4Ql9K81xK3HPxCpHMgwTZVyf+9JQ6VUbn9jjZVN7/Nkdz/Ugzs2CSjqnL/UPXroiVBVHUWUw==
+"@swc/helpers@0.4.11":
+  version "0.4.11"
+  resolved "https://registry.yarnpkg.com/@swc/helpers/-/helpers-0.4.11.tgz#db23a376761b3d31c26502122f349a21b592c8de"
+  integrity sha512-rEUrBSGIoSFuYxwBYtlUFMlE2CwGhmW+w9355/5oduSw8e5h2+Tj4UrAGNNgP9915++wj5vkQo0UuOBqOAq4nw==
   dependencies:
     tslib "^2.4.0"
 
@@ -776,6 +813,14 @@
   dependencies:
     "@types/unist" "*"
 
+"@types/hoist-non-react-statics@*":
+  version "3.3.5"
+  resolved "https://registry.yarnpkg.com/@types/hoist-non-react-statics/-/hoist-non-react-statics-3.3.5.tgz#dab7867ef789d87e2b4b0003c9d65c49cc44a494"
+  integrity sha512-SbcrWzkKBw2cdwRTwQAswfpB9g9LJWfjtUeW/jvNwbhC8cpmmNYVePa+ncbUe0rGTQ7G3Ff6mYUN2VMfLVr+Sg==
+  dependencies:
+    "@types/react" "*"
+    hoist-non-react-statics "^3.3.0"
+
 "@types/js-cookie@^2.2.6":
   version "2.2.7"
   resolved "https://registry.npmjs.org/@types/js-cookie/-/js-cookie-2.2.7.tgz"
@@ -850,6 +895,15 @@
   resolved "https://registry.npmjs.org/@types/prop-types/-/prop-types-15.7.5.tgz"
   integrity sha512-JCB8C6SnDoQf0cNycqd/35A7MjcnK+ZTqE7judS6o7utxUCg6imJg3QK2qzHKszlTjcj2cn+NwMB2i96ubpj7w==
 
+"@types/react@*":
+  version "18.2.64"
+  resolved "https://registry.yarnpkg.com/@types/react/-/react-18.2.64.tgz#3700fbb6b2fa60a6868ec1323ae4cbd446a2197d"
+  integrity sha512-MlmPvHgjj2p3vZaxbQgFUQFvD8QiZwACfGqEdDSWou5yISWxDQ4/74nCAwsUiX7UFLKZz3BbVSPj+YxeoGGCfg==
+  dependencies:
+    "@types/prop-types" "*"
+    "@types/scheduler" "*"
+    csstype "^3.0.2"
+
 "@types/react@18.0.26", "@types/react@>=16":
   version "18.0.26"
   resolved "https://registry.npmjs.org/@types/react/-/react-18.0.26.tgz"
@@ -864,6 +918,20 @@
   resolved "https://registry.npmjs.org/@types/scheduler/-/scheduler-0.16.3.tgz"
   integrity sha512-5cJ8CB4yAx7BH1oMvdU0Jh9lrEXyPkar6F9G/ERswkCuvP4KQZfZkSjcMbAICCpQTN4OuZn8tz0HiKv9TGZgrQ==
 
+"@types/styled-components@^5.1.34":
+  version "5.1.34"
+  resolved "https://registry.yarnpkg.com/@types/styled-components/-/styled-components-5.1.34.tgz#4107df8ef8a7eaba4fa6b05f78f93fba4daf0300"
+  integrity sha512-mmiVvwpYklFIv9E8qfxuPyIt/OuyIrn6gMOAMOFUO3WJfSrSE+sGUoa4PiZj77Ut7bKZpaa6o1fBKS/4TOEvnA==
+  dependencies:
+    "@types/hoist-non-react-statics" "*"
+    "@types/react" "*"
+    csstype "^3.0.2"
+
+"@types/stylis@4.2.0":
+  version "4.2.0"
+  resolved "https://registry.yarnpkg.com/@types/stylis/-/stylis-4.2.0.tgz#199a3f473f0c3a6f6e4e1b17cdbc967f274bdc6b"
+  integrity sha512-n4sx2bqL0mW1tvDf/loQ+aMX7GQD3lc3fkCMC55VFNDu/vBOabO+LTIeXKM14xK0ppk5TUGcWRjiSpIlUpghKw==
+
 "@types/unist@*", "@types/unist@^2.0.0", "@types/unist@^2.0.2":
   version "2.0.6"
   resolved "https://registry.npmjs.org/@types/unist/-/unist-2.0.6.tgz"
@@ -1309,13 +1377,6 @@ buffer@^5.5.0:
     base64-js "^1.3.1"
     ieee754 "^1.1.13"
 
-busboy@1.6.0:
-  version "1.6.0"
-  resolved "https://registry.npmjs.org/busboy/-/busboy-1.6.0.tgz"
-  integrity sha512-8SFQbg/0hQ9xy3UNTB0YEnsNBbWfhf7RtnzpL7TkBiTBRfrQ9Fxcnz7VJsleJpyp6rVLvXiuORqjlHi5q+PYuA==
-  dependencies:
-    streamsearch "^1.1.0"
-
 call-bind@^1.0.0, call-bind@^1.0.2:
   version "1.0.2"
   resolved "https://registry.npmjs.org/call-bind/-/call-bind-1.0.2.tgz"
@@ -1356,6 +1417,11 @@ camelcase@^1.0.2:
   resolved "https://registry.npmjs.org/camelcase/-/camelcase-1.2.1.tgz"
   integrity sha512-wzLkDa4K/mzI1OSITC+DUyjgIl/ETNHE9QvYgy6J6Jvqyyz4C0Xfd+lQhb19sX2jMpZV4IssUn0VDVmglV+s4g==
 
+camelize@^1.0.0:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/camelize/-/camelize-1.0.1.tgz#89b7e16884056331a35d6b5ad064332c91daa6c3"
+  integrity sha512-dU+Tx2fsypxTgtLoE36npi3UqcjSSMNYfkqgmoEhtZrraP5VWq0K7FkWVTYa8eMPtnU/G2txVsfdCJTn9uzpuQ==
+
 caniuse-lite@^1.0.30001406, caniuse-lite@^1.0.30001426, caniuse-lite@^1.0.30001449:
   version "1.0.30001570"
   resolved "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001570.tgz"
@@ -1682,6 +1748,11 @@ cross-spawn@^7.0.2:
     shebang-command "^2.0.0"
     which "^2.0.1"
 
+css-color-keywords@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/css-color-keywords/-/css-color-keywords-1.0.0.tgz#fea2616dc676b2962686b3af8dbdbe180b244e05"
+  integrity sha512-FyyrDHZKEjXDpNJYvVsV960FiqQyXc/LlYmsxl2BcdMb2WPx0OGRVgTg55rPSyLSNMqP52R9r8geSp7apN3Ofg==
+
 css-in-js-utils@^3.1.0:
   version "3.1.0"
   resolved "https://registry.npmjs.org/css-in-js-utils/-/css-in-js-utils-3.1.0.tgz"
@@ -1689,6 +1760,15 @@ css-in-js-utils@^3.1.0:
   dependencies:
     hyphenate-style-name "^1.0.3"
 
+css-to-react-native@3.2.0:
+  version "3.2.0"
+  resolved "https://registry.yarnpkg.com/css-to-react-native/-/css-to-react-native-3.2.0.tgz#cdd8099f71024e149e4f6fe17a7d46ecd55f1e32"
+  integrity sha512-e8RKaLXMOFii+02mOlqwjbD00KSEKqblnpO9e++1aXS1fPQOpS1YoqdVHBqPjHNoxeF2mimzVqawm2KCbEdtHQ==
+  dependencies:
+    camelize "^1.0.0"
+    css-color-keywords "^1.0.0"
+    postcss-value-parser "^4.0.2"
+
 css-tree@^1.1.2:
   version "1.1.3"
   resolved "https://registry.npmjs.org/css-tree/-/css-tree-1.1.3.tgz"
@@ -1707,6 +1787,11 @@ csstype@3.1.1, csstype@^3.0.2, csstype@^3.0.6:
   resolved "https://registry.npmjs.org/csstype/-/csstype-3.1.1.tgz"
   integrity sha512-DJR/VvkAvSZW9bTouZue2sSxDwdTN92uHjqeKVm+0dAqdfNykRzQ95tay8aXMBAAPpUiq4Qcug2L7neoRh2Egw==
 
+csstype@3.1.2:
+  version "3.1.2"
+  resolved "https://registry.yarnpkg.com/csstype/-/csstype-3.1.2.tgz#1d4bf9d572f11c14031f0436e1c10bc1f571f50b"
+  integrity sha512-I7K1Uu0MBPzaFKg4nI5Q7Vs2t+3gWWW648spaF+Rg7pI9ds18Ugn+lvg4SHczUdKlHI5LWBXyqfS8+DufyBsgQ==
+
 cytoscape-cose-bilkent@^4.1.0:
   version "4.1.0"
   resolved "https://registry.yarnpkg.com/cytoscape-cose-bilkent/-/cytoscape-cose-bilkent-4.1.0.tgz#762fa121df9930ffeb51a495d87917c570ac209b"
@@ -3306,7 +3391,7 @@ hey-listen@^1.0.8:
   resolved "https://registry.npmjs.org/hey-listen/-/hey-listen-1.0.8.tgz"
   integrity sha512-COpmrF2NOg4TBWUJ5UVyaCU2A88wEMkUPK4hNqyCkqHbxT92BbvfjoSozkAIIm6XhicGlJHhFdullInrdhwU8Q==
 
-hoist-non-react-statics@^3.3.2:
+hoist-non-react-statics@^3.3.0, hoist-non-react-statics@^3.3.2:
   version "3.3.2"
   resolved "https://registry.npmjs.org/hoist-non-react-statics/-/hoist-non-react-statics-3.3.2.tgz"
   integrity sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==
@@ -4881,29 +4966,33 @@ next-themes@^0.2.0, next-themes@^0.2.1:
   resolved "https://registry.npmjs.org/next-themes/-/next-themes-0.2.1.tgz"
   integrity sha512-B+AKNfYNIzh0vqQQKqQItTS8evEouKD7H5Hj3kmuPERwddR2TxvDSFZuTj6T7Jfn1oyeUyJMydPl1Bkxkh0W7A==
 
-next@^13.0.0:
-  version "13.3.0"
-  resolved "https://registry.npmjs.org/next/-/next-13.3.0.tgz"
-  integrity sha512-OVTw8MpIPa12+DCUkPqRGPS3thlJPcwae2ZL4xti3iBff27goH024xy4q2lhlsdoYiKOi8Kz6uJoLW/GXwgfOA==
+next@13.0.0:
+  version "13.0.0"
+  resolved "https://registry.yarnpkg.com/next/-/next-13.0.0.tgz#6f07064a4f374562cf58677bef4dd06326ca648b"
+  integrity sha512-puH1WGM6rGeFOoFdXXYfUxN9Sgi4LMytCV5HkQJvVUOhHfC1DoVqOfvzaEteyp6P04IW+gbtK2Q9pInVSrltPA==
   dependencies:
-    "@next/env" "13.3.0"
-    "@swc/helpers" "0.4.14"
-    busboy "1.6.0"
+    "@next/env" "13.0.0"
+    "@swc/helpers" "0.4.11"
     caniuse-lite "^1.0.30001406"
     postcss "8.4.14"
-    styled-jsx "5.1.1"
+    styled-jsx "5.1.0"
+    use-sync-external-store "1.2.0"
   optionalDependencies:
-    "@next/swc-darwin-arm64" "13.3.0"
-    "@next/swc-darwin-x64" "13.3.0"
-    "@next/swc-linux-arm64-gnu" "13.3.0"
-    "@next/swc-linux-arm64-musl" "13.3.0"
-    "@next/swc-linux-x64-gnu" "13.3.0"
-    "@next/swc-linux-x64-musl" "13.3.0"
-    "@next/swc-win32-arm64-msvc" "13.3.0"
-    "@next/swc-win32-ia32-msvc" "13.3.0"
-    "@next/swc-win32-x64-msvc" "13.3.0"
-
-nextra-theme-docs@^2.12.3:
+    "@next/swc-android-arm-eabi" "13.0.0"
+    "@next/swc-android-arm64" "13.0.0"
+    "@next/swc-darwin-arm64" "13.0.0"
+    "@next/swc-darwin-x64" "13.0.0"
+    "@next/swc-freebsd-x64" "13.0.0"
+    "@next/swc-linux-arm-gnueabihf" "13.0.0"
+    "@next/swc-linux-arm64-gnu" "13.0.0"
+    "@next/swc-linux-arm64-musl" "13.0.0"
+    "@next/swc-linux-x64-gnu" "13.0.0"
+    "@next/swc-linux-x64-musl" "13.0.0"
+    "@next/swc-win32-arm64-msvc" "13.0.0"
+    "@next/swc-win32-ia32-msvc" "13.0.0"
+    "@next/swc-win32-x64-msvc" "13.0.0"
+
+nextra-theme-docs@2.12.3:
   version "2.12.3"
   resolved "https://registry.yarnpkg.com/nextra-theme-docs/-/nextra-theme-docs-2.12.3.tgz#f69a46884718ffc3d8fa54f7092a5da6a144ccd6"
   integrity sha512-aZywZwokk/h5HrUTh/bsU981Sd2prZks7ci+HNG9wuMnm+drp3PBmRKIuQxBCiJurePVBJ2Qk2/wTV3VECGKnA==
@@ -4922,7 +5011,7 @@ nextra-theme-docs@^2.12.3:
     scroll-into-view-if-needed "^3.0.0"
     zod "^3.20.2"
 
-nextra@^2.12.3:
+nextra@2.12.3:
   version "2.12.3"
   resolved "https://registry.yarnpkg.com/nextra/-/nextra-2.12.3.tgz#9ef4fc3f2c62fbd3f8ba557565061f97813daad1"
   integrity sha512-0d8wXpGAccFpMFZuxnlnN56MIZj+AWGYXW3Xk6ByXyr0Mb+B/C/0aGZV5YrBex0V1wEqMGQl4LLAJI+AfCbSXg==
@@ -5331,7 +5420,7 @@ postcss-selector-parser@^6.0.10:
     cssesc "^3.0.0"
     util-deprecate "^1.0.2"
 
-postcss-value-parser@^4.0.0, postcss-value-parser@^4.2.0:
+postcss-value-parser@^4.0.0, postcss-value-parser@^4.0.2, postcss-value-parser@^4.2.0:
   version "4.2.0"
   resolved "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz"
   integrity sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==
@@ -5354,6 +5443,15 @@ postcss@8.4.20:
     picocolors "^1.0.0"
     source-map-js "^1.0.2"
 
+postcss@8.4.31:
+  version "8.4.31"
+  resolved "https://registry.yarnpkg.com/postcss/-/postcss-8.4.31.tgz#92b451050a9f914da6755af352bdc0192508656d"
+  integrity sha512-PS08Iboia9mts/2ygV3eLpY5ghnUcfLV/EXTOW1E2qYxJKGGBUtNjN76FYHnMs36RmARn41bC0AZmn+rR0OVpQ==
+  dependencies:
+    nanoid "^3.3.6"
+    picocolors "^1.0.0"
+    source-map-js "^1.0.2"
+
 postcss@^8.4.18:
   version "8.4.23"
   resolved "https://registry.npmjs.org/postcss/-/postcss-8.4.23.tgz"
@@ -5921,6 +6019,11 @@ set-harmonic-interval@^1.0.1:
   resolved "https://registry.npmjs.org/set-harmonic-interval/-/set-harmonic-interval-1.0.1.tgz"
   integrity sha512-AhICkFV84tBP1aWqPwLZqFvAwqEoVA9kxNMniGEUvzOlm4vLmOFLiTT3UZ6bziJTy4bOVpzWGTfSCbmaayGx8g==
 
+shallowequal@1.1.0:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/shallowequal/-/shallowequal-1.1.0.tgz#188d521de95b9087404fd4dcb68b13df0ae4e7f8"
+  integrity sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==
+
 sharp@^0.31.3:
   version "0.31.3"
   resolved "https://registry.npmjs.org/sharp/-/sharp-0.31.3.tgz"
@@ -6126,11 +6229,6 @@ stream-length@^1.0.1, stream-length@^1.0.2:
   dependencies:
     bluebird "^2.6.2"
 
-streamsearch@^1.1.0:
-  version "1.1.0"
-  resolved "https://registry.npmjs.org/streamsearch/-/streamsearch-1.1.0.tgz"
-  integrity sha512-Mcc5wHehp9aXz1ax6bZUyY5afg9u2rv5cqQI3mRrYkGC8rW2hM02jWuwjtL++LS5qinSyhj2QfLyNsuc+VsExg==
-
 string.prototype.matchall@^4.0.8:
   version "4.0.8"
   resolved "https://registry.npmjs.org/string.prototype.matchall/-/string.prototype.matchall-4.0.8.tgz"
@@ -6252,13 +6350,33 @@ style-to-object@^0.4.1:
   dependencies:
     inline-style-parser "0.1.1"
 
-styled-jsx@5.1.1:
-  version "5.1.1"
-  resolved "https://registry.npmjs.org/styled-jsx/-/styled-jsx-5.1.1.tgz"
-  integrity sha512-pW7uC1l4mBZ8ugbiZrcIsiIvVx1UmTfw7UkC3Um2tmfUq9Bhk8IiyEIPl6F8agHgjzku6j0xQEZbfA5uSgSaCw==
+styled-components@^6.1.8:
+  version "6.1.8"
+  resolved "https://registry.yarnpkg.com/styled-components/-/styled-components-6.1.8.tgz#c109d36aeea52d8f049e12de2f3be39a6fc86201"
+  integrity sha512-PQ6Dn+QxlWyEGCKDS71NGsXoVLKfE1c3vApkvDYS5KAK+V8fNWGhbSUEo9Gg2iaID2tjLXegEW3bZDUGpofRWw==
+  dependencies:
+    "@emotion/is-prop-valid" "1.2.1"
+    "@emotion/unitless" "0.8.0"
+    "@types/stylis" "4.2.0"
+    css-to-react-native "3.2.0"
+    csstype "3.1.2"
+    postcss "8.4.31"
+    shallowequal "1.1.0"
+    stylis "4.3.1"
+    tslib "2.5.0"
+
+styled-jsx@5.1.0:
+  version "5.1.0"
+  resolved "https://registry.yarnpkg.com/styled-jsx/-/styled-jsx-5.1.0.tgz#4a5622ab9714bd3fcfaeec292aa555871f057563"
+  integrity sha512-/iHaRJt9U7T+5tp6TRelLnqBqiaIT0HsO0+vgyj8hK2KUk7aejFqRrumqPUlAqDwAj8IbS/1hk3IhBAAK/FCUQ==
   dependencies:
     client-only "0.0.1"
 
+stylis@4.3.1:
+  version "4.3.1"
+  resolved "https://registry.yarnpkg.com/stylis/-/stylis-4.3.1.tgz#ed8a9ebf9f76fe1e12d462f5cc3c4c980b23a7eb"
+  integrity sha512-EQepAV+wMsIaGVGX1RECzgrcqRRU/0sYOHkeLsZ3fzHaHXZy4DaOOX0vOlGQdlsjkh3mFHAIlVimpwAs4dslyQ==
+
 stylis@^4.0.6:
   version "4.1.3"
   resolved "https://registry.npmjs.org/stylis/-/stylis-4.1.3.tgz"
@@ -6491,16 +6609,16 @@ tslib@2.4.0:
   resolved "https://registry.npmjs.org/tslib/-/tslib-2.4.0.tgz"
   integrity sha512-d6xOpEDfsi2CZVlPQzGeux8XMwLT9hssAsaPYExaQMuYskwb+x1x7J371tWlbBdWHroy99KnVB6qIkUbs5X3UQ==
 
+tslib@2.5.0, tslib@^2.1.0, tslib@^2.3.1, tslib@^2.4.0:
+  version "2.5.0"
+  resolved "https://registry.npmjs.org/tslib/-/tslib-2.5.0.tgz"
+  integrity sha512-336iVw3rtn2BUK7ORdIAHTyxHGRIHVReokCR3XjbckJMK7ms8FysBfhLR8IXnAgy7T0PTPNBWKiH514FOW/WSg==
+
 tslib@^1.8.1, tslib@^1.9.3:
   version "1.14.1"
   resolved "https://registry.npmjs.org/tslib/-/tslib-1.14.1.tgz"
   integrity sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==
 
-tslib@^2.1.0, tslib@^2.3.1, tslib@^2.4.0:
-  version "2.5.0"
-  resolved "https://registry.npmjs.org/tslib/-/tslib-2.5.0.tgz"
-  integrity sha512-336iVw3rtn2BUK7ORdIAHTyxHGRIHVReokCR3XjbckJMK7ms8FysBfhLR8IXnAgy7T0PTPNBWKiH514FOW/WSg==
-
 tsutils@^3.21.0:
   version "3.21.0"
   resolved "https://registry.npmjs.org/tsutils/-/tsutils-3.21.0.tgz"
@@ -6788,6 +6906,11 @@ urlobj@0.0.11:
     is-string "^1.0.4"
     object-assign "^4.1.1"
 
+use-sync-external-store@1.2.0:
+  version "1.2.0"
+  resolved "https://registry.yarnpkg.com/use-sync-external-store/-/use-sync-external-store-1.2.0.tgz#7dbefd6ef3fe4e767a0cf5d7287aacfb5846928a"
+  integrity sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA==
+
 useragent@^2.1.8:
   version "2.3.0"
   resolved "https://registry.npmjs.org/useragent/-/useragent-2.3.0.tgz"