00:19:29 <UkoeHB> looks like it stores a 128bit number
01:01:54 <bevanoff[m]1> Ohhh so those low wide and top values can be recombined to get the original 128bit number?
01:03:18 <UkoeHB> seems that way
01:03:49 <bevanoff[m]1> Ahh thank you so much
01:04:15 <UkoeHB> swide is just recording the number as a string
01:04:39 <UkoeHB> low and top store it in 64bit variables
01:06:34 <bevanoff[m]1> Yea I see now ty
14:00:21 <spackle[m]> I didn't see any tools or example scripts to help with churning, and decided to write one. I have a python script that times transactions at intervals matching the decoy selection algorithm, and performs the transactions via monero-wallet-rpc. Before publishing or expanding on it I figured I'd check in here. Has this sort of thing already been written? Is there anything you would like to me do with it? Does this sound like a
14:00:22 <spackle[m]> useful/good/interesting thing to throw out there?
14:10:23 <spackle[m]> I did see that other people have written churn handlers, though they've just selected the wait time randomly from within a range instead of trying to reproduce decoy selection.
14:21:38 <SparshGupta[m]> Greetings Everyone , 
14:21:38 <SparshGupta[m]> I am an CSE & Data Science undergrad student, here to contribute to XMR in whatever way possible. I just simply don't know where to start. I am a programmer .(Period)
14:21:51 <SparshGupta[m]> s/an/a/
14:24:24 <louipcD> SparshGupta[m]: start with building the software i guess ;)
14:26:43 <dEBRUYNE> SparshGupta[m]: Have you already compiled the software and read (part of) the code?
14:27:04 <SparshGupta[m]> Nope sir
14:29:57 <UkoeHB> I think a good starting point is installing and learning how to run the different kinds of tests.
14:30:47 <louipcD> run a testnet
14:31:11 <SparshGupta[m]> Sure 
15:20:01 <ErCiccione> https://github.com/monero-project/monero-site/pull/1448#issuecomment-962466587
15:20:19 <ErCiccione> ^ if you are familiar with Monero's rpc calls, please review that PR so we can get it done.
15:25:34 <louipcm> hmm maybe documentation should be generated from code
15:33:09 <ErCiccione> You still need somebody to take care of it, which is the current issue
16:56:11 <Guest83> HI
17:08:10 <anarkiocrypto[m]> > I didn't see any tools or example scripts to help with churning, and decided to write one.
17:08:10 <anarkiocrypto[m]> I churn manually but more research and development into churns is good. Wrote some ideas and questions about churning here: https://nitter.net/AnarkioC/status/1446255669619970048
17:08:10 <anarkiocrypto[m]> What do you think about the plausible deniability of churns: 1/11^x (x = number of churns) or less effective? Threat model is a generic colluding sender and recipient, e.g. employer -> you -> Bitcoin ATM or exchange -> you -> marketplace.
17:08:10 <anarkiocrypto[m]> Personally I feel like it is safer to wait multiple hours or better multiple days between churns if possible. Also from my experience single-input churns create 2/2 TXs, but there are often only 2 or 3 2/2 TXs included as decoys...
17:17:12 <nioc> I don't think that feelings matter :)
18:17:25 <spackle[m]> > <@anarkiocrypto:halogen.city> > I didn't see any tools or example scripts to help with churning, and decided to write one.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/0789fb6ee6b5d297a8d16af3a01c64754439e3ea)
18:19:42 <Rucknium[m]> spackle: I think overall that it's a good initiative, but use of such a script should not be promoted until churning is better understood. MRL has been trying to study it in fits and starts, but I don't think anything definitive has been concluded about best practices.