Request failed with status code 400?

Wallet
,
1

Yesterday I went to redeem my midnight tokens through the portal but I kept getting this message error. I’ve tried again this morning still the same issue. I never had any problems before from previous redemptions until now :frowning: is there any update on fix for this from the midnight team?

I took my issue to Reddit commenters recommended I use a dapp called syncstrand or zestlayer to revalidate my wallet. Are those dapps legit and will it fix my issue? I don’t want to take that risk.. please help!

2

I’m having the same issue. The first two redemptions worked just fine, but this one keeps erroring out.

I wouldn’t trust those suggestions. Scammers always scammin!

1 Like
3

I’m relieved to see I’m not the only one with this issue! :pensive_face: And yes those dapps look sketchy to say the very least for now I’m just going to wait it out, the last 2 redemptions worked perfectly fine. Do you know of any update or fix on this issue? I can’t seem to fine anything from the midnight team addressing this concern..

4

Hi Midnight team,

I am seeing the same “Request failed with status code 400” issue when trying to redeem NIGHT. I am intentionally not sharing my wallet address publicly.

The portal UI shows that I have a thaw amount currently redeemable, and my previous redemptions completed successfully. However, when I click Redeem and confirm the wallet selection, the flow never reaches the wallet signing step.

The failing request is:

POST https://mainnet.prod.gd.midnighttge.io/thaws/[redacted-address]/transactions/build

Response:

{
  "info": "NoRedeemableThaws {nextThaw = POSIXTime {getPOSIXTime = 1789084800000}, now = POSIXTime {getPOSIXTime = 1782123376096}}",
  "message": "Incorrect build transaction request",
  "type": "build_transaction_incorrect_request"
}

The backend says NoRedeemableThaws and reports the next thaw as 2026-09-11 00:00:00 UTC, while the portal UI still shows an amount as redeemable now. Could someone from the team check why the frontend and backend thaw state disagree?

I can provide my wallet address privately through an official support channel if needed. I will not use any third-party “wallet revalidation” dapps and would appreciate official guidance.

1 Like
5

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:

  1. Wait don’t use random dapps; don’t re-share seeds/keys anywhere unofficial.
  2. Official path: we’re escalating via servicedesk
  3. 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].

4 Likes
6

Thanks for the detailed response! Will be on the look out for an update!

1 Like