You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to recognize a series of successive joins on the the blockchain. Starting at an initially given tx, we would trace back its history or origin to see how many prior join transactions it is the child of.
The text was updated successfully, but these errors were encountered:
Yes, one possible initial implementation would be to simply specify a depth of how far into the history you want to scan. It would likely be sane to have a max depth to scan in any case. A join transaction can be defined as a transaction with multiple inputs and multiple outputs, where the outputs are at least 2 of an identical amount which would make it impossible to know the source input with certainty.
We should be able to recognize a series of successive joins on the the blockchain. Starting at an initially given tx, we would trace back its history or origin to see how many prior join transactions it is the child of.
The text was updated successfully, but these errors were encountered: