xlmluner
11/05/2026, 9:12 AMgetFee() amount — exactly 0.000001 ETH — and the library pays it from the calling contract's own ETH balance (here the cUSDC token contract itself). Its balance was 0, so the fee payment failed after the fee refresh. The frontend attaches no ETH value and gives users no way to fund this fee, so the step is broken for everyone out of the box.
Workaround applied (proof)
1. Sent 0.01 ETH (testnet) directly to the cUSDC contract as a fee float:
tx 0x360f5dcd8595916a2ac7ea085493e3f5cc2940578cc0e6cc6a2b6169e9b6df4b
2. Retried the identical transfer → succeeded immediately:
tx 0x528dcbf7dead48400789287fbb8777c68f00fd6d1d93bc4fd685a28751485f26
3. Remaining float afterwards: 0.009999 ETH = exactly one 0.000001 ETH fee consumed.
Suggested fix
• Keep the demo cUSDC contract funded with a small ETH float and refill/monitor it, or
• Let the caller pay the input fee (msg.value = getFee()), or
• Document the requirement + show a clear frontend error instead of a raw revert.
Note: the float I added (~0.009999 ETH left) covers roughly the next 9,999 transfers — it will break again once exhausted unless fixed.
(2/2)