03:20:16 <chaser[m]> what could be the reason for `--do-not-relay` not working for me? it just broadcasts the transaction as usual.
07:22:43 <lous1F> anyone around an OpenAlias dev?
07:23:33 <lous1F> I tested it earlier, found new things
07:23:48 <lous1F> that should be put onto OpenAlias.org
10:12:47 <moneromooo> chaser[m]: how did you send this tx ?
11:00:59 <xorpd[m]> 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.
11:01:38 <xorpd[m]> This method seems a little bit hacky to me, I was wondering what is the correct way to do this.
11:02:33 <xorpd[m]> 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?
11:03:32 <xorpd[m]> 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.
11:04:25 <xorpd[m]> 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.
12:06:13 <moneromooo> Some RPC calls are racy in the first place.
12:07:34 <moneromooo> IIRC you get number of confirmations in get_transfers or get_somehingsimilar.
14:47:36 <chaser[m]> <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`
14:49:12 <chaser[m]> it ignores --do-not-relay for transfers and sweeps too
14:49:29 <moneromooo> Was it relayed at once, or hours later ?
14:52:17 <chaser[m]> 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
14:53:54 <moneromooo> --do-not-relay is unrelated to writing to a local file AFAIK.
14:54:13 <moneromooo> Feel free to file a bug about it, it used to work.
14:56:42 <chaser[m]> 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.
14:57:17 <chaser[m]> thanks, I'll check the docs and file an issue is this functionality is no lo longer present
14:59:51 <moneromooo> 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.
14:59:58 <moneromooo> So ignore what I said, I was wrong.
15:02:17 <moneromooo> (except the "please file a bug" line, that one was not wrong :))
15:05:48 <chaser[m]> got it. actually this has been an issue for me for a few months so in September I filed an issue: https://github.com/monero-project/monero/issues/7947 . if others could test the behavior and comment there whether they can replicate it, it would be great
15:06:27 <dynemeloun> i used --do-not-relay 2 days before, it worked and created raw_monero_tx
15:06:33 <dynemeloun> on wallet-cli
15:10:36 <chaser[m]> 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`
15:12:22 <dynemeloun> 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
15:14:15 <dynemeloun> version is v0.17.3.0-release, i just did not rename  folder
15:25:20 <chaser[m]> <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`?
15:30:37 <dynemeloun> 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
15:31:26 <dynemeloun> 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
15:32:02 <dynemeloun> both made raw_monero_tx
15:33:18 <chaser[m]> thanks for checking! then I wonder what else could cause this
15:33:52 <chaser[m]> it sure is not the wallet flags
15:47:49 <SerHack> I do not remember correctly, are monero binaries statically compiled or dynamically linked?
16:10:42 <hyc> release binaries are static
16:10:52 <hyc> they must be, to be usable on multiple distros
16:16:44 <SerHack> thanks hyc
18:08:51 <hyc> they still use dynamic libc. but just about all other dependencies are static
18:24:45 <DeanGuss> Big thank you to everybody involved with getting tor p2p support integrated in the latest release!  Been waiting *soooo* long for that! THANK YOU!!!!
18:24:55 <DeanGuss> https://github.com/monero-project/monero/issues/6950 You can finally close this because torsocks is no longer needed
18:25:13 <DeanGuss> Might be worth updating monerod.service systemd file @ https://github.com/monero-project/monero/blob/master/utils/systemd/monerod.service
18:25:41 <DeanGuss> to reflect the fact that torsocks is not required any longer
18:28:46 <xorpd[m]> <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.
18:42:28 <xorpd[m]> <moneromooo> "IIRC you get number of confirmat..." <- Thanks! get_transfer_by_txid() of the wallet rpc looks like something that I can use.
18:48:37 <moneromooo> Not as far as I know.
18:49:36 <moneromooo> I was thinking of getinfo, which can return height and diff that aren't in sync.
18:50:18 <moneromooo> Which reminds me, I added a lock at some point which goes some way to fixing this... Might actually have fixed it...
18:52:02 <moneromooo> 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.
18:53:01 <jberman[m]> I did that for getinfo + some other functions here: https://github.com/monero-project/monero/pull/7936
18:54:00 <moneromooo> Nice, thanks :)
19:16:31 <BigmenPixel[m]> Hello. Why is monero-wallet-gui not starting?... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/123aa2de4d128591cae0d23dfbef65e193993ccc)
19:17:28 <BigmenPixel[m]>  * Hello. Why is monero-wallet-gui not starting? (0.17.3.0)... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/1f416229ba4f7c8899e6eedd15f4f2f9c97801b2)
19:20:31 <moneromooo> What architecture ?
19:20:44 <BigmenPixel[m]> moneromooo: x86_64
19:20:56 <moneromooo> Ouch. Dunno then.
19:21:07 <moneromooo> Did you compile it yourself ?
19:22:12 <BigmenPixel[m]> moneromooo: No. It's precompiled flatpak and archlinux packages
19:22:48 <moneromooo> Ah, if precompiled from not getmonero.org, possibly it got compiled with insns specific to a later family.
19:22:57 <moneromooo> Do you have an old CPU ?
19:23:30 <moneromooo> Old being defined as older than the person who built that precompiled binary :D
19:23:48 <BigmenPixel[m]> moneromooo: Intel Pentium 5405U (2019 like...)
19:24:03 <moneromooo> OK, sounds pretty recent. Out of ideas then, sorry.
19:24:47 <moneromooo> Pentium sounds very 1999 though.
19:24:47 <BigmenPixel[m]> Sadly... :(
19:27:02 <BigmenPixel[m]> moneromooo: https://en.wikichip.org/wiki/intel/pentium_gold/5405u
19:27:02 <BigmenPixel[m]> Q1, 2019
19:27:27 <BigmenPixel[m]> Time to change CPU :)
21:01:03 <chaser[m]> <DeanGuss> "https://github.com/monero-..." <- with that, what is now the best way to torify Monero?