I found another bug when writing unit tests - if there are multiple valid entries in a ring only one is tracked due to the DB sorting algorithm. #87 confirms the fix. I decided to put this in a separate PR to make it easier to backport into the release branch.
Hitting this case is extremely rare, you'd have to select your own output as a decoy in a ring, then have that decoy take precendence in the sorting algorithm over the real spend.
I found another bug when writing unit tests - if there are multiple valid entries in a ring only one is tracked due to the DB sorting algorithm. #87 confirms the fix. I decided to put this in a separate PR to make it easier to backport into the release branch.
Hitting this case is extremely rare, you'd have to select your own output as a decoy in a ring, then have that decoy take precendence in the sorting algorithm over the real spend.