Merge pull request #11 from Gonbatfire/main
Revamped Stake and Use section
This commit is contained in:
Ravaga
GitHub
commit
367f079d0d
38 changed files with 378 additions and 376 deletions
69
docs/build/deeplinks.md
vendored
Normal file
69
docs/build/deeplinks.md
vendored
Normal file
|
|
@ -0,0 +1,69 @@
|
|||
---
|
||||
slug: /use/deeplinks
|
||||
---
|
||||
|
||||
# Deeplinks
|
||||
|
||||
Based on materials of Matthew Reichardt [me@matthewreichardt.com](mailto\:me@matthewreichardt.com) ([https://github.com/hyle-team/zano/issues/269](https://github.com/hyle-team/zano/issues/269))
|
||||
|
||||
### Zano URI Scheme
|
||||
|
||||
**action** - type of action requested, supported actions:
|
||||
|
||||
- send - simply send coins to given address
|
||||
- escrow - create escrow-contract
|
||||
- marketplace\_offer\_create - create marketplace offer
|
||||
|
||||
### Action "send"
|
||||
|
||||
Example of **send** command:
|
||||
|
||||
**zano\:action
|
||||
\=send\&address=ZxCkvE7zhS6JuFE5neAaTtcY8PUT2CwfLZJQWP32jrELB1Vg9oSJyGJDyRWurqX6SXSqxjGz2yrAKaMqmxDa7E8313igosBVT\&comment='Some payment'\&mixins=11\&hide\_sender=true\&hide\_receiver=true**
|
||||
|
||||
- address - address of recipient
|
||||
- comment - comment about payment\[optional]
|
||||
- mixins - number of mixins\[optional]
|
||||
- hide\_sender - specify if sender address should be included in transaction(and visible for receiver)
|
||||
- hide\_receiver - specify if receiver address should be included in transaction(and visible for sender later, if wallet been restored from seed phrase)
|
||||
|
||||
### Action "marketplace\_offer\_create"
|
||||
|
||||
Example of **marketplace\_offer\_create** command:
|
||||
|
||||
**zano\:action
|
||||
\=marketplace\_offer\_create\&mixins=11\&hide\_sender=true\&hide\_receiver=true\&title='Random t-shirt'\&description='One size fits all'\&category='merch-tshirt'\&price=10\&img-url=''\&contact='@ravaga'\&comments='zzzz'**
|
||||
|
||||
**Basic params:**
|
||||
|
||||
- mixins - number of mixins\[optional]
|
||||
- hide\_sender - specify if sender address should be included in transaction(and visible for receiver)
|
||||
- hide\_receiver - specify if receiver address should be included in transaction(and visible for sender later, if wallet been restored from seed phrase)
|
||||
|
||||
**Offer details:**
|
||||
|
||||
- title – offer title
|
||||
- description – detailed offer description
|
||||
- category – store defined category
|
||||
- price – price in ZANO
|
||||
- img-url – ipfs/arweave link to offer image
|
||||
- contact – preferred way of communication (telegram, email, zano alias)
|
||||
- comments -additional comments about the offer
|
||||
|
||||
### Action "escrow"
|
||||
|
||||
Example of **escrow** command:
|
||||
|
||||
**zano\:action
|
||||
\=escrow\&description='Some Description'\&seller\_address='ZxCXALhZRodKmqRCWUPNAUCXqprJBNKv4eFsjzcMooAGVM6J2U2vSyTNpxNybwBnvzGWLtSWpBiddSZhph8HNfBn1bVE3c6ix'\&amount='10'\&my\_deposit='5'\&seller\_deposit='5'\&comment='Some comment if needed'**
|
||||
|
||||
**Escrow parameters:**
|
||||
|
||||
- description – Escrow description
|
||||
- seller\_address – Address of the wallet that have to accept/reject this offer
|
||||
- amount – Total amount of the deal (not include security deposits)
|
||||
- my\_deposit – amount of coins that buyer put as a deposit
|
||||
- seller\_deposit – amount of coins that seller supposed to put as a deposit if he accept escrow
|
||||
- comment – any comments regarding this deal
|
||||
|
||||
All mentioned information will be encrypted and won't be available for third party.
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Estimating Rewards
|
||||
|
||||
Proof-of-stake earnings depend on current PoS difficulty and the number of coins you have locked for staking. The more coins you stake, the better chance you have to “win” the right to sign the next PoS block. Of course, it’s important to estimate your chances and predict how much you can earn in some way. Here is the most straightforward way to do so.
|
||||
|
||||
First, we need to get the current PoS difficulty, which can be found in the [block explorer](https://explorer.zano.org/). This value is then divided by $1000000000000 = 10^{12}$, which in the Zano network is one coin basis.
|
||||
|
||||
Second, we again divide it by 288. This operation lets us take the PoS mining timestamp frame into account. Without further details, this factor provides hash variety in PoS mining and can be somewhere between 256 and 320. It’s reasonable to use the value of 288 here.
|
||||
|
||||
Now we have an estimation of how many coins participate in PoS mining currently as:
|
||||
|
||||
$$
|
||||
C = D_{PoS} \thinspace / \thinspace 288 \thinspace / \thinspace 10^{12} = D_{PoS} \cdot 2.88 \cdot 10^{-14}
|
||||
$$
|
||||
|
||||
where $C$ is the total amount of coins participating in PoS mining, and $D_{PoS} \thinspace$ is the current PoS difficulty.
|
||||
|
||||
As you may know, the Zano network emits an average of 1 coin each minute with a 50-50 spread between PoS and PoW. That makes it 720 potential PoS reward coins per day. So if you owned all the coins in PoS, that could be your total day earnings. And if you divide $C$ by 720, you will get the number of coins you need to mine 1 Zano coin a day. Now, you can estimate the number of coins you will earn as:
|
||||
|
||||
$$
|
||||
E_{daily} = \frac{720 \cdot N}{C} \approx \frac{2.07 \cdot 10^{17} \cdot N}{D_{PoS}}
|
||||
$$
|
||||
|
||||
where $\thinspace E_{daily} \thinspace$ is the estimated number of coins you'll earn per day, and $N$ is the number of coins you're staking.
|
||||
|
||||
Please keep in mind that all the above is an expectation and can vary heavily.
|
||||
|
|
@ -2,12 +2,91 @@
|
|||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Proof of Stake Mining
|
||||
# Staking Zano
|
||||
|
||||
Proof of stake mining or staking is typically implemented in such way that a random coin owner obtains the right to sign a new block. Zano PoS implementation keeps miners in full anonymity and is as simple as a push of a button, literally.
|
||||
Proof-of-stake mining or staking is typically implemented in such a way that a random coin owner obtains the right to sign a new block. Zano PoS implementation keeps miners in full anonymity and is as simple as a push of a button.
|
||||
|
||||
Open Zano app, make sure the blockchain is synchronised and turn on `Staking` switch.
|
||||
## Benefits of Zano Staking
|
||||
|
||||
<figcaption style={{textAlign: "center" }} >Proof-of-stake mining</figcaption>
|
||||
- 100% Anonymous: Your staked balance always remains hidden thanks to our [Zarcanum Technology.](https://docs.zano.org/docs/learn/zano-features/overview#zarcanum-anonymous-proof-of-stake)
|
||||
|
||||
You can observe your progress in the `Staking` tab of your staking wallet. The amount of earnings depends on the wallet balance. Note that funds, that participate in proof-of-stake will be locked. When you turn `Staking` off, balance will get unlocked right away. You can switch `Staking` on and off without any limitations.
|
||||
- No lock-ups: Unstake your coins at any chosen time.
|
||||
|
||||
- No minimum amounts: Stake any amount of ZANO you want.
|
||||
|
||||
- Truly decentralized: Anyone can start staking. There are **no** validators or special nodes.
|
||||
|
||||
- No slashing.
|
||||
|
||||
- Easy-to-use: Flip the switch and start staking.
|
||||
|
||||
The only requirement is to run a Zano node (currently, this can only be done on a desktop device). The Zano desktop wallet automatically functions as a Zano node.
|
||||
|
||||
There is no "delegation" function in Zano Staking, as we believe that it goes against network decentralization, and running a Zano node takes very few resources.
|
||||
|
||||
## How to Stake Zano
|
||||
|
||||
Simply open the Zano desktop wallet, make sure the blockchain is synchronised, and turn on the `Staking` switch.
|
||||
|
||||
```mdx-code-block
|
||||
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0 }}>
|
||||
<iframe
|
||||
src="https://www.youtube.com/embed/VruRhPSasPU"
|
||||
title="YouTube video player"
|
||||
style={{
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
}}
|
||||
frameBorder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowFullScreen
|
||||
/>
|
||||
</div>
|
||||
```
|
||||
|
||||
:::tip
|
||||
|
||||
You can observe your progress in the `Staking` tab of your staking wallet. The amount of earnings depends on the wallet balance. You can switch `Staking` on and off without any limitations.
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
## Estimating PoS Rewards
|
||||
|
||||
Proof-of-stake earnings depend on the current PoS difficulty and the number of coins being staked. The more coins you stake, the better chance you have to “win” the right to sign the next PoS block. Of course, it’s important to estimate your chances and predict how much you can earn in some way. **The most straightforward way to do so is to use the community-made [Staking Simulator](https://zanostats.com/staking).**
|
||||
|
||||
:::note
|
||||
|
||||
Please keep in mind that this is just an estimation and can vary heavily. Similarly to PoW, you only get a reward if your stake wins a block, and since block creation is probabilistic, your rewards are too.
|
||||
|
||||
:::
|
||||
|
||||
You can calculate your estimation manually using the following approach:
|
||||
|
||||
First, we need to get the current PoS difficulty, which can be found in the [block explorer](https://explorer.zano.org/). This value is then divided by `1000000000000=10¹²`, which in the Zano network is one coin basis.
|
||||
|
||||
Second, we again divide it by 288. This operation lets us take the PoS mining timestamp frame into account. Without further details, this factor provides hash variety in PoS mining and can be somewhere between 256 and 320. It’s reasonable to use the value of 288 here.
|
||||
|
||||
Now we have an estimation of how many coins participate in PoS mining currently as:
|
||||
|
||||
```mdx-code-block
|
||||
$$
|
||||
C = D_{PoS} \thinspace / \thinspace 288 \thinspace / \thinspace 10^{12} = D_{PoS} \cdot 2.88 \cdot 10^{-14}
|
||||
$$
|
||||
|
||||
Where $C$ is the total amount of coins participating in PoS mining, and $D_{PoS} \thinspace$ is the current PoS difficulty.
|
||||
```
|
||||
|
||||
As you may know, the Zano network emits an average of 1 coin each minute with a 50-50 spread between PoS and PoW. That makes it 720 potential PoS reward coins per day. So if you owned all the coins in PoS, that could be your total daily earnings. And if you divide C*C* by 720, you will get the number of coins you need to mine 1 Zano coin a day. Now, you can estimate the number of coins you will earn as:
|
||||
|
||||
```mdx-code-block
|
||||
$$
|
||||
E_{daily} = \frac{720 \cdot N}{C} \approx \frac{2.07 \cdot 10^{17} \cdot N}{D_{PoS}}
|
||||
$$
|
||||
|
||||
Where $\thinspace E_{daily} \thinspace$ is the estimated number of coins you'll earn per day, and $N$ is the number of coins you're staking.
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,34 +1,42 @@
|
|||
---
|
||||
sidebar_position: 2
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Server/Console mode POS mining
|
||||
# Server/Console mode Staking
|
||||
|
||||
In certain situations, performing Staking/PoS mining without the GUI application may be necessary. The following steps provide guidance on how to accomplish this:
|
||||
|
||||
In certain situations, performing PoS mining without the GUI application may be necessary. The following steps provide guidance on how to accomplish this:
|
||||
1. Download [Zano daemon (zanod executable)](https://zano.org/downloads) and simplewallet or build them following the [instructions](https://docs.zano.org/docs/build/building-from-sources).
|
||||
2. Ensure that no other instance of Zano is running at the moment; close it if necessary.
|
||||
3. Navigate to the Zano folder.
|
||||
4. For the next steps, you will need to launch two processes (node and wallet) and keep them running. The method differs based on your operating system. For desktop OS such as MacOS, Windows, or Ubuntu Desktop, launch a terminal window instance for both the node and wallet, and leave it running. In this case, **you can skip this step and proceed with the subsequent steps.** If you're connecting to a remote server or using a Unix-like system or MacOS, consider using virtual session managers like the screen command. Here's an example of creating a new virtual console with it:
|
||||
|
||||
```
|
||||
screen -S session_name
|
||||
```
|
||||
Learn more about using **screen** [here](https://www.gnu.org/software/screen/manual/screen.html).
|
||||
6. Next, start the node daemon **zanod** with the following console command:
|
||||
|
||||
Learn more about using **screen** [here](https://www.gnu.org/software/screen/manual/screen.html).\
|
||||
6\. Next, start the node daemon **zanod** with the following console command:
|
||||
|
||||
```
|
||||
zano_install_path\zanod
|
||||
```
|
||||
|
||||
NOTE: For MacOS bundle binary (both zanod and simplewallet) located in /Applications/**Zano.app/Contents/MacOS/** folder, ensure you use the correct path to launch the binary.
|
||||
|
||||
It's better to wait until the daemon is synchronized. You'll know this has happened when you see the following string in the console output:
|
||||
:
|
||||
It's better to wait until the daemon is synchronized. You'll know this has happened when you see the following string in the console output: :
|
||||
|
||||
```
|
||||
Synchronized set to TRUE
|
||||
```
|
||||
8. Start simplewallet with PoS mining enabled:
|
||||
|
||||
1. Start simplewallet with PoS mining enabled:
|
||||
|
||||
```
|
||||
./simplewallet --wallet-file=PATH_TO_WALLET_FILE --rpc-bind-port=RPC_PORT_NUMBER --do-pos-mining --deaf
|
||||
```
|
||||
NOTE: RPC_PORT_NUMBER should be any port number not in use by your system. It will be used by the RPC server. The --deaf option puts the server in a mode where no other programs can perform any RPC requests to the wallet service, which is recommended for security concerns.
|
||||
|
||||
NOTE: RPC\_PORT\_NUMBER should be any port number not in use by your system. It will be used by the RPC server. The --deaf option puts the server in a mode where no other programs can perform any RPC requests to the wallet service, which is recommended for security concerns.
|
||||
|
||||
Some of the parameters are required, and some are optional. Here's what they mean:
|
||||
|
||||
|
|
@ -38,7 +46,7 @@ Some of the parameters are required, and some are optional. Here's what they mea
|
|||
- `--log-level=LOG_LEVEL` (optional) — sets the log level, possible values are from 0 (less verbose) to 4 (extremely verbose). May be useful for debugging. Default is 0;
|
||||
- `--log-file=PATH_TO_LOG` (optional) — sets path to the log file. Default is 'simplewallet.log' in the same folder where simplewallet binary is located;
|
||||
- `--deaf` (optional) — turns on so called 'deaf mode'. simplewallet's RPC server will reject any requests with error 500. This is useful if you just want to mine PoS and don't want that anyone would be able to do RPCs on your wallet. **Highly recommend**. Default: off;
|
||||
- `--pos-mining-reward-address=REWARD_ADDR` (optional) — sets an explicit address for receiving mining rewards. By default, all rewards will be received by the same wallet where staking coins are, so its balance will be gradually increasing. If you use this option, staking coins will be kept in the main wallet (specified by--wallet-file parameter), and mining rewards will be sent to the specified REWARD_ADDR. In such a case, the balance of the main wallet won't be changing due to the mining process.
|
||||
- `--pos-mining-reward-address=REWARD_ADDR` (optional) — sets an explicit address for receiving mining rewards. By default, all rewards will be received by the same wallet where staking coins are, so its balance will be gradually increasing. If you use this option, staking coins will be kept in the main wallet (specified by--wallet-file parameter), and mining rewards will be sent to the specified REWARD\_ADDR. In such a case, the balance of the main wallet won't be changing due to the mining process.
|
||||
|
||||
Here's a real-world example of the command using recommended options (**don't forget to tailor it to your needs**):
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Guide: Stake Zano automatically on system startup
|
||||
|
||||
## Introduction
|
||||
|
|
|
|||
|
|
@ -1,35 +0,0 @@
|
|||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Aliases
|
||||
|
||||
Each Zano user can register with an alias, for example: @easytouse, a human-readable name associated with a payment address and text comment, which is stored in the blockchain. This alias provides a short, easy-to-remember name rather than a long and confusing string of random characters. Blockchain storage ensures that aliases are protected from being altered or commandeered.
|
||||
|
||||
Each alias is assigned to a particular wallet. Only one alias can be created per wallet. To register an alias choose `Register an alias` from wallet main window.
|
||||
|
||||
To reduce possibility of phishing we set limitations on alias registrations. Users can use any combination of the lower-case Latin letters a-z and the Arabic numerals 0-9. Additionally, there is a length minimum of 6 characters, and a maximum length of 12.
|
||||
|
||||
The comment section will be temporarily stored in the blockchain until passing a checkpoint. For more information on pruning mechanism please refer to the [whitepaper](https://docs.zano.org/docs/whitepaper).\
|
||||
|
||||
|
||||
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0 }}>
|
||||
<iframe
|
||||
src="https://www.youtube.com/embed/ImbcSEc6cTU"
|
||||
title="YouTube video player"
|
||||
style={{
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
}}
|
||||
frameBorder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowFullScreen
|
||||
/>
|
||||
</div>
|
||||
|
||||
*<figcaption style={{textAlign: "center" }}>Alias registration</figcaption>*
|
||||
|
||||
Aliases can be used for more than just Zano transactions. Think of them as a decentralised address book with universal IDs that can be used for various services based on the Zano platform.
|
||||
|
|
@ -1,66 +0,0 @@
|
|||
---
|
||||
sidebar_position: 6
|
||||
---
|
||||
|
||||
# Deeplinks
|
||||
|
||||
Based on materials of Matthew Reichardt me@matthewreichardt.com (https://github.com/hyle-team/zano/issues/269)
|
||||
|
||||
### Zano URI Scheme
|
||||
|
||||
**action** - type of action requested, supported actions:
|
||||
|
||||
- send - simply send coins to given address
|
||||
- escrow - create escrow-contract
|
||||
- marketplace_offer_create - create marketplace offer
|
||||
|
||||
### Action "send"
|
||||
|
||||
Example of **send** command:
|
||||
|
||||
**zano:action=send&address=ZxCkvE7zhS6JuFE5neAaTtcY8PUT2CwfLZJQWP32jrELB1Vg9oSJyGJDyRWurqX6SXSqxjGz2yrAKaMqmxDa7E8313igosBVT&comment='Some payment'&mixins=11&hide_sender=true&hide_receiver=true**
|
||||
|
||||
- address - address of recipient
|
||||
- comment - comment about payment[optional]
|
||||
- mixins - number of mixins[optional]
|
||||
- hide_sender - specify if sender address should be included in transaction(and visible for receiver)
|
||||
- hide_receiver - specify if receiver address should be included in transaction(and visible for sender later, if wallet been restored from seed phrase)
|
||||
|
||||
### Action "marketplace_offer_create"
|
||||
|
||||
Example of **marketplace_offer_create** command:
|
||||
|
||||
**zano:action=marketplace_offer_create&mixins=11&hide_sender=true&hide_receiver=true&title='Random t-shirt'&description='One size fits all'&category='merch-tshirt'&price=10&img-url=''&contact='@ravaga'&comments='zzzz'**
|
||||
|
||||
**Basic params:**
|
||||
|
||||
- mixins - number of mixins[optional]
|
||||
- hide_sender - specify if sender address should be included in transaction(and visible for receiver)
|
||||
- hide_receiver - specify if receiver address should be included in transaction(and visible for sender later, if wallet been restored from seed phrase)
|
||||
|
||||
**Offer details:**
|
||||
|
||||
- title – offer title
|
||||
- description – detailed offer description
|
||||
- category – store defined category
|
||||
- price – price in ZANO
|
||||
- img-url – ipfs/arweave link to offer image
|
||||
- contact – preferred way of communication (telegram, email, zano alias)
|
||||
- comments -additional comments about the offer
|
||||
|
||||
### Action "escrow"
|
||||
|
||||
Example of **escrow** command:
|
||||
|
||||
**zano:action=escrow&description='Some Description'&seller_address='ZxCXALhZRodKmqRCWUPNAUCXqprJBNKv4eFsjzcMooAGVM6J2U2vSyTNpxNybwBnvzGWLtSWpBiddSZhph8HNfBn1bVE3c6ix'&amount='10'&my_deposit='5'&seller_deposit='5'&comment='Some comment if needed'**
|
||||
|
||||
**Escrow parameters:**
|
||||
|
||||
- description – Escrow description
|
||||
- seller_address – Address of the wallet that have to accept/reject this offer
|
||||
- amount – Total amount of the deal (not include security deposits)
|
||||
- my_deposit – amount of coins that buyer put as a deposit
|
||||
- seller_deposit – amount of coins that seller supposed to put as a deposit if he accept escrow
|
||||
- comment – any comments regarding this deal
|
||||
|
||||
All mentioned information will be encrypted and won't be available for third party.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
{
|
||||
"label": "Boolberry/Legacy",
|
||||
"label": "Legacy",
|
||||
"position": 99
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
sidebar_position: 7
|
||||
slug: /use/escrow-contracts
|
||||
---
|
||||
|
||||
# Escrow contracts
|
||||
|
|
@ -20,13 +20,13 @@ Each escrow contract starts with the buyer proposal. Once it's sent the deposit
|
|||
- Time until response - proposal expiration time
|
||||
- Payment ID - transaction payment identifier provided by seller
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Contract proposal</figcaption>_
|
||||
_<figcaption style={{textAlign: "center" }} >Contract proposal</figcaption>_
|
||||
|
||||
### Confirmation
|
||||
|
||||
When the seller accepts the proposal a special multi signature transaction will be sent to the blockchain. Then after 10 confirmations a new contract will be started. The seller can now fulfil contract terms like shipping the item to the buyer.
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Contract response</figcaption>_
|
||||
_<figcaption style={{textAlign: "center" }} >Contract response</figcaption>_
|
||||
|
||||
The buyers contract window will get three options to continue with: `Cancel and return deposits`, `Terminate and burn deposits` and `Complete and release deposits`.
|
||||
|
||||
|
|
@ -42,4 +42,4 @@ When parties cannot find mutual agreement on any occasions one can decide to bur
|
|||
|
||||
If buyer is satisfied with the delivery or a provided service the contract can be closed. Releasing deposits will return both parties collaterals.
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Contract confirmation</figcaption>_
|
||||
_<figcaption style={{textAlign: "center" }} >Contract confirmation</figcaption>_
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
sidebar_position: 11
|
||||
slug: /use/zarcanum-migration
|
||||
---
|
||||
|
||||
# Zarcanum Migration
|
||||
|
|
@ -12,8 +12,7 @@ Auto Migration is an automated process within the Zano wallet that takes pre-Zar
|
|||
|
||||
**Collection**: The wallet automatically gathers all old outputs in your Zano wallet that were created before the Zarcanum hardfork.
|
||||
|
||||
**Consolidation**: These outputs are then consolidated into a few transactions. This step is crucial because it reduces the complexity and size of your wallet, making it more
|
||||
efficient.
|
||||
**Consolidation**: These outputs are then consolidated into a few transactions. This step is crucial because it reduces the complexity and size of your wallet, making it more efficient.
|
||||
|
||||
**Recreation**: The consolidated funds are sent to your own wallet address. This step recreates the outputs in the post-Zarcanum format, making your funds compatible with the new network rules.
|
||||
|
||||
|
|
@ -25,7 +24,7 @@ Using the Auto Migration feature is simple, thanks to the new wallet interface.
|
|||
|
||||
**Look for the Migration Button**: When you open your updated Zano wallet, look for the 'Migrate wallet to Zarcanum' button, typically located at the top of the screen.
|
||||
|
||||
<figcaption style={{textAlign: "center" }} >Migration button</figcaption>
|
||||
<figcaption style={{textAlign: "center" }}>Migration button</figcaption>
|
||||
|
||||
**Initiate Migration**: If your wallet detects pre-Zarcanum outputs, a popup will appear informing you of the number of outputs and the total ZANO amount they represent. For example, "There are 112 outputs with a total amount of 24 ZANO".
|
||||
|
||||
|
|
@ -35,7 +34,7 @@ Using the Auto Migration feature is simple, thanks to the new wallet interface.
|
|||
|
||||
**Confirm Migration**: By clicking the 'Migrate' button, the wallet will consolidate your outputs and recreate them in the post-Zarcanum format.
|
||||
|
||||
<figcaption style={{textAlign: "center" }} >Migration popup</figcaption>
|
||||
<figcaption style={{textAlign: "center" }}>Migration popup</figcaption>
|
||||
|
||||
**Complete the Process**: The migration transaction will be sent. It require 10 blocks time to get confirmed, just like any other transaction.
|
||||
|
||||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
sidebar_position: 10
|
||||
sidebar_position: 98
|
||||
---
|
||||
|
||||
# Reporting issues
|
||||
|
|
|
|||
|
|
@ -1,94 +0,0 @@
|
|||
---
|
||||
sidebar_position: 9
|
||||
---
|
||||
|
||||
# Tip Bot Guide
|
||||
|
||||
A simple guide on how to get tipping Zano on Discord
|
||||
|
||||
Using Zano’s Discord TipBot is fairly straightforward and intuitive, but here we’ll give an overview of its usage to help you get started, quickly.
|
||||
|
||||
#### Get Discord
|
||||
|
||||
In order to use the Discord TipBot, we must first have Discord installed, head over to their website (or your package manager) and get signed up!<br/>
|
||||
https://discord.com/download/
|
||||
|
||||
#### Join Zano’s Discord Channel
|
||||
|
||||
Now that we have Discord, head over to our discord
|
||||
channel and join the rest of the community! Simply click
|
||||
the link below.<br/>
|
||||
https://discord.gg/wE3rmYY
|
||||
|
||||
### The Tip Bot
|
||||
|
||||
Welcome to Zano Discord, now that you’re here, you should have something that looks like the below image:
|
||||
|
||||
#### Head to TipBot Settings
|
||||
|
||||
Head to the ‘Bounties’ category and select the ‘tip-bot-settings’ channel, here lies a summary of the tip bots usage.
|
||||
|
||||
|
||||
|
||||
### Get tipping!
|
||||
|
||||
Let's take a look at the tip bots functionality, the below image shows what we can do with the bot.
|
||||
|
||||
|
||||
|
||||
#### Deposit
|
||||
|
||||
Before we can begin tipping, we must have some Zano in our tip bot wallet, to do this click on ‘Deposit’, get your wallet address and send some Zano to it.
|
||||
|
||||
|
||||
|
||||
#### Register alias
|
||||
|
||||
Before you can withdraw Zano others have tipped you, you must register an alias, more on aliases can be found here: https://docs.zano.org/docs/aliases
|
||||
|
||||
Click ‘register alias’ and enter your alias.
|
||||
|
||||
|
||||
|
||||
#### How to tip
|
||||
|
||||
Tipping users is done with one simple command, to see this command, click ‘how to tip’
|
||||
|
||||
|
||||
|
||||
:::tip Tip command
|
||||
|
||||
$tip
|
||||
|
||||
:::
|
||||
|
||||
Simply replace and with the values you want to use, a real world example within discord looks something like this
|
||||
|
||||
|
||||
|
||||
#### Balance
|
||||
|
||||
To view how much Zano you have, simply click balance, and the tip bot will show how much Zano is in your wallet.
|
||||
|
||||
|
||||
|
||||
#### History & simple view
|
||||
|
||||
There are 2 history buttons, one designated History, and the other History (simple view).
|
||||
|
||||
|
||||
|
||||
History is formatted as a table, whereas History (simple) is a simple one-liner.
|
||||
|
||||
#### Rate
|
||||
|
||||
If you want to know the current price of Zano, click ‘Rate’, to see the current price in $USD.
|
||||
|
||||
|
||||
|
||||
#### Redeem coupon
|
||||
|
||||
If you have a coupon code, the ‘Redeem Coupon’ button allows you to exchange your coupon for Zano coins.
|
||||
Simply click the button and enter your coupon code.
|
||||
|
||||
|
||||
4
docs/use/wallet-features/_category_.json
Normal file
4
docs/use/wallet-features/_category_.json
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
"label": "Wallet Features",
|
||||
"position": 3
|
||||
}
|
||||
47
docs/use/wallet-features/aliases.md
Normal file
47
docs/use/wallet-features/aliases.md
Normal file
|
|
@ -0,0 +1,47 @@
|
|||
---
|
||||
sidebar_position: 3
|
||||
slug: /use/aliases
|
||||
---
|
||||
|
||||
# Aliases
|
||||
|
||||
Each Zano user can register with an alias, for example, @easytouse, a human-readable name associated with a payment address and text comment stored in the blockchain. This alias provides a short, easy-to-remember name rather than a long, confusing string of random characters. Blockchain storage ensures that aliases are protected from being altered.
|
||||
|
||||
Each alias is assigned to a particular wallet. Only one alias can be created per wallet. To register an alias, select `Register an alias` from the wallet main window.
|
||||
|
||||
To reduce the possibility of phishing, we set limitations on alias registrations. Users can use any combination of the lower-case Latin letters a-z and the Arabic numerals 0-9. Additionally, the length must be a minimum of 6 characters and a maximum of 12.
|
||||
|
||||
:::note
|
||||
|
||||
Aliases shorter than 6 characters can only be issued by the Zano Core Team. Users can win one by participating in our monthly community events.
|
||||
|
||||
:::
|
||||
|
||||
The comment section will be temporarily stored in the blockchain until it passes a checkpoint. For more information on the pruning mechanism please refer to the [whitepaper](https://docs.zano.org/docs/whitepaper).
|
||||
|
||||
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0 }}>
|
||||
<iframe
|
||||
src="https://www.youtube.com/embed/ImbcSEc6cTU"
|
||||
title="YouTube video player"
|
||||
style={{
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
}}
|
||||
frameBorder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowFullScreen
|
||||
/>
|
||||
</div>
|
||||
|
||||
*<figcaption style={{textAlign: "center" }}>Alias registration</figcaption>*
|
||||
|
||||
Aliases can be used for more than just Zano transactions. Think of them as a decentralised address book with universal IDs that can be used for various services based on the Zano platform.
|
||||
|
||||
:::note
|
||||
|
||||
You will be able to trade your aliases on a upcoming Alias Auction Platform.
|
||||
|
||||
:::
|
||||
|
|
@ -1,14 +1,15 @@
|
|||
---
|
||||
sidebar_position: 5
|
||||
slug: /use/auditable-wallets.md
|
||||
---
|
||||
|
||||
# Auditable wallets FAQ
|
||||
# Auditable Wallets
|
||||
|
||||
### What is an auditable wallet?
|
||||
|
||||
Auditable is the type of wallet that allows 3rd party to see the balance and transaction history without permission to spend it or interact in any other way.
|
||||
|
||||
### How can I tell if wallet is auditable
|
||||
### How can I tell if a wallet is auditable
|
||||
|
||||
It's a wallet with an address in a special format that starts with "aZx", for instance: aZxawNXAuekCXcnzutthLaPZQxAyaofb59FpzNBSCQb7iT7D1nsaxdTCvK4Xhn6nfuRpqDiNjeUNx2J9KWfTXHmDWNQ85v2bpbi
|
||||
|
||||
|
|
@ -58,8 +59,7 @@ aZxb9v1DFtaK6Z4bW7UUuaZcmq7MZBzz875eZ5N3vSRa2vWz9wBVE3vVKFGNH8414TTjhiwPz7PTV5tt
|
|||
Anyone having this tracking seed is able to watch your balance and transaction history, but unable to spend coins.
|
||||
```
|
||||
|
||||
Tracking seed technically is an auditable address, secret view key and a creation timestamp combined with a colon:
|
||||
aZxawNXAuekCXcnzutthLaPZQxAyaofb59FpzNBSCQb7iT7D1nsaxdTCvK4Xhn6nfuRpqDiNjeUNx2J9KWfTXHmDWNQ85v2bpbi:1be5866b6fda704c0c4a08f9c79c774911fda72dcd8cc8c7ca31bc1a6fda4d0b:1593998615
|
||||
Tracking seed technically is an auditable address, secret view key and a creation timestamp combined with a colon: aZxawNXAuekCXcnzutthLaPZQxAyaofb59FpzNBSCQb7iT7D1nsaxdTCvK4Xhn6nfuRpqDiNjeUNx2J9KWfTXHmDWNQ85v2bpbi:1be5866b6fda704c0c4a08f9c79c774911fda72dcd8cc8c7ca31bc1a6fda4d0b:1593998615
|
||||
|
||||
### I got a tracking seed. How can I track the wallet it is bound to?
|
||||
|
||||
|
|
@ -83,23 +83,16 @@ your wallet again. Your wallet keys is NOT under risk anyway.
|
|||
|
||||
Or in GUI wallet:
|
||||
|
||||
|
||||
|
||||
|
||||
### Are there any restrictions of using auditable wallets?
|
||||
### Are there any restrictions on using auditable wallets?
|
||||
|
||||
Only one: you cannot use mixins when you send coins from an auditable wallet.
|
||||
|
||||
**_Obsolete_**<br/>
|
||||
The following limitations were effective until hardfork 2:
|
||||
|
||||
1. An alias cannot be assigned to an auditable address.
|
||||
2. When sending coins from an auditable address the sender address is always hidden.
|
||||
3. When sending coins to an auditable address the receiver address is always hidden. Once the blockchain passed hardfork 2 these limitations were removed.
|
||||
|
||||
### Can I use integrated addresses with the auditable feature?
|
||||
|
||||
Yes. An integrated address for an auditable wallet can be generated as usual. Such addresses will have "aiZ" prefix.
|
||||
|
||||
### Can I mine PoS with my auditable wallet?
|
||||
|
||||
Yes, you can. Also, you can use a corresponding watch-only wallet to monitor your balance without the risk of leaking your spend key. The only tradeoff is you can not use mixins but only directly spend coins from your auditable wallet.
|
||||
Yes, you can. Also, you can use a corresponding watch-only wallet to monitor your balance without the risk of leaking your spend key.
|
||||
1
docs/use/wallet-features/control-assets.md
Normal file
1
docs/use/wallet-features/control-assets.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
# Control Assets
|
||||
1
docs/use/wallet-features/ionic-swaps.md
Normal file
1
docs/use/wallet-features/ionic-swaps.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
# Ionic Swaps
|
||||
4
docs/use/wallets/cli/_category_.json
Normal file
4
docs/use/wallets/cli/_category_.json
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
"label": "Command Line Wallet (CLI)",
|
||||
"position": 6
|
||||
}
|
||||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
sidebar_position: 4
|
||||
slug: /use/wallets/install-zano-cli-wallet-ubuntu
|
||||
---
|
||||
|
||||
# Install a Zano CLI Wallet (Ubuntu)
|
||||
|
|
@ -12,19 +13,19 @@ Go to the official site: https://zano.org and navigate to the downloads section
|
|||
|
||||
Download Linux (Ubuntu 16.04+) CLI Wallet
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 3**
|
||||
|
||||
Right click the file and select Properties
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 4**
|
||||
|
||||
Copy the file name
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 5**
|
||||
|
||||
|
|
@ -36,8 +37,8 @@ sha256sum zano-linux-x64-v<XXX>.tar.bz2
|
|||
|
||||
(Results should match release notes from Download page)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 6**
|
||||
|
||||
|
|
@ -47,7 +48,7 @@ If checksums match, decompress & extract the .tar.bz2 file:
|
|||
tar -xvjf zano-linux-x64-release-devtools-v1.5.0.143[336fac2].tar.bz2
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
**Steps 7-9**
|
||||
|
||||
|
|
@ -59,14 +60,14 @@ tar -xvjf zano-linux-x64-release-devtools-v1.5.0.143[336fac2].tar.bz2
|
|||
./zanod
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 11**
|
||||
|
||||
Wait for the blockchain to download and sync. This may take quite a few hours, depending on your download speed. And leave the daemon running! We’ll need that to create our new wallet.
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 12**
|
||||
|
||||
|
|
@ -82,13 +83,13 @@ Replace “name” with your new wallet’s name, e.g.,:
|
|||
./simplewallet --generate-new-wallet=zanocli.wallet
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 13**
|
||||
|
||||
When asked, enter a password for your wallet. You should use a password generator, found in password managers such as KeePass.
|
||||
|
||||
|
||||
|
||||
|
||||
**Steps 14-15**
|
||||
|
||||
|
|
@ -100,7 +101,7 @@ When asked, enter a password for your wallet. You should use a password generato
|
|||
|
||||
15. Enter your password, when prompted. Notice that the wallet displays your receive address after “Opened wallet.” You will use this to fund your new wallet.
|
||||
|
||||
|
||||
|
||||
|
||||
**Steps 16-17**
|
||||
|
||||
|
|
@ -112,6 +113,6 @@ show_seed
|
|||
|
||||
17. Again, when prompted provide a password for the seed phrase you’re about to get. Confirm the password, and be sure to save both it and your seed phrase!!
|
||||
|
||||
|
||||
|
||||
|
||||
**You've successfully installed your new Zano Wallet!**
|
||||
|
|
@ -1,5 +1,6 @@
|
|||
---
|
||||
sidebar_position: 5
|
||||
slug: /use/wallets/using-zano-cli-wallet-ubuntu
|
||||
---
|
||||
|
||||
# Using a Zano CLI Wallet (Ubuntu)
|
||||
|
|
@ -18,7 +19,7 @@ Open another terminal in the same directory (with simplewallet). Start your wall
|
|||
|
||||
Enter your password, when prompted. Notice that the wallet displays your receive address after “Opened wallet.” You will use this to fund your new wallet.
|
||||
|
||||
|
||||
|
||||
|
||||
P.S. Zanod (your node) can be left running, if you’ll be transferring funds to your wallet soon. If not, close your wallet by giving the command:
|
||||
|
||||
|
|
@ -45,7 +46,7 @@ The command for sending ZANO consists of four important bits of information:
|
|||
For example:<br/>
|
||||
(1) (2) (3) (4)
|
||||
|
||||
|
||||
|
||||
|
||||
### Creating an Auditable CLI Wallet
|
||||
|
||||
|
|
@ -63,7 +64,7 @@ Give the following command, substituting "name":
|
|||
|
||||
When prompted, enter your new password, preferably generated from a password generator.
|
||||
|
||||
|
||||
|
||||
|
||||
You now have an auditable CLI. Anyone to whom you provide the tracking seed will be able to see the wallet's balance and transaction history.
|
||||
|
||||
|
|
@ -73,7 +74,7 @@ If you ever need to retrieve the tracking seed, simply open the wallet and give
|
|||
tracking_seed
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
Now, we must get our seed phrase, in case we ever need to restore our auditable CLI wallet. Within the wallet, give the command:
|
||||
|
||||
|
|
@ -83,7 +84,7 @@ show_seed
|
|||
|
||||
Again, when prompted, supply and confirm another password, specific to the seed itself.
|
||||
|
||||
|
||||
|
||||
|
||||
Lastly, note that the address of an auditable wallet always begins with an initial "a", in contrast to a standard wallet, which always begins with "Zx":
|
||||
|
||||
|
|
@ -103,7 +104,7 @@ After starting zanod, open another terminal in the simple-wallet directory. Give
|
|||
|
||||
You will then be asked to reenter the seedphrase, enter the password specific to that seedphrase, and then enter your restored wallet's password.
|
||||
|
||||
|
||||
|
||||
|
||||
### Creating a Watch-Only CLI Wallet
|
||||
|
||||
|
|
@ -113,7 +114,7 @@ If you wish to allow someone to merely view your wallet, without being able to s
|
|||
save_watch_only new_name.wallet password_for_wallet
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
### Other Useful in-Terminal Flags
|
||||
|
||||
|
|
@ -2,34 +2,86 @@
|
|||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# GUI Wallet
|
||||
# Create and Manage Wallets (GUI)
|
||||
|
||||
Zano app is available for Windows, Linux and MacOS. It can be downloaded [here](https://zano.org/downloads).
|
||||
Zano Wallet lets you manage multiple ZANO wallets, which can be easily created, restored, and removed from the app. The core of each wallet is a seed phrase, a sequence of 24 words that can be used to recover your wallet's private and public keys. A unique sequence is generated every time you create a new wallet within the app. **It's important to always keep it safe and accessible.**
|
||||
|
||||
### Open Zano app
|
||||
For your convenience, it's not necessary to use a seed phrase to manage your wallet. In the official Zano Wallet apps, when you create a wallet, a wallet file is generated as well. This file is secured with an additional password, granting access to wallet features and the seed phrase. It can be copied to another device and used with another app.
|
||||
|
||||
|
||||
Zano is available for mobile (Android/iOS) and desktop (Windows, Linux and MacOS). It can be downloaded [here](https://zano.org/downloads).
|
||||
|
||||
First you need to create a master password. It will let you manage your Zano wallets inside the app. Note that each wallet account will have separate password as well. Hit `Next` when ready.
|
||||
## Desktop Wallet Guide
|
||||
|
||||
### Create new wallet
|
||||
```mdx-code-block
|
||||
<div style={{ position: 'relative', paddingBottom: '56.25%', height: 0 }}>
|
||||
<iframe
|
||||
src="https://www.youtube.com/embed/8UXgs-lgCYQ"
|
||||
title="YouTube video player"
|
||||
style={{
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
}}
|
||||
frameBorder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowFullScreen
|
||||
/>
|
||||
</div>
|
||||
```
|
||||
|
||||
|
||||
:::info
|
||||
|
||||
Once app is open it will start syncing with the blockchain. While in progress some features such as sending transactions and contracts will be locked. Meanwhile you can still create your first Zano wallet by clicking `Create new wallet` .
|
||||
Some antivirus programs do not recognize wallet software and automatically flag it as a virus, resulting in a false positive. In that case, you will need to add zano.exe to your exclusion list.
|
||||
|
||||
|
||||
:::
|
||||
|
||||
Enter wallet name and password, then click `Select wallet location`. Note that both can be changed later in wallet details menu.
|
||||
### Create a new wallet
|
||||
|
||||
|
||||
|
||||
|
||||
When wallet file is created you can continue with `Create wallet`. This file can be used to quickly import or restore closed wallets in Zano app.
|
||||
Once the app is open, it will start syncing with the blockchain. While in progress, some features such as sending transactions and contracts will be locked. Meanwhile, you can still create your first Zano wallet by clicking `Create new wallet`.
|
||||
|
||||
|
||||
|
||||
|
||||
To finalise wallet creation store wallet's seed phrase. IMPORTANT: using the seed phrase anyone can restore and take full control of the wallet. Keep it in a secured location and avoid unauthorized access to it by any means. Note that you can review the seed phrase later in wallet details menu.
|
||||
Enter wallet name and password, then click `Select wallet location`. Note that both can be changed later in the `Wallet options` menu.
|
||||
|
||||
|
||||
|
||||
|
||||
Now the wallet has been created. You can copy wallet address and use it to receive ZANO from exchanges, mining pools and other sources.
|
||||
When the wallet file is created, you can continue with `Create wallet`. This file can be used to quickly import or restore wallets in both official Zano Wallets (Desktop and Mobile).
|
||||
|
||||
|
||||
|
||||
To finalise wallet creation, generate and store the wallet's seed phrase.
|
||||
|
||||
You will be prompted to add an extra password to further secure the seed, known as a passphrase ([Learn more about what this means here](https://docs.zano.org/docs/use/seed-phrase)). If you choose to generate it without it, you can still later add it in the `Wallet options` menu.
|
||||
|
||||
:::danger
|
||||
|
||||
IMPORTANT: Using the seed phrase, anyone can restore and take full control of the wallet. Keep it in a secure location and avoid unauthorized access to it by any means. Note that you can review the seed phrase later in the `Wallet options` menu.
|
||||
|
||||
:::
|
||||
|
||||
|
||||
|
||||
The wallet has been created. You can copy your wallet address to receive ZANO or Confidential Assets from exchanges, mining pools, and other sources.
|
||||
|
||||
### Wallet options
|
||||
|
||||
Each Zano wallet can be identified by a custom name assigned upon creation. This name can be edited in `Wallet options` the section at any time. Information about the wallet file location and its seed phrase is available here. Note that you can copy the seed phrase by clicking the right mouse button over it and choosing `COPY` from the context menu.
|
||||
|
||||
You can remove a wallet from the Zano app by clicking `Close wallet` in the same section. Note that the wallet file will remain unaffected, and you can import it again anytime if necessary.
|
||||
|
||||
### Changing wallet password
|
||||
|
||||
In case you want to change the wallet file password, you need to use `Restore from backup`. The following steps will be required:
|
||||
|
||||
1. Make sure you have the seed phrase saved
|
||||
2. Click `Close wallet` from wallet `Details`
|
||||
3. Delete the wallet file
|
||||
4. Click `+Add` from `Wallets` menu and choose `Restore from backup`
|
||||
5. Enter new wallet info
|
||||
6. Recover and enter the previously stored seed phrase
|
||||
7. Click `Select wallet location` to choose the wallet file location and name
|
||||
8. Continue with `Create wallet`
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
sidebar_position: 8
|
||||
sidebar_position: 4
|
||||
slug: /use/locked-balance
|
||||
---
|
||||
|
||||
# Locked balance
|
||||
# Locked Balance
|
||||
|
||||
On occasion, you may notice that part of your wallet balance is temporarily locked. The reason behind it is complex, but let us offer a simplified explanation here. For more details, please refer to the [whitepaper](https://docs.zano.org/docs/whitepaper).
|
||||
|
||||
|
|
@ -1,59 +0,0 @@
|
|||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Managing wallets
|
||||
|
||||
Zano app lets you manage multiple ZANO wallets, which can be easily created, restored and removed from the app. The core of each wallet is a seed phrase. It's a sequence of 24 words, that can be used to recovery your wallet private and public keys. Every time you create a new wallet within the app, a unique sequence is generated. It's important to always keep it safe and accessible.
|
||||
|
||||
For your convenience it's not necessary to use a seed phrase to manage your wallet. When you create a wallet the wallet file is generated as well. The file is secured with additional password and grants access to wallet features and the seed phrase. It can be copied to another device and used with another app.
|
||||
|
||||
### Creating wallets
|
||||
|
||||
There are 3 ways to create a wallet in Zano app. From the `Wallets` `Add` section choose
|
||||
|
||||
- Create new wallet
|
||||
|
||||
1. Enter wallet name and password
|
||||
2. Click `Select wallet location` to choose wallet file location and name
|
||||
3. Continue with `Create wallet`
|
||||
4. Save shown seed phrase in a secure place and click `Create`
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Create new wallet</figcaption>_
|
||||
|
||||
- Open existing wallet
|
||||
|
||||
1. Locate wallet file
|
||||
2. Enter password then open wallet
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Open existing wallet</figcaption>_
|
||||
|
||||
- Restore from backup
|
||||
|
||||
1. Enter new wallet info
|
||||
2. Recover and enter previously stored seed phrase
|
||||
3. Click `Select wallet location` to choose wallet file location and name
|
||||
4. Continue with `Create wallet`
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Restore from backup</figcaption>_
|
||||
|
||||
### Wallet details
|
||||
|
||||
Each Zano wallet can be identified by a custom name assigned on creation. This name can be edited in `Details` section anytime. Information about wallet file location and it's seed phrase available here as well. Note that you can copy the seed phrase by clicking right mouse button over it and choosing `COPY` from the context menu.
|
||||
|
||||
You can remove a wallet from the Zano app by clicking `Close wallet` in the same section. Note that wallet file will remain unaffected and you can import it again anytime if necessary.
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Wallet details</figcaption>_
|
||||
|
||||
### Changing wallet password
|
||||
|
||||
In case you want to change wallet file password, you need to use `Restore from backup``. The following step will be required.
|
||||
|
||||
1. Make sure you have the seed phrase saved
|
||||
2. Click `Close wallet` from wallet `Details`
|
||||
3. Delete wallet file
|
||||
4. Click `+Add` from `Wallets` menu and choose `Restore from backup`
|
||||
5. Enter new wallet info
|
||||
6. Recover and enter previously stored seed phrase
|
||||
7. Click `Select wallet location` to choose wallet file location and name
|
||||
8. Continue with `Create wallet`
|
||||
|
|
@ -6,20 +6,24 @@ sidebar_position: 1
|
|||
|
||||
### Desktop Apps
|
||||
|
||||
Zano GUI Wallets available for Windows, Mac OS and Linux
|
||||
Zano GUI Wallet is available for Windows, Mac OS and Linux
|
||||
|
||||
### Mobile Apps
|
||||
|
||||
Zano supports App Store and Play Store apps, for Android we also provide APK
|
||||
Zano is available in both App Store and Play Store, for Android we also provide an APK.
|
||||
|
||||
### Browser extension
|
||||
### Browser Extension
|
||||
|
||||
Currently Zano Companion only available for Zarcanum Testnet and works with Testnet Build provided below
|
||||
You can use Zano Companion on Chrome (Connects to your desktop wallet)
|
||||
|
||||
### Download links
|
||||
### Download Links
|
||||
|
||||
Available on the [Zano Website](https://new.zano.org/downloads) and [Github](https://github.com/hyle-team/zano/releases)
|
||||
|
||||
### Testnet builds and resources
|
||||
### Third-Party Wallets
|
||||
|
||||
Zano has also been integrated into other multi-coin wallets [available here](https://zano.org/ecosystem/wallets)
|
||||
|
||||
### Testnet builds and Resources
|
||||
|
||||
For development purposes we provide a pre-built Testnet apps available [Testnet Resources](https://docs.zano.org/docs/build/testnet-resources/testnet-builds) section
|
||||
|
|
|
|||
4
docs/use/wallets/security/_category_.json
Normal file
4
docs/use/wallets/security/_category_.json
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
"label": "Security",
|
||||
"position": 5
|
||||
}
|
||||
|
|
@ -1,9 +1,12 @@
|
|||
---
|
||||
slug: /use/seed-phrase
|
||||
---
|
||||
|
||||
# Secure Seed Phrases and Passphrases in Zano
|
||||
|
||||
A **seed phrase** (also known as a recovery phrase or mnemonic phrase) is a set of words generated by your wallet that gives you access to the funds associated with that wallet. In Zano, a seed phrase consists of 24 to 26 words chosen from a standardized list of 1626 words. This phrase is all you need to recover your funds if you lose access to your wallet.
|
||||
|
||||
A **passphrase** is an additional layer of security that can be added to your seed phrase. When used together, the seed phrase and passphrase create a two-factor authentication system for accessing your wallet.
|
||||
Here’s a detailed explanation of how a seed phrase secured with a passphrase works:
|
||||
A **passphrase** is an additional layer of security that can be added to your seed phrase. When used together, the seed phrase and passphrase create a two-factor authentication system for accessing your wallet. Here’s a detailed explanation of how a seed phrase secured with a passphrase works:
|
||||
|
||||
## Seed Phrase
|
||||
|
||||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
slug: /use/zano-passwords.md
|
||||
---
|
||||
|
||||
# Different Password Types in Zano Wallets
|
||||
|
||||
When managing Zano wallets, utilizing multiple password types enhances security and convenience. Each password serves a unique purpose:
|
||||
|
|
@ -6,6 +10,7 @@ When managing Zano wallets, utilizing multiple password types enhances security
|
|||
|
||||
- **Purpose:** This is the basic level of security for your Zano wallet file.
|
||||
- **Use Case:**
|
||||
|
||||
- If you run your Zano wallet on a remote server for staking, the wallet password protects the wallet file from unauthorized access.
|
||||
- When opening your wallet locally on a GUI wallet, the wallet password is required on the first launch. If the master password is enabled, the wallet password will be stored and not required for subsequent launches.
|
||||
|
||||
|
|
@ -18,6 +23,7 @@ When managing Zano wallets, utilizing multiple password types enhances security
|
|||
|
||||
- **Feature:** This is primarily a feature in Zano GUI wallets.
|
||||
- **Benefit:**
|
||||
|
||||
- Allows users to bypass entering individual wallet passwords every time they open the application, and it secures all GUI data, including secrets and ports that allow connections to the Zano browser extension.
|
||||
- Particularly useful for users operating multiple Zano wallets, as it eliminates the need to enter each wallet password repeatedly on every launch.
|
||||
- **Convenience:** Simplifies access and enhances usability, especially when managing multiple wallets.
|
||||
|
|
@ -1,4 +1,8 @@
|
|||
# Zano Matrix Guide
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Zano Matrix
|
||||
|
||||
Zano Matrix enables secure, private messaging.
|
||||
|
||||
|
|
@ -29,11 +33,11 @@ With an increase in compromised communication platforms like Telegram and WhatsA
|
|||
src="https://www.youtube.com/embed/UycIuP5_EII?si=cvi4l6YkzjL2I6q4"
|
||||
title="YouTube video player"
|
||||
style={{
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
position: 'absolute',
|
||||
top: 0,
|
||||
left: 0,
|
||||
width: '100%',
|
||||
height: '100%'
|
||||
}}
|
||||
frameBorder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
|
|
@ -59,7 +63,7 @@ Furthermore, it's possible to connect with people via the Zano Explorer.
|
|||
|
||||
Simply click the Matrix connection icon to be forwarded to a one-on-one chat using the Zano Matrix Messenger!
|
||||
|
||||
|
||||
|
||||
|
||||
## Frequent Asked Questions
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 448 KiB |
BIN
static/img/stake/staking-zano/zano-staking.jpg
Normal file
BIN
static/img/stake/staking-zano/zano-staking.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 158 KiB |
BIN
static/img/use/gui-wallet/create.png
Normal file
BIN
static/img/use/gui-wallet/create.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
BIN
static/img/use/gui-wallet/create2.png
Normal file
BIN
static/img/use/gui-wallet/create2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
BIN
static/img/use/gui-wallet/create3.png
Normal file
BIN
static/img/use/gui-wallet/create3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
static/img/use/gui-wallet/seedphrase.png
Normal file
BIN
static/img/use/gui-wallet/seedphrase.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
BIN
static/img/use/gui-wallet/wallet.png
Normal file
BIN
static/img/use/gui-wallet/wallet.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 71 KiB |
BIN
static/img/use/wallet-features/aliases/aliascreation.png
Normal file
BIN
static/img/use/wallet-features/aliases/aliascreation.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
BIN
static/img/use/wallet-features/auditablewallet.png
Normal file
BIN
static/img/use/wallet-features/auditablewallet.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 240 KiB After Width: | Height: | Size: 240 KiB |
Loading…
Add table
Reference in a new issue