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
> Refer to [GitHub Docs: Configuring a remote for a fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork).
@@ -184,4 +184,4 @@ Always keep your JSON file in a secure and offline location. Losing this file an
184
184
185
185
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.
186
186
187
-
Ready to explore further? Navigate to the next guide to learn [<ins>how to use the Goldberg Testnet Explorer</ins>](/docs/end-user-guide/explorer) and get hands-on experience with the network.
187
+
Ready to explore further? Navigate to the next guide to learn [<ins>how to use the Avail Explorer</ins>](/docs/end-user-guide/explorer) and get hands-on experience with the network.
Copy file name to clipboardexpand all lines: pages/docs/end-user-guide/balance-transfers.mdx
+2-17
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
id: balance-transfers
3
3
title: How to Perform Balance Transfers on Avail
4
4
sidebar_label: Balance Transfers
5
-
description: 'Learn how to perform balance transfers on the Goldberg testnet.'
5
+
description: 'Learn how to perform balance transfers on the Avail Network.'
6
6
keywords:
7
7
- docs
8
8
- avail
@@ -22,21 +22,6 @@ import { Callout } from 'nextra/components'
22
22
23
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.
24
24
25
-
<Callouttype="info">
26
-
CLASH OF NODES<br/>
27
-
In the balance transfer challenge part of Clash of Nodes, participants must follow these guidelines:
28
-
29
-
1.**Token Acquisition**: To participate in balance transfers, tokens must be acquired through the designated [<ins>faucet</ins>](/docs/end-user-guide/faucet).
30
-
2.**Faucet Transfer Limit**: Participants can obtain tokens from the [<ins>faucet</ins>](/docs/end-user-guide/faucet) only once per day.
31
-
3.**Regular Engagement**: Participants are encouraged to engage with the challenge daily. The daily acquisition of tokens from the faucet and subsequent transfers cultivate consistent participation.
32
-
</Callout>
33
-
34
-
<Callout>
35
-
USING SUBWALLET<br/>
36
-
[<ins>SubWallet</ins>](https://www.subwallet.app/) currently supports the Goldberg testnet and can be used for balance transfers.
37
-
38
-
Please view the third-party content disclaimer [<ins>here</ins>](https://github.com/availproject/availproject.github.io/blob/main/CONTENT_DISCLAIMER.md).
On Avail, similar to other Substrate-based chains, an account must hold a minimum balance to stay active. This minimum, known as the Existential Deposit (ED), is set at **0.00001 AVAIL on the Goldberg testnet**. The ED helps prevent blockchain bloat from accounts with tiny or zero balances, thereby maintaining network efficiency and low fees. If an account's balance falls below this threshold, it gets deactivated, and the remaining balance is removed. Reactivating the account requires a deposit larger than the ED, but this won't restore the lost funds.
36
+
On Avail, similar to other Substrate-based chains, an account must hold a minimum balance to stay active. This minimum, known as the Existential Deposit (ED), is set at **0.000001 AVAIL on the Avail Network**. The ED helps prevent blockchain bloat from accounts with tiny or zero balances, thereby maintaining network efficiency and low fees. If an account's balance falls below this threshold, it gets deactivated, and the remaining balance is removed. Reactivating the account requires a deposit larger than the ED, but this won't restore the lost funds.
52
37
</Callout>
53
38
54
39
4. When you are ready to execute your transaction, enter your password and click on the "Sign and Submit" button.
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.
19
+
The [<ins>Avail 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.
This guide will walk you through the process of setting an on-chain identity on the Goldberg testnet.
18
+
This guide will walk you through the process of setting an on-chain identity on the Avail network.
19
19
20
20
## Reserve Funds for Identity Bonding
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://explorer.avail.so/#/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>Avail Explorer</ins>](/docs/end-user-guide/explorer).
With the binary ready in our working directory, it's time to run it and see what we get.
45
45
46
46
```bash
47
-
./data-avail
47
+
./avail-node
48
48
```
49
49
50
50
Output:
51
51
52
52
```
53
-
Error: Input("Please specify which chain you want to run, e.g. --chain goldberg")
53
+
Error: Input("Please specify which chain you want to run, e.g. --chain turing")
54
54
```
55
55
56
56
Yikes, an error. This is okay; by default, our node doesn't know which chain (network) it should connect to. To fix this, we will provide one, but not the recommended one, not yet.
57
57
58
58
Instead, we are going to run a development network:
59
59
60
60
```bash
61
-
./data-avail --chain dev
61
+
./avail-node --chain dev
62
62
```
63
63
64
64
Output:
65
65
66
66
```bash
67
67
2023-11-27 16:26:31 Avail Node
68
-
2023-11-27 16:26:31 ✌️ version 1.8.3-6d8aff28012
69
-
2023-11-27 16:26:31 ❤️ by Anonymous, 2017-2023
68
+
2023-11-27 16:26:31 ✌️ version 2.1.4-9d88dbf7b4f
69
+
2023-11-27 16:26:31 ❤️ by Avail Project <[email protected]>, 2017-2024
70
70
2023-11-27 16:26:31 📋 Chain specification: Avail Development Network
71
71
2023-11-27 16:26:31 🏷 Node name: cagey-owl-5997
72
72
2023-11-27 16:26:31 👤 Role: FULL
@@ -124,7 +124,7 @@ The last line, `👤 Role: FULL`, reveals that our node is in Full mode, meaning
124
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:
125
125
126
126
```bash
127
-
./data-avail --chain dev --name KingMagnifico
127
+
./avail-node --chain dev --name KingMagnifico
128
128
```
129
129
130
130
Output:
@@ -146,7 +146,7 @@ To run our node in validator mode, add the `--validator` flag along with the oth
146
146
Stop your node again with Ctrl+C and rerun it with the `--validator` flag::
147
147
148
148
```bash
149
-
./data-avail --chain dev --name KingMagnifico --validator
149
+
./avail-node --chain dev --name KingMagnifico --validator
150
150
```
151
151
152
152
Output:
@@ -177,7 +177,7 @@ Our node is operating in validator mode, but the network expects validator 'Alic
177
177
Let's stop our node again with Ctrl+C and rerun it with the `--alice` flag:
178
178
179
179
```bash
180
-
./data-avail --chain dev --name KingMagnifico --validator --alice
180
+
./avail-node --chain dev --name KingMagnifico --validator --alice
181
181
```
182
182
183
183
Output:
@@ -222,7 +222,7 @@ Although we've used several flags to run a development network, there's an easie
222
222
Stop the node again with Ctrl+C and rerun it with the `--dev` flag:
223
223
224
224
```bash
225
-
./data-avail --dev --name KingMagnifico
225
+
./avail-node --dev --name KingMagnifico
226
226
```
227
227
228
228
Output:
@@ -242,14 +242,14 @@ Output:
242
242
243
243
And we get the same result.
244
244
245
-
### Temporary and Persistante Storage
245
+
### Temporary and Persistent Storage
246
246
247
247
When our node runs a network, it needs to store network-related data. By not specifying a location, it stores the data in a default location, which is often not what we want.
248
248
249
249
Using the `--tmp` flag makes it use a different location each time we run our network. This is implied when using `--dev` and is useful when we don't care about preserving our state. To make our storage persistent through runs, we can use the `-d` flag.
@@ -279,7 +279,7 @@ With all this preliminary knowledge ready to be used, we can now finally take th
279
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:
2023-11-27 17:24:41 💾 Database: RocksDb at ./node-data/chains/avail_goldberg_testnet/db/full
294
+
2023-11-27 17:24:41 💾 Database: RocksDb at ./node-data/chains/avail_turing_testnet/db/full
295
295
```
296
296
297
297
Okay, so far so good. Our role is `AUTHORITY`, which means that we are running in validator mode. Our name is clearly the correct one, KingMagnifico, and our database location is correct. Let's see the next few log lines:
| Spheron | Cloud-based, decentralized, infrastructure services for blockchain applications, offering simplicity and scalability. | Hosted |[<ins>Deploy and Operate an Avail Testnet Validator</ins>](https://blog.spheron.network/deploy-an-avail-node-in-minutes-using-spheron-compute)|
22
-
| OnFinality | Provides infrastructure for blockchain networks. Specialized in setting up validators. | Hosted |[<ins>Set up an Avail Goldberg Testnet Validator</ins>](https://documentation.onfinality.io/support/set-up-an-avail-goldberg-testnet-validator)|
21
+
| Spheron | Cloud-based, decentralized, infrastructure services for blockchain applications, offering simplicity and scalability. | Hosted |[<ins>Deploy and Operate an Avail Testnet Validator</ins>](https://blog.spheron.network/deploy-an-avail-node-in-minutes-using-spheron-compute)|
0 commit comments