selat fund via Eco gasless (1 USDC, Base → Gateway/Polygon) left my wallet successfully but was never credited to Gateway, and ~18h later has not refunded either.
On-chain trace
- Source wallet:
0x921b2205cd77fc8913c6912c9a5272a439d6ffda
- Deposit tx (Base, SUCCESS):
0x6c0bc84224f367ffdd91564c6c3c09a460f185a2e1648f7f59d502493ed236d0
- 1 USDC landed at Eco deposit address
0x242871880C997CD38ade293BFa77Eb970831F657; a "Create Intent" tx fired ~2s later (Base block 49747687) but the intent was never filled
circle gateway balance --all: 0 on all 7 domains (Ethereum, Avalanche, Optimism, Arbitrum, Base, Polygon, Unichain)- Backing EOA from the deposit receipt (
0xa353db29c88ba05301cddbf948bc75e0a2201850): zero balance, zero transactions
- Method: eco gasless, domain 7 (Polygon), amount 1 USDC (~$0.98 expected after fee), ~14:11 UTC 2026-08-09
The USDC is sitting in the Eco deposit contract as an unfilled intent. The Base leg succeeded; the destination fill/credit never executed. Likely cause: sub-$1 net amount is uneconomical for a solver to fill.
Two CLI/UX bugs worth flagging
selat fund Eco gasless reports "success" on submission even when the intent never fills. The output says "Deposited 1 USDC to Gateway via Eco… lands within ~30 seconds," which reads as a completed deposit. There is no in-CLI status showing "intent pending / unfilled," so the user has no signal the money is stuck. Consider surfacing intent state, and/or warning when the amount is below a fillable threshold.selat doctor router-reachability check flip-flops between ✓ /healthz returns 200 and ✗ https://router.selat.ai unreachable or returned (network error) across runs. Direct probes show /healthz → HTTP 200 and root / → HTTP 404, so this looks like the check hitting the root (404) or a short timeout, producing false negatives. Worth hardening.
Requested
Fill the intent and credit Gateway, or refund 1 USDC to the source wallet 0x921b2205cd77fc8913c6912c9a5272a439d6ffda.
Environment: macOS (Darwin 25.5.0), Node v25.5.0, @selat-ai/selat-plugins, @circle-fin/cli.
selat fundvia Eco gasless (1 USDC, Base → Gateway/Polygon) left my wallet successfully but was never credited to Gateway, and ~18h later has not refunded either.On-chain trace
0x921b2205cd77fc8913c6912c9a5272a439d6ffda0x6c0bc84224f367ffdd91564c6c3c09a460f185a2e1648f7f59d502493ed236d00x242871880C997CD38ade293BFa77Eb970831F657; a "Create Intent" tx fired ~2s later (Base block 49747687) but the intent was never filledcircle gateway balance --all: 0 on all 7 domains (Ethereum, Avalanche, Optimism, Arbitrum, Base, Polygon, Unichain)0xa353db29c88ba05301cddbf948bc75e0a2201850): zero balance, zero transactionsThe USDC is sitting in the Eco deposit contract as an unfilled intent. The Base leg succeeded; the destination fill/credit never executed. Likely cause: sub-$1 net amount is uneconomical for a solver to fill.
Two CLI/UX bugs worth flagging
selat fundEco gasless reports "success" on submission even when the intent never fills. The output says "Deposited 1 USDC to Gateway via Eco… lands within ~30 seconds," which reads as a completed deposit. There is no in-CLI status showing "intent pending / unfilled," so the user has no signal the money is stuck. Consider surfacing intent state, and/or warning when the amount is below a fillable threshold.selat doctorrouter-reachability check flip-flops between✓ /healthz returns 200and✗ https://router.selat.ai unreachable or returned (network error)across runs. Direct probes show/healthz→ HTTP 200 and root/→ HTTP 404, so this looks like the check hitting the root (404) or a short timeout, producing false negatives. Worth hardening.Requested
Fill the intent and credit Gateway, or refund 1 USDC to the source wallet
0x921b2205cd77fc8913c6912c9a5272a439d6ffda.Environment: macOS (Darwin 25.5.0), Node v25.5.0, @selat-ai/selat-plugins, @circle-fin/cli.