Docusaurus core and preset: 2.4.1 → 3.9.2
This commit is contained in:
ravaga
parent
fcaf2371d1
commit
7fc2e54f7c
10 changed files with 10882 additions and 5502 deletions
|
|
@ -4,22 +4,6 @@ sidebar_position: 1
|
|||
|
||||
# Exchange integration full guide
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [Exchange integration full guide](#exchange-integration-full-guide)
|
||||
- [Table of Contents](#table-of-contents)
|
||||
- [Introduction](#introduction)
|
||||
- [Custom transaction generation process and TSS](#custom-transaction-generation-process-and-tss)
|
||||
- [Creating a Wallet](#creating-a-wallet)
|
||||
- [Creating a Wallet from custom seed phrase](#creating-a-wallet-from-custom-seed-phrase)
|
||||
- [Seed phrase backup](#seed-phrase-backup)
|
||||
- [Receiving Money with Payment ID](#receiving-money-with-payment-id)
|
||||
- [Processing Incoming Transactions](#processing-incoming-transactions)
|
||||
- [Requesting Wallet Balance](#requesting-wallet-balance)
|
||||
- [Searching for Transactions in the Wallet](#searching-for-transactions-in-the-wallet)
|
||||
- [Transfer Coins](#transfer-coins)
|
||||
- [Legacy methods](#legacy-methods)
|
||||
|
||||
## Introduction
|
||||
|
||||
Zano is a privacy-oriented blockchain from the CryptoNote family, which makes working with the wallet somewhat different from traditional blockchains like Bitcoin or Ethereum. In this article, we will show how to work with the wallet and how to build multi-user custody on it.
|
||||
|
|
@ -80,17 +64,19 @@ After you have created a new wallet, run it in command line mode to save the see
|
|||
0.0 ZANO d6329b5b1f7c0805b5c345f4957554002a2f557845f64d7645dae0e051a6498a
|
||||
[Zano wallet ZxCk74]:
|
||||
|
||||
After the wallet has synchronized, enter the command **show_seed**. First, the wallet will ask for its own password for security reasons (the one you specified when creating the wallet). After this, you will be prompted to enter a special password that will protect your seed phrase. ([More about Secure Seed](https://docs.zano.org/docs/use/seed-phrase/)) If you leave this password empty, an unprotected seed phrase will be generated, and anyone who gains access to the seed phrase will be able to control all assets.
|
||||
After the wallet has synchronized, enter the command **show_seed**. First, the wallet will ask for its own password for security reasons (the one you specified when creating the wallet). After this, you will be prompted to enter a special password that will protect your seed phrase. ([More about Secure Seed](/docs/use/seed-phrase/)) If you leave this password empty, an unprotected seed phrase will be generated, and anyone who gains access to the seed phrase will be able to control all assets.
|
||||
|
||||
[Zano wallet ZxCk74]: show_seed
|
||||
Enter password to confirm operation:
|
||||
*****
|
||||
Please enter a password to secure this seed. Securing your seed is HIGHLY recommended. Leave password blank to stay unsecured.
|
||||
Remember, restoring a wallet from Secured Seed can only be done if you know its password.
|
||||
Enter seed password: **********
|
||||
Confirm seed password: **********
|
||||
heart eat cost little goodbye arrive commit dreamer stick reason freeze left okay cousin frustrate certainly focus town proud chin stretch difference easily content couple land
|
||||
[Zano wallet ZxCk74]:
|
||||
```
|
||||
[Zano wallet ZxCk74]: show_seed
|
||||
Enter password to confirm operation:
|
||||
*****
|
||||
Please enter a password to secure this seed. Securing your seed is HIGHLY recommended. Leave password blank to stay unsecured.
|
||||
Remember, restoring a wallet from Secured Seed can only be done if you know its password.
|
||||
Enter seed password: **********
|
||||
Confirm seed password: **********
|
||||
heart eat cost little goodbye arrive commit dreamer stick reason freeze left okay cousin frustrate certainly focus town proud chin stretch difference easily content couple land
|
||||
[Zano wallet ZxCk74]:
|
||||
```
|
||||
|
||||
!!! Be sure to save this seed phrase in a secure place. If the seed phrase is lost, the wallet may become impossible to restore, and all assets may be lost.
|
||||
|
||||
|
|
@ -102,7 +88,7 @@ Once you’ve backed up your seed phrase, you can launch the wallet in server mo
|
|||
|
||||
Each wallet file in Zano is always one address and one secret key (in fact, it's a two secrete keys, but this is not important in the context of this manual). Zano does not support HD wallets for a number of technical reasons. Instead, for multi-user support, a so-called **payment_id** is used, which is a special identifier associated with the user. Each incoming transaction that contains this payment_id is considered credited to the balance of this user. Typically, a **payment_id** is an 8-byte random number generated by an exchange (or another custody service). It can be up to 128 bytes, but it is usually 8 bytes.
|
||||
|
||||
**IMPORTANT**: Users should never "operate" their payment_id anywhere under any circumstances. Instead, an **integrated address** is used. An **integrated address** is a special address format that encodes the user's payment_id along with the base wallet address, eliminating errors or typos. To generate an integrated address, you can use the WALLET RPC API [make_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/make_integrated_address/) (similar API present in daemon [get_integrated_address](https://docs.zano.org/docs/build/rpc-api/daemon-rpc-api/get_integrated_address) ):
|
||||
**IMPORTANT**: Users should never "operate" their payment_id anywhere under any circumstances. Instead, an **integrated address** is used. An **integrated address** is a special address format that encodes the user's payment_id along with the base wallet address, eliminating errors or typos. To generate an integrated address, you can use the WALLET RPC API [make_integrated_address](/docs/build/rpc-api/wallet-rpc-api/make_integrated_address/) (similar API present in daemon [get_integrated_address](/docs/build/rpc-api/daemon-rpc-api/get_integrated_address) ):
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -127,13 +113,13 @@ Each wallet file in Zano is always one address and one secret key (in fact, it's
|
|||
```
|
||||
|
||||
An address that starts with a lowercase letter "i" is an **Integrated Address**. It is always longer than a regular address and looks something like this: "iZ2EEMZWeKBRvbHrvebi5fgBLXDWukJ3VRXk6PENQ4orUTRfh11EHjCgCBxokeg5FEPHumvqJ76ikKHnD43iGjsECvV53PeAEkM3CLGRmST3". Only such an address can be shown to the user as their own deposit address. Transactions sent to this address will always have the payment_id specified when creating the address.
|
||||
Note: if **payment_id** is empty during the call of [make_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/make_integrated_address/) then it’s generated as random of 8 bytes, please use this with caution since it might not be safe to use without potential collision verification (ie check every newly generated payment_id against existing users).
|
||||
Note: if **payment_id** is empty during the call of [make_integrated_address](/docs/build/rpc-api/wallet-rpc-api/make_integrated_address/) then it’s generated as random of 8 bytes, please use this with caution since it might not be safe to use without potential collision verification (ie check every newly generated payment_id against existing users).
|
||||
|
||||
## Processing Incoming Transactions
|
||||
|
||||
There are several ways to get information about transactions for a Zano wallet. We will review most convenient and also mention other legacy approaches at the end.
|
||||
|
||||
The main method for obtaining transaction history information is [get_recent_txs_and_info2](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/). In the example below, we removed excessive and irrelevant for this article information from the response and left only those fields that are essential for processing custody.
|
||||
The main method for obtaining transaction history information is [get_recent_txs_and_info2](/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/). In the example below, we removed excessive and irrelevant for this article information from the response and left only those fields that are essential for processing custody.
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -210,7 +196,7 @@ Response:
|
|||
}
|
||||
```
|
||||
|
||||
You can read the transaction feed either from the oldest to the most recent (set "**order**" to "**FROM_END_TO_BEGIN**"), or vice versa - from the most recent to the oldest (set "**order**" to "**FROM_BEGIN_TO_END**"). Generally, when doing custody, you read the transaction feed from the wallet starting from the oldest transactions and read the entire history to the most recent transactions. To do this, set the "**order**" field in the request to "**FROM_END_TO_BEGIN**". If the response returns fewer elements than the "count" specified in the request (in our example, this is 100), it means that you have read the entire transaction history from end to the most recent transactions. If not, you need to continue calling [get_recent_txs_and_info2](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/) in such a way that each subsequent call passes the "**offset**" value, which indicates how many elements have already been read from the feed (if using the **FROM_END_TO_BEGIN** mode, you can also use the value from the "**transfer_internal_index**" field in the most recent element of the "transfers" array). Keep in mind that the number of transactions you count as transfers to users may differ from the total number of transactions read due to some transactions that you may decide to ignore as non-legit.
|
||||
You can read the transaction feed either from the oldest to the most recent (set "**order**" to "**FROM_END_TO_BEGIN**"), or vice versa - from the most recent to the oldest (set "**order**" to "**FROM_BEGIN_TO_END**"). Generally, when doing custody, you read the transaction feed from the wallet starting from the oldest transactions and read the entire history to the most recent transactions. To do this, set the "**order**" field in the request to "**FROM_END_TO_BEGIN**". If the response returns fewer elements than the "count" specified in the request (in our example, this is 100), it means that you have read the entire transaction history from end to the most recent transactions. If not, you need to continue calling [get_recent_txs_and_info2](/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/) in such a way that each subsequent call passes the "**offset**" value, which indicates how many elements have already been read from the feed (if using the **FROM_END_TO_BEGIN** mode, you can also use the value from the "**transfer_internal_index**" field in the most recent element of the "transfers" array). Keep in mind that the number of transactions you count as transfers to users may differ from the total number of transactions read due to some transactions that you may decide to ignore as non-legit.
|
||||
|
||||
The list of transactions is in the "transfers" array. The response header has a **pi.current_height field**, which indicates the current highest known blockchain height to the wallet. Relative to this number, you will calculate the number of confirmations for each transaction in the "**transfers**" array (specifically, subtract the "**height**" field from **pi.current_height field**).
|
||||
|
||||
|
|
@ -244,7 +230,7 @@ IMPORTANT:
|
|||
- Do not account deposits for transactions that have not reached 10 confirmations. Sometimes the network undergoes reorganisation among the last 2-3 blocks. This is normal, and within this number of confirmations, the transaction sequence may change, including the removal of transactions that previously appeared with 2-3 confirmations. Read the history only until those transactions that got 10 confirmations, when it comes to transactions that haven't mach this number of transactions - re-read **get_recent_txs_and_info2** until you see those transactions in response with 10 confirmations. Make your code fully aware of such situations and re-read history for those transactions.
|
||||
- Do not count on **"remote_addresses"** or **"remote_aliases"** fields, as those fields are optional and might be or **might not be present** in transactions, due to privacy nature of transactions.
|
||||
- Consider only those **asset_id** that you know, and ignore any others.
|
||||
- When depositing an asset, ensure the correct interpretation of the decimal point, as it may differ for each asset. You can request asset details via the DAEMON RPC API [get_asset_info](https://docs.zano.org/docs/build/rpc-api/daemon-rpc-api/get_asset_info/). Native coins have the asset_id d6329b5b1f7c0805b5c345f4957554002a2f557845f64d7645dae0e051a6498a and should always be deposited for.
|
||||
- When depositing an asset, ensure the correct interpretation of the decimal point, as it may differ for each asset. You can request asset details via the DAEMON RPC API [get_asset_info](/docs/build/rpc-api/daemon-rpc-api/get_asset_info/). Native coins have the asset_id d6329b5b1f7c0805b5c345f4957554002a2f557845f64d7645dae0e051a6498a and should always be deposited for.
|
||||
- A transaction may contain both incoming and outgoing subtransfers. Check the **is_income** field for each element.
|
||||
- We also recommend specifying the **"exclude_unconfirmed": true** field in your request, as unconfirmed transactions are not important in the context of custody.
|
||||
- Do not deposit transactions where the "**unlock_time**" field is different from 0, as such transactions may be locked for a long period.
|
||||
|
|
@ -252,7 +238,7 @@ IMPORTANT:
|
|||
|
||||
## Requesting Wallet Balance
|
||||
|
||||
To request the current balance of the wallet, you can use the WALLET RPC API [getbalance](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/getbalance).
|
||||
To request the current balance of the wallet, you can use the WALLET RPC API [getbalance](/docs/build/rpc-api/wallet-rpc-api/getbalance).
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -311,7 +297,7 @@ Response:
|
|||
|
||||
Response returns a list of assets that are present in the wallet, and for each asset, there are details ("**asset_info**") as well as the balances in the "**total**" and "**unlocked**" fields. The "**unlocked**" field shows how many coins are currently available for sending (this does not include incoming transactions that have not reached 10 confirmations, for example change). The "**total**" field shows all assets, including those that have not reached the required number of confirmations.
|
||||
|
||||
IMPORTANT: Assets not included in the public or private whitelist do not appear in the [getbalance](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/getbalance) response. There is a public whitelist maintained by the project community, as well as a private whitelist for each wallet, which is stored in the wallet's file. If you want to see the balance of an asset not present in the public whitelist, you need to call the WALLET RPC API [assets_whitelist_add](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/assets_whitelist_add):
|
||||
IMPORTANT: Assets not included in the public or private whitelist do not appear in the [getbalance](/docs/build/rpc-api/wallet-rpc-api/getbalance) response. There is a public whitelist maintained by the project community, as well as a private whitelist for each wallet, which is stored in the wallet's file. If you want to see the balance of an asset not present in the public whitelist, you need to call the WALLET RPC API [assets_whitelist_add](/docs/build/rpc-api/wallet-rpc-api/assets_whitelist_add):
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -345,7 +331,7 @@ Response:
|
|||
|
||||
## Searching for Transactions in the Wallet
|
||||
|
||||
You can also search for an arbitrary transaction by its tx_id or using other available parameters in the API [search_for_transactions2](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/search_for_transactions2):
|
||||
You can also search for an arbitrary transaction by its tx_id or using other available parameters in the API [search_for_transactions2](/docs/build/rpc-api/wallet-rpc-api/search_for_transactions2):
|
||||
|
||||
```json
|
||||
{
|
||||
|
|
@ -366,7 +352,7 @@ You can also search for an arbitrary transaction by its tx_id or using other ava
|
|||
|
||||
## Transfer Coins
|
||||
|
||||
Transferring coins is done using the WALLET RPC API [transfer](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/transfer/):
|
||||
Transferring coins is done using the WALLET RPC API [transfer](/docs/build/rpc-api/wallet-rpc-api/transfer/):
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -398,10 +384,10 @@ Response:
|
|||
}
|
||||
```
|
||||
|
||||
It is good practice to check that your balance is sufficient for sending the desired asset before making a transfer; otherwise, there may be an error in sending the transaction. Sometimes, you need to wait up to 10 minutes to gather the required number of confirmations for the change (if the value in the unlocked field is still less than the value in the total field in the balances response). If you received a transaction hash in the “**tx_hash**” field, it means the transaction has been successfully created and accepted by the daemon for relay across the network. Once this transaction is included in a block and starts getting confirmations, you will see it in the results of [get_recent_txs_and_info2](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/) (the **is_income** field will be false).
|
||||
It is good practice to check that your balance is sufficient for sending the desired asset before making a transfer; otherwise, there may be an error in sending the transaction. Sometimes, you need to wait up to 10 minutes to gather the required number of confirmations for the change (if the value in the unlocked field is still less than the value in the total field in the balances response). If you received a transaction hash in the “**tx_hash**” field, it means the transaction has been successfully created and accepted by the daemon for relay across the network. Once this transaction is included in a block and starts getting confirmations, you will see it in the results of [get_recent_txs_and_info2](/docs/build/rpc-api/wallet-rpc-api/get_recent_txs_and_info2/) (the **is_income** field will be false).
|
||||
|
||||
|
||||
**IMPORTANT**: Before sending, be sure to validate address and also check that the address you are sending to does not belong to your wallet, even if it is an integrated address of another user on your base wallet. You cannot send transactions between users within the same wallet. To validate address and check the base wallet address from integrated address, you need to call the WALLET RPC API [split_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/split_integrated_address):
|
||||
**IMPORTANT**: Before sending, be sure to validate address and also check that the address you are sending to does not belong to your wallet, even if it is an integrated address of another user on your base wallet. You cannot send transactions between users within the same wallet. To validate address and check the base wallet address from integrated address, you need to call the WALLET RPC API [split_integrated_address](/docs/build/rpc-api/wallet-rpc-api/split_integrated_address):
|
||||
|
||||
```json
|
||||
Request:
|
||||
|
|
@ -430,5 +416,5 @@ You need to first check that API managed to parse address, if **"standard_addres
|
|||
|
||||
## Legacy methods
|
||||
|
||||
[get_bulk_payments](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/get_bulk_payments)
|
||||
[get_payments](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/get_payments)
|
||||
[get_bulk_payments](/docs/build/rpc-api/wallet-rpc-api/get_bulk_payments)
|
||||
[get_payments](/docs/build/rpc-api/wallet-rpc-api/get_payments)
|
||||
|
|
|
|||
|
|
@ -8,25 +8,25 @@ sidebar_position: 3
|
|||
|
||||
Original Zano whitepaper, describes general concepts used in project.
|
||||
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/Zano_WP_latest.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/Zano_WP_latest.pdf](https://github.com/hyle-team/docs/blob/master/zano/Zano_WP_latest.pdf)
|
||||
|
||||
### PoS Analysis and improvements proposal (2019)
|
||||
|
||||
With help of Maxwell Sanches we come up with more effective PoS model and upgraded the network, this document hold details of this research and improvement.
|
||||
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/arch/PoS_Analysis_and_improvements_proposal.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/arch/PoS_Analysis_and_improvements_proposal.pdf](https://github.com/hyle-team/docs/blob/master/zano/arch/PoS_Analysis_and_improvements_proposal.pdf)
|
||||
|
||||
### Auditable wallets in CryptoNote (2020)
|
||||
|
||||
This article explores several possible implementations of extending CryptoNote 2.0 with full-scale wallets auditing
|
||||
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/arch/Auditing%20wallets%20in%20CryptoNote.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/arch/Auditing%20wallets%20in%20CryptoNote.pdf](https://github.com/hyle-team/docs/blob/master/zano/arch/Auditing%20wallets%20in%20CryptoNote.pdf)
|
||||
|
||||
### Zarcanum: A Proof-of-Stake Scheme for Confidential Transactions with Hidden Amounts (2021)
|
||||
|
||||
Presenting a Proof-of-Stake mining scheme that does not reveal amounts and is compatible with ring confidential transactions. Paper also introduces an extension to the Bulletproofs+ protocol that allows range proofs on double-blinded commitments, with corresponding security statements.
|
||||
|
||||
<https://eprint.iacr.org/2021/1478>
|
||||
[https://eprint.iacr.org/2021/1478](https://eprint.iacr.org/2021/1478)
|
||||
|
||||
### Zano: Confidential Assets Scheme for RingCT and Zarcanum (2024)
|
||||
|
||||
|
|
@ -36,13 +36,13 @@ Confidential Transactions scheme. Our approach preserves public verifiability th
|
|||
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>
|
||||
[https://hyle-team.github.io/docs/zano/CA_paper/Zano_CA_for_RingCT_and_Zarcanum_v1.1.pdf](https://hyle-team.github.io/docs/zano/CA_paper/Zano_CA_for_RingCT_and_Zarcanum_v1.1.pdf)
|
||||
|
||||
### d/v-CLSAG: Extension for Concise Linkable Spontaneous Anonymous Group Signatures (2024)
|
||||
|
||||
Extension for the CLSAG (Concise Linkable Spontaneous Anonymous Group Signatures)
|
||||
|
||||
<https://eprint.iacr.org/2025/1513>
|
||||
[https://eprint.iacr.org/2025/1513](https://eprint.iacr.org/2025/1513)
|
||||
|
||||
<br />
|
||||
<br />
|
||||
|
|
@ -56,13 +56,13 @@ Introducing a solution that allows users to issue tokens that work inside Zano b
|
|||
|
||||
Note: this paper used one of the early approach to implementing assets, when each asset has unique scalar identifier but common asset-type generator, it's now oudated.
|
||||
|
||||
<https://raw.githubusercontent.com/hyle-team/docs/master/zano/arch/Zano_tokenization_platform.pdf>
|
||||
[https://raw.githubusercontent.com/hyle-team/docs/master/zano/arch/Zano_tokenization_platform.pdf](https://raw.githubusercontent.com/hyle-team/docs/master/zano/arch/Zano_tokenization_platform.pdf)
|
||||
|
||||
### Zano: confidential assets scheme (2022 - DRAFT)
|
||||
|
||||
Paper describes a practical way of implementing confidential assets (a.k.a. tokens) in Zano with unlimited decoy mixing capability and hidden amounts as an extension to the Ring Confidential Transactions scheme
|
||||
|
||||
<https://raw.githubusercontent.com/hyle-team/docs/master/zano/tokens_maths_paper/Zano__confidential_assets_with_hidden_amounts_DRAFT.pdf>
|
||||
[https://raw.githubusercontent.com/hyle-team/docs/master/zano/tokens_maths_paper/Zano__confidential_assets_with_hidden_amounts_DRAFT.pdf](https://raw.githubusercontent.com/hyle-team/docs/master/zano/tokens_maths_paper/Zano__confidential_assets_with_hidden_amounts_DRAFT.pdf)
|
||||
|
||||
|
||||
|
||||
|
|
@ -72,10 +72,10 @@ The following papers represent research toward a novel logarithmic-sized linkabl
|
|||
|
||||
- Lin2-Xor Lemma and Log-size Linkable Ring Signature (2020)
|
||||
In this paper we introduce a novel method for constructing an efficient linkable ring signature without a trusted setup which is logarithmic in the size of the signer anonymity set, its verification complexity is linear in the anonymity set size
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/arch/Lin2-Xor_Lemma_and-Log-size_Linkable_Ring_Signature.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/arch/Lin2-Xor_Lemma_and-Log-size_Linkable_Ring_Signature.pdf](https://github.com/hyle-team/docs/blob/master/zano/arch/Lin2-Xor_Lemma_and-Log-size_Linkable_Ring_Signature.pdf)
|
||||
- Hidden amounts scheme on the base of a ring signature for independent generators (2021)
|
||||
Draft of a hidden amounts scheme based on Lin2-Xor Linkable Ring Signature
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/arch/Hidden%20amounts%20scheme%20v6%20Sokolov.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/arch/Hidden%20amounts%20scheme%20v6%20Sokolov.pdf](https://github.com/hyle-team/docs/blob/master/zano/arch/Hidden%20amounts%20scheme%20v6%20Sokolov.pdf)
|
||||
- Log-size Linkable Ring Signature and Hidden Amounts integrated listing (2021)
|
||||
Unified pseudo-code listing for the Lin2-Xor Signature and Hidden Amounts schemes
|
||||
<https://github.com/hyle-team/docs/blob/master/zano/arch/Log-size%20Linkable%20Ring%20Signature%20and%20Hid-den%20Amounts%20integrated%20listing%20v3.pdf>
|
||||
[https://github.com/hyle-team/docs/blob/master/zano/arch/Log-size%20Linkable%20Ring%20Signature%20and%20Hid-den%20Amounts%20integrated%20listing%20v3.pdf](https://github.com/hyle-team/docs/blob/master/zano/arch/Log-size%20Linkable%20Ring%20Signature%20and%20Hid-den%20Amounts%20integrated%20listing%20v3.pdf)
|
||||
|
|
|
|||
|
|
@ -95,7 +95,7 @@ Since Ubuntu doesn't come with AMD's OpenCL driver, which is necessary for minin
|
|||
|
||||
### Step 4: Starting Wildrig Miner
|
||||
|
||||
Once your node is fully synced, stop it (ctl+c). In the same terminal, restart `zanod` with the following flags, substituting your wallet address for "<YOUR_WALLET_ID>"
|
||||
Once your node is fully synced, stop it (ctl+c). In the same terminal, restart `zanod` with the following flags, substituting your wallet address for `<YOUR_WALLET_ID>`
|
||||
|
||||
```
|
||||
./zanod --stratum --stratum-bind-port=11555 --stratum-miner-address=<YOUR_WALLET_ID>
|
||||
|
|
@ -109,7 +109,7 @@ The daemon should start, displaying this screen.
|
|||
|
||||
You're ready to begin mining.
|
||||
|
||||
Return to your wildrig directory and run Wildrig, again substituting your wallet address for "<YOUR_WALLET_ID>" :[^5]
|
||||
Return to your wildrig directory and run Wildrig, again substituting your wallet address for `<YOUR_WALLET_ID>` :[^5]
|
||||
|
||||
```
|
||||
cd wildrig
|
||||
|
|
|
|||
|
|
@ -36,13 +36,13 @@ nano ZANO-SOLO.sh
|
|||
|
||||
Note the contents. They provide the basic instructions for setting up TT-Miner (though they will require slight modifications):
|
||||
|
||||
> rem * Your call to start the ZANO stratrum should look like this. You have to replace <YOUR_WALLET_ID>
|
||||
> rem * with the address of your ZANO-Wallet
|
||||
>
|
||||
> rem zanod.exe --stratum --stratum-miner-address=<YOUR_WALLET_ID> --stratum-bind-port=11555
|
||||
> rem \* Your call to start the ZANO stratrum should look like this. You have to replace `<YOUR_WALLET_ID>`
|
||||
> rem \* with the address of your ZANO-Wallet
|
||||
>
|
||||
> rem zanod.exe --stratum --stratum-miner-address=`<YOUR_WALLET_ID>` --stratum-bind-port=11555
|
||||
>
|
||||
> rem TT commandline
|
||||
> ./TT-Miner -luck -coin ZANO -P <YOUR_WORKER_NAME>@127.0.0.1:11555
|
||||
> ./TT-Miner -luck -coin ZANO -P `<YOUR_WORKER_NAME>`@127.0.0.1:11555
|
||||
> pause
|
||||
|
||||
Exit Nano (`ctl+x`), but leave the terminal and directory open; we'll return to it soon.
|
||||
|
|
@ -88,7 +88,7 @@ nvcc --version
|
|||
|
||||
Once your node is fully synced, stop it (`ctl+c`). In the same terminal, restart `zanod` with the following flags, taken from the above `ZANO-SOLO.sh` file:
|
||||
|
||||
```
|
||||
```bash
|
||||
./zanod --stratum --stratum-miner-address=<YOUR_WALLET_ID> --stratum-bind-port=11555
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Zano Companion is a Metamask-like browser extension that enables authentication
|
|||
|
||||
It's your gateway to the broader Zano ecosystem!
|
||||
|
||||
::info
|
||||
:::info
|
||||
|
||||
Zano Companion is also directly integrated into the Zano Mobile Wallet app. To access it, simply click on "Browser" and navigate to the Zano dApp you wish to use.
|
||||
|
||||
|
|
|
|||
|
|
@ -202,6 +202,4 @@ 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
|
||||
sweep_below `<mixin_count>` `<amount_lower_limit>` [payment_id]: Tries to transfer all coins with amount below the given limit to the given address
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
const lightCodeTheme = require("prism-react-renderer/themes/github");
|
||||
const darkCodeTheme = require("prism-react-renderer/themes/dracula");
|
||||
const math = require("remark-math");
|
||||
const katex = require("rehype-katex");
|
||||
import {themes as prismThemes} from 'prism-react-renderer';
|
||||
import remarkMath from 'remark-math';
|
||||
import rehypeKatex from 'rehype-katex';
|
||||
|
||||
const config = {
|
||||
title: "Zano Docs",
|
||||
|
|
@ -12,7 +11,12 @@ const config = {
|
|||
baseUrl: "/",
|
||||
|
||||
onBrokenLinks: "throw",
|
||||
onBrokenMarkdownLinks: "warn",
|
||||
|
||||
markdown: {
|
||||
hooks: {
|
||||
onBrokenMarkdownLinks: "warn",
|
||||
},
|
||||
},
|
||||
|
||||
i18n: {
|
||||
defaultLocale: "en",
|
||||
|
|
@ -24,12 +28,12 @@ const config = {
|
|||
"classic",
|
||||
{
|
||||
docs: {
|
||||
sidebarPath: require.resolve("./sidebars.js"),
|
||||
remarkPlugins: [math],
|
||||
rehypePlugins: [katex],
|
||||
sidebarPath: './sidebars.js',
|
||||
remarkPlugins: [remarkMath],
|
||||
rehypePlugins: [rehypeKatex],
|
||||
},
|
||||
theme: {
|
||||
customCss: require.resolve("./src/css/custom.css"),
|
||||
customCss: './src/css/custom.css',
|
||||
},
|
||||
},
|
||||
],
|
||||
|
|
@ -192,8 +196,8 @@ const config = {
|
|||
copyright: `Copyright © ${new Date().getFullYear()} Zano.org`,
|
||||
},
|
||||
prism: {
|
||||
theme: lightCodeTheme,
|
||||
darkTheme: darkCodeTheme,
|
||||
theme: prismThemes.github,
|
||||
darkTheme: prismThemes.dracula,
|
||||
},
|
||||
algolia: {
|
||||
appId: 'GZR5BV1JNU',
|
||||
|
|
@ -203,4 +207,4 @@ const config = {
|
|||
},
|
||||
};
|
||||
|
||||
module.exports = config;
|
||||
export default config;
|
||||
|
|
|
|||
16206
package-lock.json
generated
16206
package-lock.json
generated
File diff suppressed because it is too large
Load diff
24
package.json
24
package.json
|
|
@ -14,19 +14,21 @@
|
|||
"write-heading-ids": "docusaurus write-heading-ids"
|
||||
},
|
||||
"dependencies": {
|
||||
"@docusaurus/core": "2.4.1",
|
||||
"@docusaurus/preset-classic": "2.4.1",
|
||||
"@mdx-js/react": "^1.6.22",
|
||||
"clsx": "^1.2.1",
|
||||
"hast-util-is-element": "^1.1.0",
|
||||
"prism-react-renderer": "^1.3.5",
|
||||
"react": "^17.0.2",
|
||||
"react-dom": "^17.0.2",
|
||||
"rehype-katex": "^5.0.0",
|
||||
"remark-math": "^3.0.1"
|
||||
"@docusaurus/core": "3.9.2",
|
||||
"@docusaurus/preset-classic": "3.9.2",
|
||||
"@mdx-js/react": "^3.1.1",
|
||||
"clsx": "^2.1.1",
|
||||
"hast-util-is-element": "^3.0.0",
|
||||
"prism-react-renderer": "^2.4.1",
|
||||
"react": "^18.3.1",
|
||||
"react-dom": "^18.3.1",
|
||||
"rehype-katex": "^7.0.1",
|
||||
"remark-math": "^6.0.0"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@docusaurus/module-type-aliases": "2.4.1"
|
||||
"@docusaurus/module-type-aliases": "3.9.2",
|
||||
"@docusaurus/tsconfig": "3.9.2",
|
||||
"@docusaurus/types": "3.9.2"
|
||||
},
|
||||
"browserslist": {
|
||||
"production": [
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ const content = [
|
|||
title: "Getting Started",
|
||||
items: [
|
||||
{
|
||||
link: "docs/use/overview",
|
||||
link: "/docs/use/overview",
|
||||
linkText: "Setup your environment",
|
||||
content:
|
||||
"Kickstart your Zano experience. Start with GUI wallet or get hands-on with the Zano CLI and set up your local development environment. Whether you're a developer or an enthusiast, this is your first step.",
|
||||
|
|
@ -38,13 +38,13 @@ const content = [
|
|||
title: "Mine and Stake",
|
||||
items: [
|
||||
{
|
||||
link: "docs/mine/overview",
|
||||
link: "/docs/mine/overview",
|
||||
linkText: "Mining Guide",
|
||||
content:
|
||||
"Venture into Zano's dual earning avenues. Learn how to mine Zano efficiently, ensuring optimal returns and network security.",
|
||||
},
|
||||
{
|
||||
link: "docs/stake/overview",
|
||||
link: "/docs/stake/overview",
|
||||
linkText: "Staking Guide",
|
||||
content:
|
||||
"Explore the intricacies of staking on the Zano platform. Understand the rewards, risks, and best practices to maximize your stake's potential.",
|
||||
|
|
@ -55,13 +55,13 @@ const content = [
|
|||
title: "Build on Zano",
|
||||
items: [
|
||||
{
|
||||
link: "docs/build/rpc-api/overview",
|
||||
link: "/docs/build/rpc-api/overview",
|
||||
linkText: "Development APIs",
|
||||
content:
|
||||
"Harness Zano's powerful suite of APIs. Tailored for developers looking to innovate and integrate with the Zano platform, these comprehensive guides will get you started.",
|
||||
},
|
||||
{
|
||||
link: "docs/build/confidential-assets/overview",
|
||||
link: "/docs/build/confidential-assets/overview",
|
||||
linkText: "Zano Confidential Assets",
|
||||
content:
|
||||
"Deploy a tokens with native privacy features. Experiment, test, and deploy Confidential Assets within the Zano network with ease. Perfect for developers new to privacy coins, or those looking to test new concepts.",
|
||||
|
|
@ -73,22 +73,22 @@ const content = [
|
|||
const links = [
|
||||
{
|
||||
name: "Developers",
|
||||
link: "docs/build/overview",
|
||||
link: "/docs/build/overview",
|
||||
Icon: devIcon,
|
||||
},
|
||||
{
|
||||
name: "Users",
|
||||
link: "docs/use/overview",
|
||||
link: "/docs/use/overview",
|
||||
Icon: userIcon,
|
||||
},
|
||||
{
|
||||
name: "Miners",
|
||||
link: "docs/mine/overview",
|
||||
link: "/docs/mine/overview",
|
||||
Icon: mineIcon,
|
||||
},
|
||||
{
|
||||
name: "Stakers",
|
||||
link: "docs/stake/overview",
|
||||
link: "/docs/stake/overview",
|
||||
Icon: stakeIcon,
|
||||
},
|
||||
];
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue