lthn/docs
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'hyle-team:main' into main

Browse source
This commit is contained in:
Gonbatfire 2024-09-27 16:03:24 -03:00 • committed by GitHub
commit d25e24fe2d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
20 changed files with 359 additions and 129 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/build/libraries/_category_.json vendored Normal file
View file

@ -0,0 +1,4 @@
{
"label": "Zano Libraries",
"position": 2
}

33
docs/build/libraries/overview.md vendored Normal file
View file

@ -0,0 +1,33 @@
# List of Libraries
## Zano Web3 Library (TypeScript)
Zano Web3 TS is a TypeScript library designed to facilitate interaction with the Zano Companion extension within web browsers. It enables connection to user extensions, handles authentication, and manages wallet credentials, plus it includes a server component for RPC interactions with the Zano wallet and daemon.
Github: https://github.com/hyle-team/zano_web3
Package: https://www.npmjs.com/package/zano_web
## Native Zano Wallet for IOS/Android (C++)
This C++ library provides tools for integrating Zano's wallet into native iOS and Android applications, offering a robust solution for mobile app developers working with Zano's technology. All API implemented as a plain text calls that works with JSON format, which make this library a perfect framework agnostic tool for supporting Zano.
Github: https://github.com/hyle-team/zano_native_lib
## Flutter/Android Zano Wallet Plugin (Dart)
This Dart library is tailored for integrating Zano Wallet functionalities into mobile and web applications using the Flutter framework or native Android development with Dart, making it ideal for mobile developers.
Github: https://github.com/hyle-team/zano_plugin
## SWIFT package manager plugin for Native Wallet Library for IOS/Android (C++)
A dedicated iOS library that allows for the integration of Zano's functionalities specifically within iOS applications, ensuring smooth implementation of Zano features on Apple devices.
Github: https://github.com/hyle-team/zano_native_lib_package_ios
## Zano Node Utils (JavaScript)
This utility library supports various backend operations used by mining pools
Github: https://github.com/hyle-team/zano-node-util

39
docs/build/overview.md vendored
View file

@ -4,8 +4,41 @@ sidebar_position: 1
# Building with Zano
Welcome to the "Build with Zano" page — your key resource to initiate and develop projects on the Zano platform. As we relentlessly advance the frontiers of digital privacy, we're here to provide you with the tools and insights necessary to ensure your project not only stands out but also integrates seamlessly with the Zano ecosystem.
## Starting Your Development Journey
Kickstart your journey with our RPC API Guide. Here, you'll gain a comprehensive understanding from the [Overview](rpc-api/overview.md), and delve deeper into the specifics of [How to call the API](rpc-api/how-to-call-api.md). Whether your focus is on the [Daemon RPC API](rpc-api/daemon-rpc-api/get_alias_by_address.md) or the [Wallet RPC API](rpc-api/wallet-rpc-api/get_bulk_payments.md), our guide ensures clarity at every step.
### RPC API Guide
If launching your own project centered around private transactions is your goal, our Confidential Assets section provides a clear [Overview](confidential-assets/overview) along with detailed Methods to give your initiative a solid foundation.
Kickstart your journey with our RPC API Guide [Overview](rpc-api/overview.md). Here, you'll gain a comprehensive understanding from the Overview, and delve deeper into the specifics of [How to call the API](rpc-api/how-to-call-api.md). Whether your focus is on the [Daemon RPC API](rpc-api/daemon-rpc-api/get_alias_by_address.md) or the [Wallet RPC API](rpc-api/wallet-rpc-api/get_bulk_payments.md), our guide ensures clarity at every step.
### Confidential Assets
If launching your own project centered around private transactions is your goal, our [Confidential Assets](confidential-assets/overview) section provides detailed methods to give your initiative a solid foundation.
## Exchange Listing Guidelines
If you're looking to list your project or Zano assets on exchanges, it's crucial to follow specific guidelines to ensure compliance and success in your listings. We provide a [detailed set of guidelines](exchange-guidelines/multi-assets-custody-guide) that cover everything from technical requirements to compliance with financial regulations.
## Tools and Resources
We provide a variety of tools and [libraries](libraries/overview.md) to assist you in building robust applications:
- **Zano Web3 TS**: This TypeScript library now includes a server component for RPC interactions, simplifying the connection to Zano wallets and handling transactions directly from web applications.
- **Mobile Libraries** (Flutter/Android & iOS): These have been updated to offer more robust features for mobile developers, enabling seamless integration into a wider range of applications.
- **Native Crypto Library** for iOS/Android (C++): Updated to provide essential cryptographic functionalities needed for secure and reliable app development.
## Community and Support
Join our vibrant community of developers and privacy enthusiasts:
- **Discussions**: Engage with other developers, share your projects, and get feedback in community dev channels in [discord](https://discord.gg/wE3rmYY) and [telegram](https://t.me/zanocoin).
- **Technical Support**: Our technical team is ready to assist you with any questions or challenges you may encounter.
## Contributing to Zano
We encourage contributions from developers of all skill levels. If you're interested in contributing to the Zano project, check out our guidelines on how to contribute effectively. Your innovations and contributions help us continue to enhance the security and functionality of the Zano platform.
## Stay Updated
Keep up with the latest updates and enhancements by visiting our official [blog](https://blog.zano.org) and subscribing to our newsletter. As Zano continues to evolve, we remain committed to providing the community with cutting-edge tools and support to build secure and private digital solutions.
Embark on your development journey with Zano and leverage our comprehensive resources to build something truly impactful in the realm of digital privacy.

55
docs/build/rpc-api/daemon-rpc-api/decrypt_tx_details.md vendored Normal file
View file

@ -0,0 +1,55 @@
Decrypts transaction private information. Should be used only with your own local daemon for security reasons.
URL: ```http:://127.0.0.1:11211/json_rpc```
### Request:
```json
{
"id": 0,
"jsonrpc": "2.0",
"method": "decrypt_tx_details",
"params": {
"outputs_addresses": ["ZxDNaMeZjwCjnHuU5gUNyrP1pM3U5vckbakzzV6dEHyDYeCpW8XGLBFTshcaY8LkG9RQn7FsQx8w2JeJzJwPwuDm2NfixPAXf","ZxBvJDuQjMG9R2j4WnYUhBYNrwZPwuyXrC7FHdVmWqaESgowDvgfWtiXeNGu8Px9B24pkmjsA39fzSSiEQG1ekB225ZnrMTBp"],
"tx_blob": "ewogICJ2ZXJzaW9uIjogMSwgC....iAgInZpbiI6IFsgewogICAgIC",
"tx_id": "a6e8da986858e6825fce7a192097e6afae4e889cabe853a9c29b964985b23da8",
"tx_secret_key": "2e0b840e70dba386effd64c5d988622dea8c064040566e6bf035034cbb54a5c08"
}
}
```
### Request description:
```
"outputs_addresses": Address of each of tx's output. Order is important and should correspond to order of tx's outputs. Empty strings are ignored.
"tx_blob": [or] base64-encoded or hex-encoded tx blob. Can be ommited if tx_id is provided.
"tx_id": [either] ID for a transaction if it is already in the blockchain. Can be ommited if tx_blob is provided.
"tx_secret_key": Hex-encoded transaction secret key.
```
### Response:
```json
{
"id": 0,
"jsonrpc": "2.0",
"result": {
"decoded_outputs": [{
"address": "ZxBvJDuQjMG9R2j4WnYUhBYNrwZPwuyXrC7FHdVmWqaESgowDvgfWtiXeNGu8Px9B24pkmjsA39fzSSiEQG1ekB225ZnrMTBp",
"amount": 10000000000000,
"asset_id": "cc608f59f8080e2fbfe3c8c80eb6e6a953d47cf2d6aebd345bada3a1cab99852",
"out_index": 1
}],
"status": "OK",
"tx_in_json": "ewogICJ2ZXJzaW9uIjogMSwgC....iAgInZpbiI6IFsgewogICAgIC",
"verified_tx_id": "a6e8da986858e6825fce7a192097e6afae4e889cabe853a9c29b964985b23da8"
}
}
```
### Response description:
```
"decoded_outputs": Transaction's decoded outputs
"address": Destination address.
"amount": Amount begin transferred.
"asset_id": Asset id.
"out_index": Index of the corresponding output in the transaction.
"status": Status code of operation, OK if success
"tx_in_json": Serialized transaction represented in JSON, encoded in Base64.
"verified_tx_id": (Re)calculated transaction id. Can be used in third-party proof generation.
```

55
docs/build/rpc-api/daemon-rpc-api/find_outs_in_recent_blocks.md vendored Normal file
View file

@ -0,0 +1,55 @@
Retrieves information about outputs in recent blocks that are targeted for the given address with the corresponding secret view key.
URL: ```http:://127.0.0.1:11211/json_rpc```
### Request:
```json
{
"id": 0,
"jsonrpc": "2.0",
"method": "find_outs_in_recent_blocks",
"params": {
"address": "ZxCSpsGGeJsS8fwvQ4HktDU3qBeauoJTR6j73jAWWZxFXdF7XTbGm4YfS2kXJmAP4Rf5BVsSQ9iZ45XANXEYsrLN2L2W77dH7",
"blocks_limit": 1711021795,
"viewkey": "5fa8eaaf231a305053260ff91d69c6ef1ecbd0f5"
}
}
```
### Request description:
```
"address": Target address for which outputs are being searched
"blocks_limit": Block count limit. If 0, only the transaction pool will be searched. Maximum and default is 5.
"viewkey": Secret view key corresponding to the given address.
```
### Response:
```json
{
"id": 0,
"jsonrpc": "2.0",
"result": {
"blockchain_top_block_height": 2555000,
"blocks_limit": 5,
"outputs": [{
"amount": 1000000000000,
"asset_id": "cc4e69455e63f4a581257382191de6856c2156630b3fba0db4bdd73ffcfb36b6",
"output_tx_index": 2,
"tx_block_height": 2555000,
"tx_id": "a6e8da986858e6825fce7a192097e6afae4e889cabe853a9c29b964985b23da8"
}],
"status": "OK"
}
}
```
### Response description:
```
"blockchain_top_block_height": Height of the most recent block in the blockchain.
"blocks_limit": Used limit for block count.
"outputs": List of found outputs.
"amount": The amount of the output.
"asset_id": Asset ID of the output.
"output_tx_index": Index of the output in the transaction.
"tx_block_height": Block height where the transaction is present.
"tx_id": Transaction ID where the output is present, if found.
"status": Status of the call.
```

20
docs/build/rpc-api/daemon-rpc-api/get_asset_info.md vendored
View file

@ -26,11 +26,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_descriptor": {
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"status": "OK"
@ -40,14 +40,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
### Response description:
```
"asset_descriptor": Descriptor of the given asset.
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"status": Status of the call.
```

20
docs/build/rpc-api/daemon-rpc-api/get_assets_list.md vendored
View file

@ -29,11 +29,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
}],
"status": "OK"
@ -44,14 +44,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
```
"assets": List of assets registered in Zano blockchain
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"status": Status code of operation, OK if success
```

20
docs/build/rpc-api/wallet-rpc-api/assets_whitelist_add.md vendored
View file

@ -26,11 +26,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_descriptor": {
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"status": "OK"
@ -40,14 +40,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
### Response description:
```
"asset_descriptor": Details of the asset, recieved from node
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"status": Status of the asset
```

60
docs/build/rpc-api/wallet-rpc-api/assets_whitelist_get.md vendored
View file

@ -25,33 +25,33 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
}],
"local_whitelist": [{
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
}],
"own_assets": [{
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
}]
}
@ -61,33 +61,33 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
```
"global_whitelist": Global whitelist, well-known assets with adoption, mantained by the team and community
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"local_whitelist": Local whitelist, assets that hase been added to this wallet file manually(!)
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"own_assets": Own assets, the ones that is under control of this wallet
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
```

4
docs/build/rpc-api/wallet-rpc-api/burn_asset.md vendored
View file

@ -25,12 +25,12 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"id": 0,
"jsonrpc": "2.0",
"result": {
"result_tx": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
"tx_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
}
}
```
### Response description:
```
"result_tx": Id of transaction that carries asset burn operation
"tx_id": Id of transaction that carries asset burn operation
```

30
docs/build/rpc-api/wallet-rpc-api/deploy_asset.md vendored
View file

@ -11,36 +11,38 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_descriptor": {
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"destinations": [{
"address": "ZxBvJDuQjMG9R2j4WnYUhBYNrwZPwuyXrC7FHdVmWqaESgowDvgfWtiXeNGu8Px9B24pkmjsA39fzSSiEQG1ekB225ZnrMTBp",
"amount": 10000000000000,
"asset_id": "cc608f59f8080e2fbfe3c8c80eb6e6a953d47cf2d6aebd345bada3a1cab99852"
}]
}],
"do_not_split_destinations": false
}
}
```
### Request description:
```
"asset_descriptor": Descriptor that holds all information about asset - ticker, emission, description etc
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"destinations": Addresses where to receive emitted coins. Asset id in destinations should be set to 0000000000000000000000000000000000000000000000000000000000000000
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"destinations": Addresses where to receive emitted coins. Asset id in the destinations is irreleant and can be omitted.
"address": Destination address
"amount": Amount to transfer to destination
"asset_id": Asset id to transfer
"do_not_split_destinations": If true, the provided destinations will be used as-is and won't be splitted (or altered) to avoid common issues. Default is false.
```
### Response:
@ -50,13 +52,13 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"jsonrpc": "2.0",
"result": {
"new_asset_id": "40fa6db923728b38962718c61b4dc3af1acaa1967479c73703e260dc3609c58d",
"result_tx": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
"tx_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
}
}
```
### Response description:
```
"new_asset_id": Issued asset id
"result_tx": Id of transaction that carries asset registration command, asset would be registered as soon as transaction got confirmed
"tx_id": Id of transaction that carries asset registration command, asset would be registered as soon as transaction got confirmed
```

10
docs/build/rpc-api/wallet-rpc-api/emit_asset.md vendored
View file

@ -13,17 +13,19 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"address": "ZxBvJDuQjMG9R2j4WnYUhBYNrwZPwuyXrC7FHdVmWqaESgowDvgfWtiXeNGu8Px9B24pkmjsA39fzSSiEQG1ekB225ZnrMTBp",
"amount": 10000000000000,
"asset_id": "cc608f59f8080e2fbfe3c8c80eb6e6a953d47cf2d6aebd345bada3a1cab99852"
}]
}],
"do_not_split_destinations": false
}
}
```
### Request description:
```
"asset_id": Id of the asset to emit more coins
"destinations": Addresses where to receive emitted coins. Asset id in destinations should be set to 0000000000000000000000000000000000000000000000000000000000000000
"destinations": Addresses where to receive emitted coins. Asset id in the destinations is irreleant and can be omitted.
"address": Destination address
"amount": Amount to transfer to destination
"asset_id": Asset id to transfer
"do_not_split_destinations": If true, the provided destinations will be used as-is and won't be splitted (or altered) to avoid common issues. Default is false.
```
### Response:
@ -32,12 +34,12 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"id": 0,
"jsonrpc": "2.0",
"result": {
"result_tx": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
"tx_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
}
}
```
### Response description:
```
"result_tx": Id of transaction that carries asset registration command, asset would be registered as soon as transaction got confirmed
"tx_id": Id of transaction that emits the required asset.
```

20
docs/build/rpc-api/wallet-rpc-api/getbalance.md vendored
View file

@ -27,11 +27,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"awaiting_in": 1000000000000,
@ -49,14 +49,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"balances": Balances groupped by it's asset_id
"asset_info": Asset info details
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"awaiting_in": Unconfirmed amount for receive
"awaiting_out": Unconfirmed amount for send
"total": Total coins available(including locked)

20
docs/build/rpc-api/wallet-rpc-api/mw_get_wallets.md vendored
View file

@ -30,11 +30,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"awaiting_in": 1000000000000,
@ -61,14 +61,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"balances": Balances hold by this wallet
"asset_info": Asset info details
"asset_id": Asset ID
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"awaiting_in": Unconfirmed amount for receive
"awaiting_out": Unconfirmed amount for send
"total": Total coins available(including locked)

44
docs/build/rpc-api/wallet-rpc-api/send_ext_signed_asset_tx.md vendored Normal file
View file

@ -0,0 +1,44 @@
Inserts externally made asset ownership signature into the given transaction and broadcasts it.
URL: ```http:://127.0.0.1:11211/json_rpc```
### Request:
```json
{
"id": 0,
"jsonrpc": "2.0",
"method": "send_ext_signed_asset_tx",
"params": {
"eth_sig": "674bb56a5b4fa562e679ccacc4e69455e63f4a581257382191de6856c2156630b3fba0db4bdd73ffcfb36b6add697463498a66de4f1760b2cd40f11c3a00a7a8",
"expected_tx_id": "40fa6db923728b38962718c61b4dc3af1acaa1967479c73703e260dc3609c58d",
"finalized_tx": "ewogICJ2ZXJzaW9uIjogMSwgC....iAgInZpbiI6IFsgewogICAgIC",
"unlock_transfers_on_fail": false,
"unsigned_tx": "083737bcfd826a973f74bb56a52b4fa562e6579ccaadd2697463498a66de4f1760b2cd40f11c3a00a7a80000"
}
}
```
### Request description:
```
"eth_sig": HEX-encoded ETH signature (64 bytes)
"expected_tx_id": The expected transaction id. Tx won't be sent if the calculated one doesn't match this one. Consider using 'verified_tx_id' returned by 'decrypt_tx_details' call.
"finalized_tx": Base64-encoded finalized_tx data structure, which was received from emit_asset call.
"unlock_transfers_on_fail": If true, all locked wallet transfers, corresponding to the transaction, will be unlocked on sending failure. False by default.
"unsigned_tx": Base64-encoded unsigned transaction blob, which was received from emit_asset call.
```
### Response:
```json
{
"id": 0,
"jsonrpc": "2.0",
"result": {
"status": "OK",
"transfers_were_unlocked": false
}
}
```
### Response description:
```
"status": Status of the call
"transfers_were_unlocked": If true, all input transfers that were locked when preparing this transaction, are now unlocked and may be spent. Can be true only upon sending failure and if requested.
```

8
docs/build/rpc-api/wallet-rpc-api/transfer.md vendored
View file

@ -17,7 +17,7 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"fee": 10000000000,
"hide_receiver": true,
"mixin": 15,
"payment_id": "1dfe5a88ff9effb3",
"payment_id": "",
"push_payer": false,
"service_entries": [{
"body": "dcfd7e055a6a3043ea3541a571a57a63e25dcc64e4a270f14fa9a58ac5dbec85dcfd7e055a6a3043ea3541a571a57a63e25dcc64e4a270f14fa9a58ac5dbec85",
@ -57,13 +57,15 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"id": 0,
"jsonrpc": "2.0",
"result": {
"tx_hash": "",
"tx_size": 0,
"tx_hash": "01220e8304d46b940a86e383d55ca5887b34f158a7365bbcdd17c5a305814a93",
"tx_size": 1234,
"tx_unsigned_hex": ""
}
}
```
### Response description:
```
"tx_hash": Has of the generated transaction(if succeded)
"tx_size": Transaction size in bytes
```

24
docs/build/rpc-api/wallet-rpc-api/update_asset.md vendored
View file

@ -11,11 +11,11 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"asset_descriptor": {
"current_supply": 500000000000000000,
"decimal_point": 12,
"full_name": "Zano wrapped USD",
"full_name": "Zano wrapped ABC",
"hidden_supply": false,
"meta_info": "Stable and private",
"owner": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8",
"ticker": "ZUSD",
"ticker": "ZABC",
"total_max_supply": 1000000000000000000
},
"asset_id": "40fa6db923728b38962718c61b4dc3af1acaa1967479c73703e260dc3609c58d"
@ -25,14 +25,14 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
### Request description:
```
"asset_descriptor": Descriptor that holds all information about asset that need to be updated (only owner could be updated)
"current_supply": Currently emitted supply for given asset (ignored for REGISTER operation)
"decimal_point": Decimal point
"full_name": Full name of the asset
"hidden_supply": This one reserved for future use, will be documented later
"meta_info": Any other information assetiaded with asset in a free form
"owner": Owner's key, used only for EMIT and UPDATE validation, could be changed by transferring asset ownership
"ticker": Ticker associated with asset
"total_max_supply": Maximum possible supply for given asset, can't be changed after deployment
"current_supply": Currently emitted supply for the given asset (ignored for REGISTER operation).
"decimal_point": Decimal point.
"full_name": Full name of the asset.
"hidden_supply": This field is reserved for future use and will be documented later.
"meta_info": Any other information associated with the asset in free form.
"owner": Owner's key, used only for EMIT and UPDATE validation, can be changed by transferring asset ownership.
"ticker": Ticker associated with the asset.
"total_max_supply": Maximum possible supply for a given asset, cannot be changed after deployment.
"asset_id": Id of the asset to update
```
@ -42,12 +42,12 @@ URL: ```http:://127.0.0.1:11211/json_rpc```
"id": 0,
"jsonrpc": "2.0",
"result": {
"result_tx": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
"tx_id": "f74bb56a5b4fa562e679ccaadd697463498a66de4f1760b2cd40f11c3a00a7a8"
}
}
```
### Response description:
```
"result_tx": Id of transaction that carries asset registration command, asset would be registered as soon as transaction got confirmed
"tx_id": Id of transaction that carries asset registration command, asset would be registered as soon as transaction got confirmed
```

18
docs/build/testnet-resources/testnet-builds.md vendored
View file

@ -4,26 +4,26 @@ A list of builds for the current Zano testnet
### Windows
INST: https://build.zano.org/builds/zano-win-x64-release-testnet-v2.0.0.333[59ea013]-installer.exe
INST: https://build.zano.org/builds/zano-win-x64-develop-testnet-v2.0.0.344[565e950]-installer.exe
sha256: c63615511f8f57698198d8db80b9ef234e64aa6175c41d713deb7b7d502bd354
sha256: 5ffb68d9d987bf1a75be766801fe49467261b46c5cf28c386930aaa9a142b76d
ZIP: https://build.zano.org/builds/zano-win-x64-release-testnet-v2.0.0.333[59ea013].zip
ZIP: https://build.zano.org/builds/zano-win-x64-develop-testnet-v2.0.0.344[565e950].zip
sha256: 7592fa145ea565571a18c6a1f503b9aecb4019a0f277dff53c97d445b16e9b66
sha256: e216dc76b8dc37cb00c719454b562e17403666c26a1e6d473dd9034951c68ed2
### MacOs
https://build.zano.org/builds/zano-macos-x64-release-testnet-v2.0.0.333[59ea013].dmg
https://build.zano.org/builds/zano-macos-x64-develop-testnet-v2.0.0.344[565e950].dmg
sha256: 61f121f0907d84974475ab24586a56964bb2f6489631273646b06989edbfd4a9
sha256: f03e5371b5d8e09776d639c5a148b8c135a2eba7c9f0adf33d841ca8e65aaf5c
### Linux
https://build.zano.org/builds/zano-linux-x64-release-testnet-devtools-v2.0.0.333[59ea013].AppImage
https://build.zano.org/builds/zano-linux-x64-develop-testnet-devtools-v2.0.0.344[565e950].AppImage
sha256: a2fe0d5f2538202a2fcf6055068438ac5d5c2131104f81796a971dc75d6c0f46
sha256: ca698203bfae3d2e8ef5b15d9629799a44302a23d0a495f76ec3e5fd20bff659
```
updated at 2024-07-12 16:30:00
updated at 2024-09-26 12:00:00
```

2
docs/learn/emission.md
View file

@ -2,7 +2,7 @@
sidebar_position: 6
---
# Emission
# Emission/Tokenomics
### Where does the emission come from?

2
docs/learn/whitepaper.md
View file

@ -8,7 +8,7 @@ sidebar_position: 3
Original Zano whitepaper, describes general concepts used in project.
<https://github.com/hyle-team/docs/blob/master/zano/Zano_WP_1.1.pdf>
<https://github.com/hyle-team/docs/blob/master/zano/Zano%20WP_latest.pdf>
### PoS Analysis and improvements proposal (2019)