use setion
Signed-off-by: PRavaga <trueravaga@gmail.com>
This commit is contained in:
PRavaga
parent
fadf0e871e
commit
d5f90e274d
25 changed files with 229 additions and 177 deletions
|
|
@ -1,4 +1,4 @@
|
|||
{
|
||||
"label": "Zano features",
|
||||
"label": "Zano Features",
|
||||
"position": 2
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -8,6 +12,6 @@ To reduce possibility of phishing we set limitations on alias registrations. Use
|
|||
|
||||
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).
|
||||
|
||||
*<figcaption style={{textAlign: "center" }} >Alias registration</figcaption>*
|
||||
_<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.
|
||||
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,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Auditable wallets FAQ
|
||||
|
||||
### What is an auditable wallet?
|
||||
|
|
@ -85,7 +89,7 @@ Or in GUI wallet:
|
|||
|
||||
Only one: you cannot use mixins when you send coins from an auditable wallet.
|
||||
|
||||
***Obsolete***<br/>
|
||||
**_Obsolete_**<br/>
|
||||
The following limitations were effective until hardfork 2:
|
||||
|
||||
1. An alias cannot be assigned to an auditable address.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
# Deeplinks
|
||||
|
||||
Based on materials of Matthew Reichardt me@matthewreichardt.com (https://github.com/hyle-team/zano/issues/269)
|
||||
|
|
@ -51,6 +55,7 @@ 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)
|
||||
|
|
@ -58,4 +63,4 @@ Example of **escrow** command:
|
|||
- 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.
|
||||
All mentioned information will be encrypted and won't be available for third party.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 6
|
||||
---
|
||||
|
||||
# Escrow contracts
|
||||
|
||||
Zano provides the framework for a secure and private transaction without the need for a trusted third party. Our Escrow system, as proposed, will require participants to make additional deposits, which they will forfeit if there is any attempt to act maliciously, or in a way that is contemptuous toward their counter party. For more information please refer to the "Escrow" section of the [whitepaper](https://docs.zano.org/docs/whitepaper).
|
||||
|
|
@ -16,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`.
|
||||
|
||||
|
|
@ -38,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,4 +0,0 @@
|
|||
{
|
||||
"label": "Get Started",
|
||||
"position": 2
|
||||
}
|
||||
|
|
@ -1 +0,0 @@
|
|||
# Wallet Setup
|
||||
|
|
@ -1,124 +0,0 @@
|
|||
# Install a Zano CLI Wallet (Ubuntu)
|
||||
|
||||
**Step 1**
|
||||
|
||||
Go to the official site: https://zano.org
|
||||
|
||||
|
||||
|
||||
**Step 2**
|
||||
|
||||
Go to Downloads, which takes you to: https://github.com/hyle-team/zano/releases
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 3**
|
||||
|
||||
Download Linux (Ubuntu 16.04+) CLI Wallet
|
||||
|
||||
|
||||
|
||||
**Step 4**
|
||||
|
||||
Right click the file and select Properties
|
||||
|
||||
|
||||
|
||||
**Step 5**
|
||||
|
||||
Copy the file name
|
||||
|
||||
|
||||
|
||||
**Step 6**
|
||||
|
||||
Open a terminal in this directory & validate the authenticity of the file by running a checksum (XXX represents your version):
|
||||
|
||||
```
|
||||
sha256sum zano-linux-x64-v<XXX>.tar.bz2
|
||||
```
|
||||
|
||||
(Results should match release notes from Download page)
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 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 8-10**
|
||||
|
||||
8. Delete your original .tar.bz2 file
|
||||
9. Move the Zano folder to a location of your choice
|
||||
10. Within the Zano directory, open a terminal and run the daemon to start the node and download the blockchain:
|
||||
|
||||
```
|
||||
./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**
|
||||
|
||||
Once sync is complete, open another terminal in the Zano directory with the simplewalletbinary—that's our CLI wallet executable. Give command:
|
||||
|
||||
```
|
||||
./simplewallet --generate-new-wallet=name.wallet
|
||||
```
|
||||
|
||||
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**
|
||||
|
||||
14. To open your new wallet, give the following command in the same terminal (again, substituting "name"):
|
||||
|
||||
```
|
||||
./simplewallet --wallet-file name.wallet
|
||||
```
|
||||
|
||||
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**
|
||||
|
||||
16. Now we must get our wallet’s seed phrase, as well as set an additional password for the seed itself. Give the command:
|
||||
|
||||
```
|
||||
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!**
|
||||
4
docs/use/legacy/_category_.json
Normal file
4
docs/use/legacy/_category_.json
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
"label": "Boolberry/Legacy",
|
||||
"position": 99
|
||||
}
|
||||
|
|
@ -18,7 +18,7 @@ Next step is the coin transfer. Depending on how you prefer to store your coins
|
|||
|
||||
Enter your Zano address as 'Send payment address' in the latest Boolberry wallet app. The coinswap notification will appear.
|
||||
|
||||
|
||||
|
||||
|
||||
Then enter the desired BBR amount, then press Send to proceed with the coinswap.
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ At first, you will have to make sure that you exchange uses the latest BBR daemo
|
|||
|
||||
If you use the simplewallet daemon here is an example for making the coinswap transfer.
|
||||
|
||||
|
||||
|
||||
|
||||
It is also possible to make coin swap with the transfer RPC.
|
||||
|
||||
|
|
@ -44,4 +44,4 @@ For more information please refer to [BBR Documentation](https://docs.boolberry.
|
|||
|
||||
Usually, the coinswap procedure will be completed within an hour. However, it may take up to 24 hours in some cases. You should see a similar incoming transaction shortly.
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 7
|
||||
---
|
||||
|
||||
# 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).
|
||||
|
|
@ -11,4 +15,3 @@ Transaction of 100 coins creates in the blockchain
|
|||
```
|
||||
|
||||
Zano architecture demands 10 confirmations for this change transaction and that amount gets locked in the wallet. Therefore, lock time is 10 blocks behind or approximately 10 minutes.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,4 +2,10 @@
|
|||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Using Zano
|
||||
# Getting Started
|
||||
|
||||
Here, you'll find an array of tools and resources designed to enhance your experience within the Zano ecosystem. Whether you're new to Zano or have been a part of our community for a while, this guide offers insights and detailed instructions to help you navigate our platform with ease.
|
||||
|
||||
Begin with the basics in our [Wallets Guides](wallets/overview). Explore unique functionalities like [Aliases](aliases) or understand the benefits of [Auditable Wallets](auditable-wallets-faq). If you're keen on deepening your Zano knowledge, delve into [Deeplinks](deeplinks) or the secure mechanisms behind [Escrow Contracts](escrow-contracts).
|
||||
|
||||
And if you ever run into challenges, our [Reporting Issues](reporting-issues) section is here to help. Dive in, and make the most of what Zano has to offer.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,12 @@
|
|||
---
|
||||
sidebar_position: 9
|
||||
---
|
||||
|
||||
# Reporting issues
|
||||
|
||||
Hyle team puts a lot of hard work to bring you the best blockchain experience possible and it's highly unlikeable you will face any troubles using Zano. However if you experience any technical issues we suggest you make a report to our development team.
|
||||
Zano team puts a lot of hard work to bring you the best blockchain experience possible and it's highly unlikeable you will face any troubles using our product. However if you experience any technical issues we suggest you make a report to our development team.
|
||||
|
||||
All you need to do is to follow the [report link](https://jira.hyle.io/secure/CreateIssue!default.jspa) which can also be found in top of [docs page](https://docs.zano.org/docs/docs.zano.org). The describe your situation and submit a request.
|
||||
All you need to do is to follow the [report link](https://github.com/hyle-team/zano/issues), describe your situation and submit a request. Or join our [Discord](https://discord.gg/wE3rmYY) and post it in the #support channel.
|
||||
|
||||
## Log files
|
||||
|
||||
|
|
@ -24,4 +28,4 @@ C:\Users\<USER NAME>\AppData\Roaming\Zano
|
|||
|
||||
```
|
||||
~/.Zano
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 8
|
||||
---
|
||||
|
||||
# Tip Bot Guide
|
||||
|
||||
A simple guide on how to get tipping Zano on Discord
|
||||
|
|
@ -88,5 +92,3 @@ If you have a coupon code, the ‘Redeem Coupon’ button allows you to exchange
|
|||
Simply click the button and enter your coupon code.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
4
docs/use/wallets/_category_.json
Normal file
4
docs/use/wallets/_category_.json
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
"label": "Wallets Guides",
|
||||
"position": 2
|
||||
}
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
# Getting started
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
Those few steps will make you more familiar with Zano features and capabilities.
|
||||
|
||||
### Download and install Zano app
|
||||
# GUI Wallet
|
||||
|
||||
Zano app is available for Windows, Linux and MacOS. It can be downloaded here.
|
||||
|
||||
|
|
@ -32,4 +32,4 @@ To finalise wallet creation store wallet's seed phrase. IMPORTANT: using the see
|
|||
|
||||
|
||||
|
||||
Now the wallet has been created. You can copy wallet address and use it to receive ZANO from exchanges, mining pools and other sources.
|
||||
Now the wallet has been created. You can copy wallet address and use it to receive ZANO from exchanges, mining pools and other sources.
|
||||
117
docs/use/wallets/install-zano-cli-wallet-ubuntu.md
Normal file
117
docs/use/wallets/install-zano-cli-wallet-ubuntu.md
Normal file
|
|
@ -0,0 +1,117 @@
|
|||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Install a Zano CLI Wallet (Ubuntu)
|
||||
|
||||
**Step 1**
|
||||
|
||||
Go to the official site: https://zano.org and navigate to the downloads section
|
||||
|
||||
**Step 2**
|
||||
|
||||
Download Linux (Ubuntu 16.04+) CLI Wallet
|
||||
|
||||
|
||||
|
||||
**Step 3**
|
||||
|
||||
Right click the file and select Properties
|
||||
|
||||
|
||||
|
||||
**Step 4**
|
||||
|
||||
Copy the file name
|
||||
|
||||
|
||||
|
||||
**Step 5**
|
||||
|
||||
Open a terminal in this directory & validate the authenticity of the file by running a checksum (XXX represents your version):
|
||||
|
||||
```
|
||||
sha256sum zano-linux-x64-v<XXX>.tar.bz2
|
||||
```
|
||||
|
||||
(Results should match release notes from Download page)
|
||||
|
||||
|
||||
|
||||
|
||||
**Step 6**
|
||||
|
||||
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**
|
||||
|
||||
1. Delete your original .tar.bz2 file
|
||||
2. Move the Zano folder to a location of your choice
|
||||
3. Within the Zano directory, open a terminal and run the daemon to start the node and download the blockchain:
|
||||
|
||||
```
|
||||
./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**
|
||||
|
||||
Once sync is complete, open another terminal in the Zano directory with the simplewalletbinary—that's our CLI wallet executable. Give command:
|
||||
|
||||
```
|
||||
./simplewallet --generate-new-wallet=name.wallet
|
||||
```
|
||||
|
||||
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**
|
||||
|
||||
14. To open your new wallet, give the following command in the same terminal (again, substituting "name"):
|
||||
|
||||
```
|
||||
./simplewallet --wallet-file name.wallet
|
||||
```
|
||||
|
||||
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**
|
||||
|
||||
16. Now we must get our wallet’s seed phrase, as well as set an additional password for the seed itself. Give the command:
|
||||
|
||||
```
|
||||
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,3 +1,7 @@
|
|||
---
|
||||
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.
|
||||
|
|
@ -15,15 +19,14 @@ There are 3 ways to create a wallet in Zano app. From the `Wallets` `Add` sectio
|
|||
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>*
|
||||
|
||||
_<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>*
|
||||
_<figcaption style={{textAlign: "center" }} >Open existing wallet</figcaption>_
|
||||
|
||||
- Restore from backup
|
||||
|
||||
|
|
@ -32,8 +35,7 @@ There are 3 ways to create a wallet in Zano app. From the `Wallets` `Add` sectio
|
|||
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>*
|
||||
|
||||
_<figcaption style={{textAlign: "center" }} >Restore from backup</figcaption>_
|
||||
|
||||
### Wallet details
|
||||
|
||||
|
|
@ -41,7 +43,7 @@ Each Zano wallet can be identified by a custom name assigned on creation. This n
|
|||
|
||||
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>*
|
||||
_<figcaption style={{textAlign: "center" }} >Wallet details</figcaption>_
|
||||
|
||||
### Changing wallet password
|
||||
|
||||
|
|
@ -54,4 +56,4 @@ In case you want to change wallet file password, you need to use `Restore from b
|
|||
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`
|
||||
8. Continue with `Create wallet`
|
||||
25
docs/use/wallets/overview.md
Normal file
25
docs/use/wallets/overview.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Zano Apps & Wallets
|
||||
|
||||
### Desktop Apps
|
||||
|
||||
Zano GUI Wallets available for Windows, Mac OS and Linux
|
||||
|
||||
### Mobile Apps
|
||||
|
||||
Zano supports App Store and Play Store apps, for Android we also provide APK
|
||||
|
||||
### Browser extension
|
||||
|
||||
Currently Zano Companion only available for Zarcanum Testnet and works with Testnet Build provided below
|
||||
|
||||
### 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
|
||||
|
||||
For development purposes we provide a pre-built Testnet apps available [Testnet Resources](https://docs-zano.pages.dev) section
|
||||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
# Using a Zano CLI Wallet (Ubuntu)
|
||||
|
||||
Open a terminal in the directory with Zanod. Start your node, by giving the command:
|
||||
|
|
@ -14,12 +18,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.
|
||||
|
||||
|
||||
|
||||
You are now ready to get yourself some ZANO! Two exchanges to consider:
|
||||
|
||||
Trade Ogre: https://tradeogre.com <br/>
|
||||
Stex: https://www.stex.com/
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
|
@ -42,13 +41,11 @@ The command for sending ZANO consists of four important bits of information:
|
|||
3. the receiving address
|
||||
4. the amount of ZANO you wish to send
|
||||
|
||||
|
||||
<br/>
|
||||
For example:<br/>
|
||||
(1) (2) (3) (4)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Creating an Auditable CLI Wallet
|
||||
|
||||
|
|
@ -66,7 +63,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.
|
||||
|
||||
|
|
@ -76,7 +73,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:
|
||||
|
||||
|
|
@ -86,7 +83,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":
|
||||
|
||||
|
|
@ -106,7 +103,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
|
||||
|
||||
|
|
@ -116,7 +113,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
|
||||
|
||||
|
|
@ -206,4 +203,4 @@ show_seed = Displays secret 24 word phrase used to recover wallet
|
|||
|
||||
sweep_below <mixin_count>
|
||||
|
||||
<amount_lower_limit> [payment_id]: Tries to transfer all coins with amount below the given limit to the given address
|
||||
<amount_lower_limit> [payment_id]: Tries to transfer all coins with amount below the given limit to the given address
|
||||
|
|
@ -32,7 +32,7 @@ const config = {
|
|||
],
|
||||
|
||||
themeConfig: {
|
||||
image: "img/zano-social-card.png",
|
||||
image: "img/zano_dev_meta.png",
|
||||
navbar: {
|
||||
title: "Zano Docs",
|
||||
logo: {
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ function StartArticle({ content }) {
|
|||
<div className={styles.intro}>
|
||||
<article>
|
||||
<div className={styles.welcome}>
|
||||
<h1>Zano Documentation</h1>
|
||||
<h1>Zano Docs</h1>
|
||||
<span>
|
||||
Welcome to Zano's comprehensive documentation, your gateway to
|
||||
understanding and engaging with our unique cryptocurrency ecosystem.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ const Home = () => {
|
|||
const { siteConfig } = useDocusaurusContext();
|
||||
return (
|
||||
<Layout
|
||||
title={`Hello from ${siteConfig.title}`}
|
||||
title={`Welcome to ${siteConfig.title}`}
|
||||
description="Blockchain privacy for mass adoption"
|
||||
>
|
||||
<StartPage />
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 528 KiB |
BIN
static/img/zano_dev_meta.png
Normal file
BIN
static/img/zano_dev_meta.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 594 KiB |
Loading…
Add table
Reference in a new issue