Hello. When i tried to redeem thaw 3 there was an anomaly: thaw 2 displayed “not available to redeem” and thaw 3 showed a cumulated amount corresponding to 2+3. Tentatives to redeem thaw 3 failed. Now I try to redeem thaw 3 and 4, and it’s the same problem: thaw 2 and 3 showing “not available to redeem”, and thaw 4 shows the total of 2+3+4 but tentatives to redeem fail. Can somebody help? Is it a known issue?
I am experiencing what appears to be the same issue.
An earlier thaw was successfully redeemed on-chain and the tokens were received in my registered destination wallet. I have verified the successful redemption transaction on Cardano.
However, the Redemption Portal currently shows “Redeemed so far: 0”, and the /schedule API also reports zero claimed allocations and no transaction ID for the successful previous redemption.
A later thaw now shows a cumulative redeemable amount which includes the amount that was already redeemed on-chain.
Any attempt to redeem this cumulative amount fails server-side at:
POST /thaws/{destination_address}/transactions/build
with HTTP 500 Internal Server Error.
I previously experienced the same issue with Yoroi. There’s sufficient ADA. And I can now reproduce it using another wallet interface.
This looks like a possible mismatch between the successful on-chain redemption state and the state recorded by the redemption backend.
Could someone from the Midnight team please confirm whether this is a known issue and whether affected redemption records can be reconciled with their on-chain transactions?
I am also facing the same issue, my first and second thaw was redeemed but the backend only recorded my first thaw redeemed and showed a cumulative amount for the third and now fourth where all attempts to redeem since the third thaw and now have been failing. The error message I get is “Transaction failed, please try again when you are ready.”
I faced this problem on secondfi in June during the third thaw and since secondfi has been shut down, I’ve backed up my seed phrase on typhoon and lace but both these wallets also show the same error. Based on my understanding, it is Midnight’s backend system wrongly recording the redemption values which is causing the failed subsequent redemptions. I have been sending multiple emails to midnight support on this matter but to no avail, they keep pushing the blame to secondfi or a wallet issue but it clearly isn’t and other solutions proposed like clearing cache and using different browsers doesn’t work.
Please share any other solutions if you guys have, will share more updates here from midnight support if I get any.
Hi. What email do you use to reach support team? I tried to use support@midnight.network but i get error messages like the email is undeliverable at this adress… Is there any other official reliable email? Thanks
Hi everyone, apparently the database is fixed, now the “available to redeem” displayed number is correct, the redeemed thaws are correctly marked “redeemed” and the remaining thaws redeem transaction works flawlessly ![]()