1. You can submit data to Avail DA using a specific `app_id` that you created. If you don't know how, -read more [in our docs here](/api-reference/avail-node-api/da-create-application-key).
+read more [in our docs here](/da/api-reference/avail-node-api/da-create-application-key).
2. You can submit data to **ANY** `app_id`, even if you didn't create it. This however does not contitute an attack vector since the rollups building on top of Avail DA can always filter out DA submissions. diff --git a/app/da/api-reference/avail-node-api/nomination-pools-create-with-pool-id/page.mdx b/app/da/api-reference/avail-node-api/nomination-pools-create-with-pool-id/page.mdx index b31f78216..8d0dbaf6d 100644 --- a/app/da/api-reference/avail-node-api/nomination-pools-create-with-pool-id/page.mdx +++ b/app/da/api-reference/avail-node-api/nomination-pools-create-with-pool-id/page.mdx @@ -62,7 +62,7 @@ This object contains the details of the transaction and your newly created nomin
-Please go through [this page in our docs](/docs/build-with-avail/turbo-da) to get started with Turbo DA +Please go through [this page in our docs](/da/build-with-availilturbo-da) to get started with Turbo DA before you get started with the API.
Before configuring Avail DA, complete these essential steps: 1. [`Create an Avail Account`](https://docs.availproject.org/user-guides/accounts): Set up your account to interact with the Avail network -2. [`Get Testnet Tokens`](https://docs.availproject.org/docs/build-with-avail/interact-with-avail-da/faucet): Obtain AVAIL tokens on the Turing testnet for transactions -3. [`Create an AppID`](https://docs.availproject.org/docs/build-with-avail/interact-with-avail-da/app-id): Required to identify your application on the Avail network +2. [`Get Testnet Tokens`](https://docs.availproject.org/da/build-with-availinteract-with-avail-da/faucet): Obtain AVAIL tokens on the Turing testnet for transactions +3. [`Create an AppID`](https://docs.availproject.org/da/build-with-availinteract-with-avail-da/app-id): Required to identify your application on the Avail network
- To obtain a reliable RPC endpoint for production use, please reach out to our [external partners](https://docs.availproject.org/docs/networks#alternate-endpoints). They provide dedicated endpoint access with enhanced reliability and performance for production-ready infrastructure. + To obtain a reliable RPC endpoint for production use, please reach out to our [external partners](https://docs.availproject.org/da/networks#alternate-endpoints). They provide dedicated endpoint access with enhanced reliability and performance for production-ready infrastructure.
-You can go through [this page in our docs](/docs/learn-about-avail/app-ids) for a deeper understanding of how +You can go through [this page in our docs](/da/learn-about-avail/app-ids) for a deeper understanding of how AppIDs work on Avail.
-You can check out our [API reference](/api-reference/avail-node-api/da-create-application-key) for the same. +You can check out our [API reference](/da/api-reference/avail-node-api/da-create-application-key) for the same.
We recommend you go through these two pages in our docs before proceeding: -1. [`Get Testnet Tokens`](/docs/build-with-avail/interact-with-avail-da/faucet): To help you get set with some `AVAIL` tokens on the Turing testnet. -2. [`Create an AppID`](/docs/build-with-avail/interact-with-avail-da/app-id): The guide below focusses on reading & submitting data on a particular AppID. It will help +1. [`Get Testnet Tokens`](/da/build-with-availinteract-with-avail-da/faucet): To help you get set with some `AVAIL` tokens on the Turing testnet. +2. [`Create an AppID`](/da/build-with-availinteract-with-avail-da/app-id): The guide below focusses on reading & submitting data on a particular AppID. It will help to be familiar with the concept.
-In this guide we will use Avail's dedicated SDKs to interact with the [Turing testnet](/docs/networks). -To set up a dev environment for the SDK of your choice, please follow the steps [outlined here](/api-reference/avail-node-api#setting-up-the-dev-environment). +In this guide we will use Avail's dedicated SDKs to interact with the [Turing testnet](/da/networks). +To set up a dev environment for the SDK of your choice, please follow the steps [outlined here](/da/api-reference/avail-node-api#setting-up-the-dev-environment).
`AppIDs` are a core concept every developer building on top of Avail DA should be familiar with. -You can go through [this page in our docs for the same](/docs/learn-about-avail/app-ids). +You can go through [this page in our docs for the same](/da/learn-about-avail/app-ids).
@@ -73,7 +73,7 @@ Click on the `Generate new key` button to generate a new API key.
### Step 5: Use the API key to submit data [#submit-data-to-turbo-da]
Once you have your API key, feel free to head on over to our
-[API reference](/api-reference/avail-turbo-da-api) to start leveraging the power of Turbo DA.
+[API reference](/da/api-reference/avail-turbo-da-api) to start leveraging the power of Turbo DA.
diff --git a/app/da/build-with-avail/vectorx/page.mdx b/app/da/build-with-avail/vectorx/page.mdx
index d9fc9d6e5..f74d43095 100644
--- a/app/da/build-with-avail/vectorx/page.mdx
+++ b/app/da/build-with-avail/vectorx/page.mdx
@@ -21,7 +21,7 @@ interpreted or executed in any way.
You can submit data to Avail DA in a variety of ways, but we recommend using our dedicated SDKs.
-You can check out examples on how to submit new data to Avail DA in our [API reference](/api-reference/avail-node-api/da-submit-data). \
+You can check out examples on how to submit new data to Avail DA in our [API reference](/da/api-reference/avail-node-api/da-submit-data). \
You can check out a complete example on submitting data and verifying the data blob inclusion [on our github](https://github.com/availproject/avail/blob/main/avail-js/examples/node-examples/src/validium.ts).
@@ -48,7 +48,7 @@ When the data root is bridged to the Ethereum network, it is possible to query f
deployed for Turing testnet.
-You can find detailed documentation on our `bridge-API` in our [API reference](/api-reference/avail-bridge-api).
+You can find detailed documentation on our `bridge-API` in our [API reference](/da/api-reference/avail-bridge-api).
diff --git a/app/da/faqs/page.mdx b/app/da/faqs/page.mdx
index 392d456fd..838eb7798 100644
--- a/app/da/faqs/page.mdx
+++ b/app/da/faqs/page.mdx
@@ -18,7 +18,7 @@ import { Callout } from 'nextra/components'
CLASH OF NODES FAQS
For all questions and queries related to the Clash of Nodes campaign, -please visit **[this page](/docs/clash-of-nodes/faqs.mdx)**. +please visit **[this page](/da/clash-of-nodes/faqs.mdx)**.
## What problem does Avail solve?
@@ -61,8 +61,8 @@ Then comes Fusion Security to enable fair and additive crypto economic security.
## How can I get involved?
- [Use Avail DA](https://docs.availproject.org/) for your chain
-- Run a [Validator](https://docs.availproject.org/docs/operate-a-node/become-a-validator)
-- Run a [light client](https://docs.availproject.org/docs/operate-a-node/run-a-light-client)
+- Run a [Validator](https://docs.availproject.org/da/operate-a-node/become-a-validator)
+- Run a [light client](https://docs.availproject.org/da/operate-a-node/run-a-light-client)
- Join [Discord](https://discord.gg/AvailProject)
- Follow us on [X](https://twitter.com/AvailProject)
- Join the [Avail Uncharted](https://github.com/availproject/avail-uncharted) Technical Contributor's program
@@ -73,7 +73,7 @@ Then comes Fusion Security to enable fair and additive crypto economic security.
- Technical questions → [Discord](https://discord.gg/AvailProject) or [Forum](https://forum.availproject.org/)
## I found a bug/vulnerability. Where do I report it?
-We have a bug bounty program where you can report the vulnerability. Please check out the [Bug Bounty](/docs/bug-bounty) page for detailed information on how to responsibly report it.
+We have a bug bounty program where you can report the vulnerability. Please check out the [Bug Bounty](/da/bug-bounty) page for detailed information on how to responsibly report it.
## What is a popular use case of a light client?
@@ -108,12 +108,12 @@ The only exception is data availability sampling. In order to verify that data i
## Who is behind Avail?
Avail is led by former Polygon co-founder [Anurag Arjun](https://twitter.com/anuragarjun) and former Polygon research lead [Prabal Banerjee](https://twitter.com/prabalbanerjee).
-The [Avail team](https://www.availproject.org/aboutus) consists of more than 40 professionals with solid experience in their areas of expertise ranging from marketing to blockchain design and programming. +The [Avail team](https://availproject.org/aboutus) consists of more than 40 professionals with solid experience in their areas of expertise ranging from marketing to blockchain design and programming. Many have proven track records in the Web3 space and a diverse background that forms the foundation of a solid team. ## What Partnerships are in place? -Avail has a strong list of strategic partnerships in place across different ecosystems. For a full list of partners, please see [Ecosystem Page](https://www.availproject.org/ecosystem). +Avail has a strong list of strategic partnerships in place across different ecosystems. For a full list of partners, please see [Ecosystem Page](https://availproject.org/ecosystem). New partnerships will be announced soon so follow us on [X](https://twitter.com/AvailProject) to keep up to date. ## Is Avail DA the same as Celestia? diff --git a/app/da/learn-about-avail/app-ids/page.mdx b/app/da/learn-about-avail/app-ids/page.mdx index 3800f1277..5d359fa43 100644 --- a/app/da/learn-about-avail/app-ids/page.mdx +++ b/app/da/learn-about-avail/app-ids/page.mdx @@ -9,11 +9,11 @@ import { Callout, Steps, Tabs } from 'nextra/components'
**DON'T CARE ABOUT THEORY?**
If you are just looking for the easiest way to create your own AppID on Avail to continue building, -you can skip to [this page](/docs/build-with-avail/interact-with-avail-da/app-id). +you can skip to [this page](/da/build-with-availinteract-with-avail-da/app-id).
**LOOKING FOR PROGRAMMATIC INSTRUCTIONS?**
-You can check out our [API reference](/api-reference/avail-node-api/da-create-application-key) for the same. +You can check out our [API reference](/da/api-reference/avail-node-api/da-create-application-key) for the same.
## Introduction
@@ -150,14 +150,14 @@ No need to pass any params, just click the `+` button next to the method name.
## How to register my own `appID`?
1. Make sure you have one or more Avail DA wallets connected to the explorer. If you don't know how to do so,
-you can follow our docs on [setting up a new wallet](/docs/end-user-guide/accounts#creating-an-account-on-avail-da).
+you can follow our docs on [setting up a new wallet](/user-guides/accounts#creating-an-account-on-avail-da).
2. Simply [click this link](https://explorer.availproject.org/#/extrinsics) OR navigate to the `extrinsics` section of the explorer through the `developer` tab.
Please note that the `Developer` tab does not show the `extrinsics` section at all if you don't
have a wallet set up on the explorer or an extension wallet connected to it.
-So make sure you have an [Avail DA wallet set up](/docs/end-user-guide/accounts) before moving forward.
+So make sure you have an [Avail DA wallet set up](/user-guides/accounts) before moving forward.
3. Select the `dataAvailability` pallet, and the `createApplicationKey` method.
@@ -202,7 +202,7 @@ You can submit data to your, or any other `appID` on Avail DA using the explorer
`submitData` extrinsic from within the `dataAvailability` pallet.
1. Make sure you have one or more Avail DA wallets connected to the explorer. If you don't know how to do so,
-you can follow our docs on [setting up a new wallet](/docs/end-user-guide/accounts#creating-an-account-on-avail-da).
+you can follow our docs on [setting up a new wallet](/user-guides/accounts#creating-an-account-on-avail-da).
2. Simply [click this link](https://explorer.availproject.org/#/extrinsics) OR navigate to the `extrinsics` section of the explorer through the `developer` tab.
@@ -248,7 +248,7 @@ you can follow our docs on [setting up a new wallet](/docs/end-user-guide/accoun
1. As stated earlier, the `key` and `id` fields of every `appID` are unique. This means if you try to create an `appID` with the same `key` as an existing one,
the operation will fail. This is why it makes sense to use the `appKeys` method to check if your desired name is already taken.
-2. If you're a developer and are looking for more programmatic instructions, you can check out our [API reference](/api-reference/avail-node-api/da-create-application-key).
+2. If you're a developer and are looking for more programmatic instructions, you can check out our [API reference](/da/api-reference/avail-node-api/da-create-application-key).
3. **Anyone can submit any sort of data to any `appID` regardless of whether or not they created it.** \
*But what does this mean? And is this an attack vector?*
diff --git a/app/da/learn-about-avail/avail-apps-explorer/page.mdx b/app/da/learn-about-avail/avail-apps-explorer/page.mdx
index 4756a5f68..a0f46e26c 100644
--- a/app/da/learn-about-avail/avail-apps-explorer/page.mdx
+++ b/app/da/learn-about-avail/avail-apps-explorer/page.mdx
@@ -25,7 +25,7 @@ This tutorial will focus on helping advanced users and devs get started with the
-The Avail Apps explorer currently supports [Avail mainnet](https://mainnet.explorer.availproject.org/) and [Avail Turing testnet](https://turing.explorer.availproject.org/).
+The Avail Apps explorer currently supports [Avail mainnet](https://explorer.availproject.org/?rpc=wss%3A%2F%2Fmainnet-rpc.avail.so%2Fws&light=https%3A%2F%2Fapi.lightclient.mainnet.avail.so%2Fv1) and [Avail Turing testnet](https://explorer.availproject.org/?rpc=wss%3A%2F%2Fturing-rpc.avail.so%2Fws&light=https%3A%2F%2Fapi.lightclient.turing.avail.so%2Fv1).
To switch networks:
@@ -232,7 +232,7 @@ But `system_account` method won't return anything without an `AccountId32` param
You can also use the `AvailApps` explorer to sign custom transactions/extrinsics and submit them to the network.
We have covered different examples of doing so in our docs. Here is one of them:
-[Submit data to a particular `AppID` by submitting a `dataAvailability_submitData` extrinsic](/docs/learn-about-avail/app-ids#how-to-submit-data-to-my-appid).
+[Submit data to a particular `AppID` by submitting a `dataAvailability_submitData` extrinsic](/da/learn-about-avail/app-ids#how-to-submit-data-to-my-appid).
### Bonus: How to query chain constants using the explorer
diff --git a/app/da/learn-about-avail/page.mdx b/app/da/learn-about-avail/page.mdx
index 99728e6a4..3cb8eb42e 100644
--- a/app/da/learn-about-avail/page.mdx
+++ b/app/da/learn-about-avail/page.mdx
@@ -10,7 +10,7 @@ import { FileIcon, FilesIcon } from '@components/icons'
# Learn more about Avail
-
diff --git a/app/da/networks/page.mdx b/app/da/networks/page.mdx
index 38b17e87c..a7e343242 100644
--- a/app/da/networks/page.mdx
+++ b/app/da/networks/page.mdx
@@ -29,7 +29,7 @@ We will keep this page updated with the latest information on new networks.
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ---------------------------------------------------------------------------------------------------------------------------------|
| **Status** | **Active** | **Active** |
| **Subscan Explorer** | [avail.subscan.io](https://avail.subscan.io/) | [avail-turing.subscan.io](https://avail-turing.subscan.io/) |
-| **AvailApps Explorer** | [mainnet.explorer.availproject.org](http://mainnet.explorer.availproject.org/) | [turing.explorer.availproject.org](http://turing.explorer.availproject.org/) |
+| **AvailApps Explorer** | [mainnet.explorer.availproject.org](https://explorer.availproject.org/?rpc=wss%3A%2F%2Fmainnet-rpc.avail.so%2Fws&light=https%3A%2F%2Fapi.lightclient.mainnet.avail.so%2Fv1) | [turing.explorer.availproject.org](https://explorer.availproject.org/?rpc=wss%3A%2F%2Fturing-rpc.avail.so%2Fws&light=https%3A%2F%2Fapi.lightclient.turing.avail.so%2Fv1) |
| **RPC Endpoints** | [https://avail-mainnet.public.blastapi.io/](https://avail-mainnet.public.blastapi.io/)
[https://mainnet-rpc.avail.so/rpc](https://mainnet-rpc.avail.so/rpc)
| [https://turing-rpc.avail.so/rpc](https://turing-rpc.avail.so/rpc) | | **WS Endpoints** | [wss://avail-mainnet.public.blastapi.io/](wss://avail-mainnet.public.blastapi.io/)
[wss://mainnet.avail-rpc.com/](wss://mainnet.avail-rpc.com/)
| [wss://turing-rpc.avail.so/ws](wss://turing-rpc.avail.so/ws) | | **Chain Spec** | [chainspec.raw.json](https://raw.githubusercontent.com/availproject/avail/main/misc/genesis/mainnet.chain.spec.raw.json) | [chainspec.raw.json](https://github.com/availproject/avail/blob/main/misc/genesis/testnet.turing.chain.spec.raw.json) | diff --git a/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx b/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx index 99a436048..2d1b88ad2 100644 --- a/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx +++ b/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx @@ -73,4 +73,4 @@ EQUIVIVOCAITON RISK
Never run two nodes with identical keys at the same time to avoid double-signing.
-This method is not recommended for routine transitions between nodes. For safer alternatives, consult the [Upgrading Guide](/docs/operate-a-node/become-a-validator/upgrade-your-validator).
+This method is not recommended for routine transitions between nodes. For safer alternatives, consult the [Upgrading Guide](/da/operate-a-node/become-a-validator/upgrade-your-validator).
diff --git a/app/da/operate-a-node/become-a-validator/page.mdx b/app/da/operate-a-node/become-a-validator/page.mdx
index b2bd94c2f..539844d65 100644
--- a/app/da/operate-a-node/become-a-validator/page.mdx
+++ b/app/da/operate-a-node/become-a-validator/page.mdx
@@ -10,13 +10,13 @@ import { FileIcon } from '@components/icons'
# Become a Validator
-
diff --git a/app/da/operate-a-node/become-a-validator/stake-your-validator/page.mdx b/app/da/operate-a-node/become-a-validator/stake-your-validator/page.mdx
index 5a7db2078..6900a2c57 100644
--- a/app/da/operate-a-node/become-a-validator/stake-your-validator/page.mdx
+++ b/app/da/operate-a-node/become-a-validator/stake-your-validator/page.mdx
@@ -142,7 +142,7 @@ Once your validator node has accrued enough stake, it will be elected for valida
Below is an example image of an elected validator node actively producing blocks.
In addition, please check out the guide on validator monitoring available
-[here](/docs/operate-a-node/become-a-validator/monitor-your-validator).
+[here](/da/operate-a-node/become-a-validator/monitor-your-validator).
@@ -156,8 +156,8 @@ You should be seeing something like this:
As you move forward, here are some essential actions to consider:
1. **Backup Your Validator**: Ensure you have a secure backup of your validator settings and keys. Refer to the
- [Backup Guide](/docs/operate-a-node/become-a-validator/backup-your-validator) for detailed steps.
+ [Backup Guide](/da/operate-a-node/become-a-validator/backup-your-validator) for detailed steps.
-2. **Start Monitoring**: If you haven't already, set up monitoring tools to keep track of your validator's performance. Check out the [Monitoring Guide](/docs/operate-a-node/become-a-validator/monitor-your-validator) for recommendations.
+2. **Start Monitoring**: If you haven't already, set up monitoring tools to keep track of your validator's performance. Check out the [Monitoring Guide](/da/operate-a-node/become-a-validator/monitor-your-validator) for recommendations.
3. **Join the Community**: Connect with other validators and the Avail team on the official [Discord Channel](https://discord.com/invite/AvailProject). It's a great place to share experiences, ask questions, and get updates.
diff --git a/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx b/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
index 292360b8c..00c5955a1 100644
--- a/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
+++ b/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
@@ -31,7 +31,7 @@ sudo systemctl stop avail.service
```
- Locate your Avail binary, create a backup of the current binary, and then uninstall the existing binary by deleting the binary. Proceed to download the most recent binary announced in Discord, which will replace the previous binary version.
- To provide an example, assuming your existing binary is located at `/home/avail/avail-node/` and is named `data-avail`, and you used the [validator](/docs/operate-a-node/become-a-validator) setup guidelines while obtaining a pre-built binary from the Avail GitHub repository, proceed as outlined below.
+ To provide an example, assuming your existing binary is located at `/home/avail/avail-node/` and is named `data-avail`, and you used the [validator](/da/operate-a-node/become-a-validator) setup guidelines while obtaining a pre-built binary from the Avail GitHub repository, proceed as outlined below.
```
cd /home/avail/avail-node/
diff --git a/app/da/operate-a-node/node-types/page.mdx b/app/da/operate-a-node/node-types/page.mdx
index 44aafba05..bd25e7e4a 100644
--- a/app/da/operate-a-node/node-types/page.mdx
+++ b/app/da/operate-a-node/node-types/page.mdx
@@ -49,6 +49,6 @@ RPC nodes expose an API for remote interactions, serving as a gateway for develo
## Next Steps
-Now that you have a comprehensive understanding of the various node types within the Avail network, it's recommended to take your first step by setting up a Light Client. Before you begin, make sure to review the [System Requirements guide](/docs/operate-a-node/run-a-full-node/requirements). Once you're ready, you can proceed to the [Light Client Deployment guide](/docs/operate-a-node/run-a-light-client/0010-light-client) to get started.
+Now that you have a comprehensive understanding of the various node types within the Avail network, it's recommended to take your first step by setting up a Light Client. Before you begin, make sure to review the [System Requirements guide](/da/operate-a-node/run-a-full-node/requirements). Once you're ready, you can proceed to the [Light Client Deployment guide](/da/operate-a-node/run-a-light-client/0010-light-client) to get started.
> Light Clients provide an accessible entry point to the Avail network, enabling quick interactions without storing the full blockchain. Ideal for newcomers, they play an integral role in maintaining a robust data availability layer.
diff --git a/app/da/operate-a-node/page.mdx b/app/da/operate-a-node/page.mdx
index 802f9da2e..a6c453604 100644
--- a/app/da/operate-a-node/page.mdx
+++ b/app/da/operate-a-node/page.mdx
@@ -10,10 +10,10 @@ import { FileIcon, FilesIcon } from '@components/icons'
# Run a Node on Avail
-
diff --git a/app/da/operate-a-node/run-a-full-node/full-node/page.mdx b/app/da/operate-a-node/run-a-full-node/full-node/page.mdx
index 781baeeef..9b38821b9 100644
--- a/app/da/operate-a-node/run-a-full-node/full-node/page.mdx
+++ b/app/da/operate-a-node/run-a-full-node/full-node/page.mdx
@@ -76,7 +76,7 @@ required to make sure your node can be used to access all RPC methods:
Enable the Kate pallet.
-- Looking for a list of all available config flags? Check out the [last section of this page](/docs/operate-a-node/run-a-full-node/full-node#additional-configs).
+- Looking for a list of all available config flags? Check out the [last section of this page](/da/operate-a-node/run-a-full-node/full-node#additional-configs).
diff --git a/app/da/operate-a-node/run-a-full-node/page.mdx b/app/da/operate-a-node/run-a-full-node/page.mdx
index 922bb908c..a7d9c6ce7 100644
--- a/app/da/operate-a-node/run-a-full-node/page.mdx
+++ b/app/da/operate-a-node/run-a-full-node/page.mdx
@@ -10,6 +10,6 @@ import { FileIcon } from '@components/icons'
# Run an Avail node
-
diff --git a/app/da/operate-a-node/run-a-light-client/0010-light-client/page.mdx b/app/da/operate-a-node/run-a-light-client/0010-light-client/page.mdx
index e306485c7..4249f2ebf 100644
--- a/app/da/operate-a-node/run-a-light-client/0010-light-client/page.mdx
+++ b/app/da/operate-a-node/run-a-light-client/0010-light-client/page.mdx
@@ -19,7 +19,7 @@ import { Callout } from 'nextra/components'
**LOOKING FOR THE LIGHT CLIENT API REFERENCE?**
-Go to [light client API reference](/api-reference/avail-lc-api) +Go to [light client API reference](/da/api-reference/avail-lc-api)
1. Use [Availup](https://github.com/availproject/availup) to run the light client.
@@ -51,7 +51,7 @@ This data can then be accessed via a local HTTP endpoint.
**WE RECOMMEND LEARNING ABOUT APP IDs on AVAIL DA**
-App IDs are an important concept in the context of Avail. We recommend you go through [this page in our docs](/docs/learn-about-avail/app-ids) to understand how they work before moving forward. +App IDs are an important concept in the context of Avail. We recommend you go through [this page in our docs](/da/learn-about-avail/app-ids) to understand how they work before moving forward.
## Running the light client
diff --git a/app/da/operate-a-node/run-a-light-client/Overview/page.mdx b/app/da/operate-a-node/run-a-light-client/Overview/page.mdx
index 316e71456..882bea764 100644
--- a/app/da/operate-a-node/run-a-light-client/Overview/page.mdx
+++ b/app/da/operate-a-node/run-a-light-client/Overview/page.mdx
@@ -29,7 +29,7 @@ This is the hardware configuration required to set up an Avail light client:
**JUST LOOKING FOR INSTRUCTIONS?**
-If you're not interested in theory, skip [to this link](/docs/operate-a-node/run-a-light-client/0010-light-client) for instructions on how to run an Avail light client. +If you're not interested in theory, skip [to this link](/da/operate-a-node/run-a-light-client/0010-light-client) for instructions on how to run an Avail light client.
## Introduction
@@ -79,7 +79,7 @@ while reducing the load on full nodes.
The light client is capable of downloading and verifying
application-specific data submitted to Avail, which can be conveniently queried using the light client API.
-You can check out all the different methods supported by the Avail light client in our [Light Client API Reference](/docs/operate-a-node/run-a-light-client/Reference/embedding-the-light-client#api-reference).
+You can check out all the different methods supported by the Avail light client in our [Light Client API Reference](/da/operate-a-node/run-a-light-client/Reference/embedding-the-light-client#api-reference).
The light client exposes an HTTP API that enables users to query the status, confidence, and application data
diff --git a/app/da/operate-a-node/run-a-light-client/page.mdx b/app/da/operate-a-node/run-a-light-client/page.mdx
index 88782c1ff..163903ccd 100644
--- a/app/da/operate-a-node/run-a-light-client/page.mdx
+++ b/app/da/operate-a-node/run-a-light-client/page.mdx
@@ -10,6 +10,6 @@ import { FileIcon } from '@components/icons'
# Run a Light Client
-
diff --git a/app/da/welcome-to-avail-docs/page.mdx b/app/da/welcome-to-avail-docs/page.mdx
index c1413d0fe..2e6fd66ea 100644
--- a/app/da/welcome-to-avail-docs/page.mdx
+++ b/app/da/welcome-to-avail-docs/page.mdx
@@ -40,32 +40,32 @@ learn more about our upcoming offerings as well as our vision for the unified fu
### Developer Documentation
-
### API reference
-
### Bug Bounty
-
diff --git a/app/layout.tsx b/app/layout.tsx
index c916b3a39..deb0a7d12 100644
--- a/app/layout.tsx
+++ b/app/layout.tsx
@@ -25,7 +25,7 @@ const defaultSearchOptions = {
const banner = (
Avail Nexus is now live!{" "}
-
+
Check out our docs
to get started.
diff --git a/app/nexus/avail-nexus-sdk/bridge-methods/bridge-and-execute/page.mdx b/app/nexus/avail-nexus-sdk/bridge-methods/bridge-and-execute/page.mdx
index ae259db14..175634c77 100644
--- a/app/nexus/avail-nexus-sdk/bridge-methods/bridge-and-execute/page.mdx
+++ b/app/nexus/avail-nexus-sdk/bridge-methods/bridge-and-execute/page.mdx
@@ -17,7 +17,7 @@ Use the `bridgeAndExecute()` function to bridge a token and execute a contract f
Use the `simulateBridgeAndExecute()` function to simulate `bridgeAndExecute()` before sending an actual transaction.
-**Note:** Check out the [API reference](/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
+**Note:** Check out the [API reference](/da/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
## Method signature
diff --git a/app/nexus/avail-nexus-sdk/bridge-methods/bridge/page.mdx b/app/nexus/avail-nexus-sdk/bridge-methods/bridge/page.mdx
index 8ca092947..f163c5733 100644
--- a/app/nexus/avail-nexus-sdk/bridge-methods/bridge/page.mdx
+++ b/app/nexus/avail-nexus-sdk/bridge-methods/bridge/page.mdx
@@ -17,7 +17,7 @@ Use the `bridge()` function to bridge a specific token from one (*or many*) chai
Use the `simulateBridge()` function to simulate the bridge transaction to preview the costs and fees, before actually executing the transaction.
-**Note:** Check out the [API reference](/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
+**Note:** Check out the [API reference](/da/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
## Method signature
diff --git a/app/nexus/avail-nexus-sdk/bridge-methods/transfer/page.mdx b/app/nexus/avail-nexus-sdk/bridge-methods/transfer/page.mdx
index 315a6de0a..a857b0f19 100644
--- a/app/nexus/avail-nexus-sdk/bridge-methods/transfer/page.mdx
+++ b/app/nexus/avail-nexus-sdk/bridge-methods/transfer/page.mdx
@@ -17,7 +17,7 @@ Use the `bridgeAndTransfer()` function to source a token from multiple source ch
Use the `simulateBridgeAndTransfer()` function to simulate the bridge and transfer transaction to preview the costs and fees, before actually executing the transaction.
-**Note:** Check out the [API reference](/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
+**Note:** Check out the [API reference](/da/api-reference/avail-nexus-sdk/api-reference) for a full list of supported tokens and chains.
## Method signature
diff --git a/app/nexus/nexus-examples/nexus-initialization-basic/page.mdx b/app/nexus/nexus-examples/nexus-initialization-basic/page.mdx
index 63ed9b3c3..f5a498c1c 100644
--- a/app/nexus/nexus-examples/nexus-initialization-basic/page.mdx
+++ b/app/nexus/nexus-examples/nexus-initialization-basic/page.mdx
@@ -49,7 +49,7 @@ By the end of this tutorial you will have:
**WHAT IS A 'UNIFIED BALANCE'?**
-You can refer to this [page in our docs](/nexus/concepts/unified-balance) for more details. +You can refer to this [page in our docs](/nexus/concepts/bridge-v-swap) for more details.
## What Does 'Initialization' Mean Here?
diff --git a/app/user-guides/accounts/page.mdx b/app/user-guides/accounts/page.mdx
index afb7f935a..6f4e80ff2 100644
--- a/app/user-guides/accounts/page.mdx
+++ b/app/user-guides/accounts/page.mdx
@@ -244,4 +244,4 @@ You can update your metedata, if needed, using the [AvailApps explorer](https://
Congratulations on successfully creating and managing your Avail account! Remember to always safeguard your account details, JSON file, and seed phrase to ensure the security of your assets.
-Ready to explore further? Navigate to the next guide to learn [how to use the Avail Explorer](/docs/learn-about-avail/avail-apps-explorer) and get hands-on experience with the network.
+Ready to explore further? Navigate to the next guide to learn [how to use the Avail Explorer](/da/learn-about-avail/avail-apps-explorer) and get hands-on experience with the network.
diff --git a/app/user-guides/avail-multisig/page.mdx b/app/user-guides/avail-multisig/page.mdx
index a36e38bac..5d6dfcae0 100644
--- a/app/user-guides/avail-multisig/page.mdx
+++ b/app/user-guides/avail-multisig/page.mdx
@@ -12,7 +12,7 @@ This guide will show you how to do so.
**PREREQUISITES**
The only prerequisite is that you have access to one or more Avail DA accounts. -Refer to our docs on [setting up an Avail wallet](/docs/end-user-guide/accounts) for more details if needed +Refer to our docs on [setting up an Avail wallet](/user-guides/accounts) for more details if needed
diff --git a/app/user-guides/identity/page.mdx b/app/user-guides/identity/page.mdx
index 567d811e4..d8d573293 100644
--- a/app/user-guides/identity/page.mdx
+++ b/app/user-guides/identity/page.mdx
@@ -46,7 +46,7 @@ for each of your team members.
**PREREQUISITES**
The only prerequisite is that you have access to one or more Avail DA accounts. -Refer to our docs on [setting up an Avail wallet](/docs/end-user-guide/accounts) for more details if needed +Refer to our docs on [setting up an Avail wallet](/user-guides/accounts) for more details if needed
diff --git a/app/user-guides/staking-governance/overview/page.mdx b/app/user-guides/staking-governance/overview/page.mdx
index a328456c6..b85750738 100644
--- a/app/user-guides/staking-governance/overview/page.mdx
+++ b/app/user-guides/staking-governance/overview/page.mdx
@@ -59,7 +59,7 @@ You can monitor the wallet address here: [Public Allocation - Future Initiatives
3. **`AVAIL` Circulating Supply:**
The total circulating supply of `AVAIL` can vary, but an updated figure is always available
-at this endpoint: [https://www.availproject.org/api/circulating-supply](https://www.availproject.org/api/circulating-supply)
+at this endpoint: [https://availproject.org/api/circulating-supply](https://availproject.org/api/circulating-supply)
@@ -94,7 +94,7 @@ Please beware of any phishing or scam attempts. Only rely on official Avail comm Anyone can stake AVAIL throughout Avail's infrastructure to earn staking rewards. We will release detailed staking guides along with our products as they are released. -For now you can refer to the Avail DA staking guide [in our docs](/docs/stake-on-avail). +For now you can refer to the Avail DA staking guide [in our docs](/user-guides/staking-governance/stake-on-avail). If you want to read about staking on Avail in more detail, you can refer to [our blog](https://blog.availproject.org/avail-the-token-powering-blockchain-unification/#avail-staking).
diff --git a/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx b/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx index 85b042afb..8e9dd7ed2 100644 --- a/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx +++ b/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx @@ -60,7 +60,7 @@ If your stake amount is significantly larger than the threshold and minimum nomi ## Staking Reward Payout Lifecycle -If you have staked your AVAIL in the network, you will only start earning rewards in the **next** [era](/docs/glossary#era), and not in the era you staked in. The stake is used to increase the number of tokens held by your nominated validators, increasing their chance of being selected by the election algorithm for block production during a specific era. An era is a period of 24 hours during which an active set of validators is producing blocks and performing other actions on the chain. Hence your stake only becomes active in the next era after which you've staked. +If you have staked your AVAIL in the network, you will only start earning rewards in the **next** [era](/da/glossary#era), and not in the era you staked in. The stake is used to increase the number of tokens held by your nominated validators, increasing their chance of being selected by the election algorithm for block production during a specific era. An era is a period of 24 hours during which an active set of validators is producing blocks and performing other actions on the chain. Hence your stake only becomes active in the next era after which you've staked. Here is the lifecycle of your stake when you stake in _Era N_: diff --git a/public/reserveDocs/Optimium.mdx b/public/reserveDocs/Optimium.mdx index ec019fbdf..2a5593048 100644 --- a/public/reserveDocs/Optimium.mdx +++ b/public/reserveDocs/Optimium.mdx @@ -7,8 +7,8 @@ import { FilesIcon } from '@components/icons' There are a number of tools to spin up an optimium today. We are actively integrating with rollup stacks to give you, the developer, maximum flexibility when choosing the stack of your choice while also retaining the benefits that Avail provides. Today you can spin your optimium up with the following frameworks below.
-
## What is an optimium?
@@ -19,7 +19,7 @@ Instead of publishing data on a centralised DAC (Data Availability Committee), r
The advantage of using Ethereum as a DA layer, is that rollups can inherit Ethereum’s security guarantees. Anyone can access the L2s transaction data posted on Ethereum and use it to derive the correct chain state of the L2.
-This benefit however comes with a significant cost. Ethereum was not meant to be used as a DA solution and is not optimized for this use case. While work is being done to improve this, at the time of writing up to 90% of the costs paid by L2s to Ethereum is for managing data availability. High volume use cases processing a lot of transaction data, can bring these costs down significantly by using a purpose built data availability solution like [Avail](https://docs.availproject.org/docs/introduction-to-avail/avail-da).
+This benefit however comes with a significant cost. Ethereum was not meant to be used as a DA solution and is not optimized for this use case. While work is being done to improve this, at the time of writing up to 90% of the costs paid by L2s to Ethereum is for managing data availability. High volume use cases processing a lot of transaction data, can bring these costs down significantly by using a purpose built data availability solution like [Avail](https://docs.availproject.org/da/welcome-to-avail-docs/avail-da).
## Architecture of an optimium on Avail
diff --git a/public/reserveDocs/Optimium/arbitrum-nitro.mdx b/public/reserveDocs/Optimium/arbitrum-nitro.mdx
index 58f4d8ea1..4e88261f5 100644
--- a/public/reserveDocs/Optimium/arbitrum-nitro.mdx
+++ b/public/reserveDocs/Optimium/arbitrum-nitro.mdx
@@ -4,6 +4,6 @@ import { FileIcon, LinkIcon } from '@components/icons'
# Arbitrum Nitro stack
-
\ No newline at end of file
diff --git a/public/reserveDocs/Optimium/arbitrum-nitro/nitro-stack.mdx b/public/reserveDocs/Optimium/arbitrum-nitro/nitro-stack.mdx
index 8cadaf2c0..40de97ece 100644
--- a/public/reserveDocs/Optimium/arbitrum-nitro/nitro-stack.mdx
+++ b/public/reserveDocs/Optimium/arbitrum-nitro/nitro-stack.mdx
@@ -2,7 +2,7 @@ import { Callout } from 'nextra/components'
# Deploy Arbitrum Orbit with Avail DA
-This guide follows the deployment of an Arbitrum Orbit chain (L3) with Arbitrum Sepolia (L2) as the base chain. You can follow the same steps with any [other supported chains](/docs/build-with-avail/Optimium/arbitrum-nitro/nitro-stack#reference) with the relevant contract addresses.
+This guide follows the deployment of an Arbitrum Orbit chain (L3) with Arbitrum Sepolia (L2) as the base chain. You can follow the same steps with any [other supported chains](/da/build-with-availOptimium/arbitrum-nitro/nitro-stack#reference) with the relevant contract addresses.
This guide is based on [Arbitrum Orbit Quickstart](https://docs.arbitrum.io/launch-orbit-chain/orbit-quickstart)
@@ -13,12 +13,12 @@ This guide is based on [Arbitrum Orbit Quickstart](https://docs.arbitrum.io/laun
#### Docker
- You need to have [docker](https://docs.docker.com/engine/) and [docker-compose](https://docs.docker.com/compose/) installed on your machine.
#### Avail
-- An Avail account with some AVAIL tokens in it. You can refer to [our docs here](/docs/end-user-guide/accounts) to get started.
-- An application key (`app-id`) for your rollup. Learn [how to get your `app-id` here](/docs/build-with-avail/interact-with-avail-da/app-id).
+- An Avail account with some AVAIL tokens in it. You can refer to [our docs here](/user-guides/accounts) to get started.
+- An application key (`app-id`) for your rollup. Learn [how to get your `app-id` here](/da/build-with-availinteract-with-avail-da/app-id).
#### Arbitrum Sepolia
- At least 1 ETH over Arbsepolia Testnet. You can follow [Step 1](https://docs.arbitrum.io/launch-orbit-chain/orbit-quickstart#step-1-acquire-arbitrum-testnet-eth-and-the-native-token-for-orbit-chains-with-custom-gas-tokens) on Arbitrum Orbit Doc for acquiring testnet $ETH
-- This guide will use [Arbitrum's ArbSepolia](https://docs.arbitrum.io/build-decentralized-apps/public-chains#arbitrum-sepolia) and [Avail's Turing](/docs/networks) testnets.
+- This guide will use [Arbitrum's ArbSepolia](https://docs.arbitrum.io/build-decentralized-apps/public-chains#arbitrum-sepolia) and [Avail's Turing](/da/networks) testnets.
## Download avail-nitro-node docker image
@@ -50,7 +50,7 @@ This guide is based on [Arbitrum Orbit Quickstart](https://docs.arbitrum.io/laun
//for Arbitrum Sepolia
ROLLUP_CREATOR_ADDRESS="0xE917553b67f630C3982236B6A1d7844B1021B909"
```
- For the `ROLLUP_CREATOR_ADDRESS` on any other supported chain, [please fimd it here](/docs/build-with-avail/Optimium/arbitrum-nitro/nitro-stack#smart-contract-addresses).
+ For the `ROLLUP_CREATOR_ADDRESS` on any other supported chain, [please fimd it here](/da/build-with-availOptimium/arbitrum-nitro/nitro-stack#smart-contract-addresses).
- Add the private key of a well funded ArbSepolia account in `DEVNET_PRIVKEY`
```bash
diff --git a/public/reserveDocs/Optimium/op-stack.mdx b/public/reserveDocs/Optimium/op-stack.mdx
index 0e648c4b7..653c2b5a3 100644
--- a/public/reserveDocs/Optimium/op-stack.mdx
+++ b/public/reserveDocs/Optimium/op-stack.mdx
@@ -16,9 +16,9 @@ Learn more about the [OP Stack here](https://docs.optimism.io/stack/getting-star
Avail is the permisionless unification layer for web3. Avail is designed to be a platform that connects different ecosystems by providing a modular, scalable, and interoperable platform.
Avail's vision is to provide a cohesive, unified user experience within a flexible and modular blockchain ecosystem, drawing on lessons from Web2 to innovate in Web3.
-With Avail's foundational DA layer ([Avail DA](/docs/introduction-to-avail/avail-da)), different ecosystems can innovate on top freely, while leveraging Nexus for cross-ecosystem messaging.
+With Avail's foundational DA layer ([Avail DA](/da/welcome-to-avail-docs/avail-da)), different ecosystems can innovate on top freely, while leveraging Nexus for cross-ecosystem messaging.
-Learn more about [Avail here](/docs/introduction-to-avail).
+Learn more about [Avail here](/da/welcome-to-avail-docs).
## How does OP Stack work with Avail?
@@ -40,7 +40,7 @@ Chains built with the Avail OP Stack inherit the security guarantees of Avail’
Get started with building your Avail-powered OP Stack chain today.
-
\ No newline at end of file
diff --git a/public/reserveDocs/Validium.mdx b/public/reserveDocs/Validium.mdx
index fa20312e4..2f8871775 100644
--- a/public/reserveDocs/Validium.mdx
+++ b/public/reserveDocs/Validium.mdx
@@ -4,7 +4,7 @@ import { FileIcon, FilesIcon } from '@components/icons'
# Validium
-
\ No newline at end of file
diff --git a/public/reserveDocs/Validium/madara.mdx b/public/reserveDocs/Validium/madara.mdx
index bd95a069a..85d9f702a 100644
--- a/public/reserveDocs/Validium/madara.mdx
+++ b/public/reserveDocs/Validium/madara.mdx
@@ -4,7 +4,7 @@ import { FileIcon, FilesIcon } from '@components/icons'
# Madara Starknet
-
\ No newline at end of file
diff --git a/public/reserveDocs/Validium/madara/overview.mdx b/public/reserveDocs/Validium/madara/overview.mdx
index 94a70f9d6..b29623945 100644
--- a/public/reserveDocs/Validium/madara/overview.mdx
+++ b/public/reserveDocs/Validium/madara/overview.mdx
@@ -51,4 +51,4 @@ The Madara stack, when integrated with Avail in a Validium setup, provides a sea
### Developer Resources
-To leverage Madara with Avail, developers are encouraged to refer to the [tutorial](/docs/build-with-avail/Validium/madara/madara.mdx) on creating an Avail-powered validium with Avail. For in-depth information on Madara's features, tools, and configurations, visit [Madara Documentation](https://docs.madara.zone/).
+To leverage Madara with Avail, developers are encouraged to refer to the [tutorial](/da/build-with-availValidium/madara/madara.mdx) on creating an Avail-powered validium with Avail. For in-depth information on Madara's features, tools, and configurations, visit [Madara Documentation](https://docs.madara.zone/).
diff --git a/public/reserveDocs/Validium/zkevm.mdx b/public/reserveDocs/Validium/zkevm.mdx
index 8a7dd0e1a..c93012b81 100644
--- a/public/reserveDocs/Validium/zkevm.mdx
+++ b/public/reserveDocs/Validium/zkevm.mdx
@@ -4,8 +4,8 @@ import { FileIcon, LinkIcon } from '@components/icons'
# Validium
-
-
\ No newline at end of file
diff --git a/public/reserveDocs/app-id-redacted-.mdx b/public/reserveDocs/app-id-redacted-.mdx
index babb4e042..a8a4dbe87 100644
--- a/public/reserveDocs/app-id-redacted-.mdx
+++ b/public/reserveDocs/app-id-redacted-.mdx
@@ -102,14 +102,14 @@ No need to pass any params, just click the `+` button next to the method name.
## How to register my own `appID`?
1. Make sure you have one or more Avail DA wallets connected to the explorer. If you don't know how to do so,
-you can follow our docs on [setting up a new wallet](/docs/end-user-guide/accounts#creating-an-account-on-avail-da).
+you can follow our docs on [setting up a new wallet](/user-guides/accounts#creating-an-account-on-avail-da).
2. Simply [click this link](https://explorer.availproject.org/#/extrinsics) OR navigate to the `extrinsics` section of the explorer through the `developer` tab.
Please note that the `Developer` tab does not show the `extrinsics` section at all if you don't
have a wallet set up on the explorer or an extension wallet connected to it.
-So make sure you have an [Avail DA wallet set up](/docs/end-user-guide/accounts) before moving forward.
+So make sure you have an [Avail DA wallet set up](/user-guides/accounts) before moving forward.
3. Select the `dataAvailability` pallet, and the `createApplicationKey` method.
@@ -153,7 +153,7 @@ So make sure you have an [Avail DA wallet set up](/docs/end-user-guide/accounts)
1. As stated earlier, an the `key` and `id` fields of every `appID` are unique. This means if you try to create an `appID` with the same `key` as an existing one,
the operation will fail. This is why it makes sense to use the `appKeys` method to check if your desired name is already taken.
-2. If you're a developer and are looking for more programmatic instructions, you can check out our [API reference](/api-reference/avail-node-api/da-create-application-key).
+2. If you're a developer and are looking for more programmatic instructions, you can check out our [API reference](/da/api-reference/avail-node-api/da-create-application-key).
3. **Anyone can submit any sort of data to any `appID` regardless of whether or not they created it.** \
*But what does this mean? And is this an attack vector?*
diff --git a/public/reserveDocs/balance-transfers.mdx b/public/reserveDocs/balance-transfers.mdx
index 6a6694f1a..8c791c9a8 100644
--- a/public/reserveDocs/balance-transfers.mdx
+++ b/public/reserveDocs/balance-transfers.mdx
@@ -21,7 +21,7 @@ import { Callout, Steps, Tabs } from 'nextra/components'
## Overview
Most of our users will be more comfortable using a dedicated Avail DA wallet to transfers AVAIL, and you can [refer
-to our docs](/docs/end-user-guide/accounts) to get started on the same.\
+to our docs](/user-guides/accounts) to get started on the same.\
Users can also however use the [Avail apps explorer](https://explorer.availproject.org/#/explorer) to transfer AVAIL which allows for more customization over these transactions.
If you don't have any AVAIL to get started, you can get some on our Turing testnet [following this guide](/docs/end-user-guide/faucet).
@@ -76,4 +76,4 @@ transaction.
4. Click on the `sign and submit` button on the bottom-right, and approve the transaction dialogue that pops-up.
5. And that's it. You just transferred AVAIL tokens from one address to another using the Avail Apps explorer.
-If you are wondering how to do this programatically, check out our [API reference on the same](/api-reference/avail-node-api/balances-transfer-keep-alive).
\ No newline at end of file
+If you are wondering how to do this programatically, check out our [API reference on the same](/da/api-reference/avail-node-api/balances-transfer-keep-alive).
\ No newline at end of file
diff --git a/public/reserveDocs/end-user-guide.mdx b/public/reserveDocs/end-user-guide.mdx
index 14026910d..bb5f9acb1 100644
--- a/public/reserveDocs/end-user-guide.mdx
+++ b/public/reserveDocs/end-user-guide.mdx
@@ -4,11 +4,11 @@ import { FileIcon } from '@components/icons'
# New User Guide
-
@@ -64,7 +64,7 @@ As a general-purpose base layer, Avail is designed to support many modular chain - Upon successful transaction completion, your AppId will be displayed. - Note down the Id for future reference. -For more information on AppId, check out the documentation [here](/docs/build-with-avail/interact-with-avail-da/app-id). +For more information on AppId, check out the documentation [here](/da/build-with-availinteract-with-avail-da/app-id). diff --git a/public/reserveDocs/learn-about-avail.mdx b/public/reserveDocs/learn-about-avail.mdx index 2b73c8bdc..230e1d821 100644 --- a/public/reserveDocs/learn-about-avail.mdx +++ b/public/reserveDocs/learn-about-avail.mdx @@ -4,6 +4,6 @@ import { FileIcon,FilesIcon } from '@components/icons' # Learn about Avail
-
\ No newline at end of file
diff --git a/public/reserveDocs/learn-about-avail/consensus.mdx b/public/reserveDocs/learn-about-avail/consensus.mdx
index d37ef06af..7bf08127a 100644
--- a/public/reserveDocs/learn-about-avail/consensus.mdx
+++ b/public/reserveDocs/learn-about-avail/consensus.mdx
@@ -4,7 +4,7 @@ import { FileIcon } from '@components/icons'
# Consensus
-
\ No newline at end of file
diff --git a/public/reserveDocs/learn-about-avail/consensus/babe.mdx b/public/reserveDocs/learn-about-avail/consensus/babe.mdx
index 600380bb0..742b89b0e 100644
--- a/public/reserveDocs/learn-about-avail/consensus/babe.mdx
+++ b/public/reserveDocs/learn-about-avail/consensus/babe.mdx
@@ -23,7 +23,7 @@ autonomously, offering probabilistic finality, or it can be integrated with a fi
BABE operates on a slot-based algorithm, dividing time into eras, epochs, further segmented into slots. Within the Avail context, each slot lasts for twenty seconds, aligning with the
target block time. In every slot, BABE determines an author (or potentially multiple authors) responsible for producing a block.
-If you're not familiar with Avail's terminology, you may check out our [Glossary](/docs/learn-about-avail/glossary).
+If you're not familiar with Avail's terminology, you may check out our [Glossary](/da/learn-about-avail/glossary).
On Avail's explorer, you can observe the eras and epochs by navigating to the staking page and locating the information at the top-right corner.
diff --git a/public/reserveDocs/overview.mdx b/public/reserveDocs/overview.mdx
index 873dc8fa5..33f0d0b7c 100644
--- a/public/reserveDocs/overview.mdx
+++ b/public/reserveDocs/overview.mdx
@@ -38,20 +38,20 @@ The first step to building a rollup with Avail DA is choosing the framework or p
### Optimium
-Optimiums are optimistic L2s that use external DA providers such as Avail DA for data availability. More information about optimiums [here](/docs/build-with-avail/Optimium).
+Optimiums are optimistic L2s that use external DA providers such as Avail DA for data availability. More information about optimiums [here](/da/build-with-availOptimium).
-
### Validium
-Validiums are validity-proven L2s that use external DA providers such as Avail DA for data availability. More information about validiums [here](/docs/build-with-avail/Validium).
+Validiums are validity-proven L2s that use external DA providers such as Avail DA for data availability. More information about validiums [here](/da/build-with-availValidium).
-
@@ -62,7 +62,7 @@ Sovereign rollups use DA providers like Avail DA for transaction ordering and da
-
Avail's Developer toolkit is going to be your best friend as you build on Avail DA. Avail supports a number of SDKs and Libraries to directly interact with the network.
diff --git a/public/reserveDocs/quickstart.mdx b/public/reserveDocs/quickstart.mdx
index 45ca46c96..e55be3282 100644
--- a/public/reserveDocs/quickstart.mdx
+++ b/public/reserveDocs/quickstart.mdx
@@ -19,7 +19,7 @@ import { Callout, Steps, Tabs } from 'nextra/components'
**LOOKING FOR ENDPOINTS TO INTERACT WITH AVAIL?**
-Check out the [networks page](/docs/networks). +Check out the [networks page](/da/networks).
## Get started with the Avail light client
@@ -46,9 +46,9 @@ avail lc up
curl -sL1 avail.sh | bash
```
-- You can find more detailed instructions for running the light client [here](/docs/operate-a-node/run-a-light-client/0010-light-client).
+- You can find more detailed instructions for running the light client [here](/da/operate-a-node/run-a-light-client/0010-light-client).
-- You can check out the light client API reference [here](/api-reference/avail-lc-api).
+- You can check out the light client API reference [here](/da/api-reference/avail-lc-api).
## Start using Avail's SDKs
@@ -64,7 +64,7 @@ They are available in three languages:
**Setting up the dev environments**
-Please refer to [this page in our docs](/api-reference/avail-node-api#setting-up-the-dev-environment) to set up the respective dev environments for the SDKs. +Please refer to [this page in our docs](/da/api-reference/avail-node-api#setting-up-the-dev-environment) to set up the respective dev environments for the SDKs.
With your dev environment set up, we are ready to explore what the SDKs can offer.
@@ -74,7 +74,7 @@ The next few snippets will focus on important lines within the code, but we have
Creating an instance of the SDK is quite straightforward. The only argument that needs to be passed is the
provider endpoint that we connect to. For this example, we will establish a connection to a an Avail DA node running on the `Turing Testnet`.
-You can find more endpoints in the [networks page](/docs/networks).
+You can find more endpoints in the [networks page](/da/networks).
diff --git a/public/reserveDocs/sovereign-rollups.mdx b/public/reserveDocs/sovereign-rollups.mdx
index 74c5e50b0..cde72d919 100644
--- a/public/reserveDocs/sovereign-rollups.mdx
+++ b/public/reserveDocs/sovereign-rollups.mdx
@@ -7,7 +7,7 @@ import { LinkIcon } from '@components/icons'
For all questions and queries related to the Clash of Nodes campaign, -please visit **[this page](/docs/clash-of-nodes/faqs.mdx)**. +please visit **[this page](/da/clash-of-nodes/faqs.mdx)**.
-The [Avail team](https://www.availproject.org/aboutus) consists of more than 40 professionals with solid experience in their areas of expertise ranging from marketing to blockchain design and programming. +The [Avail team](https://availproject.org/aboutus) consists of more than 40 professionals with solid experience in their areas of expertise ranging from marketing to blockchain design and programming. Many have proven track records in the Web3 space and a diverse background that forms the foundation of a solid team. ## What Partnerships are in place? -Avail has a strong list of strategic partnerships in place across different ecosystems. For a full list of partners, please see [Ecosystem Page](https://www.availproject.org/ecosystem). +Avail has a strong list of strategic partnerships in place across different ecosystems. For a full list of partners, please see [Ecosystem Page](https://availproject.org/ecosystem). New partnerships will be announced soon so follow us on [X](https://twitter.com/AvailProject) to keep up to date. ## Is Avail DA the same as Celestia? diff --git a/app/da/learn-about-avail/app-ids/page.mdx b/app/da/learn-about-avail/app-ids/page.mdx index 3800f1277..5d359fa43 100644 --- a/app/da/learn-about-avail/app-ids/page.mdx +++ b/app/da/learn-about-avail/app-ids/page.mdx @@ -9,11 +9,11 @@ import { Callout, Steps, Tabs } from 'nextra/components'
If you are just looking for the easiest way to create your own AppID on Avail to continue building, -you can skip to [this page](/docs/build-with-avail/interact-with-avail-da/app-id). +you can skip to [this page](/da/build-with-availinteract-with-avail-da/app-id).
-You can check out our [API reference](/api-reference/avail-node-api/da-create-application-key) for the same. +You can check out our [API reference](/da/api-reference/avail-node-api/da-create-application-key) for the same.
[https://mainnet-rpc.avail.so/rpc](https://mainnet-rpc.avail.so/rpc)
| [https://turing-rpc.avail.so/rpc](https://turing-rpc.avail.so/rpc) | | **WS Endpoints** | [wss://avail-mainnet.public.blastapi.io/](wss://avail-mainnet.public.blastapi.io/)
[wss://mainnet.avail-rpc.com/](wss://mainnet.avail-rpc.com/)
| [wss://turing-rpc.avail.so/ws](wss://turing-rpc.avail.so/ws) | | **Chain Spec** | [chainspec.raw.json](https://raw.githubusercontent.com/availproject/avail/main/misc/genesis/mainnet.chain.spec.raw.json) | [chainspec.raw.json](https://github.com/availproject/avail/blob/main/misc/genesis/testnet.turing.chain.spec.raw.json) | diff --git a/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx b/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx index 99a436048..2d1b88ad2 100644 --- a/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx +++ b/app/da/operate-a-node/become-a-validator/backup-your-validator/page.mdx @@ -73,4 +73,4 @@ EQUIVIVOCAITON RISK
Never run two nodes with identical keys at the same time to avoid double-signing.
@@ -156,8 +156,8 @@ You should be seeing something like this:
As you move forward, here are some essential actions to consider:
1. **Backup Your Validator**: Ensure you have a secure backup of your validator settings and keys. Refer to the
- [Backup Guide](/docs/operate-a-node/become-a-validator/backup-your-validator) for detailed steps.
+ [Backup Guide](/da/operate-a-node/become-a-validator/backup-your-validator) for detailed steps.
-2. **Start Monitoring**: If you haven't already, set up monitoring tools to keep track of your validator's performance. Check out the [Monitoring Guide](/docs/operate-a-node/become-a-validator/monitor-your-validator) for recommendations.
+2. **Start Monitoring**: If you haven't already, set up monitoring tools to keep track of your validator's performance. Check out the [Monitoring Guide](/da/operate-a-node/become-a-validator/monitor-your-validator) for recommendations.
3. **Join the Community**: Connect with other validators and the Avail team on the official [Discord Channel](https://discord.com/invite/AvailProject). It's a great place to share experiences, ask questions, and get updates.
diff --git a/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx b/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
index 292360b8c..00c5955a1 100644
--- a/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
+++ b/app/da/operate-a-node/become-a-validator/upgrade-your-validator/page.mdx
@@ -31,7 +31,7 @@ sudo systemctl stop avail.service
```
- Locate your Avail binary, create a backup of the current binary, and then uninstall the existing binary by deleting the binary. Proceed to download the most recent binary announced in Discord, which will replace the previous binary version.
- To provide an example, assuming your existing binary is located at `/home/avail/avail-node/` and is named `data-avail`, and you used the [validator](/docs/operate-a-node/become-a-validator) setup guidelines while obtaining a pre-built binary from the Avail GitHub repository, proceed as outlined below.
+ To provide an example, assuming your existing binary is located at `/home/avail/avail-node/` and is named `data-avail`, and you used the [validator](/da/operate-a-node/become-a-validator) setup guidelines while obtaining a pre-built binary from the Avail GitHub repository, proceed as outlined below.
```
cd /home/avail/avail-node/
diff --git a/app/da/operate-a-node/node-types/page.mdx b/app/da/operate-a-node/node-types/page.mdx
index 44aafba05..bd25e7e4a 100644
--- a/app/da/operate-a-node/node-types/page.mdx
+++ b/app/da/operate-a-node/node-types/page.mdx
@@ -49,6 +49,6 @@ RPC nodes expose an API for remote interactions, serving as a gateway for develo
## Next Steps
-Now that you have a comprehensive understanding of the various node types within the Avail network, it's recommended to take your first step by setting up a Light Client. Before you begin, make sure to review the [System Requirements guide](/docs/operate-a-node/run-a-full-node/requirements). Once you're ready, you can proceed to the [Light Client Deployment guide](/docs/operate-a-node/run-a-light-client/0010-light-client) to get started.
+Now that you have a comprehensive understanding of the various node types within the Avail network, it's recommended to take your first step by setting up a Light Client. Before you begin, make sure to review the [System Requirements guide](/da/operate-a-node/run-a-full-node/requirements). Once you're ready, you can proceed to the [Light Client Deployment guide](/da/operate-a-node/run-a-light-client/0010-light-client) to get started.
> Light Clients provide an accessible entry point to the Avail network, enabling quick interactions without storing the full blockchain. Ideal for newcomers, they play an integral role in maintaining a robust data availability layer.
diff --git a/app/da/operate-a-node/page.mdx b/app/da/operate-a-node/page.mdx
index 802f9da2e..a6c453604 100644
--- a/app/da/operate-a-node/page.mdx
+++ b/app/da/operate-a-node/page.mdx
@@ -10,10 +10,10 @@ import { FileIcon, FilesIcon } from '@components/icons'
# Run a Node on Avail
-Go to [light client API reference](/api-reference/avail-lc-api) +Go to [light client API reference](/da/api-reference/avail-lc-api)
-App IDs are an important concept in the context of Avail. We recommend you go through [this page in our docs](/docs/learn-about-avail/app-ids) to understand how they work before moving forward. +App IDs are an important concept in the context of Avail. We recommend you go through [this page in our docs](/da/learn-about-avail/app-ids) to understand how they work before moving forward.
-If you're not interested in theory, skip [to this link](/docs/operate-a-node/run-a-light-client/0010-light-client) for instructions on how to run an Avail light client. +If you're not interested in theory, skip [to this link](/da/operate-a-node/run-a-light-client/0010-light-client) for instructions on how to run an Avail light client.
-You can refer to this [page in our docs](/nexus/concepts/unified-balance) for more details. +You can refer to this [page in our docs](/nexus/concepts/bridge-v-swap) for more details.
The only prerequisite is that you have access to one or more Avail DA accounts. -Refer to our docs on [setting up an Avail wallet](/docs/end-user-guide/accounts) for more details if needed +Refer to our docs on [setting up an Avail wallet](/user-guides/accounts) for more details if needed
The only prerequisite is that you have access to one or more Avail DA accounts. -Refer to our docs on [setting up an Avail wallet](/docs/end-user-guide/accounts) for more details if needed +Refer to our docs on [setting up an Avail wallet](/user-guides/accounts) for more details if needed
@@ -94,7 +94,7 @@ Please beware of any phishing or scam attempts. Only rely on official Avail comm Anyone can stake AVAIL throughout Avail's infrastructure to earn staking rewards. We will release detailed staking guides along with our products as they are released. -For now you can refer to the Avail DA staking guide [in our docs](/docs/stake-on-avail). +For now you can refer to the Avail DA staking guide [in our docs](/user-guides/staking-governance/stake-on-avail). If you want to read about staking on Avail in more detail, you can refer to [our blog](https://blog.availproject.org/avail-the-token-powering-blockchain-unification/#avail-staking).
diff --git a/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx b/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx index 85b042afb..8e9dd7ed2 100644 --- a/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx +++ b/app/user-guides/staking-governance/stake-on-avail/overview/page.mdx @@ -60,7 +60,7 @@ If your stake amount is significantly larger than the threshold and minimum nomi ## Staking Reward Payout Lifecycle -If you have staked your AVAIL in the network, you will only start earning rewards in the **next** [era](/docs/glossary#era), and not in the era you staked in. The stake is used to increase the number of tokens held by your nominated validators, increasing their chance of being selected by the election algorithm for block production during a specific era. An era is a period of 24 hours during which an active set of validators is producing blocks and performing other actions on the chain. Hence your stake only becomes active in the next era after which you've staked. +If you have staked your AVAIL in the network, you will only start earning rewards in the **next** [era](/da/glossary#era), and not in the era you staked in. The stake is used to increase the number of tokens held by your nominated validators, increasing their chance of being selected by the election algorithm for block production during a specific era. An era is a period of 24 hours during which an active set of validators is producing blocks and performing other actions on the chain. Hence your stake only becomes active in the next era after which you've staked. Here is the lifecycle of your stake when you stake in _Era N_: diff --git a/public/reserveDocs/Optimium.mdx b/public/reserveDocs/Optimium.mdx index ec019fbdf..2a5593048 100644 --- a/public/reserveDocs/Optimium.mdx +++ b/public/reserveDocs/Optimium.mdx @@ -7,8 +7,8 @@ import { FilesIcon } from '@components/icons' There are a number of tools to spin up an optimium today. We are actively integrating with rollup stacks to give you, the developer, maximum flexibility when choosing the stack of your choice while also retaining the benefits that Avail provides. Today you can spin your optimium up with the following frameworks below.
@@ -64,7 +64,7 @@ As a general-purpose base layer, Avail is designed to support many modular chain - Upon successful transaction completion, your AppId will be displayed. - Note down the Id for future reference. -For more information on AppId, check out the documentation [here](/docs/build-with-avail/interact-with-avail-da/app-id). +For more information on AppId, check out the documentation [here](/da/build-with-availinteract-with-avail-da/app-id). diff --git a/public/reserveDocs/learn-about-avail.mdx b/public/reserveDocs/learn-about-avail.mdx index 2b73c8bdc..230e1d821 100644 --- a/public/reserveDocs/learn-about-avail.mdx +++ b/public/reserveDocs/learn-about-avail.mdx @@ -4,6 +4,6 @@ import { FileIcon,FilesIcon } from '@components/icons' # Learn about Avail
-Check out the [networks page](/docs/networks). +Check out the [networks page](/da/networks).
-Please refer to [this page in our docs](/api-reference/avail-node-api#setting-up-the-dev-environment) to set up the respective dev environments for the SDKs. +Please refer to [this page in our docs](/da/api-reference/avail-node-api#setting-up-the-dev-environment) to set up the respective dev environments for the SDKs.