Thanks for reporting and do not use third-party “wallet revalidation” dapps (e.g. syncstrand, zestlayer). Those are not Midnight-supported and are a common scam pattern.
What the error means:
The redemption API is returning NoRedeemableThaws the backend believes no thaw is available to redeem right now, with nextThaw around 2026-09-11 UTC (exact timestamp varies slightly per wallet). That’s different from a wallet signing failure; the flow never reaches your wallet because transaction build is rejected with 400.
The confusing part (and why you’re not alone): several of you see a non-zero “Redeemable now” in the portal UI while the API says NoRedeemableThaws. That points to a portal UI vs backend thaw-state mismatch, not something wrong with your wallet from the first two successful redemptions.
What to do:
- Wait don’t use random dapps; don’t re-share seeds/keys anywhere unofficial.
- Official path: we’re escalating via servicedesk
- If you want private follow-up, provide wallet address only through servicedesk or an official support channel not in this public thread.
Not a fix on your side: reinstalling wallet, “revalidating,” or third-party dapps won’t resolve a backend thaw-window / UI sync issue.
We’ll post back when we have team confirmation. Related reports: [link other forum thread].