Hi @MidnightNtwrk team,
I am posting this as a separate issue because this has remained unresolved for five days.
Since June 22, 2026, the official NIGHT redemption portal has shown that my current thaw is redeemable. However, every attempt to redeem fails before the wallet-signing step with:
“Request failed with status code 400”
The backend response is:
{
“info”: “NoRedeemableThaws {nextThaw = POSIXTime {getPOSIXTime = 1789084800000}, now = POSIXTime {getPOSIXTime = 1782123376096}}”,
“message”: “Incorrect build transaction request”,
“type”: “build_transaction_incorrect_request”
}
This is not a completed redemption:
- The current thaw was not redeemed.
- The flow never reaches wallet signing.
- No transaction hash is created.
- No new NIGHT output has arrived on-chain.
- My address shows only the two previous successful redemption outputs.
- I cleared site data and tried a different wallet, but the same HTTP 400 error remains.
The portal tells me the thaw is redeemable, while the backend says there are no redeemable thaws and reports the next thaw as September 11, 2026. These two states directly contradict each other.
At this point, this does not appear to be a wallet, browser, cache, or user-side issue. It appears to be an allocation/thaw state problem in the official redemption system.
I need a clear response from the Midnight team:
- Is this a known issue affecting the current thaw period?
- Can someone check whether the allocation has been incorrectly marked as unavailable, consumed, or redeemed on the backend?
- What is the official private support channel for providing my wallet address securely?
- Is there an expected resolution date?
Please do not direct users to third-party “wallet validation” or “revalidation” services. I will provide my address only through a verified official Midnight support channel.
I expect an acknowledgement and a concrete next step, not another generic cache or wallet recommendation.
Hi @adavolun,
Thank you for the detailed report and for separating this from typical wallet/browser troubleshooting.
Official update (28 June 2026): The Midnight Foundation has temporarily suspended Glacier Drop redemptions as a precaution following a security incident affecting a subset of Cardano wallets associated with SecondFi.
- This does not relate to Midnight infrastructure, products, or services.
- All redemptions are paused while additional safeguards are implemented including for users not linked to the incident.
- Redemptions will resume when it is appropriate to do so. Updates will be published on official channels.
Announcement: Glacier Drop Redemptions Temporarily Suspended | Midnight blog
Relevance to your case
The behaviour you describe the portal indicating a redeemable thaw, while the backend returns HTTP 400 with NoRedeemableThaws before wallet signing is consistent with redemption being blocked at the service layer during the suspension. The UI/backend inconsistency you reported may warrant separate investigation, but redemption attempts are expected to fail until the pause is lifted. This is not something that can be resolved by changing wallet, browser, or cache at this time.
Your questions
Known issue for the current thaw period?
Redemptions are globally paused from 28 June 2026. Failures before that date may reflect a separate backend state issue; failures since are expected under the suspension.
Expected resolution date?
No public ETA at this time. Monitor the blog and Discord announcements for restoration notice.
Recommended next steps
- Monitor Midnight | Blog and official Discord announcements for resumption notice.
- If you require allocation verification before restoration, open a ticket here
- Do not use third-party “wallet validation” or “revalidation” services.
- Do not share seed phrases, recovery phrases, or private keys. Midnight will never request these via DM.
Thank you for your patience.