<s​yntheticbird:monero.social> hyc are you there?

<j​effro256:monero.social> selsta: I see you tagged v0.18.4.0 : monero-project/monero #9722

not yet tagged

<j​effro256:monero.social> Is it okay if we delay until we get #9135 and #9740

<j​effro256:monero.social> sorry you're right, not tagged

<j​effro256:monero.social> But all the same, these changes should be included in release IMO

<j​effro256:monero.social> Pending approvals, of course

yes i wanted to include it

we also have to figure out what caused this p2p test failure before release

could be a regression

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

help in this.

Here is my code: pastebin.com/gSpRVWYk

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

<j​effro256:monero.social> selsta: the same issue triggered as early as the "merge PR #9523" commit: github.com/monero-project/monero/ac…0111386/job/35829685047#step:9:1460

<j​effro256:monero.social> Sorry #9491

ok that means it's not related to the recent network changes

could still be a regression from somewhere else

<j​effro256:monero.social> Yes, definitely

<j​effro256:monero.social> victzo: I'll set up a private testnet and check it out

about the earlier problem with transactions, my pc crashed and i lost all the responses, so can i do anything about this problem?

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

<j​effro256:monero.social> All the IRC responses?

registration is indeed disabled @ monero social

j​effro256 yes the responses about the transactions bug

<j​effro256:monero.social> libera.monerologs.net

oh thanks

didnt know that

<j​effro256:monero.social> plowsof: is there a way to invite people to register?

good idea will ask

<j​effro256:monero.social> It would be nice if there was an invite queue or something like that

<j​effro256:monero.social> B/c locking all new people from registering on monero.social isn't ideal, but also the spam was pretty brutal

<r​avfx:xmr.mx> Admin can create a registration token while invite are off. Then the invitee have to somehow create an account using said token.

<r​avfx:xmr.mx> curl -s --header "Authorization: Bearer admin_user_access_token" -H "Content-Type:application/json" -XPOST "monero.social/_synapse/admin/v1/registration_tokens/new" -d '{"uses_allowed":1}' | jq

<s​yntheticbird:monero.social> RavFX our savior

j​effro256 i'll wait for your check about the transactions, thanks again

<j​effro256:monero.social> 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?

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

so i changed wallet and recipient

so i woudnt have to wait as long

im sending it to a different wallet

<j​effro256:monero.social> But the script you provided is intended to do a self-send?

yes but to a different wallet

<j​effro256:monero.social> What do you mean by a "different wallet"? Do you have two wallets open with the same account keys?

<j​effro256:monero.social> *wallet instances

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

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

and wallet2 (receiver) doesnt see any transaction

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";

and the commented receiver string in code is address of the sender wallet

and the uncommented one is the receiver one

you should double check that. your observation is consistent with sending the tx to an address of wallet1 instead of wallet2

unfortunately thats not it :/

oh my god

yeees thats it

but not in the stirng but in the public keys

sorry for the confusion

and thanks again for all the help

<j​effro256:monero.social> of course

<j​effro256:monero.social> haha was just coming back to say that it worked lol

<j​effro256:monero.social> selsta:

<j​effro256:monero.social> > ok that means it's not related to the recent network changes

<j​effro256:monero.social> Actually it could mean it's related, it was only merged one week ago. Which are the recent changes you're referring to?