01:31:42 <guzzi> guess it is time to get back into Monero.  Spent a couple years doing my own thing on the side and learned a lot.
01:31:58 <guzzi> c++ is callin my name again
06:47:01 <dEBRUYNE> Welcome back!
13:58:17 <sethsimmons> vtnerd: not sure if you've seen or not, but BIP324 may be relevant to your work on e2ee of p2p comms: https://gist.github.com/dhruv/5b1275751bc98f3b64bcafce7876b489#Abstract
13:59:48 <sethsimmons> Initial associated PR: https://github.com/bitcoin/bitcoin/pull/18242
14:00:08 <sethsimmons> Might be useless, but as they're working on a similar protocol change at the same time figured I'd share to be sure it was known 🙂
14:09:49 <sethsimmons> For anyone who is willing and able to implement this into Monero, I will give a 5XMR bounty for it's inclusion into the codebase via an accepted PR: https://github.com/monero-project/research-lab/issues/73
14:09:50 <sethsimmons> This is the best way to get over a key UX hurdle in Monero, and seems to have no drawbacks other than the implementation necessary.
14:17:13 <sethsimmons> > <@sethsimmons:monero.social> For anyone who is willing and able to implement this into Monero, I will give a 5XMR bounty for it's inclusion into the codebase via an accepted PR: https://github.com/monero-project/research-lab/issues/73... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/7327c4c5ef5aeade87cc89ae9eb7d60ca7499baf)
15:01:06 <UkoeHB> Anyone have thoughts on SipHash for computing view tags? It was recommended to me https://github.com/veorq/SipHash
15:20:44 <sethsimmons> Already up to 15XMR 😎
15:21:02 <sech1> UkoeHB it's better to use keccak (cn_fast_hash in Monero codebase IIRC)
15:21:11 <sech1> no need to add one more hash just for one thing
15:25:01 <UkoeHB> sech1: the point is it might be way faster, which allows some speedup on view scanning
15:25:09 <UkoeHB> I will do some tests today
15:25:28 <sech1> you're optimizing 1% of the total time, the rest is scalar mult
15:25:35 <sech1> and other crypto operations
15:25:42 <UkoeHB> it might be 3%
15:25:59 <UkoeHB> so, I will test
15:26:08 <UkoeHB> since this SipHash is very trivial to use
15:27:25 <sech1> is it cryptographically secure?
15:27:41 <sech1> ok, it is
15:28:05 <sech1> we also have Blake (in RandomX), it might be also faster
15:28:20 <sech1> *Blake2
15:28:47 <sech1> since you'll be testing performance, it makes sense to test everything we have in the codebase already
15:30:32 <UkoeHB> I will take a look
16:05:35 <selsta> .merge+ 8029 8030
16:05:35 <xmr-pr> Added
16:27:20 <hyc> so for anyone curious ... I did some tests with LMDB on NFS, which appeared to work, but ...
16:27:49 <hyc> it looks like mmap'ing stuff permanently ate up RAM, possibly in the nfs daemons
16:28:34 <hyc> so the NFS server started OOM killing things even though top showed none of them were big memory consumers
16:28:58 <hyc> and top didn't show *any* big memory consumers. but 3GB went up in smoke till reboot.
18:33:54 <aberdeenik[m]> How can monero completely replace cash, what property it should be given such that it becomes a full substitute for cash. One area is the fluctuations  in price need to be stabilized. Can't it be tethered to say gold reserves?
18:35:49 <moneromooo> Crash is not tethered to gold reserves anyway. But one of the big problems is reliance on electricity.
18:36:05 <moneromooo> You can give someone cash if the power's off.
18:36:58 <moneromooo> Crash is also massively parallel. Your ability to transact in cash does not get lessened if there's a sudden massive increase of cash transactions elsewhere in the world.
18:37:21 <moneromooo> Cash is also not subject to reorgs and/or 51% attacks.
18:38:06 <moneromooo> Cash is more private (assuming the serial numbers aren't read as a matter of course)
18:40:15 <moneromooo> I see you asked the same thing in -lounge, that is a more appropriate venue indeed.
18:40:41 <aberdeenik[m]> Offline moneros can be generated right , like having a dedicated wallet for each monero and then giving it out as a card
18:40:56 <aberdeenik[m]> Which has the privatekey
18:49:51 <aberdeenik[m]> So instead of doing transaction on network we just send the card which has the  private key?
19:06:05 <UkoeHB> sech1: is it `blake256_hash()` that you want me to test?
19:07:46 <moneromooo> Probably blake2b_{init,update,final}
19:09:32 <sech1> int blake2b(void *out, size_t outlen, const void *in, size_t inlen,
19:09:32 <sech1>  const void *key, size_t keylen);
19:09:39 <UkoeHB> oh found it
19:09:44 <sech1> in monero\external\randomx\src\blake2\blake2.h
19:10:08 <sech1> the last 2 parameters can be 0
19:44:05 <UkoeHB> how do I include this into a test?
19:45:04 <moneromooo> See tests/performance_tests, make a new file (copy from, eg, cn_fast_hash.h), replace with your hash.
19:45:15 <moneromooo> Then call from main.cp
19:46:11 <moneromooo> If you want to call the whole wallet2 thing, it's more complex I guess.
19:46:21 <UkoeHB> I just want blake2b...
19:46:33 <moneromooo> Then: See tests/performance_tests, make a new file (copy from, eg, cn_fast_hash.h), replace with your hash. 
19:47:13 <moneromooo> subaddress_expand.h does call wallet2, you can start off that if you want to call the "is this output for me" thing with various hashes.
19:47:24 <UkoeHB> no I know how to do all that
19:47:39 <UkoeHB> I guess blake2 is not exposed to users of randomx
20:13:14 <UkoeHB> Ok I have perf tests running. Not sure what to do with them.
20:19:56 <UkoeHB> The tests are in here if anyone wants to look at it closer: https://github.com/UkoeHB/monero/blob/seraphis_perf/tests/performance_tests/view_scan.h.
20:22:03 <UkoeHB> On my machine: siphash 3.7us, cnhash 4.9us, blake2b 4.1us, view-scan ~72us. So cnhash -> siphash is about 1.5% faster, and cnhash -> blake2b is about 1% faster.
20:22:46 <UkoeHB> view-scan with 100% view tag failures*
20:33:02 <atomfried[m]> is this on your machine? maybe it would be nice to test this speedup on ARM to verify mobile devices and wallets will also profit 
20:33:04 <selsta> .merge+ 8020 8017
20:33:04 <xmr-pr> Added
20:33:51 <selsta> 8021, 8023, 8016, 7997 need a review, the first three are easy and the last one is just backporting
20:36:26 <UkoeHB> atomfried[m]: go for it
20:39:02 <atomfried[m]> i have a raspberry pi with an ARMv8 do you think this will be comparable to mobile phones?
20:40:47 <moneromooo> tbh, AIUI siphash is well used/tested on bitcoin so appears a safe enough choice.
20:42:06 <moneromooo> I guess it'd need a cryptographer to check whether it'd be the same properties that get exercised in both uses.
20:48:38 <UkoeHB> atomfried[m]: idk, maybe? lmao'
20:51:19 <moneromooo> Most rpi do not have hardwaes AES, and thus suck at PoW verification.
20:51:42 <moneromooo> I don't know which variants might have HW AES. Maybe yours does.
20:51:43 <atomfried[m]> hmm ok i guess it would be worthless then
20:51:53 <atomfried[m]> i will check
20:52:09 <moneromooo> For mining, certainly useless.
22:34:44 <vtnerd> sethsimmons : I was (mostly) aware of that BIP - even commented on a variation of it years ago on bitcoin-dev
22:35:55 <vtnerd> or wait this is a different BIP than what I saw previously
22:36:25 <vtnerd> a lot of the BIP is working with the existing Bitcoin protocol, which differs from the Monero protocol