From fcaf2371d1b7767a237d43e0cb4bbbf7d4e5702f Mon Sep 17 00:00:00 2001 From: ravaga Date: Tue, 28 Oct 2025 12:10:25 +0400 Subject: [PATCH] fixed broken links --- docs/build/exchange-guidelines/exchange-faq.md | 2 +- .../exchange-guidelines/integrated-addresses-for-exchanges.md | 2 +- docs/build/libraries/overview.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/build/exchange-guidelines/exchange-faq.md b/docs/build/exchange-guidelines/exchange-faq.md index 678e200..121f8c7 100644 --- a/docs/build/exchange-guidelines/exchange-faq.md +++ b/docs/build/exchange-guidelines/exchange-faq.md @@ -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? diff --git a/docs/build/exchange-guidelines/integrated-addresses-for-exchanges.md b/docs/build/exchange-guidelines/integrated-addresses-for-exchanges.md index 0c31696..b740e40 100644 --- a/docs/build/exchange-guidelines/integrated-addresses-for-exchanges.md +++ b/docs/build/exchange-guidelines/integrated-addresses-for-exchanges.md @@ -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.
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. \ No newline at end of file +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. \ No newline at end of file diff --git a/docs/build/libraries/overview.md b/docs/build/libraries/overview.md index 0fe7933..b9e4855 100644 --- a/docs/build/libraries/overview.md +++ b/docs/build/libraries/overview.md @@ -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++)