Changes from dhub
This commit is contained in:
dhub-sync[bot]
GitHub
parent
9bfb3e90ae
commit
246dcd5abc
26 changed files with 202 additions and 147 deletions
17
docs/build/building-from-sources.md
vendored
17
docs/build/building-from-sources.md
vendored
|
|
@ -46,7 +46,7 @@ git clone --recursive https://github.com/hyle-team/zano.git
|
|||
|
||||
### Set environment variables
|
||||
|
||||
For instance, by adding the following lines to ~/.bashrc
|
||||
For instance, by adding the following lines to \~/.bashrc
|
||||
|
||||
Server version
|
||||
|
||||
|
|
@ -90,14 +90,12 @@ utils/build_script_linux.sh
|
|||
|
||||
## Windows
|
||||
|
||||
Install required prerequisites (Boost, Qt, CMake, OpenSSL)
|
||||
Install required prerequisites (Boost, Qt, CMake, OpenSSL)\
|
||||
Rename `utils/configure_local_paths.cmd.example` to `utils/configure_local_paths.cmd` and edit paths in this file so they correspond to your environment.
|
||||
|
||||
Mainnet:
|
||||
Run one of `utils/configure_win64_msvsNNNN_gui.cmd` according to your MSVC version.
|
||||
Mainnet: Run one of `utils/configure_win64_msvsNNNN_gui.cmd` according to your MSVC version.
|
||||
|
||||
Testnet:
|
||||
Run one of `utils/configure_win64_msvsNNNN_testnet.cmd` according to your MSVC version.
|
||||
Testnet: Run one of `utils/configure_win64_msvsNNNN_testnet.cmd` according to your MSVC version.
|
||||
|
||||
Go to the build folder and open generated Zano.sln in MSVC and build it.
|
||||
|
||||
|
|
@ -105,14 +103,11 @@ Go to the build folder and open generated Zano.sln in MSVC and build it.
|
|||
|
||||
In order to correctly deploy Qt GUI application, you also need to do the following:
|
||||
|
||||
Copy Zano.exe to a folder (e.g. `depoy`).
|
||||
Run `PATH_TO_QT\bin\windeployqt.exe deploy\Zano.exe`.
|
||||
Copy folder `\src\gui\qt-daemon\html` to `deploy\html`.
|
||||
Now you can run `Zano.exe`
|
||||
Copy Zano.exe to a folder (e.g. `depoy`). Run `PATH_TO_QT\bin\windeployqt.exe deploy\Zano.exe`. Copy folder `\src\gui\qt-daemon\html` to `deploy\html`. Now you can run `Zano.exe`
|
||||
|
||||
## MacOS
|
||||
|
||||
Install required prerequisites.
|
||||
Install required prerequisites.\
|
||||
Set environment variables as stated in `utils/macosx_build_config.command`
|
||||
|
||||
```
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ ZxDAcbaxXkyWRgYbeARBpngfmFat5TjDjjQA5NAbouB9eytwGWJqA5shAVYeCAHWPo254DF2o2X1td79
|
|||
|
||||
Initiator is planning to offer Finalizer to exchange 2 coins of the CT token that she possesses (but Finalizer does not) for 10 native coins of ZANO (which Finalizer has). To do this, she generates a proposal through an API call [ionic_swap_generate_proposal](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/ionic_swap_generate_proposal) in her wallet with the following parameters:
|
||||
|
||||
```json json
|
||||
```json
|
||||
{
|
||||
"jsonrpc": "2.0",
|
||||
"id": "0",
|
||||
|
|
|
|||
4
docs/build/confidential-assets/overview.md
vendored
4
docs/build/confidential-assets/overview.md
vendored
|
|
@ -7,7 +7,9 @@ sidebar_position: 1
|
|||
Confidential Assets are privacy tokens with all the features of native Zano coin
|
||||
|
||||
:::info
|
||||
|
||||
Currently asset creation is only supported on Zano Testnet and will be brought to mainnet with upcoming Zarcanum hardfork
|
||||
|
||||
:::
|
||||
|
||||
Confidential Assets Commands are availabe trough CLI interface (simplewallet)
|
||||
|
|
@ -39,4 +41,4 @@ deploy_new_asset <asset specs file location>
|
|||
|
||||
You should see a confirmation message upon successful execution
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,20 +10,15 @@ Starting the wallet in RPC server mode:
|
|||
2. Run simplewallet with the following options:
|
||||
|
||||
```shell
|
||||
simplewallet --wallet-file PATH_TO_WALLET_FILE --password PASSWORD
|
||||
--rpc-bind-ip RPC_IP --rpc-bind-port RPC_PORT
|
||||
simplewallet --wallet-file PATH_TO_WALLET_FILE --password PASSWORD
|
||||
--rpc-bind-ip RPC_IP --rpc-bind-port RPC_PORT
|
||||
--daemon-address DEAMON_ADDR:DAEMON_PORT --log-file LOG_FILE_NAME
|
||||
```
|
||||
|
||||
where:
|
||||
|
||||
**PATH_TO_WALLET_FILE** — path to an existing wallet file (should be created beforehand using --generate-new-wallet command);<br/>
|
||||
**PASSWORD** — wallet password;<br/>
|
||||
**RPC_IP** — IP address to bind RPC server to (127.0.0.1 will be used if not specified);<br/>
|
||||
**RPC_PORT** — TCP port for RPC server;<br/>
|
||||
**DEAMON_ADDR:DAEMON_PORT** — daemon address and port (may be omitted if the daemon is running on the same machine with the default settings);<br/>
|
||||
**LOG_FILE_NAME** — path and filename of simplewallet log file.<br/>
|
||||
**PATH_TO_WALLET_FILE** — path to an existing wallet file (should be created beforehand using --generate-new-wallet command);<br /> **PASSWORD** — wallet password;<br /> **RPC_IP** — IP address to bind RPC server to (127.0.0.1 will be used if not specified);<br /> **RPC_PORT** — TCP port for RPC server;<br /> **DEAMON_ADDR\:DAEMON_PORT ** — daemon address and port (may be omitted if the daemon is running on the same machine with the default settings);<br /> **LOG_FILE_NAME** — path and filename of simplewallet log file.<br />
|
||||
|
||||
Examples in [List of Wallet RPCs](https://docs.zano.org/docs/api-reference-1) are given with assumption that the wallet application is running in RPC server mode and listening at 127.0.0.1:12233.
|
||||
|
||||
All amounts and balances are represented as unsigned integers and measured in atomic units — the smallest fraction of a coin. One coin equals 10^12 atomic units.
|
||||
All amounts and balances are represented as unsigned integers and measured in atomic units — the smallest fraction of a coin. One coin equals 10^12 atomic units.
|
||||
|
|
|
|||
12
docs/build/rpc-api/daemon-rpc.md
vendored
12
docs/build/rpc-api/daemon-rpc.md
vendored
|
|
@ -14,7 +14,7 @@ zanod --rpc-bind-ip RPC_IP --rpc-bind-port RPC_PORT
|
|||
|
||||
where:
|
||||
|
||||
**RPC_IP** — IP address to bind RPC server to (127.0.0.1 will be used if not specified);
|
||||
**RPC_IP** — IP address to bind RPC server to (127.0.0.1 will be used if not specified);\
|
||||
**RPC_PORT** — TCP port for RPC server (11211 is default);
|
||||
|
||||
All examples below are based on the assumption that the daemon is listening for RPC at 127.0.0.1:11211.
|
||||
|
|
@ -25,7 +25,7 @@ One coin is equal to 10^12 atomic units.
|
|||
|
||||
## JSON RPC BUSY response
|
||||
|
||||
All JSON RPC calls are served via http\://RPC_IP:RPC_PORT/json_rpc URI.
|
||||
All JSON RPC calls are served via http\://RPC_IP\:RPC_PORT /json_rpc URI.
|
||||
|
||||
Any request may receive a BUSY response if the daemon is synchronizing with the network. In such cases the user should repeat the request later.
|
||||
|
||||
|
|
@ -43,12 +43,12 @@ Alternative blocks are not stored between subsequent runs of the daemon applicat
|
|||
|
||||
## Connect Legacy JSON API
|
||||
|
||||
This API is legacy and not compliant with the JSON RPC specification. Please note that all methods in this section are accessed by http\://RPC_IP:RPC_PORT/METOD_NAME URI.
|
||||
This API is legacy and not compliant with the JSON RPC specification. Please note that all methods in this section are accessed by http\://RPC_IP\:RPC_PORT /METOD_NAME URI.
|
||||
|
||||
## Connect Binary RPC API
|
||||
|
||||
Binary API uses binary protocol for communication, which is more compact and faster than JSON-API, especially when transferring large amounts of data. It was designed to communicate with a wallet application.
|
||||
You may want to use epee serialization, in particular
|
||||
Binary API uses binary protocol for communication, which is more compact and faster than JSON-API, especially when transferring large amounts of data. It was designed to communicate with a wallet application.\
|
||||
You may want to use epee serialization, in particular\
|
||||
**epee::serialization::store_t_to_binary** and **epee::serialization::load_t_from_binary** methods, to serialize your data before passing to API, and to deserialize upon retrieving from API. Alternatively, you may use **epee::net_utils::invoke_http_bin_remote_command2**
|
||||
|
||||
All methods in this section are accessible by http\://RPC_IP:RPC_PORT/METOD_NAME URI.
|
||||
All methods in this section are accessible by http\://RPC_IP\:RPC_PORT /METOD_NAME URI.
|
||||
|
|
|
|||
12
docs/build/rpc-api/overview.md
vendored
12
docs/build/rpc-api/overview.md
vendored
|
|
@ -9,7 +9,9 @@ Welcome to the Zano API documentation! As a digital currency enthusiast, develop
|
|||
Our aim with this documentation is to help you harness the full potential of Zano's feature-rich platform, allowing you to integrate, innovate, and build on top of Zano's powerful privacy-oriented blockchain.
|
||||
|
||||
:::info
|
||||
|
||||
Read more on the [JSON-RPC 2.0 Specification](https://www.jsonrpc.org/specification)
|
||||
|
||||
:::
|
||||
|
||||
## Formatting example
|
||||
|
|
@ -46,22 +48,28 @@ Additionally, endpoints will be grouped according to whether they call the Daemo
|
|||
## Running Daemon and Wallet in RPC mode (brief guide)
|
||||
|
||||
:::info
|
||||
|
||||
All examples below are based on the assumption that the daemon is listening for RPC at 127.0.0.1:11211
|
||||
|
||||
:::
|
||||
|
||||
In order to send JSON requests, both the Zano Daemon and Wallet must be ran in RPC mode
|
||||
|
||||
:::tip
|
||||
|
||||
For additional info on RPC mode, for wallet visit [Wallet RPC Mode](wallet-rpc), and [Daemon RPC Mode](daemon-rpc)
|
||||
|
||||
:::
|
||||
|
||||
### How to run Daemon in RPC mode
|
||||
|
||||
:::info
|
||||
|
||||
In order to interact with the Marketplace API, you must include the following flag: '--enable-offers-service'
|
||||
|
||||
:::
|
||||
|
||||
```Text console
|
||||
```Text
|
||||
./zanod --rpc-bind-ip 127.0.0.1 --rpc-bind-port 11211 --enable-offers-service
|
||||
```
|
||||
|
||||
|
|
@ -74,7 +82,7 @@ In order to interact with the Marketplace API, you must include the following fl
|
|||
|
||||
### How to run Wallet in RPC mode
|
||||
|
||||
```Text console
|
||||
```Text
|
||||
./simplewallet --wallet-file example.wallet --password password --rpc-bind-ip 127.0.0.1 --rpc-bind-port 11212 --daemon-address 127.0.0.1:11211
|
||||
```
|
||||
|
||||
|
|
|
|||
6
docs/build/rpc-api/wallet-rpc.md
vendored
6
docs/build/rpc-api/wallet-rpc.md
vendored
|
|
@ -12,7 +12,7 @@ In order to start the wallet in RPC server mode, a user needs the following:
|
|||
|
||||
2. Run simplewallet with the following options:
|
||||
|
||||
```shell shell
|
||||
```shell
|
||||
simplewallet --wallet-file PATH_TO_WALLET_FILE --password PASSWORD --rpc-bind-ip RPC_IP --rpc-bind-port RPC_PORT --daemon-address DEAMON_ADDR:DAEMON_PORT
|
||||
```
|
||||
|
||||
|
|
@ -22,9 +22,9 @@ simplewallet --wallet-file PATH_TO_WALLET_FILE --password PASSWORD --rpc-bind-ip
|
|||
- PASSWORD — wallet’s password;
|
||||
- RPC_IP — IP address to bind RPC server to (127.0.0.1 will be used if not specified);
|
||||
- RPC_PORT — TCP port for RPC server;
|
||||
- DEAMON_ADDR:DAEMON_PORT — daemon address and port (may be omitted if the daemon is running on the same machine with the default settings);
|
||||
- DEAMON_ADDR\:DAEMON_PORT  — daemon address and port (may be omitted if the daemon is running on the same machine with the default settings);
|
||||
|
||||
All examples below are given in assumption that the wallet application is running in RPC server mode and listening at 127.0.0.1:12233.
|
||||
|
||||
All amounts and balances are represented as unsigned integers and measured in atomic units — the smallest fraction of a coin.
|
||||
All amounts and balances are represented as unsigned integers and measured in atomic units — the smallest fraction of a coin.\
|
||||
1 coin is equal to 10^12 atomic units.
|
||||
|
|
|
|||
|
|
@ -4,23 +4,23 @@ sidebar_position: 5
|
|||
|
||||
# Specifications
|
||||
|
||||
| General info | |
|
||||
| :------------------- | ------------------------------------- |
|
||||
| Release | 2019 |
|
||||
| Currency | Zano |
|
||||
| Symbol | ZANO |
|
||||
| Hash algorithm | ProgPowZ |
|
||||
| Language | C++ |
|
||||
| Blockchain | PoS + PoW |
|
||||
| **Emission** | |
|
||||
| Block time | 1 minute |
|
||||
| Block reward | 1 ZANO |
|
||||
| Initial total supply | 17517203 ZANO |
|
||||
| Maximum Supply | ∞ (uncapped) |
|
||||
| **Resources** | |
|
||||
| Website | https://zano.org/ |
|
||||
| Repository | https://github.com/hyle-team/zano |
|
||||
| Explorer | https://explorer.zano.org/ |
|
||||
| **Requirements** | |
|
||||
| Wallet requirements | 2 core x64 CPU, 3 GB RAM |
|
||||
| Wallet platforms | x64 Windows 7, Linux or Mac OS X 10.9 |
|
||||
| General info | |
|
||||
| --- | --- |
|
||||
| Release | 2019 |
|
||||
| Currency | Zano |
|
||||
| Symbol | ZANO |
|
||||
| Hash algorithm | ProgPowZ |
|
||||
| Language | C++ |
|
||||
| Blockchain | PoS + PoW |
|
||||
| **Emission** | |
|
||||
| Block time | 1 minute |
|
||||
| Block reward | 1 ZANO |
|
||||
| Initial total supply | 17517203 ZANO |
|
||||
| Maximum Supply | ∞ (uncapped) |
|
||||
| **Resources** | |
|
||||
| Website | [https://zano.org/](https://zano.org/) |
|
||||
| Repository | [https://github.com/hyle-team/zano](https://github.com/hyle-team/zano) |
|
||||
| Explorer | [https://explorer.zano.org/](https://explorer.zano.org/) |
|
||||
| **Requirements** | |
|
||||
| Wallet requirements | 2 core x64 CPU, 3 GB RAM |
|
||||
| Wallet platforms | x64 Windows 7, Linux or Mac OS X 10.9 |
|
||||
|
|
|
|||
|
|
@ -43,11 +43,7 @@ blockchain, which have the same properties as transactions with a native token
|
|||
|
||||
### Zano: Confidential Assets Scheme for RingCT and Zarcanum (2024)
|
||||
|
||||
In this paper, we describe a practical way of implementing confidential assets (a.k.a. tokens or colored
|
||||
coins) in Zano with unlimited decoy mixing capability and hidden amounts, as an extension to the Ring
|
||||
Confidential Transactions scheme. Our approach preserves public verifiability that no transaction either
|
||||
creates or destroys coins. We further extend this approach to show how it can be combined with
|
||||
Zarcanum, a Proof-of-Stake scheme for transaction with hidden amounts
|
||||
In this paper, we describe a practical way of implementing confidential assets (a.k.a. tokens or colored coins) in Zano with unlimited decoy mixing capability and hidden amounts, as an extension to the Ring Confidential Transactions scheme. Our approach preserves public verifiability that no transaction either creates or destroys coins. We further extend this approach to show how it can be combined with Zarcanum, a Proof-of-Stake scheme for transaction with hidden amounts
|
||||
|
||||
<https://hyle-team.github.io/docs/zano/CA_paper/Zano_CA_for_RingCT_and_Zarcanum_v1.1.pdf>
|
||||
|
||||
|
|
|
|||
|
|
@ -2,22 +2,15 @@
|
|||
|
||||
### Privacy
|
||||
|
||||
Zano is completely private by default, making use of stealth
|
||||
addresses, ring signatures, and from the moment we perform our Zarcanum
|
||||
hardfork, also RingCT.
|
||||
Zano is completely private by default, making use of stealth addresses, ring signatures, and from the moment we perform our Zarcanum hardfork, also RingCT.
|
||||
|
||||
### Security
|
||||
|
||||
Our blockchain is protected by our custom hybrid PoW/PoS
|
||||
consensus algorithm, pairing the advantages of each process to create a
|
||||
highly secure platform. This makes the system less prone to double-spend
|
||||
attacks, improving overall security.
|
||||
Our blockchain is protected by our custom hybrid PoW/PoS consensus algorithm, pairing the advantages of each process to create a highly secure platform. This makes the system less prone to double-spend attacks, improving overall security.
|
||||
|
||||
### Scalability
|
||||
|
||||
Achieving computational excellence with forward/backward
|
||||
compatibility, modular design, and an asynchronous core. This makes our
|
||||
blockchain scalable and ready to handle high volumes of traffic.
|
||||
Achieving computational excellence with forward/backward compatibility, modular design, and an asynchronous core. This makes our blockchain scalable and ready to handle high volumes of traffic.
|
||||
|
||||
### Zarcanum
|
||||
|
||||
|
|
@ -25,9 +18,7 @@ World’s first Proof of Stake scheme that enhances traditional PoS with untrace
|
|||
|
||||
### Confidential Assets
|
||||
|
||||
Anyone can easily issue their own currencies and digital tokens on the Zano chain; assets secured by the same mechanisms
|
||||
that make Zano so much more secure than first-generation cryptocurrencies,
|
||||
namely hidden addresses, hidden amounts and IP obfuscation.
|
||||
Anyone can easily issue their own currencies and digital tokens on the Zano chain; assets secured by the same mechanisms that make Zano so much more secure than first-generation cryptocurrencies, namely hidden addresses, hidden amounts and IP obfuscation.
|
||||
|
||||
### Ionic Swaps
|
||||
|
||||
|
|
@ -39,22 +30,16 @@ Explore our dynamic API, facilitating a seamless integration into the marketplac
|
|||
|
||||
### Escrow Contracts
|
||||
|
||||
Our escrow service empowers users with customizable contracts in a trustless environment, secured by deposits to deter
|
||||
malfeasance.
|
||||
Our escrow service empowers users with customizable contracts in a trustless environment, secured by deposits to deter malfeasance.
|
||||
|
||||
### Staking
|
||||
|
||||
Our implementation of Proof of Stake is as egalitarian as it can be. There is no minimum staking amount, so anyone can participate, contributing
|
||||
to our vision of having a highly decentralized ecosystem that anyone can use.
|
||||
Our implementation of Proof of Stake is as egalitarian as it can be. There is no minimum staking amount, so anyone can participate, contributing to our vision of having a highly decentralized ecosystem that anyone can use.
|
||||
|
||||
### Aliases
|
||||
|
||||
All Zano network users can create aliases, for example: @username. These aliases can be linked to a payment address, which makes
|
||||
our network more user friendly. In the long run, aliases will be used in a
|
||||
dedicated messenger, a user reputation service, and an alias-based
|
||||
authentication system.
|
||||
All Zano network users can create aliases, for example: @username. These aliases can be linked to a payment address, which makes our network more user friendly. In the long run, aliases will be used in a dedicated messenger, a user reputation service, and an alias-based authentication system.
|
||||
|
||||
### Auditable wallets
|
||||
|
||||
Auditable wallets give people and organizations the option to create transparent wallets for situations where we would rather verify than
|
||||
trust.
|
||||
Auditable wallets give people and organizations the option to create transparent wallets for situations where we would rather verify than trust.
|
||||
|
|
|
|||
|
|
@ -5,29 +5,37 @@ sidebar_position: 2
|
|||
# Server/Console mode POS mining
|
||||
|
||||
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
|
||||
./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.
|
||||
|
||||
Some of the parameters are required, and some are optional. Here's what they mean:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ sidebar_position: 6
|
|||
|
||||
# Deeplinks
|
||||
|
||||
Based on materials of Matthew Reichardt me@matthewreichardt.com (https://github.com/hyle-team/zano/issues/269)
|
||||
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
|
||||
|
||||
|
|
@ -18,11 +18,11 @@ Based on materials of Matthew Reichardt me@matthewreichardt.com (https://github.
|
|||
|
||||
Example of **send** command:
|
||||
|
||||
**zano:action=send&address=ZxCkvE7zhS6JuFE5neAaTtcY8PUT2CwfLZJQWP32jrELB1Vg9oSJyGJDyRWurqX6SXSqxjGz2yrAKaMqmxDa7E8313igosBVT&comment='Some payment'&mixins=11&hide_sender=true&hide_receiver=true**
|
||||
**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]
|
||||
- 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)
|
||||
|
||||
|
|
@ -30,11 +30,11 @@ Example of **send** command:
|
|||
|
||||
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'**
|
||||
**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]
|
||||
- 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)
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ Example of **marketplace_offer_create** command:
|
|||
|
||||
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'**
|
||||
**zano\:action \=escrow\&description='Some Description'\&seller_address='ZxCXALhZRodKmqRCWUPNAUCXqprJBNKv4eFsjzcMooAGVM6J2U2vSyTNpxNybwBnvzGWLtSWpBiddSZhph8HNfBn1bVE3c6ix'\&amount='10'\&my_deposit='5'\&seller_deposit='5'\&comment='Some comment if needed'**
|
||||
|
||||
**Escrow parameters:**
|
||||
|
||||
|
|
|
|||
|
|
@ -3,13 +3,17 @@
|
|||
As you may already know, Boolberry holders can swap their coins to the Zano network. The dev team managed to make this process as simple as possible. Basically, all you need is a transaction from the Boolberry wallet to a desired Zano address. The rest of the swap process will be completed automatically. The Boolberry funds will be burnt and after 20 confirmations your Zano address will receive the amount in Zano.
|
||||
|
||||
:::danger ⠀
|
||||
|
||||
Swapped coins will no longer exist in the Boolberry network and this action is irreversible.
|
||||
|
||||
:::
|
||||
|
||||
The first step to coin swap is to obtain a Zano address. There is a [Getting started](https://docs.zano.org/docs/getting-started-1) article which will guide you through the process.
|
||||
|
||||
:::danger ⠀
|
||||
|
||||
Make sure you have Boolberry wallet version 93 or higher, available [here](https://boolberry.com/#downloads).
|
||||
|
||||
:::
|
||||
|
||||
Next step is the coin transfer. Depending on how you prefer to store your coins there are three options.
|
||||
|
|
@ -18,7 +22,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 +34,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 +48,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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,15 +10,11 @@ Using Zano’s Discord TipBot is fairly straightforward and intuitive, but here
|
|||
|
||||
#### 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/
|
||||
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/](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
|
||||
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](https://discord.gg/wE3rmYY)
|
||||
|
||||
### The Tip Bot
|
||||
|
||||
|
|
@ -28,33 +24,33 @@ Welcome to Zano Discord, now that you’re here, you should have something that
|
|||
|
||||
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
|
||||
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](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
|
||||
|
||||
|
|
@ -64,19 +60,19 @@ $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.
|
||||
|
||||
|
|
@ -84,11 +80,10 @@ History is formatted as a table, whereas History (simple) is a simple one-liner.
|
|||
|
||||
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.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,25 +6,25 @@ sidebar_position: 4
|
|||
|
||||
**Step 1**
|
||||
|
||||
Go to the official site: https://zano.org and navigate to the downloads section
|
||||
Go to the official site: [https://zano.org](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**
|
||||
|
||||
|
|
@ -36,8 +36,7 @@ sha256sum zano-linux-x64-v<XXX>.tar.bz2
|
|||
|
||||
(Results should match release notes from Download page)
|
||||
|
||||
|
||||
|
||||
 
|
||||
|
||||
**Step 6**
|
||||
|
||||
|
|
@ -47,7 +46,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 +58,13 @@ 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,36 +80,36 @@ 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"):
|
||||
1. 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.
|
||||
1. 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:
|
||||
1. 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!!
|
||||
1. 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!**
|
||||
|
|
|
|||
|
|
@ -18,7 +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.
|
||||
|
||||
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
|
@ -41,11 +41,12 @@ 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/>
|
||||
<br />
|
||||
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
|
||||
|
||||
|
|
|
|||
69
docs/use/zano-trade.md
Normal file
69
docs/use/zano-trade.md
Normal file
|
|
@ -0,0 +1,69 @@
|
|||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Zano Trade
|
||||
|
||||
A decentralized exchange to trade native Zano and all the Confidential Assets launched on Zano’s ecosystem. Zano Trade requires no user registration and uses an on-chain order matching system to facilitate [Ionic Swaps](https://docs.zano.org/docs/learn/frequently-asked-questions#what-are-ionic-swaps) between native Zano and the Confidential Assets. It is impossible to see what asset type, amount, or address was involved in the transaction.
|
||||
|
||||
## How to use
|
||||
|
||||
1. Zano Trade, like all Zano dApps, requires using Zano Companion, [click here](https://docs.zano.org/docs/use/companion) if you haven't set it up already.
|
||||
|
||||
2. Once your Companion is ready (make sure to have your desktop wallet open and unlocked) head to [trade.zano.org](http://trade.zano.org) and click "Connect Wallet".
|
||||
|
||||
3. On the first time, a popup will appear on the Companion to authorize the connection, click "Accept".
|
||||
|
||||
|
||||
|
||||
4. To do a trade, search and select the desired trading pair. 
|
||||
|
||||
If multiple tokens under the same/similar name exist, make sure to check the unique Asset ID.
|
||||
|
||||
|
||||
|
||||
5. Now you can either post a buy/sell order or take an existing one.
|
||||
|
||||
#### Create an order
|
||||
|
||||
For this example, we will be buying "ZNOPP" tokens:
|
||||
|
||||
Price: How much of the base pair (in this case, ZANO) do we want to pay per unit of ZNOOP?
|
||||
|
||||
Amount: How many tokens do we want to acquire at this price?
|
||||
|
||||
Click "Buy" to post the order.
|
||||
|
||||
|
||||
|
||||
#### Take an order
|
||||
|
||||
For this example, we'll be selling "ZNOOP" tokens:
|
||||
|
||||
Scroll down to see the order book
|
||||
|
||||
Since we are happy with receiving 0.01 ZANO per token, we'll proceed to click "Take Order"
|
||||
|
||||
|
||||
|
||||
This will take us back above and automatically set the fields for our sell order, simply click "Sell".
|
||||
|
||||
|
||||
|
||||
#### Complete the trade
|
||||
|
||||
Scroll down to see your list of pending orders.
|
||||
|
||||
|
||||
|
||||
Since our order matches the one from Timmy03, all that is left to do is click "Apply".
|
||||
|
||||
This will open Zano Companion, prompting us to confirm the trade.
|
||||
|
||||
|
||||
|
||||
Now we wait for Timmy03 to apply our order in the same way we just did.
|
||||
|
||||
|
||||
|
||||
And that's it! We just completed a peer-to-peer trade made possible by Zano's Ionic Swaps, preserving our privacy across the whole process.
|
||||
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
BIN
static/img/use/zano-trade/completed_trade.png
Normal file
BIN
static/img/use/zano-trade/completed_trade.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
static/img/use/zano-trade/ionic_swap1.png
Normal file
BIN
static/img/use/zano-trade/ionic_swap1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
static/img/use/zano-trade/my_orders.png
Normal file
BIN
static/img/use/zano-trade/my_orders.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
BIN
static/img/use/zano-trade/new_order.png
Normal file
BIN
static/img/use/zano-trade/new_order.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
BIN
static/img/use/zano-trade/new_order1.png
Normal file
BIN
static/img/use/zano-trade/new_order1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
static/img/use/zano-trade/new_order2.png
Normal file
BIN
static/img/use/zano-trade/new_order2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
BIN
static/img/use/zano-trade/order_book1.png
Normal file
BIN
static/img/use/zano-trade/order_book1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
BIN
static/img/use/zano-trade/trading-pairs.png
Normal file
BIN
static/img/use/zano-trade/trading-pairs.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Loading…
Add table
Reference in a new issue