Trezor support of Midnight airdrop

Coins and transactions Supported coins
1

We have some great news to share about Trezor support of the Midnight airdrop! The new firmware for Trezor Safe 5, Safe 3, and Model T (version 2.9.1) supports the message signing needed to complete the claim process on the Midnight portal directly.

First things first: Check if you are eligible for the claim

  1. Head over to :point_right: https://claim.midnight.gd/
  2. Start a new claim
  3. Choose “I want to enter an address manually”
  4. Enter your Cardano address
  5. If your address is eligible, simply click “Next” to continue.

Step two: Enter your claim address

  1. Select “I want to enter an address manually”
  2. Paste an unused Cardano address (make sure it hasn’t been used before)
  3. Read and accept the terms and conditions.

Step three: Make sure your Trezor is up to date

Before signing the message, make sure your Trezor is running the latest signed firmware (v2.9.1).

  1. To do so, open Trezor Suite
  2. Make sure Trezor Suite is updated to the latest version, 25.9.2 or higher, by going to Settings > Application > Trezor Suite version
  3. If your version is still below version 25.9.2, update it by clicking the Check for updates button and following the prompts for updating.
  4. After updating Trezor Suite, you’ll be able to update your Trezor device firmware to 2.9.1.

Step four: Sign the message

  1. In Trezor Suite, open “Sign message” under your Cardano account (click the three dots next to “Receive/Send” in the top-right corner)
  2. Copy the message that needs to be signed from the claim portal
  3. Select the address you’ll use for signing (as instructed in the claim portal)
  4. Sign the message with your Trezor
  5. Copy the signature and public key into the claim portal
  6. Submit your claim
  7. You should see a success confirmation.

For a full walkthrough with screenshots, check out our article:

If you have any questions about claiming $NIGHT tokens using this method feel free to create a ticket via our Chatbot Hal or post in this forum thread forum.

Please keep general discussion about the Midnight airdrop, including discussion of any alternative, unofficially supported claim methods in the Midnight airdrop general discussion thread.

2 Likes
2

thanks @NickW , really appreciate you guys getting this over the line. Never doubted you… :wink:

That said, I am falling at what i think may be the final hurdle, i have followed your process above, all goes well until i get to signing in Trezor Suite (i’m using a Trezor T)

I add the message

In the address field I am copying the address that comes after ‘When signing please use the keypair of the following address:’ in the claim portal - IS THIS CORRECT?

i then press sign and get the following error message

Message signing error: ui-device_firmware_old

Any guidance much appreciated

3

@Klaus Please navigate to Settings > Device and check if your device is running the latest firmware, version 2.9.1. You need to follow the above directions, including joining our early access program at this time to update it.

4

yep, that’s worked - thanks again

5

Thank You NickW and to all the Trezor Team for making it possible.

Is there any way for xrp, avax and Sol?

Cheers

6

Or firstly insert a signing Option for the same way for SOL and AVAX, because for now XRP is only supported from the XAMAN Mobile Wallet.

Is there any Chance to get this also fixed?

King Regards
George

7

I ment SOL only. AVAX is on Ledger.

8

Thank you for the update! I am still having issues claiming on the BTC network. My BTC is on
Legacy SegWitt accounts. The Midnight claiming portal states the wallets are ineligible. Both of the accounts in question have been used for years. Also have one of my ETH accounts with the same issue. On a side note all other eligible wallets have been completed claimed. Just having issues with these 2 coins. Thank you in advance for your help!

9

Thanks Nick for the update. I’ve successfully followed your steps to sign the tx.

Appreciate your efforts here and that of your dev team too :grinning:

1 Like
10

@Stacker You can access Legacy SegWit accounts when selecting your Bitcoin account in the Trezor Connect popup

Access to an Ethereum account should now also be available in the Midnight claim portal.

Please keep in mind that only accounts holding $100 or more of BTC or ETH at the time of the snapshot are eligible

image
image1126×560 18.3 KB

11

I have upgraded Trezor Suite to 25.9.1 OK. I can connect to Trezor Model T OK. When I try to do the firmware upgrade from Universal 2.8.10 to Universal 2.9.1, after confirming that I have a wallet backup, then pressing “install firmware”, I get the message

“Installation failed: Error: Unexpected header”.

That’s as far as I can go. Anything I can do?

12

Hi. I am trying to find the Early Access Program to no avail.

Trezor Suite Web Application

Settings > Application Tab > Experimental → Toggle on “Experimental features”
then in the Experimental area the following 2 options appear
*Migrate Dropbox passwords
*NFTs

…but no mention of early access program.

Is the early access program only for Trezor Suite downloaded application?.. but not the web interface?

13

okay, I’ve answered my own question.

I downloaded the desktop application and found the Early Access Program there.
It’s not present on the web application FYI. Might want to update the guide to reflect that.

Cheers

15

Thanks for the feedback.

16

Nick
I know the specs of the air drop. My accounts should be eligible for the claim. 2 of my BTC accounts keep popping up ineligible. Same thing with one of my ETH accounts. I followed your instructions and still keep getting the same results. Please advise!
Thank you for your help. I have been in the space since 2017. I am not a developer or a coder. I do know enough to navigate thru most things. Just trying to maximize my investments as possible. I know this is frustrating to you as well, but I am not a noob. I should be able to get this figured out with a little help from you.

Thank you in advance for you assistance!

17

@Stacker Could you please be more descriptive, what is the error message you see? Can you provide a screenshot.

18

@Schorse66 Regarding your question about XRP, unfortunately, given the lack of standardization for signing off-chain messages on the XRP Ledger, we cannot implement a message signing system with Trezor. It appears that the Midnight team selected a non-standardized signing method supported by XAMAN wallet and its associated Xumm ecosystem.

For that reason, we don’t have a path to add support for XRP message signing in Trezor Suite. It isn’t a matter of development capacity so much as the absence of a broadly adopted, secure standard we could implement consistently across our devices.

While it is theoretically possible to import a BIP-39 wallet backup (formerly recovery seed) into the XAMAN wallet, the risks are serious enough that it is not something we recommend. Doing so would expose your recovery information to a hot environment, which means the wallet could no longer be considered secure, and you would need to move your funds already on the Trezor elsewhere first. Therefore, it has to be said that the claim process for XRP through XAMAN adds significant extra steps and complexity (needing to move funds to a new backup, making multiple claim signatures and transactions at different times with the old wallet, etc.). For many users, the practical benefit of doing so may be limited compared to the effort and risks involved.

I know this isn’t the answer you were hoping for, but I want to be transparent so you can plan accordingly. Trezor’s focus has to remain on implementing message signing only where secure, standardized approaches exist, so that support is consistent and trustworthy.

1 Like
19

@raine thanks for reporting. This is a rather unusual error, and I’d appreciate if you could please clarify the following

  • Was your Trezor setup recently (within the past 3 months)?
  • Has this error happened repeatedly?
  • Do you have a stable internet or WiFi connection?
  • Just to confirm, the error reads exactly "Installation failed: Error: Unexpected header"? Usually such an error is not associated with firmware installation.

If you are still getting the error message, it might be a good idea to create a support ticket via our Chatbot Hal. My colleagues in support agent could assist you with getting your Trezor Suite logs, and do a deeper investigation.

20

It will not let me upload a screen shot or a jpeg

Spent over 30 minutes
I give up

21

Do you have a email?