01:24:12 <moneromooo> Someone reported 4 MB data being exchanged when connecting a wallet to a daemon. I get ~ 2.5 kB here. So apply https://github.com/moneromooo-monero/bitmonero/commit/ea906f3fbafd15f77391d228f20a192b65da472a, run with *.dump*:TRACE, repro, compress the log, post it somewhere.
01:24:23 <moneromooo> And make sure the wallet is synced first. And make sure the daemon is trusted.
01:37:00 <moneromooo> kayront: ping, that was you
08:50:50 <Flenst> o/
08:51:05 <rottensox> \o
08:53:01 <Flenst> I am currently trying to find ways for monitoring my public node. I found so far the "on_get_blocks" DEBUG log message. If I understand it right this is close to what I search. (statistics of the usage of my rpc for remote node purposes)
08:55:19 <Flenst> Is there something built-in I did not find? Basically I want to monitor stuff like "how many blocks did I distribute to other nodes" and "how many blocks did my public node check for other wallets?"
09:21:02 <M5M400> moneromooo: around?
09:23:31 <M5M400> or anyone who can answer some technical questions about get_transfer_by_txid
09:27:44 <M5M400> dEBRUYNE: maybe?
09:28:04 <sech1> what questions?
09:28:13 <sech1> I can look in the code
11:00:31 <moneromooo> There is rpc_access_tracking.
11:05:35 <Flenst> Thx, I will take a look.
11:31:05 <spoke0> is there still a switch to send out long payment_id's and if what version of the wallet uses it in v0.15.0.1
11:31:28 <fluffypony> you have to say a prayer, rotate three times, and throw salt over your left shoulder
11:37:14 <rottensox> lol.
11:37:28 <moneromooo> The code was removed.
11:37:39 <moneromooo> From the cli wallet anyway.
11:37:40 <rottensox> payment ids are ded.
11:37:47 <fluffypony> rip payment ids
11:47:00 <spoke0> i was just a bit confused, since the rpc transfer call used to take a parameter payment_id, i suspected that it would make an in integrated address from that since v0.14.1.2, but it looks that was not the case since this parameter is completely gone from that endpoint now
11:47:46 <Inge-> good riddance.
13:30:21 <moneromooo> I wanted to mirror gitian.sigs to repo.getmonero.org, so that the update program would not be DoSed by github being down. Turns out we can't pull mirrors, only push. I suggest moving gitian.sigs to repo.getmonero.org, and we can mirror it to github instead. Opinions ?
13:31:13 <moneromooo> We could also make a manual mirror. This would also protect against the master repo being compromised auto-compromising the second one.
13:31:25 <moneromooo> The tool would check both for valid sigs.
15:09:09 <scoobybejesus> I'm thankful for stability.  `Height: 1976913/1976913 (100.0%) on mainnet, not mining, net hash 297.42 MH/s, v11, update needed, 8(out)+93(in) connections, uptime 183d 1h 21m 7s`  ... Now time to switch to v0.15...
15:48:53 <M5M400> .tr Buongiorno sto usando ez monero miner scaricato da microsoft store però non mi aggiorna il saldo volevo sapere come configurare app e quando il saldo viene aggiornato grazie
15:49:08 <M5M400> .tr stronzo
15:49:12 <M5M400> .rip
15:49:34 <M5M400> man, I'm spamming in the wrong channel again. they always look the same after a matrix meltdown. sry
16:37:15 <peach34> does anyone know why the ledger app (loaded from source) refuses to allow the cli to pull blocks unless the DEBUG_HWDEVICE and IODUMMYCRYPT flags are turned on?