Yessir that's correct.
Are any steps taken to help obfuscate the final TX? Example: Bob sends Alice 166.32 NEOS via Arbitrush. Given timing and the unique amount sent. It would be trivial to discover Bob was the origin of the transaction if Alice receives 166.32 NEOS in a single output.
As of right now the only obfuscation would be the timestamp as it purposely doesn't send it right away through to prevent matching up a certain send time/amount with another masked tx's. With PoT enabled it returns the one tx, but what I can do is modify it so that the amount sent is split up into fragments and just return an array of txids.
Regards,
syntaks
I think that would help. Also, if you want to get fancy, I would consider further obfuscation. Like random amounts of uneven divisions sent at slightly differing times from different exit nodes if possible.
That's exactly what came to mind when I was reading. It's literally now in my to-do. Thanks for the input
Regards,
syntaks
As per your request, I've modified Arbitrush. When you send using it, the sent amount is fragmented, and the time at which it's sent is random within reason so as not to match up timestamps within the block chain and sequence of events. This combined with other transactions taking place using Arbitrush, will obfuscate on a much better level. The endpoint still receives the intended sum though.
Best regards,
syntaks