Skip to content

Conversation

@zeugmaster
Copy link
Owner

@zeugmaster zeugmaster commented Feb 26, 2025

Improved selector should take into account or optimize:

  • input fee
  • keyset age and active state
  • amount sort order and privacy (e.g. spend small amounts vs. spend large amounts first)
  • linear time and space complexity

The selector should use as parameters a list of ProofRepresenting objects, a target amount and unit.
Return values should be a Result type with either the optimal selection of proofs, or a meaningful failure response differentiating between different failure reasons (e.g. unit mismatch, insufficient amounts (not) including fees, etc.). This could also be done via error types.

@zeugmaster zeugmaster self-assigned this Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants