CoinOS with nonkycai provider causes ReadableStream error leading to fund loss

[sh1ftred]

Issue Description

When using CoinOS with the nonkycai provider, we encounter an object ReadableStream error. This error is critical as it leads to loss of funds.

Provider Details

• Provider: nonkycai
• Service: CoinOS
• Error Type: ReadableStream object error

Impact

• ⚠️ CRITICAL: Results in loss of funds
• Affects users attempting to use CoinOS through nonkycai provider

Priority

This issue requires immediate attention due to the financial impact on users.

[sh1ftred]

🚨 Critical Fix Implemented

I've identified and fixed the root cause of the CoinOS ReadableStream error that was causing fund loss.

🔍 Root Cause

The issue occurs when the nonkycai provider returns [object ReadableStream] instead of proper response content. The existing code tried to parse this as JSON/text, causing processing failures without issuing refunds.

🛠️ Solution

Pull Request #197 implements a comprehensive fix:

1. ReadableStream Detection - Added safe_read_response_content() to detect and handle ReadableStream objects
2. Emergency Refund System - Automatically issues refunds when ReadableStream errors are detected
3. Fund Loss Prevention - Multiple safety nets ensure users always get refunds
4. Comprehensive Testing - Added extensive test coverage for all edge cases

🛡️ Fund Protection

• Emergency refunds issued immediately on ReadableStream detection
• Small processing fee (60 units) deducted to cover transaction costs
• Multiple retry attempts for refund token creation
• Fallback mechanisms when primary refund fails

📊 Impact

• ✅ Prevents fund loss - Users get refunds when errors occur
• ✅ Maintains functionality - Graceful degradation to streaming responses
• ✅ Better monitoring - Enhanced logging for debugging
• ✅ Backward compatible - No breaking changes

The fix is ready for immediate deployment and will prevent any further fund loss from this issue.

PR Link: #197