03:47:35 https://fluff-guilty-aaf.notion.site/Appeal-for-Assistance-Victim-of-FTX-Scam-a26b3e3a65b241008934532d8af31c4d 18:36:13 selsta (rbrunner advised me to seek your help) do you know how to disable github checks? 18:36:13 initially github didn't do any checks in my draft PR (https://github.com/seraphis-migration/monero/pull/16), but suddenly they appeared after every commit 20:47:36 Do we have something like performance benchmark/test in our testcases? If yes, which one should I run to focus mostly on performance. 20:55:50 tests/performance_tests 20:56:26 Run --help to see interesting options. 20:59:20 tx 21:06:39 Hi all 21:06:39 just a random question... with Seraphis and transaction chaining, will it be possible to build something like Lightning (I guess with PTLCs instead of HTLC)? 21:09:33 Hello 21:09:54 Is there anyone who can help me? 21:14:46 Monero Support 21:15:22 > <@m-relay:monero.social> Is there anyone who can help me? 21:15:22 In reply to @m-relay:monero.social 21:15:22 Is there anyone who can help me? 21:15:23 Monero Support Monero Support 21:15:39 > <@m-relay:monero.social> Is there anyone who can help me? 21:15:39 In reply to m-relay 21:15:40 Is there anyone who can help me? 21:15:40 In reply to @m-relay:monero.social 21:15:41 Is there anyone who can help me? 21:15:41 Monero Support 21:16:43 I have a question about Monero GUI Wallet connections 21:17:00 I think this is a developer challenge 21:17:49 Would write in the monero support channel.. This room is more about the monero development 21:18:27 I can't find Monero Support Channel here 21:22:00 Alright. Whats the issue? 21:22:57 Since today, Monero GUI Wallet on macOS started asking permission to connect to hundreds of different external IP addresses 21:23:10 I have LittleSnitch to monitor my connection 21:23:44 And this was very, very strange since the wallet finished to sync 5 days ago 21:24:38 These are few example: 21:24:41 action: deny 21:24:42 direction: outgoing 21:24:42 priority: regular 21:24:43 process: /Applications/monero-wallet-gui.app/Contents/MacOS/monero-wallet-gui 21:24:43 owner: me 21:24:44 destination: 23.88.42.188 21:24:44 ports: any 21:24:45 protocol: any 21:24:45 notes: On 15 Jan 2024, monero-wallet-gui via monerod tried to establish a connection to 23.88.42.188. The request was denied via connection alert. 21:24:46 action: deny 21:24:46 direction: outgoing 21:24:47 priority: regular 21:24:47 process: /Applications/monero-wallet-gui.app/Contents/MacOS/monero-wallet-gui 21:24:48 owner: me 21:24:48 destination: 23.106.62.20 21:24:49 ports: any 21:24:49 protocol: any 21:24:50 notes: On 15 Jan 2024, monero-wallet-gui via monerod tried to establish a connection to 23.106.62.20. The request was denied via connection alert. 21:25:01 process: /Applications/monero-wallet-gui.app/Contents/MacOS/monero-wallet-gui 21:25:01 owner: me 21:25:02 destination: 37.187.74.171 21:25:02 ports: any 21:25:03 protocol: any 21:25:03 notes: On 15 Jan 2024, monero-wallet-gui via monerod tried to establish a connection to 37.187.74.171. The request was denied via connection alert. 21:26:26 Some of these IP addresses belong to a into this list: 21:26:39 *to static.chello.pl 21:26:56 https://gist.github.com/cablej/bdc2ee2c84915d0b68eec9d4d4747e19 21:27:11 This is the list 21:28:55 I received 89 different outgoing request related to 89 different IP addresses until I force closed the app 21:29:20 It was driving me crazy 21:30:10 That is a seed node ip 21:31:34 More ontopic in #monero-gui / #monero 21:31:52 Why did it start after one week? 21:32:05 The local node was already updated 22:38:24 Did you switch to simple/boostrap mode? 22:40:23 Unrelated: does anyone know why the design decision was made to not do batch RingCT signature verification when adding transactions to the main chain? 23:06:46 jeffro256: if you batch verify then it's a DOS vector because you need to redo verification on batch failure 23:06:54 To identify the culprit 23:08:45 Makes sense, but then why do we do it to get the txs to enter the mempool? Is it just because we can try multiple at a time and don't have to hold the blockchain lock so compute time isn't as critical? 23:09:45 Or rather, failures aren't as critical 23:11:05 *multiple batches 23:16:30 That much I don’t know