Routstr/sixty-nuts

AI Summary: The task is to investigate the necessity of the `_proofdict_to_mint_proof` function in `sixty_nuts/wallet.py`, document the reason for its existence (if needed), and potentially remove it if redundant. This involves code analysis to understand the data transformation and its impact on the wallet's functionality.

AI Summary: The task is to optimize the `_swap_proof_denominations` function within the Sixty Nuts Python wallet. Currently, it's a placeholder. The improvement involves adding logic to check if existing proofs already match the target denominations before initiating a swap. This optimization aims to reduce unnecessary calls to the Cashu mint API, improving efficiency.

AI Summary: The task is to implement a mapping within the `WalletState` class that links each proof ID to its corresponding event ID. This mapping will improve efficiency in managing proofs and handling rollover operations within the Sixty Nuts Bitcoin L3 wallet. The implementation should accurately track the event origin of each proof and integrate seamlessly with existing proof management functionalities.

AI Summary: The task requires implementing Lightning Network payment functionality within the Sixty Nuts wallet to enable cross-mint transfers. This involves integrating with a Lightning node or payment service, handling payment confirmations and proof minting, managing timeouts, and implementing error handling for failed payments. Both automated and manual payment flows should be supported.

AI Summary: Implement the `rebalance_until_target()` function in the Python `sixty_nuts` library. This function should automatically transfer funds between different Cashu mints to ensure a specified target mint has a sufficient balance. The implementation needs to consider Lightning payment infrastructure, fee optimization, and handle partial transfers efficiently.

AI Summary: Implement the `roll_over_proofs()` function in the Python `sixty_nuts` library to handle partial spends of Cashu tokens according to the NIP-60 specification. This involves creating a new token event with unspent proofs, marking the old event as superseded, and handling potential errors. The function should correctly format proofs, create and publish the new event, and return the new token ID.