You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: pages/docs/end-user-guide/balance-transfers.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ import { Callout } from 'nextra/components'
20
20
21
21
## Overview
22
22
23
-
Balance transfers are a method for transferring funds from one account to another. This guide will walk you through the process using [<ins>Avail-JS UI</ins>](https://goldberg.avail.tools/). Before you begin, ensure you have [<ins>created an account</ins>](/docs/end-user-guide/accounts) and have [<ins>funds available</ins>](/docs/end-user-guide/faucet) for transfer.
23
+
Balance transfers are a method for transferring funds from one account to another. This guide will walk you through the process using [<ins>Avail-JS UI</ins>](https://explorer.avail.so/). Before you begin, ensure you have [<ins>created an account</ins>](/docs/end-user-guide/accounts) and have [<ins>funds available</ins>](/docs/end-user-guide/faucet) for transfer.
Copy file name to clipboardexpand all lines: pages/docs/end-user-guide/explorer.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ import { Callout } from 'nextra/components'
16
16
17
17
## Introduction
18
18
19
-
The [<ins>Goldberg Testnet Explorer</ins>](https://goldberg.avail.tools/) serves as a powerful interface for interacting with the Avail network. Whether you're a developer, a validator, or an end-user, the explorer provides you with the tools to inspect network activities, manage accounts, and participate in governance. This guide will walk you through its key features.
19
+
The [<ins>Goldberg Testnet Explorer</ins>](https://explorer.avail.so/) serves as a powerful interface for interacting with the Avail network. Whether you're a developer, a validator, or an end-user, the explorer provides you with the tools to inspect network activities, manage accounts, and participate in governance. This guide will walk you through its key features.
Copy file name to clipboardexpand all lines: pages/docs/end-user-guide/identity.mdx
+3-2
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ This guide will walk you through the process of setting an on-chain identity on
21
21
22
22
To store personal information on-chain, users are required to lock a specific amount of funds as a bond. This bond is refundable upon the clearance of the identity.
23
23
24
-
Retrieve the necessary bond amounts by querying the [<ins>Chain state constants</ins>](https://goldberg.avail.tools/#/chainstate) on the [<ins>Goldberg Explorer</ins>](/docs/end-user-guide/explorer).
24
+
Retrieve the necessary bond amounts by querying the [<ins>Chain state constants</ins>](https://explorer.avail.so/#/chainstate) on the [<ins>Goldberg Explorer</ins>](/docs/end-user-guide/explorer).
25
25
26
26
### Accessing Chain State Constants
27
27
@@ -31,7 +31,8 @@ Determine the bond amounts via the chain's interface by doing the following:
31
31
2. Under the "Constants" tab, choose `identity` from the "selected constant query" menu. The `basicDeposit: u128` parameter will be the default.
32
32
3. To add constants to the view, click the "plus" ("+") icon.
33
33
34
-
Each information field is limited to 32 bytes. Use a [<ins>UTF8 to bytes converter</ins>](https://onlinetools.com/utf8/convert-utf8-to-bytes) when manually entering data through the [<ins>Extrinsics UI</ins>](https://goldberg.avail.tools/#/extrinsics).
34
+
Each information field is limited to 32 bytes. Use a [<ins>UTF8 to bytes converter</ins>](https://onlinetools.com/utf8/convert-utf8-to-bytes)
35
+
when manually entering data through the [<ins>Extrinsics UI</ins>](https://explorer.avail.so/#/extrinsics).
2. Under 'Staking', select 'Pools'. Here, you will see the [<ins>Staking Pool Dashboard</ins>](https://goldberg.avail.tools/#/staking/pools), which shows a list of active pools, their state, points, claimable rewards, and other details.
93
+
2. Under 'Staking', select 'Pools'. Here, you will see
94
+
the [<ins>Staking Pool Dashboard</ins>](https://explorer.avail.so/#/staking/pools),
95
+
which shows a list of active pools, their state, points, claimable rewards, and other details.
**The Goldberg Testnet is the latest test network of the Avail Project.**
47
+
**The Turing Testnet is the latest test network of the Avail Project.**
48
48
49
49
### Phase One: Laying the Groundwork
50
50
@@ -73,4 +73,8 @@ The Kate testnet offers a multitude of avenues for user engagement:
73
73
74
74
### Phase Three: Incentivized Testnet
75
75
76
-
Avail is now ushering in the [<ins>Clash of Nodes</ins>](/category/clash-of-nodes/) campaign using the Goldberg testnet. This campaign is a call to action for node operators to participate in an incentivized, real-time testnet environment. It's a critical testbed for Avail's infrastructure, designed to rigorously evaluate its capacity as a foundational layer for the next wave of rollup-centric blockchain ecosystems.
76
+
Avail is now ushering in the [<ins>Clash of Nodes</ins>](/category/clash-of-nodes/) campaign using the Goldberg testnet. This campaign is a call to action for node operators to participate in an incentivized, real-time testnet environment. It's a critical testbed for Avail's infrastructure, designed to rigorously evaluate its capacity as a foundational layer for the next wave of rollup-centric blockchain ecosystems.
77
+
78
+
### Phase Four: The final pre-mainnet run
79
+
The Turing Testnet is live and marks Avail's final and definitive pre-Mainnet testing environment, aimed at vetting Mainnet deployments,
80
+
executing extensive stress tests, and assessing network topologies for scalability and resilience.
Copy file name to clipboardexpand all lines: pages/docs/operate-a-node/become-a-validator/0010-basics.mdx
+7-70
Original file line number
Diff line number
Diff line change
@@ -31,77 +31,14 @@ Before trying anything, make sure that you fully read the chapter first before d
31
31
32
32
## Installation & Setup
33
33
34
-
Our first step is to obtain the prebuilt binary for Avail Node. We offer a wide range of prebuilds, but in case you don't see your Linux flavor or architecture here, head to the FAQ chapter to learn how to build your own executable.
Our first step is to obtain the prebuilt binary for Avail Node. [We offer a wide range of prebuilds](https://github.com/availproject/avail/releases/tag/v2.1.0.0-rc1), but in case you don't see your Linux flavor or architecture here, head to the FAQ chapter to learn how to build your own executable.
42
35
43
36
Once you have found your OS (or picked the generic one), execute the given command to obtain the needed Avail Node binary.
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-ubuntu-2004-data-avail.tar.gz && tar -xf ./x86_64-ubuntu-2004-data-avail.tar.gz
39
+
wget https://github.com/availproject/avail/releases/download/<version-number>/<your-machine-specific-executable>.tar.gz && tar -xf ./<your-machine-specific-executable>.tar.gz
50
40
```
51
41
52
-
</Tabs.Tab>
53
-
54
-
<Tabs.Tab>
55
-
56
-
```bash
57
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-ubuntu-2204-data-avail.tar.gz && tar -xf ./x86_64-ubuntu-2204-data-avail.tar.gz
58
-
```
59
-
60
-
</Tabs.Tab>
61
-
<Tabs.Tab>
62
-
63
-
```bash
64
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-ubuntu-2310-data-avail.tar.gz && tar -xf ./x86_64-ubuntu-2310-data-avail.tar.gz
65
-
```
66
-
67
-
</Tabs.Tab>
68
-
<Tabs.Tab>
69
-
70
-
```bash
71
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-debian-11-data-avail.tar.gz && tar -xf ./x86_64-debian-11-data-avail.tar.gz
72
-
```
73
-
74
-
</Tabs.Tab>
75
-
<Tabs.Tab>
76
-
77
-
```bash
78
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-debian-12-data-avail.tar.gz && tar -xf ./x86_64-debian-12-data-avail.tar.gz
79
-
```
80
-
81
-
</Tabs.Tab>
82
-
<Tabs.Tab>
83
-
84
-
```bash
85
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-fedora-38-data-avail.tar.gz && tar -xf ./x86_64-fedora-38-data-avail.tar.gz
86
-
```
87
-
88
-
</Tabs.Tab>
89
-
<Tabs.Tab>
90
-
91
-
```bash
92
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-fedora-39-data-avail.tar.gz && tar -xf ./x86_64-fedora-39-data-avail.tar.gz
93
-
```
94
-
95
-
</Tabs.Tab>
96
-
<Tabs.Tab>
97
-
98
-
```bash
99
-
wget https://github.com/availproject/avail/releases/download/v1.9.0.0/x86_64-arch-data-avail.tar.gz && tar -xf ./x86_64-arch-data-avail.tar.gz
100
-
```
101
-
102
-
</Tabs.Tab>
103
-
</Tabs>
104
-
105
42
## Running Our First Network
106
43
107
44
With the binary ready in our working directory, it's time to run it and see what we get.
@@ -184,7 +121,7 @@ The last line, `👤 Role: FULL`, reveals that our node is in Full mode, meaning
184
121
185
122
### Changing Name
186
123
187
-
To change our node's name, use the `--name` flag. Before proceeding, make sure to stop your node with Ctrl-C. Now, let's rerun it with a more appealing name:
124
+
To change our node's name, use the `--name` flag. Before proceeding, make sure to stop your node with `Ctrl-C`. Now, let's rerun it with a more appealing name:
188
125
189
126
```bash
190
127
./data-avail --chain dev --name KingMagnifico
@@ -335,14 +272,14 @@ After running the node for a minute or two, stop it by pressing Ctrl+C and rerun
335
272
336
273
Now stop the node with Ctrl+C and let's remove our storage: `rm ./node-data -r`.
337
274
338
-
## Connecting Our Node to Goldberg
275
+
## Connecting Our Node to Turing
339
276
340
-
With all this preliminary knowledge ready to be used, we can now finally take the last step and connect our node to the Goldberg network. I will use the same name as before, KingMagnifico, but I suggest you choose one that you like.
277
+
With all this preliminary knowledge ready to be used, we can now finally take the last step and connect our node to the Turing network. I will use the same name as before, KingMagnifico, but I suggest you choose one that you like.
341
278
342
279
Before running our node, ensure that our storage folder is removed or empty, and that we don't have any previous nodes already running. With that said, let's finally do what we've been waiting for since the beginning:
@@ -432,4 +369,4 @@ Once we see `💤 Idle`, we are done syncing, and our node has now fully caught
432
369
433
370
## What's Next
434
371
435
-
This is where our story ends. We have a working node connected to the Goldberg chain. It doesn't do much right now, certainly doesn't produce any blocks, but this is something that we will fix. Before that, let's discuss in the next chapter how to do a simple but effective deployment.
372
+
This is where our story ends. We have a working node connected to the Turing chain. It doesn't do much right now, certainly doesn't produce any blocks, but this is something that we will fix. Before that, let's discuss in the next chapter how to do a simple but effective deployment.
0 commit comments