looks like it stores a 128bit number

Ohhh so those low wide and top values can be recombined to get the original 128bit number?

seems that way

Ahh thank you so much

swide is just recording the number as a string

low and top store it in 64bit variables

Yea I see now ty

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

useful/good/interesting thing to throw out there?

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.

Greetings Everyone ,

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)

s/an/a/

SparshGupta[m]: start with building the software i guess ;)

SparshGupta[m]: Have you already compiled the software and read (part of) the code?

Nope sir

I think a good starting point is installing and learning how to run the different kinds of tests.

run a testnet

Sure

^ if you are familiar with Monero's rpc calls, please review that PR so we can get it done.

hmm maybe documentation should be generated from code

You still need somebody to take care of it, which is the current issue

HI

> I didn't see any tools or example scripts to help with churning, and decided to write one.

I churn manually but more research and development into churns is good. Wrote some ideas and questions about churning here: nitter.net/AnarkioC/status/1446255669619970048

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.

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...

I don't think that feelings matter :)

> <@anarkiocrypto:halogen.city> > I didn't see any tools or example scripts to help with churning, and decided to write one.... (full message at libera.ems.host/_matrix/media/r0/do…b6ee6b5d297a8d16af3a01c64754439e3ea)

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.