06:52:23 <wfaressuissia[m]> https
06:52:53 <wfaressuissia[m]>  * "https://github.com/monero-project/monero/blob/master/src/p2p/net_node.inl#L2528" 51 outgoing connections in state before_handshake are checking p2p port of incoming peers.
07:04:28 <wfaressuissia[m]> "curl -A '' -v https://paste.debian.net/plain/1197735 | grep OUT | grep -F '/43(' | wc -l", serialized ping message size is exactly 43 bytes
10:50:17 <hyc> fyi there were ~10 more incoming conns before but I was getting out-of-fd errors from libunbound
10:50:23 <hyc> so I set in_peers 150
10:51:39 <hyc> given that it runs out of fds pretty commonly, I don't think using more than 4x the out_peers limit in probes is a good idea
12:20:04 <binaryFate> <woodser> what's the difference between the global index returned from incoming_transfers and `size_t wallet2::get_transfer_details(const crypto::key_image &ki)` ?
12:20:14 <binaryFate> <woodser> the global index is not the right value to freeze or thaw outputs, but the result of the latter is not exposed to clients of monero-wallet-rpc as far as I can tell, so they won't be able to freeze or thaw outputs by anything but the key image, if I understand correctly?
12:22:05 <moneromooo> Global index is the index in blockchain order of an output within all outputs of its amount.
12:22:18 <moneromooo> The other is the index in transfer details.
17:32:31 <binaryFate> <peach44> guys what is the purpose of check_acc_out_precomp_once
17:32:37 <binaryFate> <peach44> i see that when the wallet processes new transactions it calls this with 'already seen' = true always, meaning that this function just returns without doing anything
17:32:50 <binaryFate> <peach44> anyone know?
17:32:56 <binaryFate> <peach44> what is the purpose of check_acc_out_precomp_*
17:32:59 <peach44> I figured it out
17:33:17 <binaryFate> great :) Reposting because you were hidden on IRC at least