findUnspentRecords currently calls the getTransactionId API and, upon failure, assumes that the record is unspent. Using an unspecified catch block to handle core logic is an anti-pattern. The API errors can happen for unknown reasons, which would lead to false positives.
🐛 Bug Report
findUnspentRecordscurrently calls thegetTransactionIdAPI and, upon failure, assumes that the record is unspent. Using an unspecified catch block to handle core logic is an anti-pattern. The API errors can happen for unknown reasons, which would lead to false positives.