Research
Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
S16 · E57 · 54:27

S16 E57: Trezor Safe 7 Setup with Matej Zak & Tomáš Sušánka

5 Nov 2025 · by Vlad Costea · 10 min read
Published at block 922,312
Cover art for S16 E57, Trezor Safe 7 Setup with Matej Zak & Tomáš Sušánka
MP3 (75 MB)

The audio keeps playing while you browse the site.

Read the transcript8,585 words, every line links to the minute it was said

Ask this episode

Embed this episode

Paste this on your site or blog. It is a small player that streams from here: no trackers, no cookies, no ads.

Preview the player

"It's not a gimmick," Tomáš Sušánka told me, and the remark was about a hardware wallet that has the word quantum printed on its box. Tomáš is the CTO of Trezor, Matej Zak is the CEO, and the two of them sat down with me in Prague to open the Trezor Safe 7 on camera for a 54-minute live stream, which included my first pairing attempt, a few mistakes of mine, and a story about a lawsuit threat that I did not see coming.

I should start with the mood in the room. Before the unboxing I read out the memes from the SeedSigner and Blockstream Jade crowds, who had decided that every influencer at the Prague launch had been paid. I put it to Matej directly. "No, as far as I know, we didn't," Matej said, and the arrangement described was travel and hotel. I added my own version, that "You guys basically flew everyone to Prague and put us in the same hotel next to the venue," and nobody argued with that part.

Five Layers Between You and the Wallet

The Safe 7 comes in an outer foil with Trezor printed all over it, a tamper seal, a second seal, a hologram sticker and a sticker over the USB-C port. Matej pointed at the foil as I ripped it off: "The foil that you are now ripping off actually has Trezor written all over it," and went on to describe the device itself as "our flagship product. It is the best hardware wallet that we have ever built." I had been counting layers out loud and said four. It took until later in the stream, when I went back over the box, to admit "But there are actually five."

I have opinions about seals, and I shared them. I told Matej that with a hair dryer you can lift the glue without leaving any traces, "using a blow dryer to basically remove the glue without actually removing any traces." Tomáš did not claim otherwise. As Tomáš framed it, the packaging is one of several defenses, and defeating it is "one of those 10 steps that the attacker needs to do." What decides whether a device is genuine is cryptography inside the chips, and the stickers sit on top of that.

Tomáš also listed the "three ways how to prove that your Trezor is genuine." The one called the main check is a cryptographic one: "That's like the main genuinity check because there's cryptography involved." A further part of this authenticity machinery, Tomáš added, "is not yet being used in Suite."

The device feels heavy. It is built in the Czech Republic, which Tomáš said was one of the conditions the team set, that they "be able to manufacture at some place that is close to us." The touchscreen shows millions of colors, and in the hand it has the weight of a premium gadget.

A Lucky Charm in the Keynote Pocket

Matej told me the orange Bitcoin-only Safe 7 never left a pocket during the keynote. "I kept it in my pocket for the keynote presentation because I was so scared," was how the anecdote went. I asked about the US, since the launch was in Prague, and the reply was short: "The US is our biggest market."

What "Quantum Ready" Does and Does Not Mean

The word that got the most attention in my notes is "quantum ready," so I asked Tomáš to define it. The answer started with a limit: "we cannot make a quantum safe or quantum proof hardware wallet because Bitcoin or whatever else is not actually ready for the quantum security." Then came the same point again from the chain's side: "we do not have post quantum signatures in Bitcoin."

What the label covers is narrower. The bootloader updates and the proofs of device authenticity use post-quantum signatures, so Trezor can protect its own firmware chain with schemes that Bitcoin transactions cannot yet use. As for timing, Tomáš described a threat that is far off: "There is not a cryptographically relevant quantum computer, you know, a quantum computer strong enough that would be just around the corner. There's no such thing." The estimate was that "it could be in 10 or 20 years," and the argument was that building a quantum-proof wallet before the chain supports it makes little sense: "And then it doesn't really make sense to make a quantum secure hardware wallet because the attackers would attack the blockchain itself instead of the hardware wallet, right?"

Hunter Beast's episode was S16 E35 on Bitcoin's quantum resistance and BIP 360.

Bootloader Only, Firmware Later

The Safe 7 leaves the factory with next to nothing on it. Tomáš explained: "So we only equip the device with the so-called bootloader," and the firmware gets installed during onboarding. In practice that meant my first act with a brand new Trezor was a firmware install, with the authenticity checks happening along the way.

Numbers, Not Fingerprints

For my own setup I downloaded the app on my iPhone, turned analytics off, skipped biometrics and paired the device over Bluetooth. Bluetooth is there for iPhone connectivity, and it lets Trezor stay out of Apple's MFi program. It can be switched off. I asked Tomáš whether the radio makes the device weaker, and the answer was that Bluetooth "actually cannot decrease the security. It can only increase it, right?" The reasoning given was that the pairing sits on top of Trezor's own encryption: "There's actually another pairing inside of the Bluetooth channel, which is our own Trezor Host Protocol, which is basically another layer of encryption inside the channel." Tomáš called that "basically another layer of protection inside Bluetooth," and said that for most users "I honestly believe that it would probably be enough."

While the Suite app was downloading, I read out the sponsors: SideShift.ai, which is integrated in Trezor Suite, LayerTwo Labs, NoOnes.com and news.bitcoin.com. That is SideShift.ai, LayerTwo Labs and NoOnes, for anyone who wants the links.

On the PIN screen, I did not skip anything. I told Tomáš I like the scrambled layout: "I prefer numbers as opposed to my face or my fingerprint," and later I pointed out that "you don't actually leave any fingerprint patterns on your screen." The digits move around, so smudges tell an observer nothing.

I also blew through a system dialog without reading it. Tomáš had warned me that "you cannot really change the system dialogue," meaning Apple controls that screen, and my excuse on air was that "I did not read because I'm in the middle of a live stream and I have a lot of stuff going on." Nothing bad came of it, and the lesson is that your first pairing with a new device should not happen on a live broadcast.

Two Secure Elements and One Open One

Inside, the Safe 7 has an STM32U5 microcontroller, an Infineon OPTIGA Trust M, and a TROPIC01 secure element. Tomáš's argument for two secure elements is that they add up, with TROPIC01 described as the auditable one.

TROPIC01 comes from Tropic Square, which Matej called a sibling company, founded in 2020. The name, Matej said, is "an abbreviation for TRuly OPen IC, integrated circuit." The reason it exists is a story Matej told, and it is the part of the evening I had not heard before. Trezor found a flaw in a competitor's secure element: "We actually found a vulnerability how to extract the secret from the secure element," and then ran into the vendor's paperwork. In Matej's version, the manufacturer's reply was: "Well, the manufacturer said, no, you are not going to do that. You sign the NDA and we will sue the shit out of you if you do." Matej added, "that's the point of NDA that you are not allowed to talk to anybody."

I tried to get the chip name out of them. I asked whether the NDA-bound part was Microchip's ATECC608. Tomáš's answer: "We don't comment on that."

What came out of that fight is that Tropic Square, in Matej's words, "succeeded in delivering the first ever auditable secure element to the market." I used the words "auditable and transparent" in reply, and Tomáš sketched how open it is: "In short, you can say that the digital stuff is open source, and you can find it on GitHub, just you go to GitHub, Tropic Square, that there is they have a bunch of repositories". The analog parts remain partially closed, and Tomáš said "they are still, I don't know, 10% or 20% left to do." Any manufacturer, Tomáš also said, can get hold of the chips: "you can really just contact Tropic Square, you can just get a few chips from them."

If other hardware wallet makers adopt it, "they can talk about anything, and we can improve the hardware industry altogether." I covered the company in the Slush episode on Trezor and Tropic Square, and the chip's own site is Tropic Square.

No Interest in Killing Each Other

Having just heard about the NDA lawsuit threat, I wondered how aggressive Trezor gets with competitors. Matej's answer was the reverse of what the memes at the top of the stream suggest: "I don't really believe in killing each other on a niche market." Matej allowed some friction, "A little poking is probably fine," but the goal described is "We want to bring a better product, better features, better experiences, solid hardware that feels like a super high-end electronics." The way to win, in Matej's words: "You basically deliver a better product."

Twenty Words and Skipping the Backup

The default backup is now 20 words in SLIP-39. Matej put it plainly: "the new default is 20 words, which runs on SLIP-39." Tomáš clarified that nothing is rewritten in the wallet logic: "It's just the underlying BIP-39 is replaced with SLIP-39." Multi-share backups are supported too, from 2 to 16 shares.

The part Matej admitted is still unresolved inside the company: "We, by the way, still have ongoing conversation in the company whether to allow you to skip the backup or not." On how to measure good onboarding, Matej said time is a poor yardstick, "just the time itself is not a great metric." What Matej looks at is comprehension: "I would say the main metric is whether you as a user understand what happened and what the device is for, what's the purpose, right?"

Questions From the Chat

Someone in Southeast Asia asked where to buy safely. Matej's advice: "Please in these cases, always check that they are trusted," meaning the official site or vetted resellers. Coin control on mobile is planned for a future update, and Tomáš asked people to "just give us a few months." Shipping is the one thing Matej hedged on: "We are not shipping yet, but we are actually going to start soon, probably."

Shielded Zcash was a question I wanted to hear the answer to, and then my OBS volume fader glitched and the audio dropped, so I asked Tomáš to repeat the answer. Tomáš said "I don't have any ETA on that, because honestly we have a backlog of coins that we want to add." On the question of why it was not there already, the practical reason from earlier days was: "The issue there back in the time was space, that we simply didn't have enough space in the firmware."

Matej's earlier episode was S14 E3 on Trezor's new hardware.

Listen to Matej Zak & Tomáš Sušánka on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:01:13– Introduction to the podcast episode and guests (Matej Zak, CEO, and Tomáš Sušánka, CTO of Trezor).
  2. 00:01:34– Discussion of the Trezor Safe 7 product launch event in Prague and the host's excitement about the Tropic Square chip.
  3. 00:01:55– Mention of the live unboxing and potential for things to go wrong.
  4. 00:02:17– Addressing rumors about paying influencers; clarification that no payments were made, only travel costs covered.
  5. 00:03:11– Start of unboxing the Trezor Safe 7, focusing on packaging security and tamper-proof elements.
  6. 00:09:00– Deeper dive into quantum readiness, industry trends (e.g., Cloudflare, Apple), and why it's not a gimmick.
  7. 00:12:51– Continuation of unboxing: Tamper-proof seals, holographic stickers, and physical security layers.
  8. 00:14:18– Confirmation that devices ship without firmware; installation happens via Trezor Suite for added security.
  9. 00:15:26– Setup process on iPhone: Downloading the app, Bluetooth pairing, and why iPhone compatibility was prioritized.
  10. 00:16:10– Market insights: US as the biggest market, challenges with Apple (MFi program), and opting for Bluetooth over cables.
  11. 00:18:30– Ads segment (Sideshift.ai, Layer 2 Labs, NoOnes.com, news.bitcoin.com).
  12. 00:20:13– Resuming app setup: Privacy options, biometrics, Bluetooth permissions, and pairing code.
  13. 00:21:42– Counting physical security layers (five in total) and their purpose.
  14. 00:23:07– Authenticity checks in the app: Confirming purchase source, seals, and packaging integrity.
  15. 00:24:09– Firmware installation process and confirmation that devices ship with only bootloader.
  16. 00:25:05– Discussion of dual secure elements (Tropic Square T01 and Infineon Optiga Trust M) for enhanced security.
  17. 00:26:01– Bluetooth security: End-to-end encryption using Noise protocol.
  18. 00:27:04– Haptic feedback and one-time code for pairing confirmation.
  19. 00:28:00– Device authenticity verification via secure elements.
  20. 00:29:39– More on quantum readiness: Post-quantum certificates for future implementation.
  21. 00:30:23– Tutorial walkthrough: Power button, menu options, and Tropic Square chip explanation.
  22. 00:30:59– Background on Tropic Square: Origin story, name meaning (Truly Open IC), and founding to create auditable secure elements.
  23. 00:32:06– Experience with proprietary secure elements: Discovering vulnerabilities under NDA and deciding to develop an open alternative.
  24. 00:37:18– Advantages of Tropic Square for competitors: Better security, transparency, and ability to discuss vulnerabilities openly.
  25. 00:38:46– Competition philosophy: Focus on features, software, third-party integrations, and innovation rather than aggressive tactics.
  26. 00:40:29– Bitcoin-only version mention and pre-order availability.
  27. 00:41:26– Completion of setup tutorial; default 20-word SLIP-39 backup with options for multi-share.
  28. 00:43:41– Metrics for setup experience: Emphasis on user understanding over speed.
  29. 00:45:32– Compatibility with BIP-44 for multi-asset support; differences limited to SLIP-39 replacing BIP-39.
  30. 00:47:09– Status as production-quality device; shipping soon, with room for early feedback.
  31. 00:49:19– Audience questions: Ordering in Southeast Asia (via trezor.io or vetted resellers).
  32. 00:50:35– Audience questions: Coin control in mobile app (planned for parity with desktop in a few months).
  33. 00:51:29– Audience questions: Shielded Zcash support (on backlog, no ETA; space issues resolved but requires further cryptography work).
  34. 00:53:18– Pricing ($250) and pre-order info.
  35. 00:53:43– Closing remarks: Pride in the product, future features, and thanks.

Verify this episode

This is the SHA-256 fingerprint of the MP3 as published here, timestamped in the Bitcoin blockchain with OpenTimestamps. If one byte of the file changes, the fingerprint changes.

SHA-256
a96484928f7411d7d8b4ac22c0ae5d49f6fba7e4f7a388408f11a45d131e6ebe
Proof
2025-11-10_s16_e57_trezor_safe_7_unboxing_setup_with_matej_zak_tom_su_nka.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 10 Nov 2025, but this proof was made on 3 Nov 2026 and anchored in block 974,312, so it proves this exact file existed by 3 Nov 2026, not on the release date.
How to check it yourself
  1. Download the MP3 and the proof into the same folder.
  2. Run sha256sum 2025-11-10_s16_e57_trezor_safe_7_unboxing_setup_with_matej_zak_tom_su_nka.mp3 (on a Mac: shasum -a 256 2025-11-10_s16_e57_trezor_safe_7_unboxing_setup_with_matej_zak_tom_su_nka.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-11-10_s16_e57_trezor_safe_7_unboxing_setup_with_matej_zak_tom_su_nka.mp3.ots. It hashes the MP3 again and checks the proof against your own Bitcoin node, then prints the block and the date the file existed by. Without a node, ots info 2025-11-10_s16_e57_trezor_safe_7_unboxing_setup_with_matej_zak_tom_su_nka.mp3.ots shows the block height to look up in any block explorer.

Share: X · Email · Link

Related

Comments

Comments run on my own server. No trackers, no tracking cookies.

0:000:00