18:23:33 hyc are you there? 20:50:33 selsta: I see you tagged v0.18.4.0 : https://github.com/monero-project/monero/pull/9722 20:50:50 not yet tagged 20:51:08 Is it okay if we delay until we get #9135 and #9740 20:51:15 sorry you're right, not tagged 20:51:28 But all the same, these changes should be included in release IMO 20:51:39 Pending approvals, of course 20:53:15 yes i wanted to include it 20:54:03 we also have to figure out what caused this p2p test failure before release 20:54:05 https://github.com/monero-project/monero/actions/runs/12969219043/job/36173269466?pr=9723#step:11:1380 20:54:09 could be a regression 21:03:43 Hi i have encountered an issue with creating and relaying a transaction using wallet2. My code created the transaction succesfully and have sent it but the sent transaction itself doesnt have the output i've set and only shows amount: 0.00000000 xmr and some fee, the receiver of the transaction doesnt see it at all, i would really apreciate some 21:03:43 help in this. 21:03:44 Here is my code: https://pastebin.com/gSpRVWYk 21:04:55 I have checked in debugger inside of create_transactions_2 function if the dests and outs are correct and they show my output and also ptx_vector sees the transaction, but after sending the transaction amount is randomly being 0 21:13:06 selsta: the same issue triggered as early as the "merge PR #9523" commit: https://github.com/monero-project/monero/actions/runs/12850111386/job/35829685047#step:9:1460 21:13:27 Sorry #9491 21:16:40 ok that means it's not related to the recent network changes 21:16:54 could still be a regression from somewhere else 21:17:03 Yes, definitely 21:27:15 victzo: I'll set up a private testnet and check it out 21:38:15 about the earlier problem with transactions, my pc crashed and i lost all the responses, so can i do anything about this problem? 21:40:18 and also can i somehow create account on element by connecting to monero.social because it shows me that registration has been disabled for this homeserver 21:40:33 All the IRC responses? 21:41:29 registration is indeed disabled @ monero social 21:41:47 j​effro256 yes the responses about the transactions bug 21:41:56 https://libera.monerologs.net/ 21:42:12 oh thanks 21:42:15 didnt know that 21:42:27 plowsof: is there a way to invite people to register? 21:42:52 good idea will ask 21:43:25 It would be nice if there was an invite queue or something like that 21:43:56 B/c locking all new people from registering on monero.social isn't ideal, but also the spam was pretty brutal 21:44:00 Admin can create a registration token while invite are off. Then the invitee have to somehow create an account using said token. 21:44:00 curl -s --header "Authorization: Bearer admin_user_access_token" -H "Content-Type:application/json" -XPOST "https://monero.social/_synapse/admin/v1/registration_tokens/new" -d '{"uses_allowed":1}' | jq 21:44:23 RavFX our savior 21:46:14 j​effro256 i'll wait for your check about the transactions, thanks again 21:48:57 One thing about the script: the `recipient_address` string is unused and you construct the transaction to yourself, not the given address. Is this intended? 21:50:01 one is unused because when i was debugging i changed the wallet a few times because i had to wait to get confirmations to be able to send another transaction 21:50:13 so i changed wallet and recipient 21:50:22 so i woudnt have to wait as long 21:50:40 im sending it to a different wallet 21:52:50 But the script you provided is intended to do a self-send? 21:53:08 yes but to a different wallet 21:53:49 What do you mean by a "different wallet"? Do you have two wallets open with the same account keys? 21:54:00 *wallet instances 21:55:07 i am opening wallet1 in c++ sending some xmr to wallet2, after the code execution i open both wallets in feather wallet app to check if transaction went through 21:55:30 and in the sender wallet (wallet1) i see a transaction being sent from it by amount is set to 0 and i only pay fee on this transaction 21:55:43 and wallet2 (receiver) doesnt see any transaction 21:56:58 in this case the sender is in this path "/home/adam/Monero/wallets/wallet_2"; and this is the receiver "/home/adam/Monero/wallets/wallet_5"; 21:57:36 and the commented receiver string in code is address of the sender wallet 21:57:51 and the uncommented one is the receiver one 22:01:30 you should double check that. your observation is consistent with sending the tx to an address of wallet1 instead of wallet2 22:03:58 unfortunately thats not it :/ 22:31:14 oh my god 22:31:17 yeees thats it 22:31:25 but not in the stirng but in the public keys 22:31:38 sorry for the confusion 22:32:19 and thanks again for all the help 22:55:35 of course 22:55:39 haha was just coming back to say that it worked lol 22:59:27 selsta: 22:59:28 > ok that means it's not related to the recent network changes 22:59:30 Actually it could mean it's related, it was only merged one week ago. Which are the recent changes you're referring to?