Appreciate the work being done. Realistically we probably need a decision in about 14 days so we don’t miss out on this if Trezor fails. The only other possibly compatible device appears to have many issues and may require support or multiple orders to get a working one, from user reviews of the thing.
Can you give us an idea of what date you’re targetting for your “we’re probably not going to make it” message? We don’t want to miss out because of any misplaced hubris.
Saying you’ll get it done by Oct 4th is kind of concerning. I mean if you finish it on Oct 4th, 10 minutes before the deadline… technically you met your goal… but we’re all going to miss out. And if you fail last minute, we all lose. So I suggest setting a cut-off date now and letting us know what date that is so we can all plan.
I know this isn’t a constructive question… but can you explain why development for this apparently wasn’t started until the drop? It makes me very wary of trusting Trezor devices for future needs if this is how development goes. An explanation seems appropriate to your customers and seems to have gone unanswered. Apologies if I missed the answer somewhere in this thread.
I want to reassure you that an October 4 delivery date is not our goal — we don’t want anyone forced into a scenario of having uncertainty about whether to hold out for a last minute claim.
Unfortunately, I don’t have an exact date yet for when we will know if Trezor support will exist. The additional software changes needed for compatibility with Midnight’s claim portal have taken longer to finalize than the August 26 CIP-8 PR merge.
I know that uncertainty is frustrating, and I’ll continue to post updates here as soon as there’s concrete progress to share.
Everyone makes mistakes and software often breaks. That is not the issue in my mind, its what does a “company” do when that happens. Been thru the trenches in those scenarios in multiple tech industries and its what you do when that stuff happens that matters
Look up and get the general context here. As an example Vampiric.VEGAN had to post that there was a github commit related to this fix and NickW chimes it after the fact.
I too have long pushed and bought Trezor but no longer. Words are cheap- watch what a company does, that is what matters. It should be crystal clear to those reading this where you stand in Trezor’s eyes
Thanks NickW,
This is currently race against clock, we have not a lot of time to claim, only one month left and we still do not have a solution, but I believe you can make it happen…
Like always I was trying to check if problem with claim is not on midnight front end and to my surprise I was able to claim:
Trezor T last SW
yoroi web integration
Lace DApp extension for destination address
I used claim midnight web page:
claim —> cardano
select SW integration Yoroi (which is linked to my HW trezor wallet)
You will see XXX midnight token number and new Cardano address
I have selected option other wallet and selected Lace (double checked if address is correct)
Press claim
You will get popup with redirection to trezor HUB web page to select wallet and confirm signature
confirm 0 ADA signature on Trezor HW wallet
I expected error, but I was shocked that I was able to get web integration page (trezor HUB default confirmation —> without passkey, with passkey, our default web based integration)
Claim successful
double checked check your claim and provided Lace destination wallet and I see my ETH claim and ADA claim and information that mode 2 is used which probably means that 2 wallet were used to claim.
So I can confirm that somehow it works with GOOGLE CHROME and Yoroi (HW integration) and LACE (midnight token destination address)…
Whole description, they allow null signature on midnight front end.
https ://x.com/midnightfdn/status/1962571920441831603?s=46&t=JIWq7BXdmlwcjwbclt14hw
Hi Delaneybob,
I know this is probably temporary fix done by midnight team, which I really appreciate.
You are right, I would like to get full support from Trezor, simply due to fact that next steps like redemption or thaw might require CIP8/30 support and this is only fix to claim in 60 days time window.
Hey NickW,
Please escalate providing a date that Trezor can commit to. The way Trezor has handled this so far is unacceptable. Trezor users should not have to practically beg to provide support for this. This is basically what took place. Trezor decided against the PR and now every time users are inquiring on this (via this forum and via X), Trezor is dancing around this issue by providing a world salad with zero value.
welcome, but all credits go to Midnight team, they actually changed claim method to make people like us be able to claim, in case Trezor team will not provide a E2E solution…
I have finally performed my first successful hardware wallet claim using my Trezor T with a hidden passphrase.
The steps that finally worked was to use Yoroi as per Dario2025 (using the new Null transaction signing option) but I used the default unused destination address that Yoroi provided (which was the same unused destination address that Eternl provided when I initially tried it). Lace provides a different default unused destination address which should also work.
Other things to note which may or may not have contributed to the successful claim:
Browser: Brave 1.81.137 (Official Build) (64-bit) - Brave Shields turned off.
OS: Windows 11 Pro
Wallet Software: Trezor Suite (25.8.2)
Wallet Firmware: Trezor T (2.8.10)
Now here is what I tried that did not work:
Claiming via Lace wallet. Using either the default unused destination address it provides or replacing it with the address Eternl / Yoroi provides.
Fails straight after the “hold to confirm” button stage on the Trezor T.
Error message is always the same “Invalid witness request”.
Claiming via the Eternl wallet fails even before sending the transaction to the Trezor T. Seems to be an issue with Eternl not liking the new Null transaction signing method. A future update from Eternl may resolve this.
I still have a few more wallets to claim but will leave 1 or 2 wallets unclaimed until the last week on the deadline so that I can try out any new Trezor / Keystone firmware if they release them before the month ends.
Authentication failure: Trezor transport failed due to TransportError: Transport failure: Trezor transport failed due to TransportError: Transport failure: Failed to export extended account public keyTrezorKeyAgent.signTransaction (chrome-extension://gafhhkghbfjjkeiendhlofajokpaflmk/app/228.js:1:1634903)
Tried both Edge and Brave via Lace Wallet, passphrase, null transaction. Same error. used external unused ADA address.
try to use Yoroi only, I used Lace as the target wallet due to full support of NIGHT and DUST, but using only Yoroi ass claim and target (where Night token will be dropped) should work as well.
