what could be the reason for `--do-not-relay` not working for me? it just broadcasts the transaction as usual.

anyone around an OpenAlias dev?

I tested it earlier, found new things

that should be put onto OpenAlias.org

chaser[m]: how did you send this tx ?

Hi, I am searching for the "correct" way to check the amounts of confirmations for an incoming Monero payment (by payment_id), using the wallet rpc and daemon rpc api. Currently I am using get_bulk_payments() [wallet rpc], followed by a call to get_height() [wallet rpc]. I deduce the amount of confirmations by subtracting the block heights.

This method seems a little bit hacky to me, I was wondering what is the correct way to do this.

Here is some of my reasoning against the way I am currently doing this: 1. Maybe get_height() represents the height of a block from an alternative chain that doesn't contain the incoming transaction? Is this scenario possible?

2. There is a possible "time of check time of use" issue here. If get_bulk_payments() returned a certain payment, and until I get to call get_height(), there is an alternative chain which does not include the transaction.

A reasonable solution would probably be to check all of the above in one rpc call, but I couldn't find the way to do it.

Some RPC calls are racy in the first place.

IIRC you get number of confirmations in get_transfers or get_somehingsimilar.

<moneromooo> "chaser: how did you send this tx..." <- manually, from monero-wallet-cli, which ran with flags `--do-not-relay --no-dns --wallet-file /path/to/file`

it ignores --do-not-relay for transfers and sweeps too

Was it relayed at once, or hours later ?

my impression is it was relayed at once, right away, but I didn't check. what I'm sure of is that it didn't write the tx to a local rawtx file, as it used to

--do-not-relay is unrelated to writing to a local file AFAIK.

Feel free to file a bug about it, it used to work.

hmmm. it's been a while since I last used --do-not-relay so maybe its behavior was changed? about a 1-1.5 years ago it 1) gave the response in the CLI that the raw transaction was written into a file, and 2) indeed there was a file "rawtx" created next to the monero-wallet-cli binary that contained the transaction in hex.

thanks, I'll check the docs and file an issue is this functionality is no lo longer present

Reading the code, it looks like the wallet has a --do-not-relay, which does what you say. I only knew of the daemon --do-not-relay.

So ignore what I said, I was wrong.

(except the "please file a bug" line, that one was not wrong :))

got it. actually this has been an issue for me for a few months so in September I filed an issue: monero-project/monero #7947 . if others could test the behavior and comment there whether they can replicate it, it would be great

i used --do-not-relay 2 days before, it worked and created raw_monero_tx

on wallet-cli

then could my monerod flags cause the problem? monerod runs locally with `--data-dir /path/to/datadir/ --p2p-bind-port 12345 --disable-dns-checkpoints --detach`

I used this: ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/./monero-wallet-cli --wallet-file ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/cake --daemon-host 192.168.1.140 --daemon-port 18089 --trusted-daemon --do-not-relay

version is v0.17.3.0-release, i just did not rename folder

<dynemeloun> "I used this: ~/documents/money/..." <- same version and OS here. the only meaningful differences I see is that you don't use `--no-dns` and use `--trusted-daemon`. could those affect `--do-not-relay`?

this works ok: ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/./monero-wallet-cli --wallet-file ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/cake --daemon-host 192.168.1.140 --daemon-port 18089 --trusted-daemon --do-not-relay --no-dns

this too works ok ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/./monero-wallet-cli --wallet-file ~/documents/money/monero-x86_64-linux-gnu-v0.17.2.0/cake --daemon-host 192.168.1.140 --daemon-port 18089 --do-not-relay --no-dns

both made raw_monero_tx

thanks for checking! then I wonder what else could cause this

it sure is not the wallet flags

I do not remember correctly, are monero binaries statically compiled or dynamically linked?

release binaries are static

they must be, to be usable on multiple distros

thanks hyc

they still use dynamic libc. but just about all other dependencies are static

Big thank you to everybody involved with getting tor p2p support integrated in the latest release! Been waiting *soooo* long for that! THANK YOU!!!!

monero-project/monero #6950 You can finally close this because torsocks is no longer needed

Might be worth updating monerod.service systemd file @ github.com/monero-project/monero/bl…aster/utils/systemd/monerod.service

to reflect the fact that torsocks is not required any longer

<moneromooo> "Some RPC calls are racy in the..." <- Is there a guide explaining which ones are recommended? Usually I wouldn't care about racy API, but when it comes to people's money I would like to be sure I am doing the correct thing before pushing to production.

<moneromooo> "IIRC you get number of confirmat..." <- Thanks! get_transfer_by_txid() of the wallet rpc looks like something that I can use.

Not as far as I know.

I was thinking of getinfo, which can return height and diff that aren't in sync.

Which reminds me, I added a lock at some point which goes some way to fixing this... Might actually have fixed it...

Nope, didn't fix getinfo at least. I think I originally did it for Townforge, but it could be retrofitted to monero without fuss. LockedTXN.

I did that for getinfo + some other functions here: monero-project/monero #7936

Nice, thanks :)

Hello. Why is monero-wallet-gui not starting?... (full message at libera.ems.host/_matrix/media/r0/do…2de4d128591cae0d23dfbef65e193993ccc)

* Hello. Why is monero-wallet-gui not starting? (0.17.3.0)... (full message at libera.ems.host/_matrix/media/r0/do…229ba4f7c8899e6eedd15f4f2f9c97801b2)

What architecture ?

moneromooo: x86_64

Ouch. Dunno then.

Did you compile it yourself ?

moneromooo: No. It's precompiled flatpak and archlinux packages

Ah, if precompiled from not getmonero.org, possibly it got compiled with insns specific to a later family.

Do you have an old CPU ?

Old being defined as older than the person who built that precompiled binary :D

moneromooo: Intel Pentium 5405U (2019 like...)

OK, sounds pretty recent. Out of ideas then, sorry.

Pentium sounds very 1999 though.

Sadly... :(

moneromooo: en.wikichip.org/wiki/intel/pentium_gold/5405u

Q1, 2019

Time to change CPU :)

<DeanGuss> "github.com/monero-..." <- with that, what is now the best way to torify Monero?