12:41:23 [CCS Proposals] acx acx opened merge request #616: acx Monfluo maintenance and further development 2025Q4 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/616 15:25:16 transfer 4BbmePVHhuhTsE4656ScFv2iFKy1ZmMT7d4yXAVS3FM9gUc6qkTo7H7Gz8p1zDiJPQN34hK6v9ZdaMdug5mhMYrbSGtHYuwLbckQfEeVhc 0.00009 44zkDAxE5VNAhWy2ofT9EZe8odReJbC66aAujVNezo9WhPcmXiLtC8ERBt6BTAznLmcPedr5DniTEN3zoaapvbsMBQ4oZyj 0.00005 > <@fiatdemise:matrix.org> 4BbmePVHhuhTsE4656ScFv2iFKy1ZmMT7d4yXAVS3FM9gUc6qkTo7H7Gz8p1zDiJPQN34hK6v9ZdaMdug5mhMYrbSGtHYuwLbckQfEeVhc 15:25:16 =[... more lines follow, see https://mrelay.p2pool.observer/e/s9-z07kKcXY2T21i ] 15:26:49 You musy be trying to send to 2 integrated addresses in the same tx 15:34:44 This is the exact command I entered. The first address is my primary address that I have pinned on X for CakePay. 15:34:45 transfer 47ioQfBgxqvGfbDrUZGDiHFe1Zx9Fobp8Cp1RueGRfPJU1c76SNfgSMASmT9w2UpU7EaRGme8qzDqPzdLK1e1AeBR72yFkV .0002 4Fu3rriBzgHemwBJWfU3tHLU2DBewBeX6Rtcb64psUPcEajRqQmsGPQbG2pNkVnjdFFmpNomqEED7hzAGa34gcKabF3FFWBe9LDKrdANMV .0002 15:36:26 Can you try that exact command and let me know what you find? I'll reimburse whatever funds are used for testing. 15:43:21 I can have a look in about an hour, but I assume that's beyond my expertise > <@fiatdemise:matrix.org> I tried again to do 1 primary address and 1 integrated, this time in CLI with log level set to 2. Saw this in log, "Destinations have to have exactly one output to support encrypted payment ids" Really hope it's possible to change that. 15:46:58 @fiatdemise:matrix.org: sure. Will take 20mins as i move some funds to my testing wallet 15:47:43 That would be great, even to just have one more person getting the same error I'm seeing would be useful. 15:48:32 transfer 4BbmePVHhuhTsE4656ScFv2iFKy1ZmMT7d4yXAVS3FM9gUc6qkTo7H7Gz8p1zDiJPQN34hK6v9ZdaMdug5mhMYrbSGtHYuwLbckQfEeVhc 0.00009 44zkDAxE5VNAhWy2ofT9EZe8odReJbC66aAujVNezo9WhPcmXiLtC8ERBt6BTAznLmcPedr5DniTEN3zoaapvbsMBQ4oZyj 0.00005 15:48:38 You can try this as well 15:52:55 Done, got transaction not constructed error message 15:53:22 https://mrelay.p2pool.observer/m/matrix.org/HaRaCjzjUGFOAOeSsIOPfZxD.png (image.png) 16:08:15 https://mrelay.p2pool.observer/m/matrix.org/GDcEVzeZSrbgPvjkcrSdLjVa.log (monero-wallet-cli.log) 16:08:19 I deleted log file and tried again, same error, log attached. 16:12:41 Try building master branch 16:13:17 Couple more mins for funds to clear so i can test your command 16:13:35 3 blocks 16:20:47 https://mrelay.p2pool.observer/m/xmr.mx/BVftnbKYJvPhhaAZUOZQArTT.png (share_7868402333076064563.png) 16:21:04 yours didnt work but mine did 16:21:39 Let me try switching order 16:25:14 No change. the integrated address in your command doesnt work, but xenus works for me 16:26:20 Actually doesnt seem to he the integrated address 16:26:57 Its the primary address that doesnt work 16:28:01 try using 16:28:01 transfer {integrated_address} 0.001 {primary_address_of_the_sending_wallet} 0.001 16:28:28 It succeed for me when the primary address is my own 16:38:18 I'm unavailable again, will try in couple hours. 17:23:51 just found this comment (https://github.com/monero-project/monero/blob/b591866fcfed400bc89631686655aa769ec5f2dd/src/multisig/multisig_tx_builder_ringct.cpp#L166-L169) for the same error message in multisig code 20:42:26 @ofrnxmr:xmr.mx: Tried this, and it worked for me. 20:48:34 cc @jeffro256:monero.social 23:18:58 > <@fiatdemise:matrix.org> I tried again to do 1 primary address and 1 integrated, this time in CLI with log level set to 2. Saw this in log, "Destinations have to have exactly one output to support encrypted payment ids" Really hope it's possible to change that. 23:18:58 @fiatdemise:matrix.org: That's unfortunately a limitation of the current addressing protocol. You can mix integrated addresses with subaddresses or your own main address, but not with other integrated address or other non-main addresses. The reason is that the recipient of the other main, non-integrated, address in the transa [... too long, see https://mrelay.p2pool.observer/e/jLn64LkKRVliYmQw ] 23:19:22 *or other non-integrated main addresses 23:21:28 In other words, with the current addressing protocol, trying to send to 1 integrated address and 1 main address actually sends as 1 integrated address and another integrated address with a random payment ID 23:25:48 Technically speaking, the sender wallet could search for transaction pubkey collision such that the other main address actually decrypts an all-zeros payment ID. But that might reduce security somewhat, and would take a lot of compute power, exponentially more so the more destinations you add 23:27:19 @jeffro256: The wallet could be coded to be able to be allowed to send to 1 integrated address plus multiple main addresses, as long as the user asserts that they're okay with sending a bunch of random payment IDs to the other guys 23:31:22 The reason that subaddress recipients in a transaction with payment IDs is that the receiving wallet simply ignores payment IDs if the received address is a subaddress. Similarly, the wallet also ignores payment IDs to main addresses (most likely change) if one of their owned outputs was spent in that transaction. 23:37:26 Interesting. I have found that integrated + subaddress also isn't possible, I get same error message. This is what I tried: 23:37:26 transfer {integrated_address} 0.0002 {subaddress_NOT_of_the_sending_wallet} 0.0001 23:38:30 In any case, time to learn more about CARROT and get a general sense of when that's expected.