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

fixed broken links

Browse source
This commit is contained in:
ravaga 2025-10-28 12:10:25 +04:00
parent 17c209fdfd
commit fcaf2371d1
No known key found for this signature in database
GPG key ID: 6BA9F4BFD7B4129C
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/build/exchange-guidelines/exchange-faq.md vendored
View file

@ -24,7 +24,7 @@ Make sure the daemon is synchronized with the network. It may take up to few hou
### How to validate an address?
To validate an address you can use [split_integrated_address](https://docs.zano.org/reference/split_integrated_address). It also works with standard addresses (non integrated one)
To validate an address you can use [split_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/split_integrated_address). It also works with standard addresses (non integrated one)
### How to get all integrated addresses on a wallet?

2
docs/build/exchange-guidelines/integrated-addresses-for-exchanges.md vendored
View file

@ -7,4 +7,4 @@ Unlike Bitcoin, CryptoNote family coins have different, more effective approach
An exchange generates only one address for receiving coins and all users send coins to that address. To distinguish different deposits from different users the exchange generates random identifier (called **payment ID**) for each one and a user attaches this payment ID to his transaction while sending. Upon receiving, the exchange can extract payment ID and thus identify the user.<br/>
In original CryptoNote there were two separate things: exchange deposit address (the same for all users) and payment ID (unique for all users). Later, for user convenience and to avoid missing payment ID we combined them together into one thing, called **integrated address**. So nowadays modern exchanges usually give to a user an integrated address for depositing instead of pair of standard deposit address and a payment ID.
For more information on how to handle integrated addresses, please refer to RPCs [make_integrated_address](https://docs.zano.org/reference/make_integrated_address-1) and [split_integrated_address](https://docs.zano.org/reference/split_integrated_address-1) below.
For more information on how to handle integrated addresses, please refer to RPCs [make_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/make_integrated_address) and [split_integrated_address](https://docs.zano.org/docs/build/rpc-api/wallet-rpc-api/split_integrated_address) below.

2
docs/build/libraries/overview.md vendored
View file

@ -6,7 +6,7 @@ Zano Web3 TS is a TypeScript library designed to facilitate interaction with the
Github: https://github.com/hyle-team/zano_web3
Package: https://www.npmjs.com/package/zano_web
Package: https://www.npmjs.com/package/zano_web3
## Native Zano Wallet for IOS/Android (C++)