Merge branch 'hyle-team:main' into main
This commit is contained in:
Gonbatfire
GitHub
commit
c19fc54b57
41 changed files with 394 additions and 228 deletions
26
docs/build/testnet-resources/testnet-builds.md
vendored
26
docs/build/testnet-resources/testnet-builds.md
vendored
|
|
@ -7,28 +7,28 @@ A list of builds for the current Zano testnet
|
|||
Hash: SHA512
|
||||
|
||||
Windows:
|
||||
INST: https://build.zano.org/builds/zano-win-x64-release-testnet-v2.1.13.445[9f8141c]-installer.exe
|
||||
sha256: 33aa314b739128484a9cfc2a570fd5834d685ef75c712c7e64a0d8b482d8b1ab
|
||||
INST: https://build.zano.org/builds/zano-win-x64-develop-testnet-v2.2.0.455[2edace9]-installer.exe
|
||||
sha256: e5351e1078513563ccb316acba06a6099bba9c3de471c1f8179c60770df5daf7
|
||||
|
||||
ZIP: https://build.zano.org/builds/zano-win-x64-release-testnet-v2.1.13.445[9f8141c].zip
|
||||
sha256: 79bb1c5d7e587c6a9ebcbf48eca4038f06d5bcf720e9108dcedac7b4e33e3551
|
||||
ZIP: https://build.zano.org/builds/zano-win-x64-develop-testnet-v2.2.0.455[2edace9].zip
|
||||
sha256: 39a35133f1e7318907ac9a2c0bc03e325c58a2ef56cded755767cc6c69e43abd
|
||||
|
||||
macOS:
|
||||
https://build.zano.org/builds/zano-macos-x64-release-testnet-v2.1.13.445[9f8141c].dmg
|
||||
sha256: 76f7495eee98c231991d691ce081b14bcaf6e9ff589344109040cf320016075c
|
||||
https://build.zano.org/builds/zano-macos-x64-develop-testnet-v2.2.0.455[2edace9].dmg
|
||||
sha256: 4d1a811e66a840bae8cd2b8152b0aded05e5f5dea4cbf8225f4bf576327a8c90
|
||||
|
||||
Linux:
|
||||
https://build.zano.org/builds/zano-linux-x64-release-testnet-devtools-v2.1.13.445[9f8141c].AppImage
|
||||
sha256: 33cf1dcbac4f42420b0725273a3066047f0b468c47225812f009ca6f18e30414
|
||||
https://build.zano.org/builds/zano-linux-x64-develop-testnet-devtools-v2.2.0.455[2edace9].AppImage
|
||||
sha256: 50bb746e88b6a443d0c149d4c753962da47091e3f8d29eb5513a41cdec2437bc
|
||||
-----BEGIN PGP SIGNATURE-----
|
||||
|
||||
iHUEARYKAB0WIQSAlUHSyV95S5huh5+pK4bC95+XGgUCaWDpTgAKCRCpK4bC95+X
|
||||
Ggl7AP9EXy81FPrV80T7MhF5tU88hWPVi5noabCbz9hYQQ2yMAD9Fm1JtqxmS5YN
|
||||
vp5eBawvOc5+DKLuPW6C7lipwkNUqwU=
|
||||
=dzlC
|
||||
iHUEARYKAB0WIQSAlUHSyV95S5huh5+pK4bC95+XGgUCaZkG/AAKCRCpK4bC95+X
|
||||
GrNZAP0eYecp+bElVSZQxqVKIPMNGdUI3nzo7c51DyBF/LXbuAD/V9bCAssHG3AW
|
||||
hvF+xNio4VAgGRq7C02mXMtgOGJHdAQ=
|
||||
=MGEW
|
||||
-----END PGP SIGNATURE-----
|
||||
|
||||
updated at 2026-01-09 11:57 UTC
|
||||
updated at 2026-02-21 00:15 UTC
|
||||
```
|
||||
|
||||
[How to verify downloaded builds](https://docs.zano.org/docs/build/how-to-verify-downloaded-builds/)
|
||||
|
|
|
|||
14
docs/build/testnet-resources/testnet-faucet.md
vendored
Normal file
14
docs/build/testnet-resources/testnet-faucet.md
vendored
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
# Testnet faucet
|
||||
|
||||
Need testnet ZANO coins for development and testing? Use the official testnet faucet:
|
||||
|
||||
**[https://faucet.testnet.zano.org](https://faucet.testnet.zano.org)**
|
||||
|
||||
Enter your testnet wallet address to receive free testnet ZANO. These coins have no real value and are meant for testing purposes only.
|
||||
|
||||
## Getting a testnet wallet address
|
||||
|
||||
1. Download a [testnet build](./testnet-builds.md)
|
||||
2. Launch the Zano application — it will automatically connect to the testnet network
|
||||
3. Copy your wallet address from the application
|
||||
4. Paste it into the faucet page and request coins
|
||||
1
docs/learn/password-specs.md
Normal file
1
docs/learn/password-specs.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
|
||||
|
|
@ -9,7 +9,7 @@ Each Zano user can register with an alias, for example, @easytouse, a human-read
|
|||
|
||||
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.
|
||||
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 25.
|
||||
|
||||
:::note
|
||||
|
||||
|
|
|
|||
|
|
@ -3,116 +3,121 @@ sidebar_position: 4
|
|||
slug: /use/wallets/install-zano-cli-wallet-ubuntu
|
||||
---
|
||||
|
||||
# Install a Zano CLI Wallet (Ubuntu)
|
||||
# Install a Zano CLI Wallet (Linux)
|
||||
|
||||
**Step 1**
|
||||
Download Zano, extract the CLI binaries, sync the blockchain, and create your first wallet.
|
||||
|
||||
Go to the official site: https://zano.org and navigate to the downloads section
|
||||
## 1. Download
|
||||
|
||||
**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):
|
||||
Go to [zano.org](https://zano.org) and navigate to the downloads section. Download the Linux release — it's distributed as an **AppImage** file:
|
||||
|
||||
```
|
||||
sha256sum zano-linux-x64-v<XXX>.tar.bz2
|
||||
zano-linux-x64-release-v<VERSION>[<hash>].AppImage
|
||||
```
|
||||
|
||||
(Results should match release notes from Download page)
|
||||
## 2. Verify the download
|
||||
|
||||
|
||||
|
||||
Open a terminal in the download directory and run a checksum against the file:
|
||||
|
||||
**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
|
||||
```bash
|
||||
sha256sum zano-linux-x64-release-v*.AppImage
|
||||
```
|
||||
|
||||
|
||||
Compare the output against the SHA256 hash published in the [release notes](https://github.com/hyle-team/zano/releases). If they don't match, re-download the file.
|
||||
|
||||
**Steps 7-9**
|
||||
## 3. Extract the CLI binaries
|
||||
|
||||
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:
|
||||
The AppImage contains both the GUI wallet and CLI tools. To extract the CLI binaries:
|
||||
|
||||
```bash
|
||||
chmod +x zano-linux-x64-release-v*.AppImage
|
||||
./zano-linux-x64-release-v*.AppImage --appimage-extract
|
||||
```
|
||||
|
||||
This creates a `squashfs-root/` directory. The CLI binaries you need are inside:
|
||||
|
||||
```
|
||||
squashfs-root/usr/bin/zanod # the daemon (node)
|
||||
squashfs-root/usr/bin/simplewallet # the CLI wallet
|
||||
```
|
||||
|
||||
Move them to a directory of your choice:
|
||||
|
||||
```bash
|
||||
mkdir -p ~/zano
|
||||
cp squashfs-root/usr/bin/zanod squashfs-root/usr/bin/simplewallet ~/zano/
|
||||
```
|
||||
|
||||
You can delete `squashfs-root/` after copying the binaries.
|
||||
|
||||
|
||||
|
||||
## 4. Start the daemon
|
||||
|
||||
The daemon (`zanod`) connects to the Zano network and downloads the blockchain. Open a terminal in your Zano directory and run:
|
||||
|
||||
```bash
|
||||
./zanod
|
||||
```
|
||||
|
||||
|
||||
|
||||
Wait for the blockchain to fully sync — this can take a few hours on the first run, depending on your connection speed. Keep the daemon running; you'll need it for the next step.
|
||||
|
||||
**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.
|
||||
:::tip Skip the sync with a public node
|
||||
If you don't want to download the full blockchain, you can connect your wallet directly to a public node instead. Skip to step 5 and add `--daemon-address` when opening your 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
|
||||
```bash
|
||||
./simplewallet --generate-new-wallet name.wallet --daemon-address 37.27.100.59:10500
|
||||
```
|
||||
|
||||
Replace “name” with your new wallet’s name, e.g.,:
|
||||
See [Public Nodes](/docs/build/public-nodes) for available endpoints.
|
||||
:::
|
||||
|
||||
```
|
||||
./simplewallet --generate-new-wallet=zanocli.wallet
|
||||
## 5. Create a new wallet
|
||||
|
||||
Once the daemon is synced (or if you're using a public node), open a new terminal in the same directory:
|
||||
|
||||
```bash
|
||||
./simplewallet --generate-new-wallet name.wallet
|
||||
```
|
||||
|
||||
|
||||
Replace `name` with whatever you'd like to call your wallet (e.g., `mywallet.wallet`).
|
||||
|
||||
**Step 13**
|
||||
You'll be prompted to create a password. Use a strong one — a password manager like KeePass or Bitwarden is recommended.
|
||||
|
||||
When asked, enter a password for your wallet. You should use a password generator, found in password managers such as KeePass.
|
||||
After the password is set, the wallet will display your receive address (starts with `Zx`). This is the address you'll use to receive ZANO.
|
||||
|
||||
|
||||
|
||||
|
||||
**Steps 14-15**
|
||||
## 6. Back up your seed phrase
|
||||
|
||||
14. To open your new wallet, give the following command in the same terminal (again, substituting "name"):
|
||||
Your seed phrase is the only way to recover your wallet if you lose the wallet file or forget the password.
|
||||
|
||||
```
|
||||
./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:
|
||||
Inside the wallet console, run:
|
||||
|
||||
```
|
||||
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'll be prompted for your wallet password, then asked to set a **seed password** (also called a [passphrase](/docs/use/seed-phrase#passphrase)). This is optional — if you set one, you'll need both the seed phrase and the passphrase to restore the wallet.
|
||||
|
||||
|
||||
The wallet will display your **seed phrase** (26 words for current wallets). Write it down and store it somewhere safe and offline.
|
||||
|
||||
**You've successfully installed your new Zano Wallet!**
|
||||
|
||||
|
||||
:::warning
|
||||
Anyone with access to your seed phrase (and passphrase, if set) can take full control of your wallet. Never share it, never store it digitally in plain text.
|
||||
:::
|
||||
|
||||
## 7. Open an existing wallet
|
||||
|
||||
To reopen your wallet in the future:
|
||||
|
||||
```bash
|
||||
./simplewallet --wallet-file name.wallet
|
||||
```
|
||||
|
||||
Enter your password when prompted.
|
||||
|
||||
**You're done.** Head over to [Using a Zano CLI Wallet](/docs/use/wallets/using-zano-cli-wallet-ubuntu) for sending, receiving, and more advanced operations.
|
||||
|
|
|
|||
67
docs/use/wallets/cli/seed-doctor.md
Normal file
67
docs/use/wallets/cli/seed-doctor.md
Normal file
|
|
@ -0,0 +1,67 @@
|
|||
---
|
||||
sidebar_position: 10
|
||||
slug: /use/wallets/seed-doctor
|
||||
---
|
||||
|
||||
# Seed Doctor: Recovering a Broken Seed Phrase
|
||||
|
||||
Made a typo when writing down your seed phrase? Accidentally swapped two words? The `--seed-doctor` flag is an experimental tool built into simplewallet that can help you recover your wallet from a slightly corrupted seed phrase.
|
||||
|
||||
## When to Use Seed Doctor
|
||||
|
||||
This tool is useful when:
|
||||
|
||||
- You have a seed phrase that doesn't work during normal wallet restoration
|
||||
- You suspect one word is misspelled or doesn't match the wordlist
|
||||
- You think two adjacent words might be swapped
|
||||
|
||||
It won't help if multiple words are wrong or missing entirely.
|
||||
|
||||
## How to Run It
|
||||
|
||||
No wallet file or daemon connection is needed. Just run:
|
||||
|
||||
```bash
|
||||
./simplewallet --seed-doctor
|
||||
```
|
||||
|
||||
You'll get three prompts:
|
||||
|
||||
1. **Enter your seed phrase** — type in the full (broken) seed phrase
|
||||
2. **Enter your wallet address** — the address you expect the seed to produce (optional but strongly recommended)
|
||||
3. **Enter your passphrase** — only if the seed was protected with a passphrase (Secured Seed)
|
||||
|
||||
## What It Does
|
||||
|
||||
Seed Doctor applies two recovery strategies, one after another:
|
||||
|
||||
### Strategy 1: Invalid Word Detection
|
||||
|
||||
The tool checks every word in your seed phrase against Zano's mnemonic wordlist. If exactly one word isn't recognized, it tries every valid word in that position and checks whether the resulting seed produces the expected wallet address (or passes the internal checksum for V2 seeds).
|
||||
|
||||
### Strategy 2: Adjacent Word Swap
|
||||
|
||||
After the brute-force check, the tool tries swapping every pair of neighboring words in the seed phrase. This catches cases where you wrote down two words in the wrong order.
|
||||
|
||||
## Seed Phrase Versions
|
||||
|
||||
How Seed Doctor behaves depends on how many words your seed phrase has:
|
||||
|
||||
| Word Count | Seed Version | Recovery Notes |
|
||||
|:---:|:---:|---|
|
||||
| 24 | Legacy (no timestamp) | A placeholder word is appended internally before recovery begins |
|
||||
| 25 | V1 | **Wallet address is required** — without it, recovery is not possible |
|
||||
| 26 | V2 (with checksum) | Can recover without a wallet address, thanks to the built-in checksum |
|
||||
|
||||
## Limitations
|
||||
|
||||
- **One error at a time.** The tool can fix one wrong word *or* one adjacent swap, not both.
|
||||
- **V1 seeds need an address.** If you have a 25-word seed and don't know the wallet address, recovery won't work.
|
||||
- **Wrong passphrase = no recovery.** If the seed was protected with a passphrase and you enter the wrong one, the chance of recovery is effectively zero.
|
||||
- **Experimental.** This feature is provided as-is. It covers the most common mistakes but can't handle heavily corrupted phrases.
|
||||
|
||||
## Tips for Successful Recovery
|
||||
|
||||
- **Always provide your wallet address** when you have it. This narrows the search down fast and works across all seed versions.
|
||||
- **Double-check your passphrase** before running the tool. A wrong passphrase will make every candidate fail.
|
||||
- If seed doctor doesn't find a match, try re-examining your written seed for any words that look ambiguous (e.g., "though" vs "through", "bard" vs "bird") and correct them manually before running it again.
|
||||
|
|
@ -3,203 +3,278 @@ sidebar_position: 5
|
|||
slug: /use/wallets/using-zano-cli-wallet-ubuntu
|
||||
---
|
||||
|
||||
# Using a Zano CLI Wallet (Ubuntu)
|
||||
# Using a Zano CLI Wallet
|
||||
|
||||
Open a terminal in the directory with Zanod. Start your node, by giving the command:
|
||||
This guide assumes you've already [installed Zano and created a wallet](/docs/use/wallets/install-zano-cli-wallet-ubuntu).
|
||||
|
||||
```
|
||||
## Starting up
|
||||
|
||||
Start the daemon in one terminal:
|
||||
|
||||
```bash
|
||||
./zanod
|
||||
```
|
||||
|
||||
Open another terminal in the same directory (with simplewallet). Start your wallet, by giving the following command, substituting the name of your wallet:
|
||||
Once it's synced, open a second terminal and launch your wallet:
|
||||
|
||||
```
|
||||
```bash
|
||||
./simplewallet --wallet-file name.wallet
|
||||
```
|
||||
|
||||
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.
|
||||
Enter your password when prompted. The wallet will display your receive address after "Opened 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:
|
||||
To close the wallet cleanly, use the `exit` command. The daemon can be left running.
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
## Checking your balance
|
||||
|
||||
After you’ve funded your new Zano CLI wallet, open it again and check for your funds (steps 1-2 above). If they’re not visible, wait a bit and then give the command:
|
||||
If you've received funds but they aren't showing, resynchronize:
|
||||
|
||||
```
|
||||
refresh
|
||||
```
|
||||
|
||||
Now let’s send some ZANO to a friend!
|
||||
|
||||
The command for sending ZANO consists of four important bits of information:
|
||||
|
||||
1. the command itself
|
||||
2. the number of UTXOs with which to mix yours (between 10-50/maximum available)
|
||||
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
|
||||
|
||||
Owing to the inherent privacy of Zano wallets, no third parties can see their content on the blockchain, as with other cryptocurrencies with transparent ledgers.
|
||||
|
||||
There are instances, however, in which a user may want, or even need, the balance and transaction history of a wallet to be visible to a third-party (e.g., a public foundation). In such a case, one can use an Zano auditable CLI wallet (the auditable wallets are currently only available as CLI).
|
||||
|
||||
For further information on the auditable wallet, see https://docs.zano.org/docs/auditable-wallets
|
||||
|
||||
Give the following command, substituting "name":
|
||||
To see your balance:
|
||||
|
||||
```
|
||||
balance
|
||||
```
|
||||
|
||||
To see balances for all assets (ZANO, confidential assets, etc.):
|
||||
|
||||
```
|
||||
balance raw
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Sending ZANO
|
||||
|
||||
The `transfer` command takes a mixin count, destination address, and amount:
|
||||
|
||||
```
|
||||
transfer <mixin_count> <address> <amount>
|
||||
```
|
||||
|
||||
- **mixin_count**: the number of decoy outputs mixed with yours for privacy. Use **15** for standard wallets, **0** for auditable wallets.
|
||||
- **address**: the recipient's Zano address (starts with `Zx` or `aZx`)
|
||||
- **amount**: the amount of ZANO to send
|
||||
|
||||
Example — send 10 ZANO:
|
||||
|
||||
```
|
||||
transfer 15 ZxD4wSgHgE5TRVHQRbPKNthSpNSJoQp6DPLNaL4f3YT5dDQarAEHB2bVroPWhkCD59GDfVDjBBHmgLd2M1P92h5c21KwPZqg 10
|
||||
```
|
||||
|
||||
You can send to multiple recipients in one transaction:
|
||||
|
||||
```
|
||||
transfer 15 <address_1> <amount_1> <address_2> <amount_2>
|
||||
```
|
||||
|
||||
An optional **payment_id** can be appended at the end for services that require it.
|
||||
|
||||
|
||||
|
||||
### Sending assets
|
||||
|
||||
To send a confidential asset other than ZANO, prefix the address with the asset ID:
|
||||
|
||||
```
|
||||
transfer 15 <asset_id>:<address> <amount>
|
||||
```
|
||||
|
||||
## Receiving ZANO
|
||||
|
||||
Your receive address is shown when the wallet opens, or at any time with:
|
||||
|
||||
```
|
||||
address
|
||||
```
|
||||
|
||||
To generate an integrated address with an embedded payment ID (useful for exchanges or services):
|
||||
|
||||
```
|
||||
integrated_address
|
||||
```
|
||||
|
||||
Or with a specific payment ID:
|
||||
|
||||
```
|
||||
integrated_address <payment_id>
|
||||
```
|
||||
|
||||
## Transaction history
|
||||
|
||||
View recent transactions (last 100 by default):
|
||||
|
||||
```
|
||||
list_recent_transfers
|
||||
```
|
||||
|
||||
With offset and count:
|
||||
|
||||
```
|
||||
list_recent_transfers <offset> <count>
|
||||
```
|
||||
|
||||
Export transaction history to CSV:
|
||||
|
||||
```
|
||||
export_history
|
||||
```
|
||||
|
||||
Export recent transfers as JSON:
|
||||
|
||||
```
|
||||
export_recent_transfers
|
||||
```
|
||||
|
||||
## Restoring a wallet from seed
|
||||
|
||||
If you've lost your wallet file or password, you can restore it using your seed phrase.
|
||||
|
||||
Start the daemon, then in another terminal:
|
||||
|
||||
```bash
|
||||
./simplewallet --restore-wallet name.wallet
|
||||
```
|
||||
|
||||
You'll be prompted to create a password for the restored wallet file, then enter your seed phrase. Current wallets use 26-word seeds; older wallets may have 24 or 25 words. If the seed was secured with a [passphrase](/docs/use/seed-phrase#passphrase), you'll need that too.
|
||||
|
||||
|
||||
|
||||
If your seed phrase has a typo or swapped words, try the [Seed Doctor](/docs/use/wallets/seed-doctor) tool:
|
||||
|
||||
```bash
|
||||
./simplewallet --seed-doctor
|
||||
```
|
||||
|
||||
## Auditable wallets
|
||||
|
||||
Zano wallets are private by default — no third party can see balances or transactions on the blockchain. An **auditable wallet** lets a third party see your balances and transactions (e.g., for a public foundation or compliance).
|
||||
|
||||
For more details, see the [Auditable Wallets](/docs/use/auditable-wallets) page.
|
||||
|
||||
### Create an auditable wallet
|
||||
|
||||
```bash
|
||||
./simplewallet --generate-new-auditable-wallet name.wallet
|
||||
```
|
||||
|
||||
When prompted, enter your new password, preferably generated from a password generator.
|
||||
Set a password when prompted. Note that auditable wallet addresses start with `aZx` (standard wallets start with `Zx`).
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
### Get the tracking seed
|
||||
|
||||
If you ever need to retrieve the tracking seed, simply open the wallet and give the following command:
|
||||
Open the auditable wallet and run:
|
||||
|
||||
```
|
||||
tracking_seed
|
||||
```
|
||||
|
||||
|
||||
Share this tracking seed with anyone who needs to audit the wallet. They can restore a read-only copy using `--restore-wallet` and entering the tracking seed instead of a seed phrase.
|
||||
|
||||
Now, we must get our seed phrase, in case we ever need to restore our auditable CLI wallet. Within the wallet, give the command:
|
||||
|
||||
|
||||
### Back up the seed phrase
|
||||
|
||||
Just like a standard wallet:
|
||||
|
||||
```
|
||||
show_seed
|
||||
```
|
||||
|
||||
Again, when prompted, supply and confirm another password, specific to the seed itself.
|
||||
## Watch-only wallets
|
||||
|
||||
|
||||
|
||||
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":
|
||||
A watch-only wallet lets someone view your wallet without being able to spend from it. Open the wallet you want to create a watch-only copy of, then:
|
||||
|
||||
```
|
||||
aZxazX8e7rgRdRgrukJnQ3US3P81jas2TZfY7tz99Hab7yUyB8rAGkAhoHH3jrBpSBJP8PyrU3YsHb7HRtmXk4CjeYvjCHVPU3g
|
||||
save_watch_only <filename> <password>
|
||||
```
|
||||
|
||||
### Restoring a CLI Wallet from Seed
|
||||
|
||||
For whatever reason, you may lose your original Zano CLI wallet (your name.wallet file) or its password. All is not lost, if you safeguarded your seed.
|
||||
|
||||
After starting zanod, open another terminal in the simple-wallet directory. Give the following command, supplying your seed phrase:
|
||||
Example:
|
||||
|
||||
```
|
||||
./simplewallet --restore-wallet your 24 word seedphrase
|
||||
save_watch_only mywallet_watchonly.wallet mypassword
|
||||
```
|
||||
|
||||
You will then be asked to reenter the seedphrase, enter the password specific to that seedphrase, and then enter your restored wallet's password.
|
||||
## PoS staking
|
||||
|
||||
|
||||
You can stake ZANO directly from the CLI wallet by launching it with the `--do-pos-mining` flag:
|
||||
|
||||
### Creating a Watch-Only CLI Wallet
|
||||
|
||||
If you wish to allow someone to merely view your wallet, without being able to spend from it, you'll create a watch-only wallet. Open the wallet for which you wish to generate a watch-only wallet. Within the console, give the command, substituting the name of, and new password for, your new watch-only wallet:
|
||||
|
||||
```
|
||||
save_watch_only new_name.wallet password_for_wallet
|
||||
```bash
|
||||
./simplewallet --wallet-file name.wallet --do-pos-mining
|
||||
```
|
||||
|
||||
|
||||
To send staking rewards to a different address:
|
||||
|
||||
### Other Useful in-Terminal Flags
|
||||
|
||||
To skip supplying your password when opening wallet
|
||||
|
||||
```
|
||||
--password arg
|
||||
```bash
|
||||
./simplewallet --wallet-file name.wallet --do-pos-mining --pos-mining-reward-address <address>
|
||||
```
|
||||
|
||||
Use daemon instance at : for changing default host and port
|
||||
For an automated staking setup with PM2, see [Stake Zano on Boot](/docs/stake/advanced-setup/stake-zano-on-boot).
|
||||
|
||||
```
|
||||
--daemon-address arg
|
||||
```
|
||||
|
||||
|
||||
Prevents connecting to Zanod (daemon) for working offline (e.g., for cold-signing)
|
||||
## Command-line flags
|
||||
|
||||
```
|
||||
--offline-mode
|
||||
```
|
||||
These flags are passed when launching simplewallet.
|
||||
|
||||
Disables Tor from running with your wallet; this may be necessary if the Tor network itself is down.
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--wallet-file <file>` | Open an existing wallet |
|
||||
| `--generate-new-wallet <file>` | Create a new standard wallet |
|
||||
| `--generate-new-auditable-wallet <file>` | Create a new auditable wallet |
|
||||
| `--restore-wallet <file>` | Restore a wallet from seed phrase or tracking seed |
|
||||
| `--password <pass>` | Supply wallet password (skip interactive prompt) |
|
||||
| `--daemon-address <host>:<port>` | Connect to a specific daemon (local or [public node](/docs/build/public-nodes)) |
|
||||
| `--offline-mode` | Don't connect to the daemon (for [cold-signing](/docs/build/exchange-guidelines/signing-transactions-offline)) |
|
||||
| `--do-pos-mining` | Enable PoS staking |
|
||||
| `--pos-mining-reward-address <addr>` | Send staking rewards to a different address |
|
||||
| `--rpc-bind-port <port>` | Run wallet as an RPC server on this port |
|
||||
| `--rpc-bind-ip <ip>` | Bind RPC server to this IP (default: 127.0.0.1) |
|
||||
| `--jwt-secret <secret>` | Enable JWT authentication for RPC |
|
||||
| `--disable-tor-relay` | Disable Tor relay (may help if Tor network is down) |
|
||||
| `--seed-doctor` | Attempt to recover a broken seed phrase (see [Seed Doctor](/docs/use/wallets/seed-doctor)) |
|
||||
| `--derive_custom_seed` | Derive a seed from custom 24 words (advanced) |
|
||||
| `--no-refresh` | Don't sync the wallet on startup |
|
||||
| `--log-file <path>` | Set log file location |
|
||||
| `--log-level <0-4>` | Set log verbosity |
|
||||
| `--deaf` | Ignore all RPC commands (safe PoS mining mode) |
|
||||
| `--command <cmd>` | Execute a wallet command non-interactively |
|
||||
|
||||
```
|
||||
--disable-tor-relay
|
||||
```
|
||||
## In-wallet commands
|
||||
|
||||
Restores wallet from seed
|
||||
These commands are used inside the wallet console after opening.
|
||||
|
||||
```
|
||||
--restore-wallet
|
||||
```
|
||||
|
||||
Provides the destination for the log file, relative to the simplewalletbinary
|
||||
|
||||
```
|
||||
--log-file arg
|
||||
```
|
||||
|
||||
Sets the level of detail for the log
|
||||
|
||||
```
|
||||
--log-level arg
|
||||
```
|
||||
|
||||
Sets the level of detail for the log (same effect as above)
|
||||
|
||||
```
|
||||
--set-log arg
|
||||
```
|
||||
|
||||
Generates a new wallet that is auditable by a third party
|
||||
|
||||
```
|
||||
--generate-new-auditable-wallet
|
||||
```
|
||||
|
||||
And finally, to run any of the following commands outside of the wallet:
|
||||
|
||||
```
|
||||
--command arg
|
||||
```
|
||||
|
||||
**Other Useful in-Wallet Commands**
|
||||
|
||||
address = Shows current wallet public address
|
||||
|
||||
balance = Shows current wallet balance
|
||||
|
||||
exit = Closes the wallet
|
||||
|
||||
export_history [filename needed?] = Exports tx history into a CSV file
|
||||
|
||||
export_recent_transfers = Writes recent transfer txs in json to wallet_recent_transfers.txt (in Zano directory)
|
||||
|
||||
help = Shows a list of flags and commands
|
||||
|
||||
list_recent_transfers = Shows recent maximum 1000 sent amounts, offset default = 0, count default = 100
|
||||
|
||||
refresh = Resynchronize transactions and balance
|
||||
|
||||
resync = Resets all transfers and re-synchronize the wallet
|
||||
|
||||
save = Saves wallet synchronized data
|
||||
|
||||
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
|
||||
| Command | Description |
|
||||
|---------|-------------|
|
||||
| `address` | Show wallet public address |
|
||||
| `balance` | Show balance (`balance raw` for all assets) |
|
||||
| `refresh` | Resynchronize transactions and balance |
|
||||
| `resync` | Reset all transfers and re-synchronize from scratch |
|
||||
| `save` | Save wallet state |
|
||||
| `exit` | Close the wallet |
|
||||
| `help` | Show all available commands |
|
||||
| `transfer` | `transfer <mixin> <addr> <amount> [payment_id]` |
|
||||
| `list_recent_transfers` | `[offset] [count]` — show recent transactions (max 1000) |
|
||||
| `list_outputs` / `lo` | `[spent\|unspent] [ticker=ZANO]` — list UTXOs |
|
||||
| `show_seed` | Display seed recovery phrase (26 words for current wallets) |
|
||||
| `spendkey` | Display secret spend key |
|
||||
| `viewkey` | Display secret view key |
|
||||
| `tracking_seed` | Display tracking seed (auditable wallets) |
|
||||
| `save_watch_only` | `<file> <password>` — export a watch-only wallet |
|
||||
| `integrated_address` | `[payment_id]` — generate or decode an integrated address |
|
||||
| `show_staking_history` | `[days]` — show PoS staking rewards |
|
||||
| `export_history` | Export transaction history to CSV |
|
||||
| `export_recent_transfers` | Export recent transfers as JSON |
|
||||
| `sweep_below` | `<mixin> <address> <amount_limit> [payment_id]` — consolidate small outputs |
|
||||
| `sweep_bare_outs` | Transfer all bare (non-ZC) outputs to self |
|
||||
| `set_log` | `<level>` — change log verbosity (0-4) |
|
||||
| `deploy_new_asset` | `<json_file>` — deploy a new confidential asset |
|
||||
| `emit_asset` | `<asset_id> <amount>` — mint more of an asset you own |
|
||||
| `burn_asset` | `<asset_id> <amount>` — burn asset tokens |
|
||||
| `check_all_tx_keys` | Verify one-time secret keys for all sent transactions |
|
||||
|
|
|
|||
|
|
@ -47,3 +47,7 @@ A **passphrase** is an additional layer of security that can be added to your se
|
|||
|
||||
- **Loss of Passphrase:** If you forget or lose the passphrase, you will be permanently locked out of your wallet.
|
||||
- **Complexity:** Managing an additional passphrase can be cumbersome and may lead to user errors if not handled properly.
|
||||
|
||||
## Recovering a Corrupted Seed Phrase
|
||||
|
||||
If your seed phrase isn't working during wallet restoration, you may have written down a word incorrectly or swapped two adjacent words. Zano's CLI wallet includes an experimental [Seed Doctor](/docs/use/wallets/seed-doctor) tool that can attempt to fix these common mistakes.
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 948 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 279 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 99 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 85 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 157 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 41 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 71 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 114 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 260 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 97 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-balance.png
Normal file
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-balance.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-staking.png
Normal file
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-staking.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-transfer.png
Normal file
BIN
static/img/use/using-zano-cli-wallet-ubuntu/usage-transfer.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 194 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 237 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 140 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 83 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 232 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 179 KiB |
Loading…
Add table
Reference in a new issue