| + Bucket + | ++ Amount (TNT) + | ++ % of Total + | ++ Mechanism + | ++ Claimable + | ++ Launch Liquidity + | +- | - | - | - | - | - | - |
|---|---|---|---|---|---|
| + {b.label} + | ++ {formatTnt(b.amountTnt)} + | ++ {formatPercent(b.amountTnt, TOTAL_TNT)} + | ++ {b.mechanism} + | ++ {b.claimable} + | ++ {b.launchLiquidity} + | +
| + Total + | ++ {formatTnt(TOTAL_TNT)} + | ++ 100.00% + | ++ Snapshot-distributed TNT (migration + carveouts) + | +
-
-
- EVM to Tangle Address Converter
-
- Enter an EVM address to convert it to the prefixed form unique to
- Tangle Network. To convert an SS58 address to a public key or other
- networks, you can use{" "}
-
- SS58.org
-
-
-
-
-
-
-
-
-
- Please note that the conversion from an EVM address to a Tangle
- address using the provided tool is a one-way operation, and you cannot
- derive the original EVM address from a Tangle address.
-
- - Learn more about Addresses on Tangle. - -
-
-
- );
-};
-
-export default AddressConverter;
diff --git a/components/GithubRepoCard.tsx b/components/GithubRepoCard.tsx
index 554b6665..ae202e31 100644
--- a/components/GithubRepoCard.tsx
+++ b/components/GithubRepoCard.tsx
@@ -67,9 +67,25 @@ const GithubRepoCard: React.FC
-
-
-
- setEvmAddress(e.target.value)}
- placeholder="Enter EVM address"
- />
-
-
-
-
-
- {tangleAddress || "Waiting..."}
-
-
-
- - - Learn more about Addresses on Tangle. - -
-
-
-
-
- );
-};
-
-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",
- wssUrl2: "wss://tangle-mainnet-rpc.n.dwellir.com/",
- explorerUrls: [
- { name: "BlockScout", url: "https://explorer.tangle.tools" },
- {
- name: "PolkadotJS",
- url: "https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.tangle.tools#/explorer",
- },
- ],
- fundingInfo: {
- url: "https://discord.gg/PQDYv5GT",
- },
- },
- ];
-
- return (
-
- {type} {cardTitle}
-
-
-
- {network}
-| Network Type | -{type} | -
|---|---|
| Native Asset Symbol | -{symbol} | -
| Native Asset Decimals | -{decimals} | -
| Chain ID | -{chainId} | -
| Public RPC URL | -- {rpcUrl} - | -
| Public WSS URL | -- {wssUrl} - {wssUrl2} - | -
| - {index === 0 ? "Interfaces & Explorers" : ""} - | -- {explorer.name} - | -
- {networks.map((network, index) => (
-
- );
-};
-
-export default NetworkInfo;
diff --git a/components/NetworkConfig.module.css b/components/NetworkConfig.module.css
deleted file mode 100644
index 7ae2f80c..00000000
--- a/components/NetworkConfig.module.css
+++ /dev/null
@@ -1,154 +0,0 @@
-.networkInfo {
- font-family: "Arial", sans-serif;
- max-width: 1200px; /* Increase the max-width */
- margin: 0 auto;
-}
-
-.networkInfo h1,
-.networkInfo h2 {
- color: #000;
- text-align: left;
-}
-
-.titleContainer {
- display: flex; /* Use flexbox to lay out the title and icon */
- align-items: center; /* Align items vertically in the center */
- cursor: pointer; /* Change the cursor to indicate it's clickable */
- border-bottom: 2px solid white;
-}
-
-.networkCard {
- border-radius: 8px;
- padding: 29px;
- margin: 20px 0 0 0;
- background: linear-gradient(45deg, rgb(168 0 198), rgba(255, 0, 0, 0) 70%),
- linear-gradient(-45deg, rgb(190 0 255 / 90%), rgba(0, 0, 255, 0) 70%),
- linear-gradient(135deg, rgb(0 242 245), rgba(0, 255, 0, 0) 70%),
- linear-gradient(-135deg, rgb(117 119 251 / 32%), rgba(255, 255, 0, 0) 70%);
- background-blend-mode: multiply;
- box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.1);
-}
-
-.networkColumn {
- flex: 0 0 48%; /* Set a fixed width for columns */
- max-width: 48%; /* Ensure columns don't exceed this width */
- padding: 0 10px;
-}
-.networkTitle {
- margin-right: 0.5em; /* Add some space between the title and the icon */
-}
-
-.networkCard h2 {
- margin-top: 0;
- color: #fff;
- font-size: 2.8em;
- font-weight: 600;
- line-height: 1.2em;
- padding-bottom: 8px;
- margin-bottom: 2px;
-}
-
-.networkCard h3 {
- margin-top: 20px;
- margin-bottom: 10px;
-}
-
-.networkType {
- color: #ffffff;
- text-transform: uppercase;
- font-family: Arial, Helvetica, sans-serif;
- font-size: 0.8em;
- margin-bottom: 0;
- font-weight: 700;
-}
-.section {
- background: #ffffff;
- border-radius: 8px;
- box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2);
- margin-bottom: 20px;
- padding: 20px;
-}
-
-.table {
- width: 100%;
- border-collapse: collapse;
- border: 0;
- margin-bottom: 8px;
-}
-
-.tableRow {
- text-align: left;
-}
-
-.tableHeader {
- color: #fff;
- font-weight: 400;
- text-align: left;
- padding: 10px;
- border-bottom: 1px solid #e1e4e8;
-}
-
-.tableCell {
- padding: 10px;
- text-align: left;
- border-bottom: 1px solid #e1e4e8;
- color: #fff;
- font-weight: 600;
-}
-
-@media (max-width: 768px) {
- .networkInfo {
- padding: 10px;
- }
-
- .table,
- .th,
- .td {
- font-size: 14px;
- }
-
- .networkColumn {
- flex: 0 0 100%; /* Make columns take full width on smaller screens */
- max-width: 100%;
- padding: 0;
- }
-}
-
-.tabsContainer {
- display: flex;
- justify-content: flex-start;
- margin-bottom: 20px;
- border-bottom: 1px white solid;
-}
-
-.tabButton {
- color: #fff;
- border: none;
- text-align: center;
- text-decoration: none;
- display: inline-block;
- font-size: 16px;
- cursor: pointer;
- transition: background-color 0.3s ease;
- padding-left: 10px;
- padding: 10px 33px 10px 33px;
- margin-right: 10px;
-}
-
-.activeTab {
- color: #fff;
- font-weight: 600;
- border-bottom: 1px solid white;
-}
-
-.networkTabContent {
- padding: 20px;
-}
-
-.mainnetStatus {
- font-size: 1em;
- font-style: italic;
- font-weight: 600;
- margin-left: 0.5em;
- color: #fff;
-}
diff --git a/components/NetworkResources.tsx b/components/NetworkResources.tsx
index 8275a4df..6e535a91 100644
--- a/components/NetworkResources.tsx
+++ b/components/NetworkResources.tsx
@@ -1,14 +1,9 @@
import React, { useState, useEffect } from "react";
import Link from "next/link";
import { BlockCopyButton } from "./ui/block-copy-button";
-import {
- FlaskConical,
- WalletMinimal,
- Waypoints,
- SendToBack,
-} from "lucide-react";
+import { FlaskConical, WalletMinimal, Waypoints } from "lucide-react";
import WalletTable from "./WalletTable";
-import EvmToSubstrateConverter from "./EvmToSubstrateConverter";
+import { DEPLOYMENTS } from "./deployments";
type NetworkDetail = {
property: string;
@@ -33,73 +28,41 @@ const NETWORK_DATA = {
},
},
{
- property: "PolkadotJS Apps",
- value: {
- type: "link",
- url: "https://polkadot.js.org/apps/?rpc=wss://rpc.tangle.tools#/explorer",
- text: "polkadot.js.org/apps/?rpc=wss://rpc.tangle.tools",
- },
+ property: "Deployment chain",
+ value: DEPLOYMENTS.mainnet.deploymentChain,
},
- { property: "Block Explorers", value: "" },
+ { property: "RPC and Explorer", value: "" },
+ { property: "Chain ID", value: DEPLOYMENTS.mainnet.chainId },
{
- property: "EVM Explorer",
- value: {
- type: "link",
- url: "https://explorer.tangle.tools",
- text: "explorer.tangle.tools",
- },
+ property: "Public RPC URL",
+ value: { type: "wss", url: DEPLOYMENTS.mainnet.rpcUrl },
},
{
- property: "Substrate Block Explorer",
+ property: "Block explorer",
value: {
type: "link",
- url: "https://tangle.statescan.io/",
- text: "tangle.statescan.io",
+ url: DEPLOYMENTS.mainnet.explorerUrl,
+ text: DEPLOYMENTS.mainnet.explorerUrl,
},
},
- { property: "Asset Details", value: "" },
- { property: "Native Asset Symbol", value: "TNT" },
- { property: "Native Asset Decimals", value: "18" },
- { property: "Developer Resources", value: "" },
- { property: "Address Prefix", value: { type: "wss", url: "tg" } },
- { property: "Network Type", value: "Substrate aka Polkadot SDK with EVM" },
- { property: "Chain ID", value: { type: "wss", url: "5845" } },
- { property: "Standard Account", value: "*25519" },
+ { property: "Protocol contracts", value: "" },
+ { property: "TNT token", value: DEPLOYMENTS.mainnet.contracts.tntToken },
+ { property: "Tangle", value: DEPLOYMENTS.mainnet.contracts.tangle },
{
- property: "Public RPC URL",
- value: { type: "wss", url: "https://rpc.tangle.tools" },
- },
- {
- property: "Public WSS URL",
- value: { type: "wss", url: "wss://rpc.tangle.tools" },
+ property: "MultiAssetDelegation",
+ value: DEPLOYMENTS.mainnet.contracts.multiAssetDelegation,
},
{
- property: "Public WSS URL by Dwellir",
- value: { type: "wss", url: "wss://tangle-mainnet-rpc.n.dwellir.com" },
- },
- {
- property: "Runtime Types",
- value: {
- type: "link",
- url: "https://www.npmjs.com/package/@tangle-network/tangle-substrate-types",
- text: "@tangle-network/tangle-substrate-types",
- },
+ property: "OperatorStatusRegistry",
+ value: DEPLOYMENTS.mainnet.contracts.operatorStatusRegistry,
},
{
- property: "Telemetry",
- value: {
- type: "link",
- url: "https://telemetry.polkadot.io/#list/0x44f68476df71ebf765b630bf08dc1e0fedb2bf614a1aa0563b3f74f20e47b3e0",
- text: "Telemetry",
- },
+ property: "LiquidDelegationFactory",
+ value: DEPLOYMENTS.mainnet.contracts.liquidDelegationFactory,
},
{
- property: "GitHub Repo",
- value: {
- type: "link",
- url: "https://github.com/tangle-network/tangle",
- text: "github.com/tangle-network/tangle",
- },
+ property: "TangleMigration",
+ value: DEPLOYMENTS.mainnet.contracts.tangleMigration ?? "TBD",
},
] satisfies NetworkDetail[],
testnet: [
@@ -113,70 +76,41 @@ const NETWORK_DATA = {
},
},
{
- property: "PolkadotJS Apps",
- value: {
- type: "link",
- url: "https://polkadot.js.org/apps/?rpc=wss://testnet-rpc.tangle.tools#/explorer",
- text: "polkadot.js.org/apps/?rpc=wss://testnet-rpc.tangle.tools",
- },
+ property: "Deployment chain",
+ value: DEPLOYMENTS.testnet.deploymentChain,
},
- { property: "Block Explorers", value: "" },
+ { property: "RPC and Explorer", value: "" },
+ { property: "Chain ID", value: DEPLOYMENTS.testnet.chainId },
{
- property: "EVM Explorers",
- value: {
- type: "link",
- url: "https://testnet-explorer.tangle.tools",
- text: "testnet-explorer.tangle.tools",
- },
+ property: "Public RPC URL",
+ value: { type: "wss", url: DEPLOYMENTS.testnet.rpcUrl },
},
{
- property: "Substrate Explorer",
+ property: "Block explorer",
value: {
type: "link",
- url: "https://polkadot.js.org/apps/?rpc=wss://testnet-rpc.tangle.tools#/explorer",
- text: "polkadot.js.org/apps/?rpc=wss://testnet-rpc.tangle.tools",
+ url: DEPLOYMENTS.testnet.explorerUrl,
+ text: DEPLOYMENTS.testnet.explorerUrl,
},
},
- { property: "Asset Details", value: "" },
- { property: "Native Asset Symbol", value: "tTNT" },
- { property: "Native Asset Decimals", value: "18" },
- { property: "Developer Resources", value: "" },
- { property: "Address Prefix", value: "tg" },
- { property: "Network Type", value: "Substrate aka Polkadot SDK with EVM" },
- { property: "Chain ID", value: "3799" },
- { property: "Address Prefix", value: "tg" },
- { property: "Standard Account", value: "*25519" },
+ { property: "Protocol contracts", value: "" },
+ { property: "TNT token", value: DEPLOYMENTS.testnet.contracts.tntToken },
+ { property: "Tangle", value: DEPLOYMENTS.testnet.contracts.tangle },
{
- property: "Public RPC URL",
- value: { type: "wss", url: "https://testnet-rpc.tangle.tools" },
+ property: "MultiAssetDelegation",
+ value: DEPLOYMENTS.testnet.contracts.multiAssetDelegation,
},
{
- property: "Public WSS URL",
- value: { type: "wss", url: "wss://testnet-rpc.tangle.tools" },
+ property: "OperatorStatusRegistry",
+ value: DEPLOYMENTS.testnet.contracts.operatorStatusRegistry,
},
{
- property: "Runtime Types",
- value: {
- type: "link",
- url: "https://www.npmjs.com/package/@tangle-network/tangle-substrate-types",
- text: "@tangle-network/tangle-substrate-types",
- },
+ property: "LiquidDelegationFactory",
+ value: DEPLOYMENTS.testnet.contracts.liquidDelegationFactory,
},
{
- property: "Telemetry",
- value: {
- type: "link",
- url: "https://telemetry.polkadot.io/#list/0x3d22af97d919611e03bbcbda96f65988758865423e89b2d99547a6bb61452db3",
- text: "Polkadot Telemetry",
- },
- },
- {
- property: "GitHub Repo",
- value: {
- type: "link",
- url: "https://github.com/tangle-network/tangle",
- text: "github.com/tangle-network/tangle",
- },
+ property: "TangleMigration",
+ value: DEPLOYMENTS.testnet.contracts.tangleMigration ?? "TBD",
},
] satisfies NetworkDetail[],
} as const;
@@ -190,7 +124,7 @@ const NetworkTabs = () => {
const hash = window.location.hash.substring(1);
// If hash matches one of our tabs, set it as active
- if (["mainnet", "testnet", "wallets", "evmToSubstrate"].includes(hash)) {
+ if (["mainnet", "testnet", "wallets"].includes(hash)) {
setActiveTab(hash);
} else {
// Explicitly set to mainnet if no valid hash is present
@@ -329,28 +263,11 @@ const NetworkTabs = () => {
Wallets
-
{activeTab === "wallets" ? (
);
diff --git a/components/RestakeFlowDiagram.tsx b/components/RestakeFlowDiagram.tsx
new file mode 100644
index 00000000..250fe5f8
--- /dev/null
+++ b/components/RestakeFlowDiagram.tsx
@@ -0,0 +1,96 @@
+import React from "react";
+
+type BoxProps = {
+ title: string;
+ lines: string[];
+};
+
+function Box({ title, lines }: BoxProps) {
+ return (
+
+
+ );
+}
+
+function Arrow() {
+ return (
+ {title}
+ -
+ {lines.map((line) => (
+
- {line} + ))} +
+ →
+
+ );
+}
+
+export default function RestakeFlowDiagram() {
+ return (
+
+
+ );
+}
diff --git a/components/Social.tsx b/components/Social.tsx
index b9e91811..2b9604ec 100644
--- a/components/Social.tsx
+++ b/components/Social.tsx
@@ -36,7 +36,7 @@ function Twitter() {
diff --git a/components/TableOfContentCards.tsx b/components/TableOfContentCards.tsx
index b4dd3750..b4889148 100644
--- a/components/TableOfContentCards.tsx
+++ b/components/TableOfContentCards.tsx
@@ -96,16 +96,16 @@ export default TableOfContentCards;
/*
const tocItems = [
{
- title: "Distributed Validator Infrastructure",
- href: "#distributed-validator-infrastructure",
+ title: "Blueprint Operators",
+ href: "#blueprint-operators",
subItems: [
{
- title: "Obol DVT and validator clusters",
- href: "#obol-dvt" // Optional specific anchor
+ title: "Running the Blueprint Manager",
+ href: "#blueprint-manager" // Optional specific anchor
},
{
- title: "Secure multi-party validation",
- href: "#secure-validation"
+ title: "Pricing and quality of service",
+ href: "#pricing-and-qos"
}
]
},
diff --git a/components/TangleQuickstart.tsx b/components/TangleQuickstart.tsx
deleted file mode 100644
index cf7b9640..00000000
--- a/components/TangleQuickstart.tsx
+++ /dev/null
@@ -1,109 +0,0 @@
-import { HiOutlineServerStack as ServerIcon } from "react-icons/hi2";
-import {
- DiscordIcon,
- TelegramIcon,
- DockerIcon,
- PrometheusIcon,
- GrafanaIcon,
-} from "./Icons";
-import { DetailedFeatureLink } from "./Feature";
-
-export const QuickDeployArea = () => {
- return (
-
+ High-level restaking flow: deposits → delegation → service activity →
+ fees/rewards → (optional) slashing.
+
+
+
+
+
+
+
+
-
- );
-};
-
-export const DeployArea = () => {
- return (
-
-
- );
-};
-
-export const SupportArea = () => {
- return (
-
-
- );
-};
-
-export const MonitoringArea = () => {
- return (
-
-
- );
-};
diff --git a/components/WalletTable.tsx b/components/WalletTable.tsx
index 5619743e..1cd9e379 100644
--- a/components/WalletTable.tsx
+++ b/components/WalletTable.tsx
@@ -2,21 +2,6 @@ import React from "react";
import Link from "next/link";
const WALLET_DATA = [
- {
- name: "Subwallet",
- supports: "Substrate",
- url: "https://www.subwallet.app/download.html",
- },
- {
- name: "Polkadot.js Extension",
- supports: "Substrate",
- url: "https://polkadot.js.org/",
- },
- {
- name: "Talisman Wallet",
- supports: "Substrate",
- url: "https://www.talisman.xyz/",
- },
{
name: "Rainbow Wallet",
supports: "EVM",
@@ -31,11 +16,9 @@ const WalletTable = () => {
Wallets
- The Tangle Network is a versatile blockchain that integrates both - Substrate and Ethereum Virtual Machine (EVM) functionalities, offering a - wide range of features and compatibility with numerous wallets. This - document outlines the wallets available for use on the Tangle Network, - including details for both the Substrate and EVM sides of the network. + Tangle apps use standard EVM wallets. Use one of the wallets below to + connect to `app.tangle.tools` and interact with Tangle deployments on + the underlying EVM chain.Network Details for Adding to Wallets
- Substrate Wallets: - Follow the specific wallet instructions to add the Tangle Network as a - custom network. We work to ensure these wallets have the latest - information and in-app support to connect. - {" "} EVM Wallets - Add the Tangle Network using the ChainID and a RPC server address on - this page. + Add the underlying EVM chain used for the Tangle deployment (mainnet or + testnet). RPC URLs, chain IDs, and explorers are deployment-dependent + and are published in the network resources tab. Please follow the standard process in your wallet to add a new network, - using the ChainID and the RPC server addresses provided above. + using the chain ID and RPC server addresses provided for that + deployment.
-
-
-Replace `Tangle Chain Information
-You can view the latest details on networks, chainIDs, RPC URLs on the [Network Information and Configurations](/network-information-configuration/) page. -- Source: Any
- Destination: 30333, 30334 TCP | - -### Running Ports - -As stated before, the standalone nodes will listen on multiple ports. The default Substrate ports are used in the standalone chain. - -The only ports that need to be open for incoming traffic are those designated for P2P. - -**Default Ports for a Tangle Full-Node:** - -| Description | Port | -| ----------- | ----------- | -| P2P | 30333 (TCP) | -| RPC | 9933 | -| WS | 9944 | -| Prometheus | 9615 | diff --git a/pages/operators/node-basics/node-software.mdx b/pages/operators/node-basics/node-software.mdx deleted file mode 100644 index 41c52571..00000000 --- a/pages/operators/node-basics/node-software.mdx +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Node Software and Binaries -description: An overview of Tangle Network software and how to run a node. ---- - -import { Tabs, Tab } from "/components/Tabs"; -import Callout from "/components/Callout"; - -# Running a Tangle Node - -This guide provides an overview of the Tangle Network software and instructions on how to run a node. - -## Prerequisites - -Before running a Tangle node, ensure that your machine meets the following requirements: - -- Operating System: Linux (recommended), macOS, or Windows -- Hardware: Sufficient CPU, RAM, and storage capacity to synchronize and store the blockchain data - -## Installing the Tangle Node Binary - -To install the Tangle node binary, follow these steps: - -1. Download the latest release binary from the [Tangle releases page](https://github.com/tangle-network/tangle/releases). The current latest version is 1.0.0. - - ```sh filename="Get binary" copy - wget https://github.com/tangle-network/tangle/releases/download/v1.0.0/tangle-default-linux-amd64 - - ``` - -2. Make the downloaded binary executable - `chmod +x tangle-default-linux-amd64` - -## Running the Tangle Node - -To start your Tangle node and begin synchronizing with the network, run the following command: -`./tangle-default-linux-amd64` - -Your node will start synchronizing with the Tangle Network. Once the synchronization process is complete, your node will be fully operational. - -### Running a Node with SystemD or Docker - -For production environments, it is recommended to run your Tangle node using a process manager like SystemD or Docker. This ensures that your node runs consistently and automatically restarts in case of any issues. - -Please refer to the guides in sidebar for instructions on running a Tangle node with SystemD or Docker. - -## Default Ports for a Tangle Node - -The following table lists the default ports used by a Tangle node: - -## Feature Flags - -The Tangle node software includes several feature flags that enable additional functionality. Here are some notable feature flags: - -- `txpool`: Enables transaction tracing and debugging for EVM transactions. -- `relayer`: Starts an embedded transaction relayer for transaction relaying and data querying. -- `light-client`: Starts an embedded light client for syncing EVM data on Tangle. - -To build the Tangle node with specific feature flags enabled, use the following command: - -`cargo build --release --features
USDT | [`0xb6dc6c8b71e88642cead3be1025565a9ee74d1c6`](https://explorer.tangle.tools/address/0xb6dc6c8b71e88642cead3be1025565a9ee74d1c6) |
-| **USD Coin** | 
USDC | [`0x97eec1c29f745dc7c267f90292aa663d997a601d`](https://explorer.tangle.tools/address/0x97eec1c29f745dc7c267f90292aa663d997a601d) |
-| **Wrapped Ether** | 
WETH | [`0x01b4ce0d48ce91eb6bcaf5db33870c65d641b894`](https://explorer.tangle.tools/address/0x01b4ce0d48ce91eb6bcaf5db33870c65d641b894) |
-| **Avail** | 
AVAIL | [`0xb8a09939F27908505C4241C3c251f3DA33a207A9`](https://explorer.tangle.tools/address/0xb8a09939F27908505C4241C3c251f3DA33a207A9) |
diff --git a/pages/resources/sablier.mdx b/pages/resources/sablier.mdx
deleted file mode 100644
index 1d2eed60..00000000
--- a/pages/resources/sablier.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# Sablier Deployments
-
-Sablier is a protocol for real-time finance on EVM blockchains, enabling programmable token streams and vesting. It allows for continuous payments where tokens are streamed over time rather than transferred in one go.
-
-## Core Contracts
-
-Below are the core contract addresses for Sablier V2 deployed on the Tangle mainnet. You can view each contract on our [Blockscout Mainnet Explorer](https://explorer.tangle.tools/).
-
-| Contract | Address | Version |
-| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
-| **SablierV2LockupDynamic** | [`0x946654AB30Dd6eD10236C89f2C8B2719df653691`](https://explorer.tangle.tools/address/0x946654AB30Dd6eD10236C89f2C8B2719df653691) | [core-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/core) |
-| **SablierV2LockupLinear** | [`0xAC19F4181E58efb7094e0cb4e1BB18c79F6AAdf4`](https://explorer.tangle.tools/address/0xAC19F4181E58efb7094e0cb4e1BB18c79F6AAdf4) | [core-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/core) |
-| **SablierV2LockupTranched** | [`0x63B92F7E2f69877184C955E63B9D8Dff55e52e14`](https://explorer.tangle.tools/address/0x63B92F7E2f69877184C955E63B9D8Dff55e52e14) | [core-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/core) |
-| **SablierV2NFTDescriptor** | [`0xe785101Cb228693cc3EFdCd5d637fEf6A6Ff7259`](https://explorer.tangle.tools/address/0xe785101Cb228693cc3EFdCd5d637fEf6A6Ff7259) | [core-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/core) |
-
-## Periphery Contracts
-
-| Contract | Address | Version |
-| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
-| **SablierV2BatchLockup** | [`0x28D116d7e917756310986C4207eA54183fcba06A`](https://explorer.tangle.tools/address/0x28D116d7e917756310986C4207eA54183fcba06A) | [periphery-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/periphery) |
-| **SablierV2MerkleLockupFactory** | [`0x5e73bb96493C10919204045fCdb639D35ad859f8`](https://explorer.tangle.tools/address/0x5e73bb96493C10919204045fCdb639D35ad859f8) | [periphery-v1.2.0](https://github.com/sablier-labs/deployments/tree/main/lockup/v1.2.0/periphery) |
diff --git a/pages/resources/safe.mdx b/pages/resources/safe.mdx
deleted file mode 100644
index 32188c77..00000000
--- a/pages/resources/safe.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Safe Deployments
-
-Safe (formerly Gnosis Safe) is a smart contract wallet focused on secure management of digital assets. It provides multi-signature functionality and other advanced security features for managing digital assets on EVM-compatible blockchains. Safe enables users to require multiple signatures to execute transactions, enhancing security for digital asset management.
-
-Safe contracts deployed deployed and a [Safe UI is hosted by Den](https://safe.onchainden.com/welcome?chain=tnt).
-
-## Contract Deployments
-
-Below are the key contract deployments for Safe on the Tangle network. You can view each contract on our [Blockscout Explorer](https://explorer.tangle.tools/).
-
-| Contract Name | Address |
-| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| **Safe Implementation** | [`0xfb1bffC9d739B8D520DaF37dF666da4C687191EA`](https://explorer.tangle.tools/address/0xfb1bffC9d739B8D520DaF37dF666da4C687191EA) |
-| **Proxy Factory** | [`0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC`](https://explorer.tangle.tools/address/0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC) |
diff --git a/pages/resources/set-identity.mdx b/pages/resources/set-identity.mdx
deleted file mode 100644
index 841588d4..00000000
--- a/pages/resources/set-identity.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
-# On-Chain Identity on the Tangle Network
-
-## Introduction
-
-The Tangle Network provides a naming system that allows participants to add personal information to their on-chain account and subsequently ask for verification of this information by registrars. This feature enhances trust and security within the ecosystem by allowing network participants to verify each other's identities through on-chain data.
-
-## Understanding Identity on the Tangle Network
-
-### Setting an Identity
-
-Users must reserve funds in a bond to store their information on-chain: ~1-6 TNT and some TNT per each field beyond the legal name. These funds are locked, not spent - they are returned when the identity is cleared.
-
-### Judgements
-
-After a user injects their information on-chain, they can request judgement from a registrar. Users declare a maximum fee that they are willing to pay for judgement, and registrars whose fee is below that amount can provide a judgement.
-
-Registrars can select up to six levels of confidence in their attestation:
-
-1. Unknown: The default value, no judgement made yet.
-2. Reasonable: The data appears reasonable, but no in-depth checks (e.g., formal KYC process) were performed.
-3. Known Good: The registrar has certified that the information is correct (this step involves verification of state-issued identity documents).
-4. Out of Date: The information used to be good but is now out of date.
-5. Low Quality: The information is low quality or imprecise but can be fixed with an update.
-6. Erroneous: The information is erroneous and may indicate malicious intent.
-
-A seventh state, "fee paid", is for when a user has requested judgement and it is in progress. Information that is in this state or "erroneous" is "sticky" and cannot be modified; it can only be removed by the complete removal of the identity.
-
-### Registrars
-
-Registrars can set a fee for their services and limit their attestation to certain fields. For example, a registrar could charge [placeholder fee] TNT to verify one's legal name, email, and GPG key.
-
-There is currently 1 registrar on the Tangle Network:
-
-1. Registrar `0`:
- - Account: `tgDhkcoQaPqWM9NSKr8WjyRmy2gFCnt1tym4RuUR8SUNEH5vD`
- - Fee: 0 TNT
-
-### Sub-Identities
-
-Users can also link accounts by setting "sub-accounts", each with its own identity, under a primary account. The system reserves a bond for each sub-account. An example of how you might use this would be a validation company running multiple validators.
-
-An account can have a maximum of 100 sub-accounts. Note that a deposit of 1 TNT is required for every sub-account.
-
-## Setting Your On-Chain Identity Using Polkadot.js Apps
-
-Follow these steps to set your on-chain identity:
-
-1. Access Polkadot.js Apps by opening your web browser and navigating to Tangle Network on [Polkadot.js Apps](https://polkadot.js.org/apps/?rpc=wss://rpc.tangle.tools#/accounts).
-2. Connect your Polkadot.js extension wallet by clicking on the "Accounts" tab in the Polkadot.js Apps interface.
-3. Navigate to the "Accounts" page and locate the account you wish to set an identity for. Click on the three dots on the right side to open a dropdown menu and select "Set on-chain identity."
-4. Fill in the identity information form with details such as your legal name, email, Twitter handle, website, Riot (Matrix) username, etc. You do not need to fill out all fields, just the ones relevant to your identity.
-5. After filling out the form, scroll down and click "Set Identity" to proceed. Your Polkadot.js extension will prompt you to sign the transaction. Review the information and fees, then sign the transaction to confirm your identity setup.
-
-## Verification (Optional)
-
-After setting your on-chain identity, you may want to get it verified by a registrar. This step is optional but adds an additional layer of trust to your identity.
-
-1. Navigate to the "Accounts" page.
-2. Next to your account with the pending identity, you'll see a "Judgements" section. Click "Request Judgement."
-3. Select a registrar from the list and follow their specific instructions for verification.
-4. You can go to the #registrar channel of our Discord to confirm your request for judgement. See our [community tab on Tangle.tools](https://www.tangle.tools/) for links to Discord.
-
-## Conclusion
-
-Setting an on-chain identity on the Tangle Network is a valuable way to enhance your visibility and trustworthiness within the ecosystem. By understanding the identity system and following the steps to set and verify your identity using Polkadot.js Apps, you can take advantage of this feature. Remember, the information you provide will be publicly visible on the blockchain, so only include details you're comfortable sharing.
diff --git a/pages/resources/useful-contracts.mdx b/pages/resources/useful-contracts.mdx
deleted file mode 100644
index 0cc8d002..00000000
--- a/pages/resources/useful-contracts.mdx
+++ /dev/null
@@ -1,131 +0,0 @@
-# Useful Contracts
-
-## MultiSend
-
-This contract allows you to send identical amounts of TNT to multiple addresses in a single transaction. Useful for batching transactions for airdrop distributions.
-
-Explorer: [0x55E25dF92f6a7384844964a6e2a85fa182f8abfa](https://explorer.tangle.tools/address/0x55E25dF92f6a7384844964a6e2a85fa182f8abfa?tab=txs)
-
-```solidity
-// SPDX-License-Identifier: MIT
-pragma solidity ^0.8.0;
-
-contract MultiSend {
- constructor() {}
-
- function multiSend(address[] calldata recipients, uint256[] calldata amounts) external payable {
- require(recipients.length == amounts.length, "Arrays must be same length");
- require(recipients.length > 0, "Must provide at least one recipient");
-
- uint256 total = 0;
- for(uint256 i = 0; i < amounts.length; i++) {
- total += amounts[i];
- }
- require(msg.value >= total, "Insufficient funds sent");
-
- for(uint256 i = 0; i < recipients.length; i++) {
- (bool success,) = recipients[i].call{value: amounts[i]}("");
- require(success, "Transfer failed");
- }
-
- // Return excess ETH if any
- uint256 remaining = msg.value - total;
- if (remaining > 0) {
- (bool success,) = msg.sender.call{value: remaining}("");
- require(success, "Failed to return remaining ETH");
- }
- }
-}
-```
-
-## Multicall3
-
-Multicall3 has two main use cases:
-
-1. Aggregate results from multiple contract reads into a single JSON-RPC request.
-2. Execute multiple state-changing calls in a single transaction.
-
-Read more about Multicall3 [here](https://github.com/mds1/multicall3).
-
-Testnet Explorer: [0xcA11bde05977b3631167028862bE2a173976CA11](https://testnet-explorer.tangle.tools/address/0xca11bde05977b3631167028862be2a173976ca11)
-
-Mainnet Explorer: [0xcA11bde05977b3631167028862bE2a173976CA11](https://explorer.tangle.tools/address/0xcA11bde05977b3631167028862bE2a173976CA11)
-
-```typescript
-import assert from 'node:assert';
-import { createPublicClient, defineChain, erc20Abi, http } from 'viem';
-
-assert(process.env.RPC_URL, 'RPC_URL is not set');
-
-const TANGLE_TESTNET = defineChain({
- id: 3799,
- name: 'Tangle EVM Testnet',
- nativeCurrency: {
- name: 'Tangle Native Token',
- symbol: 'tTNT',
- decimals: 18,
- },
- rpcUrls: {
- default: {
- http: [process.env.RPC_URL],
- },
- },
- contracts: {
- multicall3: {
- address: '0xcA11bde05977b3631167028862bE2a173976CA11',
- blockCreated: 776767,
- },
- },
-});
-
-// Setup the client.
-const client = createPublicClient({
- chain: TANGLE_TESTNET,
- transport: http(process.env.RPC_URL),
-});
-
-const ERC20_ADDRESS = '0x87d95f134221D9c2b3dE15aCe58BACe4121c07B0';
-
-async function example1() {
- // Execute the multicall and get the erc20 metadata (name, symbol, decimals). None of these calls can fail so we set
- // `allowFailure` to false. This results in each return value's type matching the type of the
- // corresponding call, e.g. `0x${string}` for addresses, `bigint` for uint256, etc. If we set
- // `allowFailure` to true then the returns types are of the following shape, using the example of
- // the address return type:
- // {
- // error: Error;
- // result?: undefined;
- // status: "error";
- // } | {
- // error?: undefined;
- // result: `0x${string}`;
- // status: "success";
- // }
- const [name, symbol, decimals] = await client.multicall({
- contracts: [
- {
- address: ERC20_ADDRESS,
- abi: erc20Abi,
- functionName: 'name',
- },
- {
- address: ERC20_ADDRESS,
- abi: erc20Abi,
- functionName: 'symbol',
- },
- {
- address: ERC20_ADDRESS,
- abi: erc20Abi,
- functionName: 'decimals',
- },
- ],
- allowFailure: false,
- });
-
- console.log(
- `Token ${name} has a symbol of ${symbol} and ${decimals} decimals at address ${ERC20_ADDRESS} on ${TANGLE_TESTNET.name}`,
- );
-}
-
-example1().catch(console.error);
-```
diff --git a/pages/restake/_meta.ts b/pages/restake/_meta.ts
index 17996508..b5b20124 100644
--- a/pages/restake/_meta.ts
+++ b/pages/restake/_meta.ts
@@ -6,36 +6,18 @@ const meta: Meta = {
title: "Introduction",
},
introduction: "Overview",
- "staking-intro": "Introduction to Staking",
- nominator: "Nominating your TNT",
- "restake-concepts": "Core concepts",
- "-- restaking": {
- type: "separator",
- title: "Restaking",
- },
"restake-introduction": "Tangle Restaking",
+ "restake-concepts": "Core Concepts",
+ risks: "Risks",
incentives: "Incentives",
- credits: "Tangle Credits",
how_to_restake: "How to Restake on Tangle",
restake_developers: "Developer Docs",
- "-- liquid staking": {
- type: "separator",
- title: "Liquid Staking",
- },
- "lst-concepts": "Introduction to Liquid Staking",
- "lst-working": "How Liquid Staking Works",
- create_a_pool: "Create a Liquid Staking Pool",
- join_a_pool: "Join a Liquid Staking Pool",
- "lst-rewards": "Incentives",
- "lst-assets": "Supported Assets",
- lst_developers: "Developer Docs",
"-- liquid restaking": {
type: "separator",
title: "Liquid Restaking",
},
- "lrt-concepts": "Introduction to Liquid Restaking",
- "lrt-vs-lst": "Liquid Restaking vs. Liquid Staking",
- lrt_developers: "Developer Docs",
+ "lrt-concepts": "Liquid Delegation Vaults",
+ lrt_developers: "Vault Developer Docs",
};
export default meta;
diff --git a/pages/restake/create_a_pool/_meta.ts b/pages/restake/create_a_pool/_meta.ts
deleted file mode 100644
index b623ce2b..00000000
--- a/pages/restake/create_a_pool/_meta.ts
+++ /dev/null
@@ -1,10 +0,0 @@
-import { Meta } from "nextra";
-
-const meta: Meta = {
- "pool-roles": "Pool Roles",
- "benefits-and-risks": "Benefits and Risks",
- "lst-pool-create-tangle": "Create using Tangle DApp",
- "lst-pool-create": "Create using PolkadotJS",
-};
-
-export default meta;
diff --git a/pages/restake/create_a_pool/benefits-and-risks.mdx b/pages/restake/create_a_pool/benefits-and-risks.mdx
deleted file mode 100644
index 77171e07..00000000
--- a/pages/restake/create_a_pool/benefits-and-risks.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
-## Benefits of Creating a Liquid Staking Pool
-
-### 1. **Earning Commission**
-
-- **Benefit:** As the root or operator of the pool, you have the ability to set commission rates on staking rewards. This commission is taken from the pool’s rewards and serves as compensation for managing and maintaining the pool.
-- **Impact:** The ability to earn a commission makes creating and managing a pool financially rewarding. Commission earnings grow as the pool attracts more participants.
-
-### 2. **Building a Community**
-
-- **Benefit:** A well-managed staking pool can attract a large number of participants. As the pool creator, you can build a strong community around your pool, fostering trust and loyalty.
-- **Impact:** A loyal community of participants ensures a steady inflow of assets into the pool, making it sustainable in the long term. This can also enhance the pool’s reputation and attract more participants.
-
-### 3. **Increased Security and Decentralization**
-
-- **Benefit:** By creating a liquid staking pool, you contribute to the overall security and decentralization of the Tangle Network. Larger pools with more participants help secure the network by distributing stake across multiple validators.
-- **Impact:** A decentralized network is more secure and resilient, benefiting the entire ecosystem. As a pool creator, you play a role in strengthening the Tangle Network’s security and robustness.
-
-## Risks of Creating and Managing a Pool
-
-### 1. **Validator Performance Risk**
-
-- **Risk:** If the pool’s nominator selects poor-performing validators, the pool could lose rewards or face slashing penalties. This could lead to a loss of trust among participants and damage the pool’s reputation.
-- **Mitigation:** To minimize this risk, pool operators should conduct thorough research and choose validators with a proven track record of reliability and performance.
-
-### 2. **Security Risks**
-
-- **Risk:** Pools can be targeted by malicious actors who seek to exploit vulnerabilities in pool management or validator selection.
-- **Mitigation:** Pool operators should implement strong security practices, such as regularly auditing pool operations, ensuring proper governance mechanisms, and closely monitoring participant behavior.
diff --git a/pages/restake/create_a_pool/lst-pool-create-tangle.mdx b/pages/restake/create_a_pool/lst-pool-create-tangle.mdx
deleted file mode 100644
index ac61f48f..00000000
--- a/pages/restake/create_a_pool/lst-pool-create-tangle.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-## How to Create a Liquid Staking Pool Using Tangle DApp
-
-### Step 1: Access Tangle DApp & Connect Wallet
-
-- Open [Tangle DApp's Liquid Staking page](https://app.tangle.tools/liquid-staking).
-- Connect your wallet to the DApp by clicking on the **Connect Wallet** button on the top right and selecting your preferred wallet provider.
-- Connect to the desired Tangle network by selecting the appropriate network from the dropdown list. Note that liquid staking pools are only available on the networks in which they are created.
-
-
-
-### Step 2: Configure & Create a Pool
-
-- Once on the liquid staking page, scroll down until you see the **CREATE POOL** button. Click on it to bring up a form where you can configure your new pool.
-
-
-
-- Choose a brief, descriptive name for your pool so that other users can easily identify it, enter an initial bond amount, and set the pool's roles (Root, Nominator, Bouncer).
-- By default, all of the roles will be assigned to the active wallet's address. You can change these addresses to other accounts if needed.
-- Some details such as the pool's commission and nominations can be set **after** the pool is created: You'll be able to easily manage it under the **My Pools** tab.
-- Once you've entered and verified all the details, click on the **Create Pool** button to initiate the transaction.
-
-
-
-### Step 3: Manage Your Pool
-
-- After you've created your pool, you can view & manage it under the **My Pools** tab. Here, you can set the commission rate, manage nominations, and view the pool's performance. In case that you don't see the pool you've just created right away, try refreshing the page.
-- Note that the `MANAGE` button or some of its dropdown options will only be visible **if the active account has the corresponding role**. For example, only the account with the nominator role will be able to see the `Update Nominations` button on the dropdown. If you've set all roles to the same account, you will have all the management options available.
-
-
diff --git a/pages/restake/create_a_pool/lst-pool-create.mdx b/pages/restake/create_a_pool/lst-pool-create.mdx
deleted file mode 100644
index ac610180..00000000
--- a/pages/restake/create_a_pool/lst-pool-create.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
-## How to Create a Liquid Staking Pool Using PolkadotJS
-
-### Step 1: Access the PolkadotJS Interface
-
-- Open [PolkadotJS Apps](https://polkadot.js.org/apps/).
-- Connect to the desired Tangle network by selecting the appropriate network from the left dropdown list. Note that liquid staking pools are only available on the networks in which they are created.
-- In case that the network that you're looking for is not listed on the dropdown list, input its RPC endpoint under the `DEVELOPMENT` → `custom endpoint` input.
-
-For convenience, here are the PolkadotJS direct links for Tangle Testnet and Mainnet:
-
-- Tangle Testnet: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftestnet-rpc.tangle.tools#/explorer
-- Tangle Mainnet: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.tangle.tools#/explorer
-
-### Step 2: Check Pool Creation Requirements
-
-- In order to prevent spam, pool creation may require a minimum bond amount to be deposited. Ensure that you have enough funds in your account to cover this requirement.
-- These funds will not be forfeited; they will be bonded to the pool and will be returned to you when the pool is dissolved.
-
-
-
-### Step 3: Create a Pool
-
-- Navigate to the **Developer** → **Extrinsics** tab on PolkadotJS.
-
-
-
-- Under the **lst** section, select **create(...)**.
-- Enter the required details such as:
- - **Initial deposit amount**: The amount of tokens you are contributing to the pool. This is in lowest unit, so should be in 18 decimal places.
- - **Root account address**: The account that will be responsible for managing the pool.
- - **Nominator account address**: The account that will nominate validators for the pool.
- - **Bouncer account address**: The account responsible for managing participant entries and exits.
- - **Pool Name**: Choose a brief and descriptive name for your pool. Does not need to be unique.
-
-You can use the same account for the root, nominator and bouncer or different accounts.
-
-
-
-Sign and submit the transaction. Make sure the account you are using has enough balance to cover the transaction fee and pool deposit.
-
-
-
-If successful, you should see the following confirmation toast notification:
-
-
-
-Let's break down the events. Navigate to the **Network** → **Explorer** tab, and you should see the following events:
-
-
-
-- **lst.Bonded**: Your initial deposit was bonded to the pool.
-- **lst.Created**: Pool creation confirmation, along with the pool's unique ID.
-- **assets.Issued**: A new asset (LST) was created and issued the staked tokens to the creator.
-
-### Step 4: Configure Commission and Roles (Optional)
-
-- Set the commission rate you wish to charge as the pool manager by navigating to the **Developer** → **Extrinsics** tab, and under the **lst** section, selecting **setCommission(...)**.
-- Note that this amount is in **perbill** (1/1,000,000) units, so a commission rate of 10% would be entered as `100 000`. Another example, a commission rate of 12.34% would be entered as `123 400`.
-
-
diff --git a/pages/restake/create_a_pool/pool-roles.mdx b/pages/restake/create_a_pool/pool-roles.mdx
deleted file mode 100644
index b045449c..00000000
--- a/pages/restake/create_a_pool/pool-roles.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
-## Roles in a Liquid Staking Pool
-
-There are several key roles involved in creating and maintaining a liquid staking pool:
-
-### 1. **Root**
-
-- **Role Description:** The root is the administrator of the pool with full control over its operations. They are responsible for setting and updating pool roles and managing critical operations like commission setup and governance decisions.
-- **Benefits:** As the root, you have the ability to control the overall direction of the pool, set commission rates, and earn a portion of the staking rewards through commissions.
-- **Risks:** The root must ensure that the pool operates fairly and transparently to maintain the trust of the participants. Mismanagement or excessive fees could drive users away.
-
-### 2. **Nominator**
-
-- **Role Description:** The nominator is responsible for selecting validators on behalf of the pool. Their role is critical in optimizing rewards for the pool members by choosing high-performing and secure validators.
-- **Benefits:** The nominator can enhance the pool’s performance by choosing the best validators, maximizing rewards for participants.
-- **Risks:** Poor validator selection could result in missed rewards or penalties, impacting the overall pool performance and the trust of participants.
-
-### 3. **Bouncer**
-
-- **Role Description:** The bouncer is responsible for managing the entry and exit of participants into the pool. They can block or allow participants, as well as manage pool access settings.
-- **Benefits:** This role ensures the integrity of the pool by maintaining strict control over its participants.
-- **Risks:** If the bouncer mismanages pool access or fails to protect against malicious actors, it can result in pool exploitation or security vulnerabilities.
-
-### 4. **Depositor**
-
-- **Role Description:** The depositor is the individual or entity that creates the pool by making an initial deposit. This role is critical because the depositor effectively initiates the pool’s staking process.
-- **Benefits:** As the creator of the pool, the depositor can dictate initial terms and pool configurations. They also have the opportunity to collect significant rewards from the pool’s success.
-- **Risks:** The depositor’s funds are locked as long as the pool remains operational, limiting liquidity. If the pool fails to attract enough participants or operate effectively, the depositor may face opportunity costs.
diff --git a/pages/restake/credits/_meta.ts b/pages/restake/credits/_meta.ts
deleted file mode 100644
index 09c936d3..00000000
--- a/pages/restake/credits/_meta.ts
+++ /dev/null
@@ -1,9 +0,0 @@
-import { Meta } from "nextra";
-
-const meta: Meta = {
- index: "Overview",
- claiming: "How to Claim Credits",
- precompile: "Credits Precompile",
-};
-
-export default meta;
diff --git a/pages/restake/credits/claiming.mdx b/pages/restake/credits/claiming.mdx
deleted file mode 100644
index 4485516a..00000000
--- a/pages/restake/credits/claiming.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: How to Claim Credits
-description: Step-by-step guide to claiming your earned credits from the Cloud Credits pallet
----
-
-# How to Claim Credits
-
-This guide walks you through the process of claiming your earned credits from TNT staking through the Cloud Credits pallet.
-
-## Prerequisites
-
-- **Active TNT Stake**: You must have TNT staked through Tangle's multi-asset delegation system
-- **Minimum Stake**: Your stake must meet the lowest tier threshold to earn credits
-- **Off-chain Account**: An identifier linking your claim to off-chain credit management
-
-## Claiming via Polkadot.js Apps
-
-### Step 1: Connect to Tangle Network
-
-1. Go to [Polkadot.js Apps](https://polkadot.js.org/apps)
-2. Connect to the Tangle Network endpoint
-3. Import or connect your account with TNT stake
-
-### Step 2: Navigate to Extrinsics
-
-1. Go to **Developer** → **Extrinsics**
-2. Select your account from the dropdown
-3. Choose `cloudCredits` from the pallet list
-4. Select `claimCredits` from the call dropdown
-
-### Step 3: Fill Parameters
-
-**Amount to Claim (`amount_to_claim`):**
-
-- Enter the number of credits you want to claim
-- Must not exceed your accrued amount within the claim window
-- Use the RPC query (see below) to check your maximum claimable amount
-
-**Off-chain Account ID (`offchain_account_id`):**
-
-- Your identifier for linking to off-chain credit systems
-- Maximum length is configurable (check pallet constants)
-- Keep this consistent across claims
-
-
-
-### Step 4: Submit Transaction
-
-1. Click **Submit Transaction**
-2. Enter your password if prompted
-3. Confirm the transaction
-4. Monitor the transaction status in the **Network** → **Explorer**
-
-## Alternative: Asset-Specific Claims
-
-For claiming credits from specific asset stakes:
-
-1. Choose `claimCreditsWithAsset` instead of `claimCredits`
-2. Add the **Asset ID** parameter for the specific asset
-3. The same amount and off-chain account ID rules apply
-
-
-
-## Events and Monitoring
-
-### CreditsClaimed Event
-
-When you successfully claim:
-
-```
-CreditsClaimed {
- who: Your_Account_ID,
- amount_claimed: Claimed_Amount,
- offchain_account_id: Your_Offchain_ID
-}
-```
-
-## Related Documentation
-
-- [Credits Overview](/restake/credits) - Understanding the Cloud Credits pallet
-- [Credits Precompile](/restake/credits/precompile) - Technical documentation for developers
-- [How to Restake](/restake/how_to_restake) - Guide to staking TNT tokens
diff --git a/pages/restake/credits/index.mdx b/pages/restake/credits/index.mdx
deleted file mode 100644
index 18e6aa24..00000000
--- a/pages/restake/credits/index.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Credits
-description: Earn free usage credits for AI tools by staking TNT tokens on Tangle.
----
-
-# Credits
-
-## What Are Credits?
-
-Credits are a way for re-stakers on Tangle to earn credits on [ai.tangle.tools](https://ai.tangle.tools). When you stake TNT tokens, you automatically earn credits that can be used for AI services like text generation, image creation, and other AI tools.
-
-## How to Earn Credits
-
-Stake TNT/LstTNT tokens on Tangle and you'll automatically start earning credits. The more TNT you stake, the more credits you earn over time. You don't need to do anything special - just stake your tokens and credits accumulate automatically.
-
-## How to Use Your Credits
-
-1. Stake TNT tokens on Tangle
-2. Visit [ai.tangle.tools](https://ai.tangle.tools)
-3. Claim your accumulated credits
-
-### Earning Mechanism
-
-Credits accumulate based on your staked TNT amount. Higher stake amounts earn credits at a higher rate.
-
-### Credit Expiry
-
-Credits have an expiry period to encourage regular usage rather than hoarding. On Tangle Mainnet, you can accumulate credits for up to one week from your last claim. After one week, your accumulated credits reset to zero and you start earning fresh credits again.
-
-This system encourages users to actively claim and use their credits rather than letting them pile up indefinitely.
-
-### Claiming Process
-
-To claim credits, you submit a transaction with your GitHub account as the off-chain ID. The system calculates how many credits you've earned based on your stake, verifies this amount, and emits an event that credits the specified amount to your GitHub account on ai.tangle.tools.
-
-## Next Steps
-
-- **[How to Claim Credits](/restake/credits/claiming)** - Learn how to claim your earned credits
-- **[Credits Precompile](/restake/credits/precompile)** - Technical documentation for developers working with the credits system
diff --git a/pages/restake/credits/precompile.mdx b/pages/restake/credits/precompile.mdx
deleted file mode 100644
index 97fe0cf8..00000000
--- a/pages/restake/credits/precompile.mdx
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Credits Precompile
-description: Solidity interface for interacting with the Tangle Credits system
----
-
-# Credits Precompile
-
-The Credits precompile provides an Ethereum-compatible interface for interacting with the Tangle Credits system. This allows smart contracts and dApps to manage credits programmatically.
-
-## Contract Address
-
-- **Mainnet & Testnet**: `0x0000000000000000000000000000000000000825`
-
-## Interface
-
-```solidity
-// SPDX-License-Identifier: GPL-3.0-only
-pragma solidity >=0.8.3;
-
-/// @dev The Credits contract's address.
-address constant CREDITS = 0x0000000000000000000000000000000000000825;
-
-/// @dev The Credits contract's instance.
-Credits constant CREDITS_CONTRACT = Credits(CREDITS);
-
-/// @author The Tangle Team
-/// @title Credits Pallet Interface
-/// @notice Interface for interacting with the Tangle Credits system
-/// @custom:address 0x0000000000000000000000000000000000000825
-interface Credits {
- /// @dev Burn TNT tokens to generate credits
- /// @param amount The amount of TNT to burn
- /// @return Success status (0 for success)
- function burn(uint256 amount) external returns (uint8);
-
- /// @dev Claim accumulated credits
- /// @param amount The amount of credits to claim
- /// @param offchainAccountId The off-chain account identifier
- /// @return Success status (0 for success)
- function claimCredits(
- uint256 amount,
- bytes calldata offchainAccountId
- ) external returns (uint8);
-
- /// @dev Get the current credit emission rate for a staked amount
- /// @param stakedAmount The amount of TNT staked
- /// @return The credits earned per block
- function getCurrentRate(uint256 stakedAmount) external view returns (uint256);
-
- /// @dev Calculate accrued credits for an account
- /// @param account The account to check
- /// @return The amount of claimable credits
- function calculateAccruedCredits(address account) external view returns (uint256);
-
- /// @dev Get the current stake tier configuration
- /// @return thresholds Array of stake thresholds
- /// @return rates Array of emission rates per block
- function getStakeTiers() external view returns (
- uint256[] memory thresholds,
- uint256[] memory rates
- );
-
- /// @dev Get stake tier for a specific asset
- /// @param assetId The asset identifier
- /// @return thresholds Array of stake thresholds
- /// @return rates Array of emission rates per block
- function getAssetStakeTiers(uint256 assetId) external view returns (
- uint256[] memory thresholds,
- uint256[] memory rates
- );
-
- /// @dev Events
- event CreditsGrantedFromBurn(address indexed account, uint256 burned, uint256 credits);
- event CreditsClaimed(address indexed account, uint256 amount, bytes offchainAccountId);
-}
-```
-
-### Claiming Credits
-
-```solidity
-contract CreditClaimer {
- Credits constant credits = Credits(0x0000000000000000000000000000000000000825);
-
- function claimMyCredits(uint256 amount, string memory accountId) external {
- // Convert string to bytes for off-chain account ID
- bytes memory offchainId = bytes(accountId);
-
- // Claim the credits
- uint8 result = credits.claimCredits(amount, offchainId);
- require(result == 0, "Claim failed");
- }
-}
-```
-
-## Related Documentation
-
-- [Credits Overview](/restake/credits/overview)
-- [Claiming Credits](/restake/credits/claiming)
-- [Multi-Asset Delegation](/developers/precompiles/features/multi-asset-delegation)
diff --git a/pages/restake/how_to_restake/_meta.ts b/pages/restake/how_to_restake/_meta.ts
index e9111314..fd30e8c3 100644
--- a/pages/restake/how_to_restake/_meta.ts
+++ b/pages/restake/how_to_restake/_meta.ts
@@ -2,7 +2,6 @@ import { Meta } from "nextra";
const meta: Meta = {
how_to_restake_tangle: "How to Restake: Tangle DApp",
- how_to_restake_polkadotjs: "How to Restake: PolkadotJS",
};
export default meta;
diff --git a/pages/restake/how_to_restake/how_to_restake_polkadotjs/_meta.ts b/pages/restake/how_to_restake/how_to_restake_polkadotjs/_meta.ts
deleted file mode 100644
index 436cb6f2..00000000
--- a/pages/restake/how_to_restake/how_to_restake_polkadotjs/_meta.ts
+++ /dev/null
@@ -1,10 +0,0 @@
-import { Meta } from "nextra";
-
-const meta: Meta = {
- deposit: "Deposit",
- delegate: "Delegate",
- unstake: "Unstake",
- withdraw: "Withdraw",
-};
-
-export default meta;
diff --git a/pages/restake/how_to_restake/how_to_restake_polkadotjs/delegate.mdx b/pages/restake/how_to_restake/how_to_restake_polkadotjs/delegate.mdx
deleted file mode 100644
index ec4613ab..00000000
--- a/pages/restake/how_to_restake/how_to_restake_polkadotjs/delegate.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
-import Callout from "/components/Callout";
-
-## Delegate Using PolkadotJS
-
-