The make_integrated_address method of wallet_rpc produces integrated address from the wallet primary one.
destination address with RPC API. (For example to reconstruct the integrated one used during a new transfer creation. Destination address and payment_id could be retrieved with get_transfers method, but not the integrated address)make_integrated_address method with optional subaddr_index parameter, to specify the account and subaddress indices for the standard address used."subaddr_index": {
"major": 0,
"minor": 0
}
major - unsigned int; Default: 0. Account index for the subaddress.
minor - unsigned int; Default: 0. Index of the subaddress in the account.
make_integrated_address method with optional address parameter, to specify arbitrary standard or integrated address to be used as base to make the new integrated one. The value of this parameter should be converted to standard address if necessary. subaddr_index ignored for such a method call.This would defeat part of the purpose of subaddesses, which is to allow a way to map a tx to a sender without having to use an extraneous piece of data.
Ok! Integrated subaddresses are meaningless, but what about make_integrated_address with base address specified? Just to reconstruct integrated address from standard address + payment ID retrieved with get_transfer_by_txid !? (p.2 of suggested solution)
That can be added, though not very useful I think since the party generating those is the recipient.
+resolved
Most helpful comment
This would defeat part of the purpose of subaddesses, which is to allow a way to map a tx to a sender without having to use an extraneous piece of data.