00:22:13 <Insight> in what file is the fee calculated
00:23:33 <Insight> transaction fees to be precise
00:27:47 <Insight> or i guess where is "fee" defined
00:35:59 <moneromooo> blockchain.cpp IIRC.
00:36:17 <moneromooo> grep for "estimate_fee" and you should find it, or links to it.
00:36:58 <moneromooo> Nope, I just looked it up, it's get_dynamic_base_fee_estimate (blockchain.cpp)
00:54:29 <Insight> damn i used the fee from tx_pool.cpp
15:31:17 <sarang> So I had hoped that BP partial rewinding could be useful for more general sender-recipient data hiding, but I think it has to be limited to data that only the sender might wish to later recover
15:32:41 <sarang> If the recipient knew the PRNG seed too, it could brute-force all amounts (but not Pedersen masks), even those not destined for it
15:33:09 <sarang> However, the sender already knows those
15:33:28 <sarang> It could be used for something like a transaction private key
17:03:45 <sarang> Reminder: research meeting in #monero-research-lab at 18:00 UTC today (about an hour from now)
18:43:17 <rosel> Hi, I'm synching the blockchain from scratch (wallet resotre height is 0), I'm at 50% and somehow my data.mdb only weigh 8 GB. I've stopped and restarted the deamon and it continued where it was (50%).
18:43:44 <rosel> Is that expected ? It used to weigh 60+ GB.
18:43:57 <hyc> sure, but earlier blocks were much smaller
18:44:24 <hyc> pre-ringCT transactions were much smaller. so yes, it sounds normal.
18:44:58 <rosel> Oh, I see. So the next 50% should be about 50GB ?
18:45:12 <rosel> that would make sense
18:45:19 <rosel> thanks hyc
18:45:53 <sarang> It would be interesting to also have some kind of time estimate
18:46:10 <sarang> (perhaps not feasible)
20:01:49 <koe> https://github.com/monero-project/research-lab/issues/58
20:26:19 <koe> Im wondering about classify_addresses(), in particular the special case where the change address is a subaddress. It seems like num_subaddresses will stay at 0, and so there won't be a tx_pubkey created for it.
20:27:11 <koe> construct_tx_with_tx_key() and generate_output_ephemeral_keys() are the two places that determination would be made
20:41:13 <koe> unless the one-time address for change outputs is calculated different.. hm
20:43:28 <koe> and yep that's how it's done; quite complex functions whew
21:00:56 <sarang> "quite complex functions" seems like a good description of the codebase sometimes :D
21:01:55 <koe> I currently have around 30 tabs open, 10 tabs each for three different function mazes
21:13:37 <hyc> hey if it was easy everyone would be doing it......