bonedaddy/mychurnero

a monero churning service designed to automatically churn your monero for you

mychurnero's Issues

v0.0.1

• Proper churnable address selection (todo)
  • when retrieving address get balance, this requires altering AddressBalance function to accept account and sub account index
  • Ignore addresses with balance below a certain amount
• Proper scheduling of transactions
• Prevent rescheduling of existing transactions
• Better churn account handling (todo)
  • right now during service initialization we check existing accounts to see if one exists whose index matches the desired churn account index
  • lets say we have churn account index of 99 and only have 2 active accounts, this check will obviously fail and we will create an account to churn to, however it wont match the index we want

Make Cool Graphs Of Churned Transaction

It would be cool to make a graph of churned transactions, outputs they include, etc... One possibility would be https://github.com/m1gwings/treedrawer

Enable Tx Fee Fingeprinting And Delay Analysis

One method of resisting timing delay analysis through tx fee amount is indicated here and would be rounding the fee amount to a few digits however this fingerprints the implementation.

A possibility to avoid this would be randomly determining the number of digits, and round amount and set this via the configuration file. This in theory should mitigate fingerprinting the mychurnero implementation as a whole, however it would fingerprint an individual instance of a running mychurnero service.

Add MermaidJS Diagrams Explaining Workflows

Using mermaidjs we can create diagrams explaining workflows

Desired Features

• Non-uniform random distribution for churn as decoy members are chosen from non-uniform distribution using a gamma distribution

Possible Issues

• Timing leak delays between tx creation and tx submission
  • https://web.getmonero.org/library/Zero-to-Monero-2-0-0.pdf section 7.3.4
  • monero-project/research-lab#70