From 91b6f8a2dad88684f7503f050bfc3231ae882608 Mon Sep 17 00:00:00 2001 From: cryptozoidberg Date: Fri, 27 Jun 2025 22:30:02 +0400 Subject: [PATCH] Update multi-assets-custody-guide.md --- docs/build/exchange-guidelines/multi-assets-custody-guide.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/build/exchange-guidelines/multi-assets-custody-guide.md b/docs/build/exchange-guidelines/multi-assets-custody-guide.md index c58e66a..122ea6e 100644 --- a/docs/build/exchange-guidelines/multi-assets-custody-guide.md +++ b/docs/build/exchange-guidelines/multi-assets-custody-guide.md @@ -102,7 +102,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/): +**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) ): ```json Request: @@ -127,6 +127,7 @@ 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). ## Processing Incoming Transactions