11:58:45 <gingeropolous> selsta, im working on getting 66.85.74.134 back online. monerod hung. i'll make it restart daily to "fix"
11:59:09 <selsta> gingeropolous: which version are you running? and can you get a backtrace?
11:59:22 <gingeropolous> looks like it was original 18 release
11:59:58 <selsta> ok, try to update to the last version and see if you still have issues
12:00:12 <selsta> daily restart should not be necessary theoretically
12:00:52 <gingeropolous> so not master, but a versioned release? but i love running master...
12:09:47 <gingeropolous> hrm. it had 104 rpc connections. ima disable its function as a remote node
12:38:46 <selsta> gingeropolous: master is fine too
12:47:49 <erembax[m]> <moneromooo> "erembax: it's mostly random..." <-  Thanks. Do you know if it will try to avoid using more than one output unless that is necessary?
12:48:11 <moneromooo> Yes, and it will not.
12:48:46 <erembax[m]> Makes sense as using on output gives the best privacy.
12:48:56 <moneromooo> Arguably, it should. I originally made it try to use two to get more txes to conform to the typical 2 in and 2 out format, but I'm not sure it was a good idea anymore.
12:49:28 <erembax[m]> Was that a thing 2 in 2 out? Why?
12:50:01 <erembax[m]> Ah to create doubt about which output is the payment!
12:50:03 <moneromooo> I don't understand the first question. And why 2 in 2 out was because most txes that that way alreadu.
12:50:17 <moneromooo> >= 2 out is enforced for rct txes.
12:50:29 <moneromooo> It's the number of ins that's more variable.
12:51:47 <erembax[m]> moneromooo: But if I sent an output to myself it creates only 1 output no?
12:52:03 <moneromooo> If it's a rct tx, no.
12:52:42 <erembax[m]> All tx have rct right? Ringct
12:52:48 <moneromooo> Most.
12:53:14 <moneromooo> If you spend very old unmixable outs, you can create non rct outs. They're rare nowadays though.
12:53:38 <erembax[m]> Aha, that is before my time I think 
12:53:45 <moneromooo> And in that case you *could* get a tx with one out if you tried.
12:54:20 <erembax[m]> So if I sent a recent output to myself what is the second output?
12:54:37 <moneromooo> A zero amount out sent to some random address.
12:55:42 <erembax[m]> moneromooo: Ah that's awesome, and I suppose it randomizes the order of the outputs. Can the 0 amount output be used as a decoy 
12:55:52 <moneromooo> Yes.
12:56:39 <erembax[m]> 👌
12:56:52 <erembax[m]> The more I learn the more awesome it is. 
12:57:02 <erembax[m]> I'm so done using bitcoin 
13:24:47 <selsta> gingeropolous: added back your node
13:54:37 <Rucknium[m]> erembax: You should add the question and response to https://monero.stackexchange.com/
14:30:06 <gingeropolous> selsta, cool. the node is on master now, still syncing. it wedged somewhere at ~94% with the last binary it was using. 
14:31:09 <selsta> will take a while, master doesn't update checkpoints
14:37:40 <gingeropolous> ... and its on a spinny .....
20:21:10 <jberman[m]> moneromooo: the algo still does try to use 2 inputs so long as the 2nd output the wallet tries to select is unrelated enough to the first (and it's not a large output when we don't have a lot of outputs left)
20:22:06 <jberman[m]> There are some good comments describing the algo here erembax 
20:22:11 <jberman[m]> https://github.com/monero-project/monero/blob/50aa0e8b7f11680be3954c176f2daa9ccf77b7dd/src/wallet/wallet2.cpp#L10160-L10164
20:22:16 <jberman[m]> https://github.com/monero-project/monero/blob/50aa0e8b7f11680be3954c176f2daa9ccf77b7dd/src/wallet/wallet2.cpp#L10201-L10204
20:22:22 <jberman[m]> https://github.com/monero-project/monero/blob/50aa0e8b7f11680be3954c176f2daa9ccf77b7dd/src/wallet/wallet2.cpp#L10233-L10253
21:07:32 <xmrack[m]> if someone has time could we turn this into a blog post so that there is better documentation on wallet input selection.
21:17:25 <moneromooo> Yes. Feel free to change it to not bother, I think it might be best.
22:13:22 <jeffro256[m]> guh that function is long