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: CONTRIBUTING.md
+41-62
Original file line number
Diff line number
Diff line change
@@ -2,48 +2,8 @@
2
2
3
3
The Documentation team at Avail are the primary maintainers of the Avail Documentation and will review all issues and pull requests created in this repository.
-[Ways to Contribute to the Avail Documentation](#ways-to-contribute-to-the-avail-documentation)
9
-
-[How to Contribute Changes via the Avail Documentation Website](#how-to-contribute-changes-via-the-avail-documentation-website)
10
-
-[How to Locally Run the Avail Documentation](#how-to-locally-run-the-avail-documentation)
11
-
-[Quick Run](#quick-run)
12
-
-[Setup Steps](#setup-steps)
13
-
-[License](#license)
14
-
<!--/ TOC -->
15
-
16
-
## Ways to Contribute to the Avail Documentation
17
-
18
-
If you spot typos or grammar mistakes, please go ahead and submit a pull request with the fixes. For more significant changes, it's advisable to start with a GitHub issue to discuss it with the maintainers. We generally prefer pull requests over issues for suggesting changes to the Docs.
19
-
20
-
| ❗ We are in the process of setting guidelines to ensure all new contributions continue to improve the Docs without compromising its quality. Please stay tuned. |
Before making a contribution, please consult any existing issues or initiate a new discussion to ensure alignment with the documentation's objectives.
24
-
Your contributions can significantly enrich the Docs in the following ways:
25
-
26
-
1.**General Overviews**: Introductory articles that provide a comprehensive understanding of Avail's data availability layer and modular approach to blockchains.
27
-
28
-
2.**Technical Deep Dives**: Detailed explorations into specific components of Avail's architecture, such as its data availability layer, modularity, and consensus algorithms.
29
-
30
-
3.**Use-Case Scenarios**: Articles that showcase real-world applications of Avail in solutions like validiums, appchains, and sovereign rollups.
31
-
32
-
4.**Tooling**: Documentation or guides on tools that facilitate development, testing, or deployment on Avail. This could include IDE plugins, testing frameworks, or monitoring tools.
33
-
34
-
5.**Third-Party Services and Deployments**: Information on external services, deployments, and implementations that integrate with Avail. This could include oracles, data analytics platforms, liquidity providers, as well as infrastructure solutions that provide Avail-based infrastructure.
35
-
36
-
6.**Community Contributions**: Lists of active Avail communities, educational resources, or upcoming events that enrich the ecosystem.
37
-
38
-
7.**Governance & Economics**: Insights into the governance model and tokenomics that underpin Avail's network.
39
-
40
-
8.**Security Practices**: Guidelines and resources for ensuring the security and integrity of applications, smart contracts, and general infrastructure on Avail.
41
-
42
-
9.**Troubleshooting Guides**: Solutions to common challenges, FAQs, and other resources that assist both newcomers and experienced users.
43
-
44
-
10.**Emerging Technologies**: Articles on upcoming features, advancements, or experimental technologies in the Avail pipeline. For instance, contributions could explore the impact of "Dank Sharding" on Avail's scalability, transaction costs, and its enablement of new decentralized applications.
45
-
46
-
> Note: This is a general overview and the actual repository may contain additional files and folders for specific functionalities.
5
+
> ℹ️ Please make sure to create an issue outlining your feedback/content request for the docs before creating a PR.
6
+
> PRs created without approval will be closed. We are open to technical articles on a wide variety of topics related to Avail and Web3 in general. If you have something in mind, please feel free to jump in with an issue on the repo.
47
7
48
8
## How to Contribute Changes via the Avail Documentation Website
49
9
@@ -56,61 +16,56 @@ Contributing to the Avail Documentation is simple. You'll need a GitHub account
56
16
5.**Initiate Pull Request**: Scroll to the bottom and click on **Create pull request**.
57
17
6.**Title Your PR**: Give your pull request a descriptive title. For example, if you're editing the "Getting Started" page, you could title it _Update /docs/getting-started.md_.
58
18
7.**Describe Changes**: In the pull request description, specify the issue your changes resolve.
19
+
59
20
> See [GitHub Docs on Linking a Pull Request to an Issue](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) for guidance.
21
+
60
22
8.**Additional Information**: Provide a concise summary of the changes you've made. Include screenshots or references if applicable.
61
23
9.**Submit**: Click **Propose changes** to finalize your pull request. This will create a new branch in your fork.
62
24
63
25
## How to Locally Run the Avail Documentation
64
26
65
-
### Quick Run
66
-
67
-
For those who want to quickly install and start the Avail Documentation locally, you can follow these steps:
This will create a repo named `docs` in your current directory.
44
+
92
45
3.**Navigate to the Repository**
93
46
94
47
```bash
95
-
cdavailproject.github.io
48
+
cddocs
96
49
```
97
50
98
51
4.**Add Upstream Remote**
99
52
100
53
> 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).
> ℹ️ You can check if the upstream was added correctly by running `git remote -v`
60
+
106
61
5.**Sync Your Fork**
107
62
108
63
> See [GitHub Docs: Syncing a fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork).
109
64
110
65
```bash
111
-
git checkout master
66
+
git checkout main
112
67
git fetch upstream
113
-
git merge upstream/master
68
+
git merge upstream/main
114
69
```
115
70
116
71
6.**Install Dependencies**
@@ -127,8 +82,32 @@ yarn start
127
82
pnpm run dev
128
83
```
129
84
130
-
This will start a local dev derver at `http://localhost:3000` on your machine.
85
+
This will start a local dev derver at `http://localhost:3000` on your machine.
86
+
87
+
## Push changes and create PR
88
+
89
+
Once you are done with all the changes, save all you files and run:
90
+
91
+
1.```bash
92
+
git add .
93
+
```
94
+
95
+
to stage all the changes.
96
+
97
+
2.```bash
98
+
git commit -m "Your commit message"
99
+
```
100
+
101
+
to commit the changes with ann appropriate commit message.
102
+
103
+
3. Once you have committed all the changes, push the changes to your forked repository by running:
104
+
105
+
```bash
106
+
git push origin main
107
+
```
108
+
109
+
Now you can use the Github UI to create a PR from your forked repository to the `staging` branch of the upstream repository.
131
110
132
111
## License
133
112
134
-
The Avail Project Developer Documentation is licensed under the [MIT License](./LICENSE) free software license.### How to Contribute Changes via the Avail Documentation Website
113
+
The Avail Project Developer Documentation is licensed under the [MIT License](./LICENSE) free software license.### How to Contribute Changes via the Avail Documentation Website.
@@ -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).
0 commit comments