15:31:55 Hi there, is it possible to set store-tx-info to 0 permanently (in the cli wallet)? I can set all other options permanently, but store-tx-info always reverts to 1 after saving and restarting the wallet... Thanks! 15:34:05 It's a bug then. It's meant to be persistent. 15:35:37 OK, I see what's going on. It's some backward compat name. I'll fix. 15:36:45 thanks! 18:48:03 so i was wondering, if block rewards are now standardized in the build im doing, can i just axe the out_amounts pointers? 18:49:31 but i think it was pointed out yesterday that it was already being done with decompose_amounts_into_digits line 18:50:12 I don't see the point. 18:50:17 Isthmus moneromooo anybody else : would you happen to know the average relay time for a block or tx between nodes? asking for a friend 18:51:13 I don't. There is no ACK so you'd need to have two nodes with logs and keeping close NTP. 18:51:31 Connected but not on the same network. 18:52:22 yeah, trying to determine the dandelion++ embargo timeout magic number 18:52:27 Insight: removing them would break some tests which rely on old versions too. 18:52:33 The folks in #noncesense-research-lab are looking into propagation and have taken data 18:52:45 Not sure how much they can extrapolate their work to general nodes 18:53:14 thats why I pinged Isthmus, but as you stated I wasn't sure if they could determine an invidual hop time 18:53:45 the Bitcoin numbers are _probably_ close, but our latencies are going to be slightly different since the code is not copied 18:53:56 yeah i figured. 19:16:18 @vtnerd we have prop time estimates for the whole network but that's over an unknown number of hops 19:16:28 relay time probably dependent on local topology 19:16:51 I think that there are clever ways we could collect data to answer this question, however 19:17:37 yes it depends on topology - the embargo timer is supposed to be slightly higher than the upper bound on the expected time to be fluffed 19:17:45 * Isthmus nods 19:17:50 *expected time until fluffed 19:17:50 Suppose we see from peerlists that node B is connected to node C 19:17:56 And we attach an archival node on either side 19:17:59 A--B--C--D 19:18:04 Oh, hold on, incoming call 19:18:29 LIFO. 19:21:14 hmm, so if I mention his name again it preempts the call? 19:22:39 Likely. 19:23:02 Unless stack overflow I guess ^_^